Laravel template: Boost repositories and repositories without a Node build #9
Loading…
Reference in a new issue
No description provided.
Delete branch "laravel-boost-and-no-node"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The dcfcymru room installed repo-map in dcfCymru (James/dcfCymru#144) and sent back 4 findings. All 4 are about Laravel repositories that do not look like the one the template was written for: dcfCymru uses Laravel Boost, has no Node build, and keeps Welsh in
_enand_cydatabase columns rather thanlang/.Changes
<laravel-boost-guidelines>block in both CLAUDE.md and AGENTS.md.php artisan boost:updaterewrites only that block, so anything put inside it would be lost on the next update.resources/jsandlang/lines carry a{{DELETE ...}}placeholder. Before, a room had to work out for itself that they could go, and a wrong line in CLAUDE.md sends every later session looking for files that do not exist.node_modules/,public/build/andpublic/hotonly apply with a Node build, so a room does not add ignore rules for folders it will never have..agents/. Boost copies.claude/skillsthere, so the layout listed the skills twice.Checks
node --test: 3 tests pass..claude/skillsand.agents/skillsnow maps.claude/and leaves out.agents/.Recorded on omp-matrix-bot#27.