2eae6ad21a
The plugin had hardcoded references to 'CORA' (Every's internal project) throughout the documentation workflow, making it project-specific rather than generic. This affected users trying to use the plugin on non-CORA projects. Changes: - Replace 'cora-critical-patterns.md' with 'critical-patterns.md' - Replace 'Which CORA module' with 'Which module or component' - Replace 'CORA-Specific Resources' with 'Project-Specific Resources' - Replace 'CORA-MODULES.md' with 'modules documentation' - Replace 'CORA system' with 'System-wide' in templates - Update cora-test-reviewer description to be generic Files modified: - learnings-researcher.md: Fixed critical patterns file reference - compound-docs/SKILL.md: Removed module and filename hardcoding - compound-docs/assets/*.md: Generalized template references - workflows/compound.md: Changed 'CORA schema' to 'solution schema' - workflows/work.md: Made test reviewer description generic This makes the plugin truly project-agnostic as advertised.
875 B
875 B
Critical Pattern Template
Use this template when adding a pattern to docs/solutions/patterns/critical-patterns.md:
N. [Pattern Name] (ALWAYS REQUIRED)
❌ WRONG ([Will cause X error])
[code showing wrong approach]
✅ CORRECT
[code showing correct approach]
Why: [Technical explanation of why this is required]
Placement/Context: [When this applies]
Documented in: docs/solutions/[category]/[filename].md
Instructions:
- Replace N with the next pattern number
- Replace [Pattern Name] with descriptive title
- Fill in WRONG example with code that causes the problem
- Fill in CORRECT example with the solution
- Explain the technical reason in "Why"
- Clarify when this pattern applies in "Placement/Context"
- Link to the full troubleshooting doc where this was originally solved