---
name: Knowledge Priming
slug: knowledge-priming
category: AI Engineering
description: Knowledge Priming loads project-specific context like tech stack, architecture, directory layout, trusted sources, and conventions before other skills run. Use it when a knowledge base exists or when asking what the project uses and how it is organized.
github: "https://github.com/techygarg/lattice/tree/main/skills/knowledge-priming"
language: Shell
stars: 185
forks: 13
install: "npx degit https://github.com/techygarg/lattice/tree/main/skills/knowledge-priming ~/.claude/skills/knowledge-priming"
installs_to: ~/.claude/skills/knowledge-priming
source_path: skills/knowledge-priming/SKILL.md
collection_size: 25
category_size: 3278
collection_url: "https://dirskills.com/collections/techygarg/lattice"
added: 2026-09-06T05:20:44.320Z
last_synced: 2026-09-06T05:20:44.320Z
canonical_url: "https://dirskills.com/skills/knowledge-priming"
---

# Knowledge Priming

Knowledge Priming loads project-specific context like tech stack, architecture, directory layout, trusted sources, and conventions before other skills run. Use it when a knowledge base exists or when asking what the project uses and how it is organized.

**Install:**

```bash
npx degit https://github.com/techygarg/lattice/tree/main/skills/knowledge-priming ~/.claude/skills/knowledge-priming
```

## README

# Knowledge Priming

## Config Resolution

1. Look for `.lattice/config.yaml` in the repo root.
2. If found, check `paths.knowledge_base` for a custom document path.
3. If a document exists at that path, read the full document.
4. **STOP: Apply the loaded document as ambient context before any design, implementation, or review work begins.**
5. If a path is configured but no document exists at it → tell the user which configured path is missing, then see "When No Document Exists".
6. If there is no config file or no `paths.knowledge_base` key → see "When No Document Exists".

## When No Document Exists

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** — a guided interview (~10 questions) producing a concise document (~50 lines).
>
> You can also create `.lattice/standards/knowledge-base.md` manually and reference it in `.lattice/config.yaml` under `paths.knowledge_base`.

Do not block. Continue without the knowledge base.

## What the Document Contains

| # | 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 |

## Scope Boundary

| 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?"*