style: format all files with prettier

This commit is contained in:
Seth Hobson
2026-01-19 17:07:03 -05:00
parent 8d37048deb
commit 56848874a2
355 changed files with 15215 additions and 10241 deletions

View File

@@ -130,24 +130,28 @@ Read and analyze the target files:
Check for:
**Spacing & Layout:**
- Inconsistent margins/padding
- Misaligned elements
- Unbalanced whitespace
- Magic numbers vs. design tokens
**Typography:**
- Font size consistency
- Line height appropriateness
- Text contrast ratios
- Font weight usage
**Colors:**
- Color contrast accessibility
- Consistent color usage
- Semantic color application
- Dark mode support (if applicable)
**Visual Hierarchy:**
- Clear primary actions
- Appropriate emphasis
- Scannable content structure
@@ -157,6 +161,7 @@ Check for:
Check for:
**Interaction Patterns:**
- Clear clickable/tappable areas
- Appropriate hover/focus states
- Loading state indicators
@@ -164,12 +169,14 @@ Check for:
- Empty state handling
**User Flow:**
- Logical tab order
- Clear call-to-action
- Predictable behavior
- Feedback on actions
**Cognitive Load:**
- Information density
- Progressive disclosure
- Clear labels and instructions
@@ -180,18 +187,21 @@ Check for:
Check for:
**Component Patterns:**
- Single responsibility
- Prop drilling depth
- State management appropriateness
- Component reusability
**Styling Patterns:**
- Consistent naming conventions
- Reusable style definitions
- Media query organization
- CSS specificity issues
**Maintainability:**
- Clear component boundaries
- Documentation/comments
- Test coverage
@@ -202,12 +212,14 @@ Check for:
Check for:
**Render Optimization:**
- Unnecessary re-renders
- Missing memoization
- Large component trees
- Expensive computations in render
**Asset Optimization:**
- Image sizes and formats
- Icon implementation
- Font loading strategy
@@ -217,7 +229,7 @@ Check for:
Generate review report in `.ui-design/reviews/{review_id}.md`:
```markdown
````markdown
# Design Review: {Component/File Name}
**Review ID:** {review_id}
@@ -230,6 +242,7 @@ Generate review report in `.ui-design/reviews/{review_id}.md`:
{2-3 sentence overview of findings}
**Issues Found:** {total_count}
- Critical: {count}
- Major: {count}
- Minor: {count}
@@ -253,6 +266,7 @@ Generate review report in `.ui-design/reviews/{review_id}.md`:
{Specific fix suggestion}
**Code Example:**
```{language}
// Before
{current_code}
@@ -260,22 +274,26 @@ Generate review report in `.ui-design/reviews/{review_id}.md`:
// After
{suggested_code}
```
````
---
## Major Issues
### Issue 2: {Title}
...
## Minor Issues
### Issue 3: {Title}
...
## Suggestions
### Suggestion 1: {Title}
...
## Positive Observations
@@ -294,6 +312,7 @@ Generate review report in `.ui-design/reviews/{review_id}.md`:
---
_Generated by UI Design Review. Run `/ui-design:design-review` again after fixes._
```
## Completion
@@ -307,22 +326,26 @@ After generating report:
2. Display summary:
```
Design Review Complete!
Target: {component/file}
Issues Found: {total}
- {critical} Critical
- {major} Major
- {minor} Minor
- {suggestions} Suggestions
- {critical} Critical
- {major} Major
- {minor} Minor
- {suggestions} Suggestions
Full report: .ui-design/reviews/{review_id}.md
What would you like to do next?
1. View detailed findings for a specific issue
2. Start implementing fixes
3. Export report (markdown/JSON)
4. Review another component
```
## Follow-up Actions
@@ -330,6 +353,7 @@ What would you like to do next?
If user selects "Start implementing fixes":
```
Which issues would you like to address?
1. All critical issues first
@@ -338,6 +362,7 @@ Which issues would you like to address?
4. Generate a fix plan for all issues
Enter choice:
```
Guide user through fixes one at a time, updating the review report as issues are resolved.
@@ -347,3 +372,4 @@ Guide user through fixes one at a time, updating the review report as issues are
- If target file not found: Suggest similar files, offer to search
- If file is not UI code: Explain and ask for correct target
- If review fails mid-way: Save partial results, offer to resume
```