principle-redesign-from-first-principles

Solid

Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.

AI & Automation 122 stars 8 forks Updated today MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
70
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
33
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Redesign From First Principles When integrating a change, don't bolt it onto the existing design. Redesign as if the requirement had been there from the start. The result should look like what we would have built if we'd known on day one. - Read all affected files and understand the current design holistically - Ask: "if we were writing this from scratch with this new requirement, what would we build?" - Propagate the change through every reference: types, docs, examples, rationale sections - Think about the redesign holistically, then deliver it incrementally This is the method for preserving option value when integrating changes into an existing design.

Details

Author
Sma1lboy
Repository
Sma1lboy/rove
Created
4 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category