patchwork

What problem does it solve?

Without guardrails, teams risk losing code intent, inconsistent terminology, and costly rework as code evolves. Patchwork keeps context anchored next to work so the agent maintains alignment with project standards.

Core Features & Use Cases

• CONTEXT.md capsule rules: place a CONTEXT.md at the project root and read capsule boundaries before editing to preserve domain terms and intent.
• Entry contract discipline: exports and signatures are surfaced through a defined entry point to prevent API drift.
• WHY comments and change-scope controls: document rationale and constrain edits to guard rails.
• Automatic capsule injection: inject ancestor CONTEXT.md chains for context continuity during tool-assisted tasks.
• Tooling guidance: aligns with MCP search/read_context and the context-doctor to keep capsules healthy.

Quick Start

Create a CONTEXT.md at the capsule root and start applying the patchwork guardrails for all code tasks.