implement-design

To implement design-driven code without drift, translate an approved design document into production-ready code using strict design conformance checks, test-driven development, and pre-commit hooks to guard against deviations from intended architecture.

The three-tier testing approach mandates writing failing tests before coding across unit, integration, and e2e layers. This test-first workflow guides implementation and ensures comprehensive test scaffolding aligned with production workflows.

Yes, you can use FCIS architecture patterns with test-driven development. The approach promotes Functional Core and Imperative Shell organization to structure code, ensuring disciplined implementation while maintaining strict design doc compliance.

To enforce pre-commit hooks are green, write a failing test first, then implement the code and verify all pre-commit hooks pass prior to commit. This disciplined workflow ensures design conformance and test validation before changes are committed.

The best way to scaffold unit, integration, and e2e tests is through a three-tier testing approach. Mandate a test-first workflow by writing failing tests before coding to guide implementation and ensure production-ready code meets design document specifications.