← Back to list

ui-finesse-workflow
by jshmllr
Opinionated UI design for AI and implementation playbook focused on interaction finesse, typography, anti-AI slop, and component standards for high-clarity product interfaces.
⭐ 49🍴 4📅 Jan 22, 2026
SKILL.md
name: ui-finesse-workflow description: Master workflow for building exceptional UIs. Use when starting UI work, building components, or when the user asks about the development process for interfaces.
UI Finesse Workflow
You are following the UI Finesse Playbook workflow for building exceptional user interfaces.
Phase 0: Mode Detection
Before starting, determine which mode applies:
Enhancement Mode (Existing Component Library)
Detected when ANY of these are true:
components/ui/button.tsxexists (shadcn/ui pattern)@radix-ui/*packages in dependencies@headlessui/*packages in dependencies
Standalone Mode (Greenfield)
Detected when NONE of the above are present.
Phase 1: Context Gathering
ALWAYS start here before building UI.
If no design context exists, gather:
- Target audience and use cases
- Brand personality (3 words)
- Aesthetic direction and references
- Anti-references (what to avoid)
Phase 2: Foundation
Standalone Mode
- Use design tokens from
/tokens/if present - Follow composition patterns in
/patterns/composition.md - Follow theme architecture in
/patterns/theming.md
Enhancement Mode
- Use the library's existing token system
- Follow extension patterns in
/patterns/extension.md - Reference
/patterns/elevation.mdfor transcending defaults
Phase 3: Building
For every component:
- Consult the
frontend-designskill for aesthetic direction - Follow
interface-guidelinesskill for interaction patterns - Reference
/docs/for specific techniques - Use composition over duplication
Phase 4: Refinement
After building:
- Run
design-polishskill for systematic final pass - Run
design-reviewskill for accessibility verification
Phase 5: Quality Gate
Before shipping, verify:
- All checklist items from
ui-checklist.md - No critical accessibility issues
- Passes the "AI slop test" (doesn't look generic)
Quick Reference
| Need | Resource |
|---|---|
| Aesthetic direction | frontend-design skill |
| Interaction patterns | interface-guidelines skill |
| Final polish | design-polish skill |
| Accessibility review | design-review skill |
| Visual techniques | /docs/ best practices |
| Extension patterns | /patterns/extension.md |
| DRY principles | /patterns/composition.md |
Anti-Patterns to Avoid
Building
- Starting without design context
- Copying styles instead of wrapping components
- Hardcoding colors/spacing instead of using tokens
Aesthetics
- Generic "AI slop" (purple gradients, glowing accents, Inter font)
- Glassmorphism everywhere
- Same-sized card grids
- Gradient text on metrics
Score
Total Score
70/100
Based on repository quality metrics
✓SKILL.md
SKILL.mdファイルが含まれている
+20
✓LICENSE
ライセンスが設定されている
+10
✓説明文
100文字以上の説明がある
+10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
Reviews
💬
Reviews coming soon