starter-kit-upgrade

Name: starter-kit-upgrade
Author: laravel

670stars28forks

How to install starter-kit-upgrade?

laravel/agent-skills/starter-kit-upgrade

$npx -y skills add laravel/agent-skills --skill starter-kit-upgrade

Installs into the current project.

Summary

Selectively pull upstream improvements from a Laravel starter kit (laravel/vue-starter-kit, laravel/react-starter-kit, laravel/svelte-starter-kit, laravel/livewire-starter-kit) into a project bootstrapped from one. Use when the user wants to update, sync, or migrate features from

Files · 1

View on GitHub

SKILL.md

1	# Laravel Starter Kit Upgrade
2
3	- Users bootstrap from `laravel/vue-starter-kit`, `react-starter-kit`, `svelte-starter-kit`, or `livewire-starter-kit`, then customize. They own the code.
4	- We pick specific features from upstream (e.g. "toast notifications", "2FA autofocus fix"), not "version upgrades."
5	- The user's git history is unrelated to the kit's. There is no common ancestor. We compare user-now vs upstream-now, byte by byte.
6	- We never auto-merge a customized file. Customizations are surfaced; the user decides.
7	- Behavior preservation is the contract: the user's currently-passing tests/typecheck/build must still pass after.
8
9	## Safety contract: non-negotiable
10
11	Read these to the user before any side effects, and live by them throughout:
12
13	1. Working tree must be clean. If `git status --porcelain` is non-empty, refuse and tell the user to commit or stash. Do not "stash for them."
14	2. All work happens on a dedicated branch (`starter-kit-upgrade/<short-id>`). The user's current branch is never modified.
15	3. Each applied feature is its own commit. That is how revertability works.
16	4. Never auto-resolve conflicts. A change touching customized code is surfaced; default action is to skip the file.
17	5. Never silently overwrite manifests or lockfiles (`composer.json`, `package.json`, `-lock.`). Show diffs; let the user decide.
18	6. Verify behavior preservation. Re-run the user's tests/typecheck/build after applying. A previously-passing check that now fails is a regression. Stop, surface, recommend revert.
19	7. Detect from unambiguous signals; ask when ambiguous. Concrete evidence (e.g. `config/fortify.php` exists) is fine. Picking a likely answer when signals are mixed or absent is not.
20
21	If any of these is violated, abort with a clear message about what went wrong and how to recover.
22
23	## Required tools
24
25	- `git` (in the user's project)
26	- `gh` (authenticated; `gh auth status` returns OK)
27	- `jq` (used by `run_tests.sh`)
28	- `bash` (for the bundled scripts)
29
30	If any is missing, stop in Phase 4 and tell the user how to install.
31
32	## Gotchas
33
34	Environment-specific behavior the agent will get wrong without being told. Read these before starting the workflow and apply throughout.
35
36	- Parallel implementations. When a feature has `new` files plus `differs` to call sites, the user may already have an in-house equivalent (their own toast helper, validation rule, etc.). Surface as a whole; don't apply the `new` files in isolation as if they're "safe." Default action is to skip the entire feature; the user can opt to adopt upstream's version and remove theirs later.
37
38	- Renamed paths. If a `new` path's basename or class name already exists elsewhere in the user's repo, the user has likely renamed/moved it. Surface, don't auto-apply, or you'll create a duplicate. Show them the upstream change and let them apply it to their renamed file by hand or wait for user confirmation.
39
40	- Later upstream edits. Copying upstream HEAD pulls in _every_ commit since the feature, not just the feature's own changes. Always run the Phase 5 step 2 check before applying. When later edits exist, scope to `<sha>:<path>` instead of `HEAD:<path>`.
41
42	- Transitive imports. New files often `import` from helpers that are NOT in the same feature commit (Vue/React/Svelte: `@/lib/...`, `@/components/...`; Livewire: `@include`, `<x-...>`, `<livewire:...>`). Phase 5 step 4 covers the scan; never declare a feature applied without it. Uncovered imports show up as runtime/compile errors.
43
44	- Lockfile drift. Manifests are user-curated. Never overwrite. Walk the user through the upstream diff, let them merge, then regenerate lockfiles via the package manager (Phase 6).
45
46	- Stale node_modules after major bumps. After Vite v7 → v8, React 18 → 19, etc., `npm install` often fails with `ERESOLVE`. Clean and reinstall (Phase 6).
47
48	- New migrations. When upstream adds migrations (e.g. "Catch migrations up to Skeleton"), surface them separately. Recommend `php artisan migrate:status` first; applying a new migration on a populated DB can fail loudly.
49
50	- Major framework bumps as features. Things like Laravel 12 → 13, Livewire 3 → 4, or Inertia v2 → v3 are too large and too breaking for the feature-by-feature flow. Do not attempt them through this skill. Instead, prompt the user to run the corresponding [Laravel Boost](https://github.com/laravel/boost) MCP slash command first, then come back and re-run this skill against the resulting (clean-tree) repo. If Boost is not yet installed: `composer require laravel/boost --dev && php

People who liked this also viewed

6 picks

Type

starter-kit-upgrade

670stars28forks

View on GitHub

How to install starter-kit-upgrade?

laravel/agent-skills/starter-kit-upgrade

$npx -y skills add laravel/agent-skills --skill starter-kit-upgrade

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Laravel Starter Kit Upgrade
2
3	- Users bootstrap from `laravel/vue-starter-kit`, `react-starter-kit`, `svelte-starter-kit`, or `livewire-starter-kit`, then customize. They own the code.
4	- We pick specific features from upstream (e.g. "toast notifications", "2FA autofocus fix"), not "version upgrades."
5	- The user's git history is unrelated to the kit's. There is no common ancestor. We compare user-now vs upstream-now, byte by byte.
6	- We never auto-merge a customized file. Customizations are surfaced; the user decides.
7	- Behavior preservation is the contract: the user's currently-passing tests/typecheck/build must still pass after.
8
9	## Safety contract: non-negotiable
10
11	Read these to the user before any side effects, and live by them throughout:
12
13	1. Working tree must be clean. If `git status --porcelain` is non-empty, refuse and tell the user to commit or stash. Do not "stash for them."
14	2. All work happens on a dedicated branch (`starter-kit-upgrade/<short-id>`). The user's current branch is never modified.
15	3. Each applied feature is its own commit. That is how revertability works.
16	4. Never auto-resolve conflicts. A change touching customized code is surfaced; default action is to skip the file.
17	5. Never silently overwrite manifests or lockfiles (`composer.json`, `package.json`, `-lock.`). Show diffs; let the user decide.
18	6. Verify behavior preservation. Re-run the user's tests/typecheck/build after applying. A previously-passing check that now fails is a regression. Stop, surface, recommend revert.
19	7. Detect from unambiguous signals; ask when ambiguous. Concrete evidence (e.g. `config/fortify.php` exists) is fine. Picking a likely answer when signals are mixed or absent is not.
20
21	If any of these is violated, abort with a clear message about what went wrong and how to recover.
22
23	## Required tools
24
25	- `git` (in the user's project)
26	- `gh` (authenticated; `gh auth status` returns OK)
27	- `jq` (used by `run_tests.sh`)
28	- `bash` (for the bundled scripts)
29
30	If any is missing, stop in Phase 4 and tell the user how to install.
31
32	## Gotchas
33
34	Environment-specific behavior the agent will get wrong without being told. Read these before starting the workflow and apply throughout.
35
36	- Parallel implementations. When a feature has `new` files plus `differs` to call sites, the user may already have an in-house equivalent (their own toast helper, validation rule, etc.). Surface as a whole; don't apply the `new` files in isolation as if they're "safe." Default action is to skip the entire feature; the user can opt to adopt upstream's version and remove theirs later.
37
38	- Renamed paths. If a `new` path's basename or class name already exists elsewhere in the user's repo, the user has likely renamed/moved it. Surface, don't auto-apply, or you'll create a duplicate. Show them the upstream change and let them apply it to their renamed file by hand or wait for user confirmation.
39
40	- Later upstream edits. Copying upstream HEAD pulls in _every_ commit since the feature, not just the feature's own changes. Always run the Phase 5 step 2 check before applying. When later edits exist, scope to `<sha>:<path>` instead of `HEAD:<path>`.
41
42	- Transitive imports. New files often `import` from helpers that are NOT in the same feature commit (Vue/React/Svelte: `@/lib/...`, `@/components/...`; Livewire: `@include`, `<x-...>`, `<livewire:...>`). Phase 5 step 4 covers the scan; never declare a feature applied without it. Uncovered imports show up as runtime/compile errors.
43
44	- Lockfile drift. Manifests are user-curated. Never overwrite. Walk the user through the upstream diff, let them merge, then regenerate lockfiles via the package manager (Phase 6).
45
46	- Stale node_modules after major bumps. After Vite v7 → v8, React 18 → 19, etc., `npm install` often fails with `ERESOLVE`. Clean and reinstall (Phase 6).
47
48	- New migrations. When upstream adds migrations (e.g. "Catch migrations up to Skeleton"), surface them separately. Recommend `php artisan migrate:status` first; applying a new migration on a populated DB can fail loudly.
49
50	- Major framework bumps as features. Things like Laravel 12 → 13, Livewire 3 → 4, or Inertia v2 → v3 are too large and too breaking for the feature-by-feature flow. Do not attempt them through this skill. Instead, prompt the user to run the corresponding [Laravel Boost](https://github.com/laravel/boost) MCP slash command first, then come back and re-run this skill against the resulting (clean-tree) repo. If Boost is not yet installed: `composer require laravel/boost --dev && php

People who liked this also viewed

6 picks

Type