Design Doc

Convert visual directions and screenshots into a stable design system document for AI coding agents to follow.

Install
cmdop skills install agensi-design-doc

Design Doc is a skill published by agensi that takes visual references, screenshots, and high-level brand goals and converts them into a rigorous design.md specification file. The output is intended to give AI coding agents a stable, enforceable design system document rather than letting them produce inconsistent or generic UI styles during frontend code generation.

The generated document covers four areas documented in the skill. Visual Principles encode enforceable rules such as Progressive Disclosure and Visual Information Density. System Definition captures hierarchical color roles, typography scales, and spacing rhythms. Component Behaviors specify rules for surface treatments, interactive state feedback (hover, active, disabled states), and motion logic. Anti-Patterns provide explicit instructions on what the agent must not do, preventing the introduction of generic filler styling.

The skill is positioned as a prerequisite step before moving into UX flow definition or multi-phase coding tasks. Instead of relying on shallow prompt instructions like “make it look like a SaaS product,” the skill extracts the underlying logic of a design language — including interface metaphor and grid behavior — so that every page or component generated afterward feels coherent with the rest of the product. It produces a single design.md artifact that downstream agents or coding tasks can reference throughout a project.

Use cases

  • Convert a set of brand screenshots into a reusable design.md specification before starting a frontend build
  • Establish consistent color roles, typography scales, and spacing rules for an AI coding agent to follow across all generated components
  • Define component-level state rules (hover, active, disabled) so generated UI behaves consistently
  • Document anti-patterns explicitly to prevent an AI agent from introducing off-brand styling
  • Create a design system document as a prerequisite step before generating UX flows or multi-phase frontend tasks

When to use it

  • Starting a new frontend project where an AI coding agent will generate UI components
  • Needing a single source-of-truth design specification that multiple coding tasks can reference
  • Working from visual references or screenshots rather than an existing coded design system
  • Wanting to prevent style drift across AI-generated pages or components

When not to use it

  • The project already has a fully coded and documented design system that agents can read directly
  • No visual references or brand goals are available as input
  • The task requires generating actual UI code rather than a design specification document
  • Backend, API, or data pipeline work with no frontend component