fix(skills): add Anti-Patterns and fix descriptions for remaining skills (batch 3)
Processed 27 skills: teaching-lesson-plan through feature-prioritisation and all figma skills. Added Anti-Patterns sections to all 27 skills. Added Quality Checks section to financial-due-diligence (was missing entirely). Converted user-research-synthesis Quality Standards to binary checkbox format. Rewrote descriptions for figma-design-critique-pm, figma-design-qa, figma-design-review, team-health-check, and user-interview-synthesis. https://claude.ai/code/session_01MuGKn3a3Gbqoe8uM5Lmuqt
This commit is contained in:
@@ -68,6 +68,14 @@ Feature name/
|
||||
- [ ] Out-of-scope section is explicit
|
||||
- [ ] Figma file structure matches screen map
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not plan only the happy path — all error states, empty states, and edge cases must be mapped before designing starts
|
||||
- [ ] Do not produce a flow map that doesn't match the Figma file structure — the page structure must reflect the flow map
|
||||
- [ ] Do not define screens without specifying all required states — a screen without its variants is an incomplete design scope
|
||||
- [ ] Do not start designing before entry and exit points are fully documented — unclear boundaries cause scope creep
|
||||
- [ ] Do not plan user flows without tying each step back to a user goal — every screen must justify its existence
|
||||
|
||||
## Example Trigger Phrases
|
||||
- "Plan the user flow for [feature] in Figma"
|
||||
- "What screens do I need to design for [feature]?"
|
||||
|
||||
Reference in New Issue
Block a user