fix(skills): add Anti-Patterns and fix descriptions for remaining skills (batch 2)

Processed 24 skills: pr-description-writer through tax-planning-checklist.
Added Anti-Patterns sections to all 24 skills.
Added Required Inputs section to product-launch-checklist.
Rewrote descriptions for retro-analysis, substack-notes-scraper, and sycophancy-challenger.

https://claude.ai/code/session_01MuGKn3a3Gbqoe8uM5Lmuqt
This commit is contained in:
Mohit
2026-06-08 12:57:05 +00:00
parent a33b4f7003
commit f170eed437
24 changed files with 204 additions and 3 deletions
+8
View File
@@ -125,6 +125,14 @@ Things to tackle in production but out of scope for this design session:
- [ ] Trade-offs section is honest (not just benefits of chosen approach)
- [ ] Data flow is described end-to-end for the critical path
## Anti-Patterns
- [ ] Do not jump to solutions before clarifying requirements — always establish functional and non-functional requirements first
- [ ] Do not present a design without discussing trade-offs — every architecture decision has costs and benefits that must be acknowledged
- [ ] Do not use vague capacity estimates — show the actual calculation (QPS, storage bytes, bandwidth) not just "this handles scale"
- [ ] Do not design for unlimited scale by default — match the design to the requirements stated
- [ ] Do not skip the data model — a system design without entity definitions and data flow is incomplete
## Usage Examples
- "Help me answer a system design interview: [question]"
- "Design [system] for a system design interview"