principle-redesign-from-first-principles

Name: principle-redesign-from-first-principles
Availability: InStock
Author: squidllee

Redesigns existing systems holistically when integrating new requirements instead of bolting them on.

Updated Aug 22, 2026

Search Tags:#architecture #code review #refactoring #software design #requirements #first principles #redesign

Ready to run

npx skills add https://github.com/squidllee/skills --skill principle-redesign-from-first-principles-squidllee

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: principle-redesign-from-first-principles
Source: https://github.com/squidllee/skills/tree/main/principle-redesign-from-first-principles
Command: npx skills add https://github.com/squidllee/skills --skill principle-redesign-from-first-principles-squidllee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a new requirement arrives, teams often bolt it onto an existing design, creating inconsistency and technical debt. This Skill guides the AI to redesign the affected system as if the requirement had been a foundational assumption from day one. ## Core Features & Use Cases - Holistic Design Review: Reads all affected files to understand the current design before proposing changes. - First-Principles Redesign: Asks what the system would look like if built from scratch with the new requirement included. - Complete Propagation: Updates every reference including types, docs, examples, and rationale sections. - Use Case: When adding multi-tenancy to an existing application, use this Skill to rethink the data model and API design as if multi-tenancy had been required from day one, then deliver the redesign incrementally. ## Quick Start Ask the AI to integrate a new requirement into your existing design by redesigning from first principles rather than patching it on.

Frequently Asked Questions about principle-redesign-from-first-principles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I integrate a new requirement into an existing design?▼

Read all affected files to understand the current design, then ask what you would build from scratch if the requirement existed from day one. Propagate the change through every reference including types, docs, and examples, and deliver the redesign incrementally.

What is redesign from first principles in software engineering?▼

It is a design method where you treat a new requirement as a foundational assumption and rethink the system as if building it from scratch. The goal is a coherent result rather than a patch bolted onto the existing structure.

When should I redesign instead of patching an existing feature?▼

Redesign when a new requirement conflicts with core assumptions of the current design, such as data models or API structure. Patching works for superficial changes, but foundational shifts need holistic rethinking to avoid accumulating inconsistency.

How do I deliver a large redesign without breaking everything?▼

Think about the redesign holistically first, then deliver it incrementally in small, reviewable steps. Propagate changes through all references including types, documentation, and examples so each increment stays consistent.

What are the limitations of first-principles redesign?▼

It requires reading and understanding all affected files, which takes more upfront effort than a quick patch. For trivial or isolated changes, a full redesign may be unnecessary overhead.