Claude Skill

principle-redesign-from-first-principles

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.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download michael-denyer-pstack-claude-plugins_pstack_skills_principle-redesign-from-first-principles-4b3933e.zip · 0 KB
Part of michael-denyer/pstack-claude — 51 skills

Install

skills CLI npx skills add https://github.com/michael-denyer/pstack-claude/tree/main/plugins/pstack/skills/principle-redesign-from-first-principles
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install michael-denyer-pstack-claude@llmmart
Git git clone https://github.com/michael-denyer/pstack-claude.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole michael-denyer/pstack-claude collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.

  • Read all affected files and understand the current design
  • 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 whole redesign, then deliver it incrementally

This is the method for preserving option value when integrating changes into an existing design.

Files (pstack-claude)
  • SKILL.md 835 B
    ---
    name: principle-redesign-from-first-principles
    description: "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."
    user-invocable: false
    ---
    
    # 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.
    
    - Read all affected files and understand the current design
    - 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 whole redesign, then deliver it incrementally
    
    This is the method for preserving option value when integrating changes into an existing design.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related