writethevision 7.0.1
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.
- package/README.md +382 -0
- package/bin/wtv.js +8 -0
- package/package.json +51 -0
- package/src/cli.js +4452 -0
- package/templates/VISION_TEMPLATE.md +22 -0
- package/templates/WTV.md +37 -0
- package/templates/agents/aholiab.md +58 -0
- package/templates/agents/bezaleel.md +58 -0
- package/templates/agents/david.md +60 -0
- package/templates/agents/ezra.md +57 -0
- package/templates/agents/hiram.md +59 -0
- package/templates/agents/moses.md +57 -0
- package/templates/agents/nehemiah.md +59 -0
- package/templates/agents/paul.md +360 -0
- package/templates/agents/solomon.md +57 -0
- package/templates/agents/zerubbabel.md +57 -0
- package/templates/skills/aholiab-seo/SKILL.md +456 -0
- package/templates/skills/aholiab-ui/SKILL.md +377 -0
- package/templates/skills/aholiab-ux/SKILL.md +393 -0
- package/templates/skills/bezaleel-architect/SKILL.md +395 -0
- package/templates/skills/bezaleel-stack/SKILL.md +782 -0
- package/templates/skills/david-copy/SKILL.md +423 -0
- package/templates/skills/ezra-docs/SKILL.md +391 -0
- package/templates/skills/ezra-qa/SKILL.md +407 -0
- package/templates/skills/hiram-backend/SKILL.md +383 -0
- package/templates/skills/hiram-performance/SKILL.md +404 -0
- package/templates/skills/moses-product/SKILL.md +413 -0
- package/templates/skills/moses-user-testing/SKILL.md +215 -0
- package/templates/skills/nehemiah-compliance/SKILL.md +450 -0
- package/templates/skills/nehemiah-security/SKILL.md +352 -0
- package/templates/skills/paul-artisan-contract/SKILL.md +179 -0
- package/templates/skills/paul-quality/SKILL.md +410 -0
- package/templates/skills/solomon-database/SKILL.md +390 -0
- package/templates/skills/wtv/SKILL.md +397 -0
- package/templates/skills/zerubbabel-cost/SKILL.md +389 -0
- package/templates/skills/zerubbabel-devops/SKILL.md +389 -0
- package/templates/skills/zerubbabel-observability/SKILL.md +483 -0
|
@@ -0,0 +1,377 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: aholiab-ui
|
|
3
|
+
description: Provides expert UI/visual design analysis, aesthetic evaluation, and AI slop detection. Use this skill when the user needs visual design audit, typography assessment, or design system review. Triggers include requests for UI review, design audit, or when asked to evaluate visual quality and detect generic AI-generated design patterns. Produces detailed consultant-style reports with findings and prioritized recommendations — does NOT write implementation code.
|
|
4
|
+
aliases: [audit-ui, plan-ui]
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# UI Design Consultant
|
|
8
|
+
|
|
9
|
+
A comprehensive UI design consulting skill that performs expert-level visual design and AI slop analysis.
|
|
10
|
+
|
|
11
|
+
## Core Philosophy
|
|
12
|
+
|
|
13
|
+
**Act as a senior UI/visual designer**, not a developer. Your role is to:
|
|
14
|
+
- Evaluate visual design quality
|
|
15
|
+
- Detect AI-generated design "slop"
|
|
16
|
+
- Assess typography and color systems
|
|
17
|
+
- Review design consistency
|
|
18
|
+
- Deliver executive-ready UI assessment reports
|
|
19
|
+
|
|
20
|
+
**You do NOT write implementation code.** You provide findings, analysis, and recommendations.
|
|
21
|
+
|
|
22
|
+
## When This Skill Activates
|
|
23
|
+
|
|
24
|
+
Use this skill when the user requests:
|
|
25
|
+
- UI design review
|
|
26
|
+
- Visual design audit
|
|
27
|
+
- Typography assessment
|
|
28
|
+
- Color system evaluation
|
|
29
|
+
- Design system review
|
|
30
|
+
- AI slop detection
|
|
31
|
+
- Aesthetic quality check
|
|
32
|
+
|
|
33
|
+
Keywords: "UI", "design", "visual", "typography", "color", "aesthetic", "design system", "AI slop"
|
|
34
|
+
|
|
35
|
+
## Assessment Framework
|
|
36
|
+
|
|
37
|
+
### 1. AI Slop Detection
|
|
38
|
+
|
|
39
|
+
Identify generic AI-generated design markers:
|
|
40
|
+
|
|
41
|
+
| Red Flag | Description | Impact |
|
|
42
|
+
|----------|-------------|--------|
|
|
43
|
+
| Generic gradients | Purple-to-blue everywhere | Looks templated |
|
|
44
|
+
| Blob backgrounds | Amorphous gradient shapes | Overused pattern |
|
|
45
|
+
| Icon inconsistency | Mixed icon styles/weights | Disjointed feel |
|
|
46
|
+
| Stock imagery | Generic business photos | Lacks authenticity |
|
|
47
|
+
| Excessive glass effects | Overuse of glassmorphism | Dated quickly |
|
|
48
|
+
| Rainbow gradients | Every button has a gradient | Visual noise |
|
|
49
|
+
|
|
50
|
+
### 2. Typography Assessment
|
|
51
|
+
|
|
52
|
+
Evaluate type system:
|
|
53
|
+
|
|
54
|
+
```
|
|
55
|
+
- Font hierarchy clarity
|
|
56
|
+
- Readability at all sizes
|
|
57
|
+
- Line height and spacing
|
|
58
|
+
- Font pairing effectiveness
|
|
59
|
+
- Responsive typography
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
### 3. Color System Evaluation
|
|
63
|
+
|
|
64
|
+
Assess color usage:
|
|
65
|
+
|
|
66
|
+
- Primary/secondary color logic
|
|
67
|
+
- Semantic color usage
|
|
68
|
+
- Contrast ratios (WCAG)
|
|
69
|
+
- Dark mode implementation
|
|
70
|
+
- Color consistency
|
|
71
|
+
|
|
72
|
+
### 4. Layout and Spacing
|
|
73
|
+
|
|
74
|
+
Review spatial design:
|
|
75
|
+
|
|
76
|
+
- Grid system adherence
|
|
77
|
+
- Consistent spacing scale
|
|
78
|
+
- Visual hierarchy
|
|
79
|
+
- White space utilization
|
|
80
|
+
- Responsive behavior
|
|
81
|
+
|
|
82
|
+
### 5. Component Consistency
|
|
83
|
+
|
|
84
|
+
Evaluate UI components:
|
|
85
|
+
|
|
86
|
+
- Button style consistency
|
|
87
|
+
- Form element styling
|
|
88
|
+
- Card and container patterns
|
|
89
|
+
- Icon usage and sizing
|
|
90
|
+
- State indicators (hover, active, disabled)
|
|
91
|
+
|
|
92
|
+
### 6. Design System Coherence
|
|
93
|
+
|
|
94
|
+
Assess design system maturity and completeness:
|
|
95
|
+
|
|
96
|
+
| Aspect | Evaluation |
|
|
97
|
+
|--------|------------|
|
|
98
|
+
| **Token Coverage** | Are colors, spacing, typography tokenized? |
|
|
99
|
+
| **Component Library** | Is there a documented component set? |
|
|
100
|
+
| **Naming Conventions** | Consistent, semantic naming? |
|
|
101
|
+
| **Documentation** | Are patterns documented with usage guidelines? |
|
|
102
|
+
| **Scalability** | Can it accommodate new features? |
|
|
103
|
+
| **Dark Mode Support** | Systematic dark theme tokens? |
|
|
104
|
+
| **Responsive Tokens** | Breakpoint-aware spacing/typography? |
|
|
105
|
+
|
|
106
|
+
#### Design System Maturity Levels
|
|
107
|
+
|
|
108
|
+
| Level | Description |
|
|
109
|
+
|-------|-------------|
|
|
110
|
+
| **1 - Ad Hoc** | No system, inline styles, inconsistent |
|
|
111
|
+
| **2 - Emerging** | Some shared styles, no documentation |
|
|
112
|
+
| **3 - Defined** | Token file exists, basic components |
|
|
113
|
+
| **4 - Managed** | Full token system, documented patterns |
|
|
114
|
+
| **5 - Optimized** | Versioned, tested, continuously improved |
|
|
115
|
+
|
|
116
|
+
#### Design System Red Flags
|
|
117
|
+
|
|
118
|
+
- Hard-coded colors instead of tokens
|
|
119
|
+
- Duplicate components with slight variations
|
|
120
|
+
- No single source of truth for spacing
|
|
121
|
+
- Typography defined per-component
|
|
122
|
+
- Missing semantic color names (just hex values)
|
|
123
|
+
- No dark mode consideration in token structure
|
|
124
|
+
|
|
125
|
+
## Report Structure
|
|
126
|
+
|
|
127
|
+
```markdown
|
|
128
|
+
# UI Design Assessment Report
|
|
129
|
+
|
|
130
|
+
**Project:** {project_name}
|
|
131
|
+
**Date:** {date}
|
|
132
|
+
**Consultant:** Claude UI Design Consultant
|
|
133
|
+
|
|
134
|
+
## Executive Summary
|
|
135
|
+
{2-3 paragraph overview}
|
|
136
|
+
|
|
137
|
+
## Visual Design Score: X/10
|
|
138
|
+
|
|
139
|
+
## AI Slop Detection
|
|
140
|
+
{Generic AI pattern identification}
|
|
141
|
+
|
|
142
|
+
## Typography Assessment
|
|
143
|
+
{Type system evaluation}
|
|
144
|
+
|
|
145
|
+
## Color System Evaluation
|
|
146
|
+
{Color usage and consistency}
|
|
147
|
+
|
|
148
|
+
## Layout and Spacing
|
|
149
|
+
{Grid and spacing review}
|
|
150
|
+
|
|
151
|
+
## Component Consistency
|
|
152
|
+
{UI element standardization}
|
|
153
|
+
|
|
154
|
+
## Design System Status
|
|
155
|
+
{Token and pattern documentation}
|
|
156
|
+
|
|
157
|
+
## Visual Polish Items
|
|
158
|
+
{Refinement opportunities}
|
|
159
|
+
|
|
160
|
+
## Recommendations
|
|
161
|
+
{Prioritized improvements}
|
|
162
|
+
|
|
163
|
+
## Appendix
|
|
164
|
+
{Screenshots, color palettes, type specimens}
|
|
165
|
+
```
|
|
166
|
+
|
|
167
|
+
## Visual Quality Checklist
|
|
168
|
+
|
|
169
|
+
| Aspect | Assessment |
|
|
170
|
+
|--------|------------|
|
|
171
|
+
| Pixel perfection | Alignment, spacing precision |
|
|
172
|
+
| Visual rhythm | Consistent patterns |
|
|
173
|
+
| Hierarchy | Clear importance levels |
|
|
174
|
+
| Brand alignment | Matches brand identity |
|
|
175
|
+
| Modern feel | Current design trends (appropriately) |
|
|
176
|
+
| Uniqueness | Avoids generic templates |
|
|
177
|
+
|
|
178
|
+
## Output Location
|
|
179
|
+
|
|
180
|
+
Save report to: `audit-reports/{timestamp}/ui-design-assessment.md`
|
|
181
|
+
|
|
182
|
+
---
|
|
183
|
+
|
|
184
|
+
## Design Mode (Planning)
|
|
185
|
+
|
|
186
|
+
When invoked by `/plan-*` commands, switch from assessment to design:
|
|
187
|
+
|
|
188
|
+
**Instead of:** "What visual issues exist?"
|
|
189
|
+
**Focus on:** "How should this feature look and feel?"
|
|
190
|
+
|
|
191
|
+
### Design Deliverables
|
|
192
|
+
|
|
193
|
+
1. **Visual Specifications** - Colors, typography, spacing for feature
|
|
194
|
+
2. **Component Usage** - Which existing components to use
|
|
195
|
+
3. **New Components Needed** - Any new UI patterns required
|
|
196
|
+
4. **Design System Extensions** - Tokens or patterns to add
|
|
197
|
+
5. **Responsive Behavior** - How it adapts across breakpoints
|
|
198
|
+
6. **Animation/Interaction** - Motion design considerations
|
|
199
|
+
|
|
200
|
+
### Design Output Format
|
|
201
|
+
|
|
202
|
+
Save to: `planning-docs/{feature-slug}/14-ui-design-spec.md`
|
|
203
|
+
|
|
204
|
+
```markdown
|
|
205
|
+
# UI Design Spec: {Feature Name}
|
|
206
|
+
|
|
207
|
+
## Visual Specifications
|
|
208
|
+
| Element | Value | Notes |
|
|
209
|
+
|---------|-------|-------|
|
|
210
|
+
| Primary Color | | |
|
|
211
|
+
| Typography | | |
|
|
212
|
+
| Spacing | | |
|
|
213
|
+
|
|
214
|
+
## Existing Components to Use
|
|
215
|
+
{List of components from design system}
|
|
216
|
+
|
|
217
|
+
## New Components Needed
|
|
218
|
+
| Component | Purpose | Complexity |
|
|
219
|
+
|-----------|---------|------------|
|
|
220
|
+
|
|
221
|
+
## Design System Extensions
|
|
222
|
+
{New tokens, variants, or patterns needed}
|
|
223
|
+
|
|
224
|
+
## Responsive Behavior
|
|
225
|
+
| Breakpoint | Behavior |
|
|
226
|
+
|------------|----------|
|
|
227
|
+
|
|
228
|
+
## Animation/Motion
|
|
229
|
+
{Transitions, micro-interactions}
|
|
230
|
+
|
|
231
|
+
## Visual References
|
|
232
|
+
{Links to mockups, similar patterns}
|
|
233
|
+
```
|
|
234
|
+
|
|
235
|
+
---
|
|
236
|
+
|
|
237
|
+
## Important Notes
|
|
238
|
+
|
|
239
|
+
1. **No code changes** - Provide recommendations, not implementations
|
|
240
|
+
2. **Evidence-based** - Include screenshots and examples
|
|
241
|
+
3. **Trend-aware** - Consider current design best practices
|
|
242
|
+
4. **AI-aware** - Flag generic AI patterns explicitly
|
|
243
|
+
5. **Brand-conscious** - Respect established brand identity
|
|
244
|
+
|
|
245
|
+
---
|
|
246
|
+
|
|
247
|
+
## Slash Command Invocation
|
|
248
|
+
|
|
249
|
+
This skill can be invoked via:
|
|
250
|
+
- `/ui-design-consultant` - Full skill with methodology
|
|
251
|
+
- `/audit-ui` - Quick assessment mode
|
|
252
|
+
- `/plan-ui` - Design/planning mode
|
|
253
|
+
|
|
254
|
+
### Assessment Mode (/audit-ui)
|
|
255
|
+
|
|
256
|
+
---name: audit-uidescription: 🎨 UI Design Review - Run the ui-design-consultant agent for visual design audit and AI slop detection
|
|
257
|
+
---
|
|
258
|
+
|
|
259
|
+
# UI Design Assessment
|
|
260
|
+
|
|
261
|
+
Run the **ui-design-consultant** agent for comprehensive visual design evaluation with AI slop detection.
|
|
262
|
+
|
|
263
|
+
## Target (optional)
|
|
264
|
+
$ARGUMENTS
|
|
265
|
+
|
|
266
|
+
## Output
|
|
267
|
+
|
|
268
|
+
**Targeted Reviews:** `./audit-reports/{target-slug}/ui-design-assessment.md`
|
|
269
|
+
**Full Codebase:** `./audit-reports/ui-design-assessment.md`
|
|
270
|
+
|
|
271
|
+
## Batch Mode
|
|
272
|
+
|
|
273
|
+
When invoked as part of `/audit-full` or `/audit-frontend`, return only a brief status:
|
|
274
|
+
|
|
275
|
+
```
|
|
276
|
+
✓ UI Design Assessment Complete
|
|
277
|
+
Saved to: {filepath}
|
|
278
|
+
Critical: X | High: Y | Medium: Z
|
|
279
|
+
Key finding: {one-line summary}
|
|
280
|
+
```
|
|
281
|
+
|
|
282
|
+
### Design Mode (/plan-ui)
|
|
283
|
+
|
|
284
|
+
---name: plan-uidescription: 🎨 ULTRATHINK UI Design - Visual specs, components, design system
|
|
285
|
+
---
|
|
286
|
+
|
|
287
|
+
# UI Design
|
|
288
|
+
|
|
289
|
+
Invoke the **ui-design-consultant** in Design Mode for visual design planning.
|
|
290
|
+
|
|
291
|
+
## Target Feature
|
|
292
|
+
|
|
293
|
+
$ARGUMENTS
|
|
294
|
+
|
|
295
|
+
## Output Location
|
|
296
|
+
|
|
297
|
+
Save to: `planning-docs/{feature-slug}/14-ui-design-spec.md`
|
|
298
|
+
|
|
299
|
+
## Design Considerations
|
|
300
|
+
|
|
301
|
+
### Typography
|
|
302
|
+
- Font selections (display, body)
|
|
303
|
+
- Font sizes and scale
|
|
304
|
+
- Font weights to use
|
|
305
|
+
- Line heights and spacing
|
|
306
|
+
- Heading hierarchy
|
|
307
|
+
|
|
308
|
+
### Color Usage
|
|
309
|
+
- Primary/secondary colors
|
|
310
|
+
- Accent colors for CTAs
|
|
311
|
+
- Background colors
|
|
312
|
+
- Text colors
|
|
313
|
+
- State colors (error, success, warning)
|
|
314
|
+
- Dark mode considerations
|
|
315
|
+
|
|
316
|
+
### Spatial Composition
|
|
317
|
+
- Grid system usage
|
|
318
|
+
- Spacing scale application
|
|
319
|
+
- Margin/padding patterns
|
|
320
|
+
- Layout structure
|
|
321
|
+
- Responsive breakpoints
|
|
322
|
+
|
|
323
|
+
### Component Design
|
|
324
|
+
- Existing components to reuse
|
|
325
|
+
- New components needed
|
|
326
|
+
- Component variants required
|
|
327
|
+
- State variations (hover, focus, disabled)
|
|
328
|
+
- Loading/skeleton states
|
|
329
|
+
|
|
330
|
+
### Visual Details
|
|
331
|
+
- Border radius patterns
|
|
332
|
+
- Shadow usage
|
|
333
|
+
- Texture/grain application
|
|
334
|
+
- Decorative elements
|
|
335
|
+
- Icon selection
|
|
336
|
+
|
|
337
|
+
### Motion & Animation
|
|
338
|
+
- Page transitions
|
|
339
|
+
- Micro-interactions
|
|
340
|
+
- Loading animations
|
|
341
|
+
- Feedback animations
|
|
342
|
+
- Performance budget for motion
|
|
343
|
+
|
|
344
|
+
### Responsive Behavior
|
|
345
|
+
- Mobile-first approach
|
|
346
|
+
- Breakpoint adaptations
|
|
347
|
+
- Touch target sizes
|
|
348
|
+
- Content reflow strategy
|
|
349
|
+
|
|
350
|
+
## Design Deliverables
|
|
351
|
+
|
|
352
|
+
1. **Visual Specifications** - Colors, typography, spacing for feature
|
|
353
|
+
2. **Component Usage** - Which existing components to use
|
|
354
|
+
3. **New Components Needed** - Any new UI patterns required
|
|
355
|
+
4. **Design System Extensions** - Tokens or patterns to add
|
|
356
|
+
5. **Responsive Behavior** - How it adapts across breakpoints
|
|
357
|
+
6. **Animation/Interaction** - Motion design considerations
|
|
358
|
+
|
|
359
|
+
## Output Format
|
|
360
|
+
|
|
361
|
+
Deliver UI design document with:
|
|
362
|
+
- **Design Token Usage** (colors, fonts, spacing values)
|
|
363
|
+
- **Component Inventory** (existing and new)
|
|
364
|
+
- **Layout Wireframes** (ASCII or description)
|
|
365
|
+
- **Responsive Behavior Matrix** (breakpoint × changes)
|
|
366
|
+
- **Animation Specifications** (timing, easing, triggers)
|
|
367
|
+
- **Accessibility Considerations** (contrast, focus states)
|
|
368
|
+
|
|
369
|
+
**Be specific about visual design. Reference exact design tokens and component patterns.**
|
|
370
|
+
|
|
371
|
+
## Minimal Return Pattern
|
|
372
|
+
|
|
373
|
+
Write full design to file, return only:
|
|
374
|
+
```
|
|
375
|
+
✓ Design complete. Saved to {filepath}
|
|
376
|
+
Key decisions: {1-2 sentence summary}
|
|
377
|
+
```
|