You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The package is named 'Laravel + Claude Code configured to work together' but currently ships zero.claude/ assets — the Claude integration is the CLAUDE.md stub, docs/standards/, and two workflow stubs.
Meanwhile the first-party ecosystem has moved: Laravel Boost ships an MCP server (docs search, Tinker, DB schema, browser logs) plus AI guidelines, and laravel/mcp makes building app-specific MCP servers trivial. We should not compete with Boost — we should compose with it.
Proposed direction (not committing yet, this is a capture):
Ship .claude/ stubs — starting with the /commit CDR command from Conversation Decision Records (CDRs) — persisting the 'why' alongside code #43 (fully specced there), plus a project settings.json with a sensible permission allowlist (vendor/bin/pint, php artisan test, vendor/bin/pest, etc.). This is cheap and immediately differentiating.
Recommend/require Laravel Boost in the installer rather than building our own MCP — claudavel:install could composer-require boost and wire its guidelines alongside our docs/standards/.
Skills over commands where the content is guidance rather than a workflow (current convention: .claude/skills/<name>/SKILL.md).
Longer-term: if the app being scaffolded wants to expose its own MCP tools, point at laravel/mcp in the docs — again, compose, don't build.
Related: #43 (CDR /commit command — the natural first shipped asset).
The package is named 'Laravel + Claude Code configured to work together' but currently ships zero
.claude/assets — the Claude integration is the CLAUDE.md stub,docs/standards/, and two workflow stubs.Meanwhile the first-party ecosystem has moved: Laravel Boost ships an MCP server (docs search, Tinker, DB schema, browser logs) plus AI guidelines, and laravel/mcp makes building app-specific MCP servers trivial. We should not compete with Boost — we should compose with it.
Proposed direction (not committing yet, this is a capture):
.claude/stubs — starting with the/commitCDR command from Conversation Decision Records (CDRs) — persisting the 'why' alongside code #43 (fully specced there), plus a projectsettings.jsonwith a sensible permission allowlist (vendor/bin/pint,php artisan test,vendor/bin/pest, etc.). This is cheap and immediately differentiating.claudavel:installcould composer-require boost and wire its guidelines alongside ourdocs/standards/..claude/skills/<name>/SKILL.md).laravel/mcpin the docs — again, compose, don't build.Related: #43 (CDR /commit command — the natural first shipped asset).