Menü
Use after fixing or investigating a hard-earned bug that took significant debugging, crossed multiple files or systems, had misleading symptoms, or revealed durable system behavior worth preserving in docs/knowledge/learnings.
| name | bug-learning |
| description | Use after fixing or investigating a hard-earned bug that took significant debugging, crossed multiple files or systems, had misleading symptoms, or revealed durable system behavior worth preserving in docs/knowledge/learnings. |
Capture only hard-earned bug knowledge, not ordinary bug reports.
knowledge learning "<Title>".references/bug-learning.md for the file shape.Known Learnings.key_files when the investigation reveals durable knowledge.knowledge check.Systematically upgrade project dependencies. Use for Composer, npm, bun, pnpm, yarn, lockfile updates, security updates, Laravel/PHP upgrades, React/JavaScript upgrades, framework bumps, package modernization, or dependency cleanup.
Use when answering questions about a project feature, documenting existing functionality, investigating product behavior, or maintaining docs/knowledge feature packs, glossary terms, aliases, key files, and feature history.
Stress-test and challenge ideas before building. Use when the user wants to think through code architecture, UX/UI, or product direction before implementation.
Find high-leverage product opportunities. Use when the user wants product strategy, asks what would make something 10x better, or wants to decide what to build next.
Run project checks from repo-root `CHECKLIST.md` and fix task-related failures, including skipped tests. Use when the user asks to run checks, lint and fix, or verify code quality.
Create, review, refine, or execute conversational plans before implementation. Use when the user asks for a plan, implementation plan, roadmap, task breakdown, sequence, scope, phases, or multi-step work. For uncertain architecture, product, UX, or pre-implementation direction, apply the workshop skill first.