package-guide-lookup

Package Guide Lookup

Provide package-specific patterns and pitfalls from the project's accumulated knowledge base.

Available Packages

Package	Description	Status
soap	Scriptable Object Architecture Pattern	Active
feel	MMFeedbacks feedback system	Planned
dotween	Tween animation	Planned

Lookup Procedure

When activated with a package context:

1. Identify which package is relevant from the conversation context
2. Read the pitfalls index: ${CLAUDE_PLUGIN_ROOT}/docs/{package}/pitfalls.md
3. Match the user's symptom against the troubleshooting table
4. If a symptom matches, read the linked detail file: ${CLAUDE_PLUGIN_ROOT}/docs/{package}/pitfalls/{issue-name}.md
5. Read patterns file if writing new code: ${CLAUDE_PLUGIN_ROOT}/docs/{package}/patterns.md

When a package has "Planned" status and no docs exist:

• Inform the user that documentation is not yet available for that package
• Suggest using the package-guide-learn skill to begin recording findings

When activated without specific package context:

• Display the available packages table above

Output Format

Present relevant information to the user:

• Debugging: Show matching troubleshooting rows and code snippets from detail files
• Writing code: Show relevant checklist items and pattern examples
• Cite the source file path for traceability

File Structure

Each package follows this documentation structure:

docs/{package}/
├── patterns.md           # Usage patterns and best practices
├── pitfalls.md           # Checklist + troubleshooting table
└── pitfalls/
    └── {issue-name}.md   # Detailed root cause analysis per issue

Priority

When multiple packages could be relevant, read each package's pitfalls.md checklist first before loading patterns. Preventing known issues is more valuable than applying patterns.