Prompt Buddy logoPrompt Buddy

Prompt Buddy · Prompt Buddy Static Skills

Designer-Quality UI

A design orchestration skill for producing app UI that feels intentionally crafted, coherent, accessible, and production-ready.

Import to Prompt Buddy

Derived skill

Files assembled from official documentation

Viewing SKILL.md

Designer-Quality UI

When To Use

Use this skill for screen-level or flow-level UI work: designing a new interface, restyling an existing surface, building a design system direction, critiquing a mockup, or polishing an implemented UI until it feels authored and production-ready.

Do not use it for backend-only work, pure copy editing, or decorative image generation detached from product UI.

Reference Files

FileUse for
docs/designer-quality-workflow.mdOrchestrator flow, subskill order, design thesis, and anti-artifact rules.
docs/ui-system-rules.mdTypography, color, spacing, iconography, imagery, microcopy, motion, and accessibility constraints.
templates/design-brief.mdNormalized brief format to fill before visual decisions.
schemas/design-system-output.jsonMachine-readable output contract for tokens, layout plans, audits, and polish notes.
tests/certification-checklist.mdAutomated and human review gates for designer-quality certification.

Operating Rules

  1. Normalize the brief before making visual decisions.
  2. Emit system decisions first: type, color roles, spacing/grid, icon policy, imagery policy, copy rules, motion rules, and accessibility constraints.
  3. Use one coherent visual language per surface. Do not mix icon families, arbitrary radii, unrelated shadows, or one-off spacing.
  4. Favor live text, semantic roles, tokenized spacing, and product-relevant visuals over decorative effects.
  5. Treat accessibility as a shaping constraint, not as final cleanup.
  6. Run polish only after hierarchy, layout, color roles, states, and accessibility are coherent.
  7. Fail the design if it reads as a collage of plausible UI tropes rather than a system with a point of view.

Expected Output

Return a compact design package:

  • normalized brief;
  • design tokens and role decisions;
  • layout and component plan;
  • content and asset policy;
  • accessibility audit;
  • polish pass;
  • open risks and next implementation steps.