fecode-cli 1.1.3 → 1.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (98) hide show
  1. package/README.md +92 -8
  2. package/dist/index.js +23293 -1
  3. package/dist/{node.browser-BsGbhAIw.js → node.browser-2EgZAKSy.js} +1 -1
  4. package/dist/{node.browser-B5CfqNxN.js → node.browser-B5Gur0wd.js} +1 -1
  5. package/dist/{node.browser-BWLpZywP.js → node.browser-BSlAsiSV.js} +1 -1
  6. package/dist/{node.browser-7pW7d9_e.js → node.browser-CdVAMgSg.js} +1 -1
  7. package/dist/{src-CxriUNOE.js → src-CSWdjU4j.js} +4836 -4522
  8. package/dist/{src-DBoGZaxi.js → src-DY3OmBmT.js} +6670 -4557
  9. package/dist/{src-B_Z8CdqT.js → src-DcYf8vsK.js} +4850 -4526
  10. package/dist/{src-Bhec3XmL.js → src-DkWmcv2Q.js} +6677 -4604
  11. package/package.json +5 -2
  12. package/skills/accessibility/SKILL.md +98 -98
  13. package/skills/css/SKILL.md +90 -90
  14. package/skills/frontend-debugging/SKILL.md +201 -201
  15. package/skills/frontend-design/SKILL.md +358 -358
  16. package/skills/frontend-performance/SKILL.md +89 -89
  17. package/skills/frontend-testing/SKILL.md +87 -87
  18. package/skills/nextjs/SKILL.md +75 -75
  19. package/skills/react/SKILL.md +213 -213
  20. package/skills/responsive-design/SKILL.md +190 -190
  21. package/skills/svelte/SKILL.md +86 -86
  22. package/skills/tailwind/SKILL.md +74 -74
  23. package/skills/ui-review/SKILL.md +245 -245
  24. package/skills/vue/SKILL.md +72 -72
  25. package/dist/App.d.ts +0 -33
  26. package/dist/App.js +0 -2224
  27. package/dist/approvalResolver.d.ts +0 -12
  28. package/dist/approvalResolver.js +0 -112
  29. package/dist/commands.d.ts +0 -11
  30. package/dist/commands.js +0 -33
  31. package/dist/error-qAR8Lv-R.js +0 -57
  32. package/dist/index.d.ts +0 -3
  33. package/dist/node.browser-C9Wg-Fje.js +0 -46
  34. package/dist/node.browser-CADgAblr.js +0 -46
  35. package/dist/node.browser-Cse19Rko.js +0 -47
  36. package/dist/node.browser-Cx8sZi1Z.js +0 -46
  37. package/dist/node.browser-DtPNhPGQ.js +0 -46
  38. package/dist/node.browser-DvjMZMaq.js +0 -46
  39. package/dist/node.browser-EewJmuUw.js +0 -46
  40. package/dist/node.browser-J7voHtuR.js +0 -10
  41. package/dist/src-4fKRO0jn.js +0 -31655
  42. package/dist/src-8kA-5Kbs.js +0 -31591
  43. package/dist/src-C8Oe06wn.js +0 -31580
  44. package/dist/src-D78uLcuc.js +0 -31573
  45. package/dist/src-EyWDnffN.js +0 -31636
  46. package/dist/src-dhvwrHAJ.js +0 -31590
  47. package/dist/ui/AppShell.d.ts +0 -14
  48. package/dist/ui/AppShell.js +0 -25
  49. package/dist/ui/ApprovalPrompt.d.ts +0 -31
  50. package/dist/ui/ApprovalPrompt.js +0 -55
  51. package/dist/ui/BlockedView.d.ts +0 -13
  52. package/dist/ui/BlockedView.js +0 -7
  53. package/dist/ui/CommandPalette.d.ts +0 -8
  54. package/dist/ui/CommandPalette.js +0 -18
  55. package/dist/ui/CurrentStepView.d.ts +0 -16
  56. package/dist/ui/CurrentStepView.js +0 -28
  57. package/dist/ui/DiagnosticsView.d.ts +0 -45
  58. package/dist/ui/DiagnosticsView.js +0 -23
  59. package/dist/ui/ExecutionTimeline.d.ts +0 -15
  60. package/dist/ui/ExecutionTimeline.js +0 -51
  61. package/dist/ui/ExecutionView.d.ts +0 -42
  62. package/dist/ui/ExecutionView.js +0 -20
  63. package/dist/ui/Header.d.ts +0 -15
  64. package/dist/ui/Header.js +0 -47
  65. package/dist/ui/HelpView.d.ts +0 -3
  66. package/dist/ui/HelpView.js +0 -35
  67. package/dist/ui/MessageBubble.d.ts +0 -9
  68. package/dist/ui/MessageBubble.js +0 -58
  69. package/dist/ui/PlanStep.d.ts +0 -16
  70. package/dist/ui/PlanStep.js +0 -71
  71. package/dist/ui/PlanView.d.ts +0 -26
  72. package/dist/ui/PlanView.js +0 -24
  73. package/dist/ui/ProgressBar.d.ts +0 -10
  74. package/dist/ui/ProgressBar.js +0 -14
  75. package/dist/ui/RecoveryView.d.ts +0 -20
  76. package/dist/ui/RecoveryView.js +0 -19
  77. package/dist/ui/ReplanView.d.ts +0 -16
  78. package/dist/ui/ReplanView.js +0 -21
  79. package/dist/ui/ResumeView.d.ts +0 -15
  80. package/dist/ui/ResumeView.js +0 -25
  81. package/dist/ui/RiskNotice.d.ts +0 -10
  82. package/dist/ui/RiskNotice.js +0 -21
  83. package/dist/ui/RunHistoryView.d.ts +0 -15
  84. package/dist/ui/RunHistoryView.js +0 -39
  85. package/dist/ui/StatusBar.d.ts +0 -16
  86. package/dist/ui/StatusBar.js +0 -104
  87. package/dist/ui/TaskInput.d.ts +0 -15
  88. package/dist/ui/TaskInput.js +0 -8
  89. package/dist/ui/ThinkingBlock.d.ts +0 -8
  90. package/dist/ui/ThinkingBlock.js +0 -13
  91. package/dist/ui/ThinkingIndicator.d.ts +0 -7
  92. package/dist/ui/ThinkingIndicator.js +0 -20
  93. package/dist/ui/TurnView.d.ts +0 -13
  94. package/dist/ui/TurnView.js +0 -11
  95. package/dist/ui/WorkspaceStatus.d.ts +0 -20
  96. package/dist/ui/WorkspaceStatus.js +0 -23
  97. package/dist/ui/index.d.ts +0 -26
  98. package/dist/ui/index.js +0 -26
