principle-redesign-from-first-principles

Redesigns existing systems as if new requirements were foundational assumptions from the start.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/jeremybrasher/grokbot-skills --skill principle-redesign-from-first-principles-jeremybrasher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principle-redesign-from-first-principles
Source: https://github.com/jeremybrasher/grokbot-skills/tree/main/collections/pstack/skills/principle-redesign-from-first-principles
Command: npx skills add https://github.com/jeremybrasher/grokbot-skills --skill principle-redesign-from-first-principles-jeremybrasher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a new requirement arrives, teams often bolt it onto an existing design, creating fragile patches and accumulated complexity. This Skill guides you to redesign the affected system as if the requirement had been present from day one, preserving architectural coherence and option value. ## Core Features & Use Cases - First-Principles Redesign: Re-examines the current design and asks what you would build from scratch with the new requirement included. - Full Propagation: Spreads the change through every reference, including types, docs, examples, and rationale sections. - Guarded Execution: Requires concrete intake evidence before acting, returns a HOLD instead of guessing when inputs are missing, and defaults to the smallest structural change. - Use Case: A new permission model must be added to an existing API. Instead of layering checks onto current endpoints, the Skill walks you through redesigning the authorization layer as if permissions were a founding constraint, then delivering the redesign incrementally. ## Quick Start Apply the redesign-from-first-principles method to integrate this new requirement into my existing design instead of bolting 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 without breaking an existing design?▼

Redesign as if the requirement had existed from the start instead of bolting it on. Read all affected files, ask what you would build from scratch with the requirement included, propagate the change through types, docs, and examples, then deliver incrementally.

What is redesign from first principles in software engineering?▼

It is a design method where a new requirement is treated as a foundational assumption rather than an add-on. You re-derive the design around it, preserving option value and avoiding patchwork architecture that accumulates over successive changes.

When should I not use first-principles redesign?▼

Avoid it when the trigger is not met, when a narrower operational skill covers the same decision, or when you would only cite the principle without changing any choice. The Skill explicitly holds rather than producing decorative citations.

What happens if required context is missing during a redesign?▼

The Skill returns a HOLD naming the missing input instead of guessing. It requires a concrete situation object, evidence the trigger fires, and a decision the principle would change before proceeding.

Does first-principles redesign mean rewriting the whole system?▼

No. The Skill defaults to the smallest structural change the principle demands and refuses full rewrites when a local application suffices. Expansion requires evidence from the request or the observed system.