Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
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.
Imported from michael-denyer/pstack-claude (plugins/pstack/skills/principle-redesign-from-first-principles/SKILL.md). Install upstream with npx skills add michael-denyer/pstack-claude --skill principle-redesign-from-first-principles. Copyright stays with the author.
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.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "michael-denyer-pstack-claude-principle-redesign-from-fir-02369f",
"kind": "skill",
"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.",
"publisher": "michael-denyer",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"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."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/michael-denyer/pstack-claude",
"path": "plugins/pstack/skills/principle-redesign-from-first-principles/SKILL.md",
"ref": "HEAD",
"url": "https://github.com/michael-denyer/pstack-claude/blob/HEAD/plugins/pstack/skills/principle-redesign-from-first-principles/SKILL.md",
"key": "michael-denyer/pstack-claude/plugins/pstack/skills/principle-redesign-from-first-principles/SKILL.md"
}
},
"instructions": "# Redesign From First Principles\n\nWhen integrating a change, don't bolt it onto the existing design. Redesign as if the requirement had been there from the start.\n\n- Read all affected files and understand the current design\n- Ask: \"if we were writing this from scratch with this new requirement, what would we build?\"\n- Propagate the change through every reference: types, docs, examples, rationale sections\n- Think about the whole redesign, then deliver it incrementally\n\nThis is the method for preserving option value when integrating changes into an existing design.",
"cost": {
"context_tokens": 142
}
}
Fetch it by URL: GET /api/v1/registry/michael-denyer-pstack-claude-principle-redesign-from-fir-02369f/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
