Cavekit Writing

Core Principle: Kits Describe WHAT, Not HOW

Kits are implementation-agnostic. They define what the system must do and how to verify it, but never prescribe a specific framework, language, or architecture.

This is the fundamental distinction in Cavekit:

• Kits = WHAT must be true (framework-agnostic, durable, portable)
• Plans = HOW to build it (framework-specific, derived from kits)
• Code = the implementation (generated from plans, validated against kits)

Why Implementation-Agnostic?

When kits avoid prescribing HOW, they become:

• Portable — the same kits can drive implementations in different frameworks
• Durable — kits survive technology migrations
• Testable — acceptance criteria are about behavior, not implementation details
• Reusable — the same kits work for greenfield, rewrites, and cross-framework evaluation