ワンクリックで
plan
Plan the implementation of a new Inertia bundle feature before writing any code. Creates a detailed implementation plan.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Plan the implementation of a new Inertia bundle feature before writing any code. Creates a detailed implementation plan.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run a complete code review of the Inertia bundle. Checks protocol compliance and Symfony bundle conventions via static analysis (no automated tools).
Complete PHP API reference for all Inertia.js v3 prop types (optional/lazy, always, defer, once, merge, deepMerge, scroll). Auto-loaded when working on Props/, Service/Inertia.php, or InertiaResponse.php.
Complete reference for the Inertia.js v3 server-side protocol. Auto-loaded when working on InertiaResponse, InertiaListener, Inertia service, or any HTTP response handling.
Start a TDD cycle for a new Inertia bundle feature or bug fix. Write the test first, then implement.
Reference patterns for creating Symfony 6.4+ reusable bundles using AbstractBundle. Auto-loaded when working on InertiaBundle.php, config/definition.php, config/services.yaml, or any DI configuration.
| name | plan |
| description | Plan the implementation of a new Inertia bundle feature before writing any code. Creates a detailed implementation plan. |
| argument-hint | <feature-description> |
$ARGUMENTS
Load .claude/skills/inertia-protocol/SKILL.md and identify which protocol behaviors are involved.
Read /home/tony/Documents/tony/inertia-laravel to see how the same feature is handled in the Laravel bundle. Use it as a reference for expected behavior and conventions.
Explore relevant files in src/ to understand the current state.
The plan must include:
Files to create (with their purpose):
src/NewClass.php — Description of responsibility
tests/Unit/... — Unit tests for NewClass
tests/Functional/... — Protocol compliance tests
Files to modify (with what changes):
src/ExistingClass.php — Add method X, modify method Y
config/services.yaml — Register new service
config/definition.php — Add new config option if needed
Implementation order (TDD sequence):
Protocol compliance checklist:
Risks / open questions:
Do NOT start implementing. Present the plan and wait for approval.
If the plan is approved, use /tdd to implement step by step.