Domain-specific patterns that guide KB content decisions. Co-evolved by humans and LLMs during the training period and beyond.
Folder taxonomy
The top-level folders answer four questions:
| Folder | Question | Examples |
|---|---|---|
company/ | Who are we? | Values, org structure, communication norms |
process/ | How do we plan? | User stories, estimation, backlog management |
engineering/ | How do we build? | Code review, PRs, placeholders, Shopify guides |
training/ | How do we learn? | Reading lists, curricula, ramp-up paths |
When deciding where a page belongs, ask: “Is this about planning work or doing
work?” Planning goes in process/. Doing goes in engineering/.
Subfolders
Add a subfolder when grouping pages by domain makes the structure clearer. Name it after the domain, not the document type.
Page naming
Filenames should name the topic, not the document type. The folder and
frontmatter type already carry that metadata.
code-review.mdnotcode-review-guidelines.mdcore-skills.mdnotcore-skills-training.mdbundles.mdnotshopify-bundles-entity.md