From package-guide
This skill should be used proactively after resolving a bug related to Unity packages (SOAP, FEEL, DOTween) where the root cause was identified and a fix was applied. Also trigger when the user asks to "record this pitfall", "add to package guide", "save this finding", "update package pitfalls", "document this bug", "remember this fix", or "learned something about SOAP/FEEL/DOTween".
npx claudepluginhub flashwade03/unity-dev-vibecoding-with-awesome-assets --plugin package-guideThis skill uses the workspace's default tool permissions.
Record newly discovered package pitfalls and patterns into the knowledge base.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
Record newly discovered package pitfalls and patterns into the knowledge base. This skill enables the package-guide to grow autonomously from real debugging sessions.
From the conversation context, extract:
Read the existing pitfalls file:
${CLAUDE_PLUGIN_ROOT}/docs/{package}/pitfalls.md
Scan the troubleshooting table for matching symptoms. If a match exists:
If the file does not exist, proceed to "Adding a New Package" section first.
Create a new file at:
${CLAUDE_PLUGIN_ROOT}/docs/{package}/pitfalls/{issue-name}.md
Use kebab-case for the filename derived from the core issue.
Follow this template:
# {Title}
## Symptom
{Observable behavior - what the user sees}
## Root Cause
{Technical explanation with code references}
## Fix
{Concrete solution - what to change}
## Prevention Checklist
- [ ] {Action item 1}
- [ ] {Action item 2}
## Related
- {Source file path}: {relevant code or setting}
Edit ${CLAUDE_PLUGIN_ROOT}/docs/{package}/pitfalls.md:
| {Symptom} | {Cause} | {Solution} | [Details](./pitfalls/{issue-name}.md) |
Report to the user what was recorded:
If the debugging session revealed a useful pattern (not just a bug):
${CLAUDE_PLUGIN_ROOT}/docs/{package}/patterns.mdIf a pitfall is found for a package not yet tracked:
${CLAUDE_PLUGIN_ROOT}/docs/{new-package}/
├── patterns.md
├── pitfalls.md
└── pitfalls/
pitfalls.md with this structure:
# {Package} Pitfalls
## Development Checklist
Check before writing code:
- [ ] {First checklist item from the discovery}
## Troubleshooting by Symptom
| Symptom | Cause | Solution | Details |
|---------|-------|----------|---------|
patterns.md with a package overview section${CLAUDE_PLUGIN_ROOT}/skills/lookup/SKILL.md: