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

skills/technical-debt-register/SKILL.md

@@ -258,3 +258,11 @@ Items where the cost of remediation currently exceeds the business value, accept
 - [ ] Accepted/deferred items have a review date and a named owner — no permanently deferred items
 - [ ] The register distinguishes between debt (deliberate or accumulated shortcuts) and bugs (unintended defects)
 - [ ] Items are closed as resolved only when acceptance criteria are met — not when the PR is merged
+
+## Anti-Patterns
+
+- [ ] Do not score debt items arbitrarily — priority scores must be calculated using the documented formula
+- [ ] Do not conflate technical debt (deliberate shortcuts) with bugs (unintended defects) — they require different remediation strategies
+- [ ] Do not underrate security and dependency items because they feel abstract — score based on actual business impact
+- [ ] Do not create "permanently deferred" items — every accepted item must have a review date and named owner
+- [ ] Do not include resolution plans that are vague descriptions — each plan must have specific, ticketable steps