This is the control hub for Project Kernel. Start here when you want to understand how the modules, packs, examples, scripts, and documentation fit together.
README.mdfor the project pitch, quick start, and adoption paths.docs/overview.mdfor the system model.modules/README.mdfor the reusable building blocks.packs/README.mdfor curated drag-and-drop combinations.examples/README.mdfor concrete usage scenarios.
Project Kernel
|-- Modules: reusable primitives
| |-- foundation: rules, standards, architecture, quality
| |-- docs: templates for project documentation
| |-- memory: continuity and decision tracking
| |-- skills: reusable operating procedures
| |-- workflow: planning, build, review, release, maintenance
| \-- philosophy: principles that shape the work
|-- Packs: curated module combinations
|-- Examples: concrete seeded-project patterns
\-- Scripts: optional helpers for copying and validation
Use this when you need just enough structure to keep a new repo from drifting.
packs/minimal-starter- Best for prototypes, experiments, and small tools.
Use this when the project needs documentation and continuity from the beginning.
packs/documented-starter- Best for real apps, libraries, and durable solo projects.
Use this when a project will outlive one session or one person.
packs/solo-dev-ospacks/team-handoff-packpacks/ai-builder-pack- Best for maintainable products, team work, open-source launches, and AI-assisted development.
The modules are independent but stronger together:
- Foundation defines the rules.
- Docs explain the project to humans.
- Memory preserves context between sessions.
- Skills provide reusable ways to solve recurring work.
- Workflow turns good habits into repeatable loops.
- Philosophy keeps the system opinionated instead of mechanical.
If you only copy three folders, copy these:
modules/foundation/
modules/docs/
modules/memory/
That gives a project rules layer, public-facing documentation, and private working continuity.
Use this rhythm inside projects seeded with Project Kernel:
- At project start: fill foundation, setup, goals, assumptions, and README.
- Before implementation: update current state and planning workflow.
- During implementation: write decisions when tradeoffs appear.
- Before merge or release: run the review skill and definition of done.
- After meaningful work: update session notes, known issues, and changelog.
Project Kernel is designed to grow through:
- stack-specific packs
- domain-specific skills
- team policy modules
- release checklists
- AI assistant rule files
- examples that show the system in real repos