Stats
Actions
Tags
From lattice
Loads project-specific context from a knowledge base document to inform all skills about the project's tech stack, architecture, and conventions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/lattice:knowledge-primingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Look for `.lattice/config.yaml` in repo root.
.lattice/config.yaml in repo root.paths.knowledge_base for custom doc path.Inform the user:
No project knowledge base found. AI skills will operate from generic assumptions about tech stack, architecture, and conventions.
To create one, trigger knowledge-priming-refiner — guided interview (~10 questions) producing a concise document (~50 lines).
Can also create
.lattice/standards/knowledge-base.mdmanually and reference in.lattice/config.yamlunderpaths.knowledge_base.
Do not block. Continue without knowledge base.
| # | Section | What It Captures |
|---|---|---|
| 1 | Architecture Overview | App type, major components, how they interact |
| 2 | Tech Stack and Versions | Specific technologies with version numbers, including "not X" clarifications |
| 3 | Curated Knowledge Sources | Official docs, trusted blogs, internal references (5–10 max) |
| 4 | Project Structure | Directory layout showing where things live |
| 5 | Project Conventions | Project-specific conventions other skills cannot infer from code |
| Concern | Owned By |
|---|---|
| Coding style, naming principles, function design | clean-code atom |
| Architectural layers, dependency direction | architecture atom |
| Domain modeling, aggregate design | domain-driven-design atom |
| Input validation, injection prevention | secure-coding atom |
| Test structure, assertion quality | test-quality atom |
Knowledge priming answers "what are we working with?" — not "how should we write?"
npx claudepluginhub techygarg/lattice --plugin latticeCreates a project-specific knowledge base document that primes AI with the project's tech stack, architecture, trusted sources, and structure. Triggered by phrases like 'set up knowledge base'.
Scans codebase to auto-generate CLAUDE.md project config and .rune/ state files for full context in AI coding sessions. Use on new repos or missing/stale context.
Analyzes project structure, tech stack, test frameworks, code conventions, and architecture to generate a compact context file for downstream dev-* skills.