agentleFS
Sign inStart free
tranhieutttranhieutt/software_development_department/.claude/skills/ui-spec/SKILL.md

ui-spec

Skill71 starsChanged 7 months agoMITView on GitHub

Use this skill when moving from a PRD (Requirements) to a technical UI design. This skill bridges the gap between wireframes and code. Save UI spec to design/specs/ui-[feature-name].md: \\\`markdown # UI Spec: [Feature Name]

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when moving from a PRD (Requirements) to a technical UI design.

    line 14
  2. Very specific:

    Prototype Ingestion: If prototype code exists (e.g., from prototyper), read it to understand components and states.

    line 20
  3. Distinctive:

    Interactions: Use EARS format (Condition-Trigger-Response) for all interactive elements.

    line 29
  4. Very specific:

    Use the UI Spec as the checklist for the frontend-developer.

    line 33
  5. Distinctive:

    Every component MUST define behavior for these 5 states:

    line 36
  6. Distinctive:

    Every interaction must have a keyboard equivalent.

    line 44
  7. Distinctive:

    Every interactive element must have an ARIA role and label.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: /ui-spec

Use this skill when moving from a PRD (Requirements) to a technical UI design. This skill bridges the gap between wireframes and code.

The UI Spec Lifecycle

1. Analysis Phase

  • Map ACs: Map every Acceptance Criterion from the PRD to a UI screen or interaction.
  • Prototype Ingestion: If prototype code exists (e.g., from prototyper), read it to understand components and states.

2. Decomposition Phase

  • Define the Component Tree.
  • Identify which components can be reused from the existing codebase vs. which need to be new.

3. Specification Phase

Fill out the ui-spec-template including:

  • State Matrix: Explicitly define what the user sees during Loading, Error, and Empty states.
  • Interactions: Use EARS format (Condition-Trigger-Response) for all interactive elements.

4. Integration Phase

  • Link the UI Spec in the feature's [Design Doc].
  • Use the UI Spec as the checklist for the frontend-developer.

The State x Display Matrix

Every component MUST define behavior for these 5 states:

  1. Default: The "Happy Path".
  2. Loading: Bone skeletal screens or spinners.
  3. Empty: Context-aware messages when no data exists.
  4. Error: User-friendly error messages with recovery actions (Retry/Reset).
  5. Partial: Behavior when some data is missing or loading.

Accessibility (A11y) Rules

  • Every interaction must have a keyboard equivalent.
  • Every interactive element must have an ARIA role and label.
  • Color contrast ratios must meet WCAG 2.1 Level AA (4.5:1 for normal text).

Output

Save UI spec to design/specs/ui-[feature-name].md:

```markdown

UI Spec: [Feature Name]

Component Tree

[Hierarchical list of components]

State Matrix

ComponentDefaultLoadingEmptyErrorPartial

Interactions

[Component] -> [Trigger] -> [Response]

Responsive Behavior

[Breakpoint-specific layout changes]

Accessibility

[Keyboard nav, ARIA labels, contrast requirements]

Open Questions

[Items needing design decision] ```

Related Skills

  • design-review — review implemented UI against spec
  • frontend-design — aesthetic direction and design system
  • design-system — reusable component library
  • review-spec — general spec review workflow

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free