@@ -1,74 +1,74 @@
1
- ---
2
- name: tailwind
3
- description: Tailwind CSS utility composition, responsive behavior, design tokens, and state variants.
4
- category: styling
5
- version: 2.1.0
6
- ---
7
-
8
- ## When to use
9
-
10
- - styling components with Tailwind CSS
11
- - building responsive layouts with utility classes
12
-
13
- ## Instructions
14
-
15
- ### Project Detection & Existing Rules
16
- - **Inspect package.json & Configuration**: Check Tailwind version, `tailwind.config.js`, CSS entrypoints, and existing utility conventions.
17
- - **Design Tokens**: Identify existing design tokens (custom colors, spacing, typography, radius, shadows). **Prefer existing project tokens.**
18
- - **Do not force Tailwind** onto projects that do not use Tailwind.
19
-
20
- ### Design Tokens
21
- - Do not introduce arbitrary values (`[#ff0000]`) when existing project tokens or standard scales can be used.
22
-
23
- ### Composition
24
- - Group utilities logically (e.g., layout first, then spacing, typography, visual).
25
- - Build reusable component patterns cleanly.
26
- - Keep class strings understandable.
27
- - Avoid duplicated utility combinations by extracting heavily repeated patterns into component abstractions (use React/Vue/Svelte components, avoid `@apply` unless it is a strong project convention).
28
-
29
- ### Responsive
30
- - Use responsive variants (`sm:`, `md:`, `lg:`) for fluid viewport adaptations.
31
- - Understand mobile-first behavior (unprefixed is mobile).
32
- - **Do not simply add every breakpoint.** Design for fluidity.
33
- - Follow `responsive-design` guidance for viewport behavior.
34
-
35
- ### State
36
- - Use interactive state modifiers (`hover:`, `focus:`, `focus-visible:`, `active:`, `disabled:`).
37
- - Use `group` and `peer` for complex relational state styling.
38
-
39
- ### Dark Mode
40
- - Respect the project's existing dark-mode strategy (e.g., `class` strategy vs `media`).
41
- - Do not introduce a new strategy. Use `dark:` variants appropriately.
42
-
43
- ### Arbitrary Values
44
- - Arbitrary values are justified for highly specific, one-off cases (e.g., a specific background image position or precise translation).
45
- - Prefer project tokens or standard scales when appropriate.
46
- - Do NOT make arbitrary values categorically forbidden, but use them sparingly.
47
-
48
- ### Component Boundaries
49
- - Do not create component abstractions solely because a class list is long.
50
- - Balance readability, reuse, and project conventions.
51
-
52
- ### Common Failure Modes
53
- - **Contradictory utilities**: Applying both `p-4` and `p-6` to the same element, causing specificity surprises.
54
- - **Excessive arbitrary values**: Flooding the codebase with `[14px]` instead of using `text-sm`.
55
- - **Duplicated classes**: Repeating the exact same long string of classes across multiple sibling elements instead of mapping over data or extracting a component.
56
- - **Breakpoint proliferation**: Hardcoding too many breakpoint overrides instead of trusting flexible layouts like Flexbox or Grid.
57
- - **Ignoring existing tokens**: Hardcoding hex codes instead of using the theme configuration.
58
- - **Inconsistent responsive behavior**: Forgetting to scale typography along with layout at different viewports.
59
-
60
- ## Anti-Patterns
61
-
62
- - **Arbitrary Values over Scale Tokens**
63
- - *What*: Writing `w-[64px]` instead of `w-16`.
64
- - *Why*: It breaks design consistency and bloats the generated CSS.
65
- - *Instead*: Use the standard tailwind scale.
66
- - **Heavy use of @apply**
67
- - *What*: Putting `@apply text-sm font-bold text-red-500` inside CSS files frequently.
68
- - *Why*: It defeats the purpose of utility-first CSS and creates hidden specificity issues.
69
- - *Instead*: Extract the HTML into a reusable framework component (React/Vue/Svelte).
70
-
71
- ## Workflow
72
-
73
- ### Verification
74
- - Use project linting, build, typecheck, and test scripts to verify the styling does not break UI components.
1
+ ---
2
+ name: tailwind
3
+ description: Tailwind CSS utility composition, responsive behavior, design tokens, and state variants.
4
+ category: styling
5
+ version: 2.1.0
6
+ ---
7
+
8
+ ## When to use
9
+
10
+ - styling components with Tailwind CSS
11
+ - building responsive layouts with utility classes
12
+
13
+ ## Instructions
14
+
15
+ ### Project Detection & Existing Rules
16
+ - **Inspect package.json & Configuration**: Check Tailwind version, `tailwind.config.js`, CSS entrypoints, and existing utility conventions.
17
+ - **Design Tokens**: Identify existing design tokens (custom colors, spacing, typography, radius, shadows). **Prefer existing project tokens.**
18
+ - **Do not force Tailwind** onto projects that do not use Tailwind.
19
+
20
+ ### Design Tokens
21
+ - Do not introduce arbitrary values (`[#ff0000]`) when existing project tokens or standard scales can be used.
22
+
23
+ ### Composition
24
+ - Group utilities logically (e.g., layout first, then spacing, typography, visual).
25
+ - Build reusable component patterns cleanly.
26
+ - Keep class strings understandable.
27
+ - Avoid duplicated utility combinations by extracting heavily repeated patterns into component abstractions (use React/Vue/Svelte components, avoid `@apply` unless it is a strong project convention).
28
+
29
+ ### Responsive
30
+ - Use responsive variants (`sm:`, `md:`, `lg:`) for fluid viewport adaptations.
31
+ - Understand mobile-first behavior (unprefixed is mobile).
32
+ - **Do not simply add every breakpoint.** Design for fluidity.
33
+ - Follow `responsive-design` guidance for viewport behavior.
34
+
35
+ ### State
36
+ - Use interactive state modifiers (`hover:`, `focus:`, `focus-visible:`, `active:`, `disabled:`).
37
+ - Use `group` and `peer` for complex relational state styling.
38
+
39
+ ### Dark Mode
40
+ - Respect the project's existing dark-mode strategy (e.g., `class` strategy vs `media`).
41
+ - Do not introduce a new strategy. Use `dark:` variants appropriately.
42
+
43
+ ### Arbitrary Values
44
+ - Arbitrary values are justified for highly specific, one-off cases (e.g., a specific background image position or precise translation).
45
+ - Prefer project tokens or standard scales when appropriate.
46
+ - Do NOT make arbitrary values categorically forbidden, but use them sparingly.
47
+
48
+ ### Component Boundaries
49
+ - Do not create component abstractions solely because a class list is long.
50
+ - Balance readability, reuse, and project conventions.
51
+
52
+ ### Common Failure Modes
53
+ - **Contradictory utilities**: Applying both `p-4` and `p-6` to the same element, causing specificity surprises.
54
+ - **Excessive arbitrary values**: Flooding the codebase with `[14px]` instead of using `text-sm`.
55
+ - **Duplicated classes**: Repeating the exact same long string of classes across multiple sibling elements instead of mapping over data or extracting a component.
56
+ - **Breakpoint proliferation**: Hardcoding too many breakpoint overrides instead of trusting flexible layouts like Flexbox or Grid.
57
+ - **Ignoring existing tokens**: Hardcoding hex codes instead of using the theme configuration.
58
+ - **Inconsistent responsive behavior**: Forgetting to scale typography along with layout at different viewports.
59
+
60
+ ## Anti-Patterns
61
+
62
+ - **Arbitrary Values over Scale Tokens**
63
+ - *What*: Writing `w-[64px]` instead of `w-16`.
64
+ - *Why*: It breaks design consistency and bloats the generated CSS.
65
+ - *Instead*: Use the standard tailwind scale.
66
+ - **Heavy use of @apply**
67
+ - *What*: Putting `@apply text-sm font-bold text-red-500` inside CSS files frequently.
68
+ - *Why*: It defeats the purpose of utility-first CSS and creates hidden specificity issues.
69
+ - *Instead*: Extract the HTML into a reusable framework component (React/Vue/Svelte).
70
+
71
+ ## Workflow
72
+
73
+ ### Verification
74
+ - Use project linting, build, typecheck, and test scripts to verify the styling does not break UI components.
@@ -1,245 +1,245 @@
1
- ---
2
- name: ui-review
3
- description: Structured UI critique and evaluation for existing interfaces. Apply when asked to review, evaluate, audit, or assess an interface — not to build or modify it. This skill produces prioritized findings across visual hierarchy, layout, typography, color, components, responsive behavior, interaction states, accessibility, content, and visual genericness. Use it before implementing improvements to establish what matters most.
4
- category: frontend
5
- version: 1.0.0
6
- ---
7
-
8
- # UI Review
9
-
10
- ## When to use
11
- - Reviewing an existing interface and identifying what should be improved
12
- - Auditing a page or component before a redesign or polish pass
13
- - Identifying the highest-impact issues before a sprint or release
14
- - Evaluating a newly implemented UI against its design intent
15
- - Producing a prioritized list of findings for a team discussion
16
-
17
- ## When not to use
18
- - Building new UI from scratch (use frontend-design instead)
19
- - Fixing a specific broken interaction (use frontend-debugging instead)
20
- - Implementing responsive layout improvements (use responsive-design instead)
21
-
22
- ## Instructions
23
- - Review the interface as a product, not merely as code.
24
- - Do not automatically modify files during a review — produce findings first.
25
- - Prioritize findings by user impact, not by personal aesthetic preference.
26
- - Ground every finding in a specific observation: where the issue occurs, what the effect is, why it matters.
27
- - Distinguish between problems that impair usability and those that are polish opportunities.
28
- - Do not invent component locations or file paths without inspecting the actual codebase.
29
-
30
- ## Core Principle
31
-
32
- A UI review evaluates whether the interface serves its users effectively.
33
-
34
- Before reviewing visual aesthetics, understand:
35
- - What is this interface for?
36
- - Who uses it?
37
- - What must they accomplish?
38
- - What is the primary action or decision?
39
-
40
- These answers determine what hierarchy problems matter and which visual choices are appropriate.
41
-
42
- ## Review Workflow
43
-
44
- 1. Understand the product and page purpose — what is this interface for?
45
- 2. Inspect the design system: existing components, tokens, conventions.
46
- 3. Read relevant component implementations.
47
- 4. Understand the primary user tasks.
48
- 5. Review visual hierarchy.
49
- 6. Review layout and spatial composition.
50
- 7. Review typography.
51
- 8. Review color.
52
- 9. Review responsive behavior.
53
- 10. Review interaction states.
54
- 11. Review accessibility basics.
55
- 12. Review content quality.
56
- 13. Identify visual genericness where it harms the product.
57
- 14. Consolidate findings by priority.
58
- 15. Produce structured output.
59
-
60
- Do NOT edit files during review. If the user requests fixes after review, use FeCode's normal write tools and approval flow.
61
-
62
- ## Review Area: Visual Hierarchy
63
-
64
- Evaluate:
65
- - **Primary action clarity**: Is the most important action visually dominant?
66
- - **Information hierarchy**: Does the layout communicate what matters most?
67
- - **Typography hierarchy**: Do heading, subheading, body, and label roles create clear differentiation?
68
- - **Visual weight**: Does emphasis land on meaningful content, or is everything equally prominent?
69
- - **Scanability**: Can a user quickly orient themselves and find what they need?
70
-
71
- Questions to answer:
72
- - What does a user see first? Is that the right thing?
73
- - Are there elements competing for attention that should not?
74
- - Does anything important get buried in visual noise?
75
-
76
- ## Review Area: Layout and Spatial Composition
77
-
78
- Evaluate:
79
- - **Alignment**: Are elements consistently aligned on a grid?
80
- - **Spacing**: Is spacing consistent? Does it communicate groupings correctly?
81
- - **Grouping**: Do related elements appear proximate? Do unrelated elements have adequate separation?
82
- - **Container width**: Is body content constrained to a readable width, or is it full-bleed on wide screens?
83
- - **Density**: Is the layout density appropriate for the use case (dashboard vs. reading view vs. form)?
84
- - **Rhythm**: Is there consistent vertical rhythm through the page?
85
-
86
- ## Review Area: Typography
87
-
88
- Evaluate:
89
- - **Readability**: Can all text be comfortably read at its current size and contrast?
90
- - **Hierarchy**: Do heading levels create meaningful visual differentiation?
91
- - **Line length**: Is body text constrained to a readable measure (roughly 55–80ch)?
92
- - **Weight usage**: Is font weight used to create hierarchy, or is it decorative?
93
- - **Size appropriateness**: Are secondary/caption/label sizes legible at 100% zoom?
94
- - **Consistency**: Is the same typographic role expressed consistently across the interface?
95
-
96
- ## Review Area: Color
97
-
98
- Evaluate:
99
- - **Semantic meaning**: Do colors communicate their intended meaning (error red, success green, primary action)?
100
- - **Contrast**: Is text readable on its background? (WCAG AA minimum)
101
- - **Accent discipline**: Are accent colors used purposefully, or scattered decoratively?
102
- - **Surface hierarchy**: Does background → surface → elevated surface create clear depth?
103
- - **Design token consistency**: Are arbitrary hex values appearing where design tokens should be used?
104
- - **Dark mode consistency**: If dark mode is present, do colors maintain their semantic meaning?
105
-
106
- ## Review Area: Components
107
-
108
- Evaluate:
109
- - **Consistency**: Do similar UI patterns use the same components?
110
- - **Reuse**: Are existing primitives (Button, Card, Input) used rather than re-implemented?
111
- - **Duplication**: Are there multiple implementations of the same visual component?
112
- - **Unnecessary complexity**: Are any components over-engineered for their actual use?
113
- - **Component boundaries**: Do components have coherent, single responsibilities?
114
-
115
- ## Review Area: Responsive Behavior
116
-
117
- Evaluate:
118
- - **Narrow viewport**: Does the layout function at 375px?
119
- - **Intermediate widths**: Does anything break awkwardly between breakpoints?
120
- - **Wide screens**: Is content meaningfully constrained on very wide viewports?
121
- - **Horizontal overflow**: Is there any unexpected horizontal scrolling?
122
- - **Navigation**: Does navigation function correctly at small sizes?
123
- - **Content wrapping**: Does text wrap gracefully, or does it truncate unexpectedly?
124
-
125
- ## Review Area: Interaction States
126
-
127
- Evaluate whether all interactive elements have defined, visible states:
128
-
129
- | State | Present | Distinct | Accessible |
130
- |-------|---------|----------|------------|
131
- | hover | ? | ? | ? |
132
- | focus-visible | ? | ? | ? |
133
- | active/pressed | ? | ? | ? |
134
- | disabled | ? | ? | ? |
135
- | loading | ? | ? | ? |
136
- | error | ? | ? | ? |
137
- | success | ? | ? | ? |
138
- | empty | ? | ? | ? |
139
-
140
- A UI where only `hover` is styled is incomplete.
141
-
142
- ## Review Area: Accessibility Basics
143
-
144
- Evaluate (do not duplicate the full accessibility skill):
145
- - **Semantic HTML**: Are interactive elements real buttons and links?
146
- - **Keyboard access**: Can the primary interaction be completed without a mouse?
147
- - **Visible focus**: Is `:focus-visible` styled and visible?
148
- - **Contrast**: Does text pass WCAG AA contrast ratios?
149
- - **Labels**: Do form fields and icon buttons have accessible labels?
150
- - **Color-only communication**: Is any state communicated by color alone, with no other indicator?
151
-
152
- For deeper accessibility evaluation, pair this review with the accessibility skill.
153
-
154
- ## Review Area: Content Quality
155
-
156
- Evaluate:
157
- - **Labels**: Are labels specific and action-oriented, or vague ("Submit", "Click here")?
158
- - **Placeholder content**: Is any placeholder text visible in the interface?
159
- - **Realistic content assumptions**: Is the layout tested with realistic content lengths?
160
- - **Empty states**: Are empty states designed, or do they leave a blank void?
161
- - **Error states**: Do error messages explain what happened and what to do?
162
- - **Long content**: Does the layout handle long names, descriptions, or list items gracefully?
163
-
164
- ## Review Area: Visual Genericness
165
-
166
- Look for patterns that indicate the interface could belong to any product:
167
-
168
- - Cards used for every content type regardless of appropriateness
169
- - Hero sections with centered headline, subtext, and two buttons on every page
170
- - Uniform rounded corners regardless of brand personality
171
- - Gradients applied without product purpose
172
- - Glassmorphism or blur effects used decoratively
173
- - Decorative blobs, particles, or abstract shapes
174
- - Every section wrapped in a card, inside another card
175
- - Bento grids with unrelated icons as content substitutes
176
- - Repetitive section structure repeated across multiple pages
177
-
178
- **Evaluate whether each pattern serves the product, not whether it is fashionable.**
179
-
180
- Some of these patterns are legitimate for specific products and design directions. Flag them only when they appear mechanical rather than deliberate.
181
-
182
- ## Finding Severity Levels
183
-
184
- Organize findings by user impact:
185
-
186
- ### Critical
187
- Problems that materially impair the user's ability to accomplish their primary task.
188
-
189
- Examples: Inaccessible interactive element, broken form validation, unreadable text contrast, layout collapse at target viewport.
190
-
191
- ### High
192
- Significant problems that reduce trust, comprehension, or efficiency without blocking the primary task.
193
-
194
- Examples: Missing interaction states, unclear hierarchy hiding important actions, inconsistent component usage, readable but poor typography hierarchy.
195
-
196
- ### Medium
197
- Polish and consistency issues that reduce the interface's quality without direct functional impact.
198
-
199
- Examples: Spacing inconsistencies, missing empty states, design token violations, minor typography inconsistencies.
200
-
201
- ### Low
202
- Minor improvements with small user impact.
203
-
204
- Examples: Wording improvements, hover animation polish, minor visual alignment corrections.
205
-
206
- ## Finding Format
207
-
208
- Each finding should ideally include:
209
- - **Issue**: What specifically is wrong
210
- - **Location**: Where it occurs (component name, page section) — only assert specific file paths after inspecting them
211
- - **Why it matters**: What user impact this has
212
- - **Suggested direction**: What kind of fix would address it (not necessarily exact implementation)
213
-
214
- Do not fabricate locations. If you have not read the relevant file, say "in the [ComponentName] component area" rather than inventing a file path.
215
-
216
- ## Self-Check Before Producing Findings
217
-
218
- - Have you understood what this interface is actually for?
219
- - Are your findings grounded in the interface's purpose, not generic UI preferences?
220
- - Have you separated functional problems from aesthetic preferences?
221
- - Have you prioritized by user impact, not by what is easy to fix?
222
- - Have you avoided recommending a redesign when the user asked for a review?
223
-
224
- ## Avoid
225
-
226
- - Automatically editing files during review — produce findings and let the user decide what to fix.
227
- - Reporting every finding as Critical — prioritize ruthlessly.
228
- - Asserting exact file paths without inspecting the actual codebase.
229
- - Flagging valid design choices as problems simply because they are not your preference.
230
- - Suggesting a full redesign when specific targeted improvements were requested.
231
- - Producing generic findings that could apply to any interface — ground them in this specific product.
232
-
233
- ## Examples
234
-
235
- ### Example: Grounded hierarchy finding
236
-
237
- Generic (unhelpful): "The visual hierarchy needs improvement."
238
-
239
- Grounded: "The 'Export' action and the 'Delete' action appear at the same visual weight. Delete is a destructive action that users should approach deliberately; its current prominence may cause accidental triggering. Consider reducing its visual weight (ghost/outline variant) relative to the primary Export action."
240
-
241
- ### Example: Distinguishing problem from preference
242
-
243
- "The rounded corners feel too soft" is a preference.
244
-
245
- "The border-radius on these cards (24px) is inconsistent with all other components in the application (8px), creating visual fragmentation" is a grounded finding.
1
+ ---
2
+ name: ui-review
3
+ description: Structured UI critique and evaluation for existing interfaces. Apply when asked to review, evaluate, audit, or assess an interface — not to build or modify it. This skill produces prioritized findings across visual hierarchy, layout, typography, color, components, responsive behavior, interaction states, accessibility, content, and visual genericness. Use it before implementing improvements to establish what matters most.
4
+ category: frontend
5
+ version: 1.0.0
6
+ ---
7
+
8
+ # UI Review
9
+
10
+ ## When to use
11
+ - Reviewing an existing interface and identifying what should be improved
12
+ - Auditing a page or component before a redesign or polish pass
13
+ - Identifying the highest-impact issues before a sprint or release
14
+ - Evaluating a newly implemented UI against its design intent
15
+ - Producing a prioritized list of findings for a team discussion
16
+
17
+ ## When not to use
18
+ - Building new UI from scratch (use frontend-design instead)
19
+ - Fixing a specific broken interaction (use frontend-debugging instead)
20
+ - Implementing responsive layout improvements (use responsive-design instead)
21
+
22
+ ## Instructions
23
+ - Review the interface as a product, not merely as code.
24
+ - Do not automatically modify files during a review — produce findings first.
25
+ - Prioritize findings by user impact, not by personal aesthetic preference.
26
+ - Ground every finding in a specific observation: where the issue occurs, what the effect is, why it matters.
27
+ - Distinguish between problems that impair usability and those that are polish opportunities.
28
+ - Do not invent component locations or file paths without inspecting the actual codebase.
29
+
30
+ ## Core Principle
31
+
32
+ A UI review evaluates whether the interface serves its users effectively.
33
+
34
+ Before reviewing visual aesthetics, understand:
35
+ - What is this interface for?
36
+ - Who uses it?
37
+ - What must they accomplish?
38
+ - What is the primary action or decision?
39
+
40
+ These answers determine what hierarchy problems matter and which visual choices are appropriate.
41
+
42
+ ## Review Workflow
43
+
44
+ 1. Understand the product and page purpose — what is this interface for?
45
+ 2. Inspect the design system: existing components, tokens, conventions.
46
+ 3. Read relevant component implementations.
47
+ 4. Understand the primary user tasks.
48
+ 5. Review visual hierarchy.
49
+ 6. Review layout and spatial composition.
50
+ 7. Review typography.
51
+ 8. Review color.
52
+ 9. Review responsive behavior.
53
+ 10. Review interaction states.
54
+ 11. Review accessibility basics.
55
+ 12. Review content quality.
56
+ 13. Identify visual genericness where it harms the product.
57
+ 14. Consolidate findings by priority.
58
+ 15. Produce structured output.
59
+
60
+ Do NOT edit files during review. If the user requests fixes after review, use FeCode's normal write tools and approval flow.
61
+
62
+ ## Review Area: Visual Hierarchy
63
+
64
+ Evaluate:
65
+ - **Primary action clarity**: Is the most important action visually dominant?
66
+ - **Information hierarchy**: Does the layout communicate what matters most?
67
+ - **Typography hierarchy**: Do heading, subheading, body, and label roles create clear differentiation?
68
+ - **Visual weight**: Does emphasis land on meaningful content, or is everything equally prominent?
69
+ - **Scanability**: Can a user quickly orient themselves and find what they need?
70
+
71
+ Questions to answer:
72
+ - What does a user see first? Is that the right thing?
73
+ - Are there elements competing for attention that should not?
74
+ - Does anything important get buried in visual noise?
75
+
76
+ ## Review Area: Layout and Spatial Composition
77
+
78
+ Evaluate:
79
+ - **Alignment**: Are elements consistently aligned on a grid?
80
+ - **Spacing**: Is spacing consistent? Does it communicate groupings correctly?
81
+ - **Grouping**: Do related elements appear proximate? Do unrelated elements have adequate separation?
82
+ - **Container width**: Is body content constrained to a readable width, or is it full-bleed on wide screens?
83
+ - **Density**: Is the layout density appropriate for the use case (dashboard vs. reading view vs. form)?
84
+ - **Rhythm**: Is there consistent vertical rhythm through the page?
85
+
86
+ ## Review Area: Typography
87
+
88
+ Evaluate:
89
+ - **Readability**: Can all text be comfortably read at its current size and contrast?
90
+ - **Hierarchy**: Do heading levels create meaningful visual differentiation?
91
+ - **Line length**: Is body text constrained to a readable measure (roughly 55–80ch)?
92
+ - **Weight usage**: Is font weight used to create hierarchy, or is it decorative?
93
+ - **Size appropriateness**: Are secondary/caption/label sizes legible at 100% zoom?
94
+ - **Consistency**: Is the same typographic role expressed consistently across the interface?
95
+
96
+ ## Review Area: Color
97
+
98
+ Evaluate:
99
+ - **Semantic meaning**: Do colors communicate their intended meaning (error red, success green, primary action)?
100
+ - **Contrast**: Is text readable on its background? (WCAG AA minimum)
101
+ - **Accent discipline**: Are accent colors used purposefully, or scattered decoratively?
102
+ - **Surface hierarchy**: Does background → surface → elevated surface create clear depth?
103
+ - **Design token consistency**: Are arbitrary hex values appearing where design tokens should be used?
104
+ - **Dark mode consistency**: If dark mode is present, do colors maintain their semantic meaning?
105
+
106
+ ## Review Area: Components
107
+
108
+ Evaluate:
109
+ - **Consistency**: Do similar UI patterns use the same components?
110
+ - **Reuse**: Are existing primitives (Button, Card, Input) used rather than re-implemented?
111
+ - **Duplication**: Are there multiple implementations of the same visual component?
112
+ - **Unnecessary complexity**: Are any components over-engineered for their actual use?
113
+ - **Component boundaries**: Do components have coherent, single responsibilities?
114
+
115
+ ## Review Area: Responsive Behavior
116
+
117
+ Evaluate:
118
+ - **Narrow viewport**: Does the layout function at 375px?
119
+ - **Intermediate widths**: Does anything break awkwardly between breakpoints?
120
+ - **Wide screens**: Is content meaningfully constrained on very wide viewports?
121
+ - **Horizontal overflow**: Is there any unexpected horizontal scrolling?
122
+ - **Navigation**: Does navigation function correctly at small sizes?
123
+ - **Content wrapping**: Does text wrap gracefully, or does it truncate unexpectedly?
124
+
125
+ ## Review Area: Interaction States
126
+
127
+ Evaluate whether all interactive elements have defined, visible states:
128
+
129
+ | State | Present | Distinct | Accessible |
130
+ |-------|---------|----------|------------|
131
+ | hover | ? | ? | ? |
132
+ | focus-visible | ? | ? | ? |
133
+ | active/pressed | ? | ? | ? |
134
+ | disabled | ? | ? | ? |
135
+ | loading | ? | ? | ? |
136
+ | error | ? | ? | ? |
137
+ | success | ? | ? | ? |
138
+ | empty | ? | ? | ? |
139
+
140
+ A UI where only `hover` is styled is incomplete.
141
+
142
+ ## Review Area: Accessibility Basics
143
+
144
+ Evaluate (do not duplicate the full accessibility skill):
145
+ - **Semantic HTML**: Are interactive elements real buttons and links?
146
+ - **Keyboard access**: Can the primary interaction be completed without a mouse?
147
+ - **Visible focus**: Is `:focus-visible` styled and visible?
148
+ - **Contrast**: Does text pass WCAG AA contrast ratios?
149
+ - **Labels**: Do form fields and icon buttons have accessible labels?
150
+ - **Color-only communication**: Is any state communicated by color alone, with no other indicator?
151
+
152
+ For deeper accessibility evaluation, pair this review with the accessibility skill.
153
+
154
+ ## Review Area: Content Quality
155
+
156
+ Evaluate:
157
+ - **Labels**: Are labels specific and action-oriented, or vague ("Submit", "Click here")?
158
+ - **Placeholder content**: Is any placeholder text visible in the interface?
159
+ - **Realistic content assumptions**: Is the layout tested with realistic content lengths?
160
+ - **Empty states**: Are empty states designed, or do they leave a blank void?
161
+ - **Error states**: Do error messages explain what happened and what to do?
162
+ - **Long content**: Does the layout handle long names, descriptions, or list items gracefully?
163
+
164
+ ## Review Area: Visual Genericness
165
+
166
+ Look for patterns that indicate the interface could belong to any product:
167
+
168
+ - Cards used for every content type regardless of appropriateness
169
+ - Hero sections with centered headline, subtext, and two buttons on every page
170
+ - Uniform rounded corners regardless of brand personality
171
+ - Gradients applied without product purpose
172
+ - Glassmorphism or blur effects used decoratively
173
+ - Decorative blobs, particles, or abstract shapes
174
+ - Every section wrapped in a card, inside another card
175
+ - Bento grids with unrelated icons as content substitutes
176
+ - Repetitive section structure repeated across multiple pages
177
+
178
+ **Evaluate whether each pattern serves the product, not whether it is fashionable.**
179
+
180
+ Some of these patterns are legitimate for specific products and design directions. Flag them only when they appear mechanical rather than deliberate.
181
+
182
+ ## Finding Severity Levels
183
+
184
+ Organize findings by user impact:
185
+
186
+ ### Critical
187
+ Problems that materially impair the user's ability to accomplish their primary task.
188
+
189
+ Examples: Inaccessible interactive element, broken form validation, unreadable text contrast, layout collapse at target viewport.
190
+
191
+ ### High
192
+ Significant problems that reduce trust, comprehension, or efficiency without blocking the primary task.
193
+
194
+ Examples: Missing interaction states, unclear hierarchy hiding important actions, inconsistent component usage, readable but poor typography hierarchy.
195
+
196
+ ### Medium
197
+ Polish and consistency issues that reduce the interface's quality without direct functional impact.
198
+
199
+ Examples: Spacing inconsistencies, missing empty states, design token violations, minor typography inconsistencies.
200
+
201
+ ### Low
202
+ Minor improvements with small user impact.
203
+
204
+ Examples: Wording improvements, hover animation polish, minor visual alignment corrections.
205
+
206
+ ## Finding Format
207
+
208
+ Each finding should ideally include:
209
+ - **Issue**: What specifically is wrong
210
+ - **Location**: Where it occurs (component name, page section) — only assert specific file paths after inspecting them
211
+ - **Why it matters**: What user impact this has
212
+ - **Suggested direction**: What kind of fix would address it (not necessarily exact implementation)
213
+
214
+ Do not fabricate locations. If you have not read the relevant file, say "in the [ComponentName] component area" rather than inventing a file path.
215
+
216
+ ## Self-Check Before Producing Findings
217
+
218
+ - Have you understood what this interface is actually for?
219
+ - Are your findings grounded in the interface's purpose, not generic UI preferences?
220
+ - Have you separated functional problems from aesthetic preferences?
221
+ - Have you prioritized by user impact, not by what is easy to fix?
222
+ - Have you avoided recommending a redesign when the user asked for a review?
223
+
224
+ ## Avoid
225
+
226
+ - Automatically editing files during review — produce findings and let the user decide what to fix.
227
+ - Reporting every finding as Critical — prioritize ruthlessly.
228
+ - Asserting exact file paths without inspecting the actual codebase.
229
+ - Flagging valid design choices as problems simply because they are not your preference.
230
+ - Suggesting a full redesign when specific targeted improvements were requested.
231
+ - Producing generic findings that could apply to any interface — ground them in this specific product.
232
+
233
+ ## Examples
234
+
235
+ ### Example: Grounded hierarchy finding
236
+
237
+ Generic (unhelpful): "The visual hierarchy needs improvement."
238
+
239
+ Grounded: "The 'Export' action and the 'Delete' action appear at the same visual weight. Delete is a destructive action that users should approach deliberately; its current prominence may cause accidental triggering. Consider reducing its visual weight (ghost/outline variant) relative to the primary Export action."
240
+
241
+ ### Example: Distinguishing problem from preference
242
+
243
+ "The rounded corners feel too soft" is a preference.
244
+
245
+ "The border-radius on these cards (24px) is inconsistent with all other components in the application (8px), creating visual fragmentation" is a grounded finding.