knowledge
Project Cortex - Structural Knowledge Injection for LLM
When & Why to Use This Skill
Project Cortex is a specialized Claude skill designed for Structural Knowledge Injection, enabling LLMs to internalize and apply project-specific rules, coding standards, and architectural decisions. It acts as a sophisticated context layer that ensures AI-generated outputs remain consistent with organizational guidelines, technical documentation, and established workflows, significantly reducing hallucinations and compliance errors in professional development environments.
Use Cases
- Enforcing Coding Standards: Automatically retrieve and apply language-specific conventions and project rules when generating or reviewing code to ensure consistency across the codebase.
- Context-Aware Version Control: Streamline the git commit process by analyzing development context and active guardrails to generate formatted, compliant commit messages.
- Architectural Q&A: Serve as an intelligent interface for technical documentation, allowing developers to query complex architecture decisions and receive synthesized, source-referenced answers.
- Automated Documentation Alignment: Ensure all technical writing adheres to specific style guides and structural requirements by pre-loading writing memory and linting rules before content creation.
- Workflow Guardrails: Prevent anti-patterns by enforcing mandatory context checks and memory loading before the agent executes critical development or documentation tasks.
| name | "knowledge" |
|---|---|
| version | "1.0.0" |
| description | "Project Cortex - Structural Knowledge Injection for LLM" |
| authors | ["omni-dev-fusion"] |
Knowledge Skill Policy
Router Logic
Scenario 1: User asks to "commit", "save", or "finish"
- Observe: Call
get_development_context() - Analyze: Extract commit types, scopes, and active guardrails
- Execute: Use
gitskill to commit (if Client lacks git) - Verify: Ensure message follows format
Scenario 2: User asks "how do I...", "what is...", "explain..."
- Analyze: Identify topic from user question
- Search: Call
consult_architecture_doc(topic) - Synthesize: Summarize relevant information
- Respond: Provide concise answer with source references
Scenario 3: User asks to write documentation
- Prepare: Call
get_writing_memory()FIRST - Follow: Apply writing style rules
- Polish: Use
writerskill for linting
Scenario 4: User asks to write code (Python, Nix, etc.)
- Standards: Call
get_language_standards(lang) - Context: Call
get_development_context() - Execute: Use appropriate skill (python, terminal, etc.)
Workflow: Commit Flow
User: commit
Claude:
1. get_development_context() → {scopes: ["mcp", "core"], guardrails: ["vale"]}
2. Generate message following format: "type(scope): description"
3. Warn user about guardrails if applicable
4. Execute git_commit
Workflow: Documentation Flow
User: write docs for feature X
Claude:
1. get_writing_memory() → Load writing rules
2. consult_architecture_doc("documentation") → Get doc structure
3. Write document following rules
4. Run vale check if available
Anti-Patterns
- Don't use knowledge tools as execution shortcuts
- Don't skip loading writing memory before documentation
- Don't ignore guardrails returned by
get_development_context()