Modules are the reusable primitives of Project Kernel. Each folder can be copied into a project on its own, and each includes a START-HERE.md file that explains how to use it.
| Module | Purpose |
|---|---|
foundation |
Project rules, standards, architecture preferences, setup checklist, and definition of done |
docs |
README, architecture, roadmap, changelog, setup, FAQ, and contributing templates |
memory |
Context, current state, decisions, assumptions, priorities, issues, and session notes |
skills |
Reusable operating procedures for debugging, review, testing, refactoring, shipping, and AI collaboration |
workflow |
Planning, implementation, review, release, triage, documentation, and maintenance loops |
philosophy |
Principles for clarity, maintainability, continuity, abstraction, and product thinking |
- Copy the module folder into your project.
- Open its
START-HERE.md. - Fill in the most important placeholders first.
- Link the module from your main project README.
- Keep the files current as the project changes.
- A module should be useful without the rest of Project Kernel.
- A module should tell the user what to read first.
- A module should produce decisions, standards, or working context.
- A module should avoid generic filler.
- A module should link to adjacent modules when they become useful.