michael-denyer/pstack-claude

principle-redesign-from-first-principles

Apply when integrating a new requirement into an existing design.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/michael-denyer/pstack-claude --skill principle-redesign-from-first-principles

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Redesign From First Principles

When integrating a change, don't bolt it onto the existing design. Redesign as if the requirement had been a foundational assumption 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.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
michael-denyer
コミュニティ

architect

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.

1時間の導入数
1
GitHub Stars
3969
更新日
11月4日
michael-denyer
コミュニティ

babysit

Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.

1時間の導入数
1
GitHub Stars
3969
更新日
11月4日
michael-denyer
コミュニティ

benchmark-checklist

Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.

1時間の導入数
1
GitHub Stars
3969
更新日
11月4日
michael-denyer
コミュニティ

blast-radius

Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief that asserts something about existing code ('make X public', 'X already handles Y') before you design against that assertion.

1時間の導入数
1
GitHub Stars
3969
更新日
11月4日