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
2026-06-08 13:01:36 +00:00
parent f170eed437
commit fb85a1cb55
27 changed files with 234 additions and 18 deletions
@@ -288,3 +288,11 @@ This log records every ring movement since the radar's first edition. Use it to
 - [ ] Maintenance process includes: nomination channel, review cadence, who decides, and ring-change criteria
 - [ ] Technologies identified as "strategic bets" in the inputs are placed in Adopt (if proven) or Trial (if being rolled out)
 - [ ] Technologies identified for deprecation are in Hold with a rationale that references the replacement
+
+## Anti-Patterns
+
+- [ ] Do not place a technology in Adopt without evidence it is proven at the team's scale — aspirational placements mislead engineers
+- [ ] Do not add a blip without a written rationale paragraph — table rows without context are unusable
+- [ ] Do not create a Hold entry without specifying a concrete migration path or target technology
+- [ ] Do not skip the maintenance process — a radar with no process for updates becomes stale within two quarters
+- [ ] Do not omit ring definitions — engineers need to know what they should do in response to each ring, not just what the ring means