← ClaudeAtlas

initlisted

Onboard a repository to the Groundwork workflow — generate thin domain-only AGENTS.md/CLAUDE.md by grounded discovery, install Laravel Boost, and drop .groundwork.json. Use once per project; re-run to refresh from current code.
YasMax91/groundwork · ★ 0 · AI & Automation · score 66
Install: claude install-skill YasMax91/groundwork
# Initialize a project Set up a Laravel repo to use this plugin. The contract files are **generated by grounded discovery, never guessed**: fill what the code/Boost/docs prove, mark the rest, and ask the human only for what cannot be derived. ## Pick the mode - **Existing repo with code** — derive the domain from reality (preferred). - **New/empty repo** — drop the template skeleton and interview the user for the few facts; re-run with refresh as code grows. - **Repo that already has a rich AGENTS.md** (e.g. migrating an existing project) — **split**, do not regenerate: move the generic process out (it now comes from this plugin) and keep only the domain. ## Grounded discovery (existing repo) Use Boost and the codebase as the source of truth, and label every section: - **Tech stack & runtime** — `composer.json`, Sail config, Boost `application-info`. `[from code]` - **Database engine** — `config/database.php` default + `.env` `DB_CONNECTION`. Set `.groundwork.json` `database.default` to it (MySQL/Postgres). If `phpunit.xml` / `.env.testing` runs tests on SQLite (`:memory:`) while the app targets MySQL/Postgres, flag it — tests must run on the real engine. `[from code]` - **Domain entities** — Boost `database-schema` + Eloquent models. `[from code]` - **Domain language** — the word each concept goes by across models, routes, and the CRD. Where the codebase and the business use different words for one thing, pick the one to keep and list the rest as synonyms