principle-redesign-from-first-principles

Read all affected files to understand the current design holistically, then ask what you would build from scratch with the new requirement included. Propagate the change through every reference including types, docs, and examples, delivering the redesign incrementally.

Redesign from first principles means treating a new requirement as if it had been a foundational assumption from day one, rather than bolting it onto the existing design. The result should look like what the team would have built originally with full knowledge.

Redesign when a new requirement conflicts with core assumptions of the current design, such as adding multi-tenancy to a single-tenant system. Patching works for peripheral changes, but foundational shifts need holistic redesign to preserve option value.

No, the redesign is thought about holistically but delivered incrementally. Only the affected files and references are reworked, with changes propagated through types, documentation, examples, and rationale sections as needed.

It requires reading and understanding all affected files upfront, which takes more effort than a quick patch. It is also unnecessary for small, peripheral changes that do not challenge the existing design's core assumptions.