Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
64 commits
Select commit Hold shift + click to select a range
a3a1d67
Chore(deps): Bump tmp from 0.2.5 to 0.2.7 (#694)
dependabot[bot] May 28, 2026
c042ea3
Chore(deps): Bump shell-quote from 1.8.3 to 1.8.4 (#711)
dependabot[bot] Jun 10, 2026
38e127b
Chore(deps-dev): Bump launch-editor from 2.13.1 to 2.14.1 (#723)
dependabot[bot] Jun 20, 2026
04d2e1f
Chore(deps-dev): Bump form-data from 4.0.5 to 4.0.6 (#722)
dependabot[bot] Jun 20, 2026
0b78a88
Chore(deps-dev): Bump @babel/core from 7.29.0 to 7.29.6 (#724)
dependabot[bot] Jun 21, 2026
06cfa09
Chore(deps): Bump ws and @wp-playground/cli (#735)
dependabot[bot] Jul 15, 2026
e6389b3
Chore(deps-dev): Bump websocket-driver from 0.7.4 to 0.7.5 (#738)
dependabot[bot] Jul 16, 2026
51e805d
Chore(deps): Bump svgo (#740)
dependabot[bot] Jul 24, 2026
35d8cc1
Chore(deps): Bump shell-quote from 1.8.4 to 1.10.0 (#742)
dependabot[bot] Jul 25, 2026
9e9a5a3
Chore(deps-dev): Bump immutable from 5.1.5 to 5.1.9 (#745)
dependabot[bot] Jul 25, 2026
8d752b1
Chore(deps): Bump fast-xml-parser from 5.10.0 to 5.10.1 (#741)
dependabot[bot] Jul 25, 2026
5091d70
Chore(deps): Bump fast-uri from 3.1.3 to 3.1.4 (#743)
dependabot[bot] Jul 25, 2026
46c16a4
Chore(deps): Bump postcss from 8.5.10 to 8.5.22 (#744)
dependabot[bot] Jul 25, 2026
de346d6
Chore(deps): Bump fast-uri from 3.1.4 to 3.1.5 (#754)
dependabot[bot] Aug 6, 2026
394fa03
Chore(deps): Bump postcss from 8.5.22 to 8.5.25 (#755)
dependabot[bot] Aug 7, 2026
61d0956
Run Copilot code review on GitHub-hosted runners
rtBot Aug 13, 2026
22f0b7d
Merge pull request #757 from rtCamp/add/copilot-code-review-runner
iamimmanuelraj Aug 13, 2026
e1d1f6d
Chore(deps): Bump postcss-selector-parser (#760)
dependabot[bot] Sep 2, 2026
29d92b6
Chore(deps): Bump fast-uri from 3.1.5 to 3.1.7 (#762)
dependabot[bot] Sep 3, 2026
5845704
Chore(deps-dev): Bump @humanfs/node from 0.16.7 to 0.16.8 (#763)
dependabot[bot] Sep 3, 2026
793bcb1
Chore(deps-dev): Bump joi from 18.0.2 to 18.2.8 (#764)
dependabot[bot] Sep 9, 2026
5212b87
Chore(deps-dev): Bump baseline-browser-mapping from 2.10.0 to 2.11.21…
dependabot[bot] Sep 10, 2026
f67a3f3
Chore(deps): Bump svgo (#765)
dependabot[bot] Sep 10, 2026
65cfc6b
Chore(deps): Bump js-yaml (#766)
dependabot[bot] Sep 10, 2026
92218f7
feat(init): init skill simplification and add dev-tools feature
Adi-ty Sep 14, 2026
27860f1
feat(tests): add dev-tools and init wrapper test cases
Adi-ty Sep 14, 2026
0be9f46
docs: add guides and documentation workflow
Adi-ty Sep 15, 2026
02ccaae
fix: update cleanup targets in scaffold config
Adi-ty Sep 18, 2026
9a4a843
docs: address PR review feedback on documentation
Adi-ty Sep 18, 2026
cca09f4
Chore(deps): Bump adm-zip and @wordpress/scripts (#780)
dependabot[bot] Sep 20, 2026
9f36e68
docs: address readability feedback across all documentation
Adi-ty Sep 22, 2026
7f12283
docs: unify troubleshooting headings, fix inaccuracies, and tighten p…
Adi-ty Sep 22, 2026
cd0ea4f
docs: drop hard-wrapped lines, rebuild asset/hmr/tailwind docs from s…
Adi-ty Sep 22, 2026
5fc0794
docs: address second-round review feedback
Adi-ty Sep 24, 2026
7bc5ae6
chore: rename wp-framework to wp-primitives
aryanjasala Sep 27, 2026
38c1a90
fix: address rename audit findings
aryanjasala Sep 28, 2026
4bfa8ff
Chore(deps): Bump markdown-it and @wordpress/scripts (#783)
dependabot[bot] Sep 30, 2026
b0ba8b1
Merge #777 feat/init-devtools into golive/integration
aryanjasala Oct 1, 2026
cf2a92f
Merge #778 docs/theme-elementary-v2 into golive/integration
aryanjasala Oct 1, 2026
ff269e8
Merge #782 rename/deps into golive/integration
aryanjasala Oct 1, 2026
af8c4cb
fix(deps): make package-lock.json installable with npm 10
aryanjasala Oct 1, 2026
2016fb1
chore(ai): sync primitives-php instructions with wp-primitives 2.0
aryanjasala Oct 1, 2026
6cc43a9
style(js): fix ESLint errors in configs, bin scripts and JS tests
aryanjasala Oct 1, 2026
e38e947
build(lint): lint every project JS file, not only src/
aryanjasala Oct 1, 2026
be18a4e
fix(phpcs): use element syntax for the I18n text_domain property
aryanjasala Oct 1, 2026
f9050f1
fix(tests): enable WP_DEBUG in the wp-env tests environment
aryanjasala Oct 1, 2026
178ebca
ci(auto-merge): only merge bot PRs after a green Test and Measure run
aryanjasala Oct 1, 2026
dd8812f
ci(docs): build on main and v2, deploy only from the default branch
aryanjasala Oct 1, 2026
d9b0e0a
docs(skills): describe lint/phpcs/full as the rtcamp/wp-phpcs standard
aryanjasala Oct 1, 2026
c3a6785
chore(node): pin .nvmrc to Node 22 to match shared CI and plugin-elem…
aryanjasala Oct 1, 2026
44c657b
Chore(deps-dev): Bump brace-expansion from 1.1.12 to 1.1.21 (#784)
dependabot[bot] Oct 1, 2026
0219fcb
build(lint): keep Jest coverage output out of ESLint
aryanjasala Oct 1, 2026
05980e7
docs(skills): say lint/phpcs/full extends the strict rtCampWP standard
aryanjasala Oct 1, 2026
8463198
fix(scaffold): keep core FeaturesSettingsPage when removing example sets
aryanjasala Oct 1, 2026
22bce42
test(js): cover webpack entry helpers and the media-text module
aryanjasala Oct 1, 2026
bd59d48
test(php): cover assets, features, settings, helpers and block extens…
aryanjasala Oct 1, 2026
f5fa160
Merge main into the v2 branch for release
aryanjasala Oct 1, 2026
dc1da4c
fix(scripts): keep npm run lint:all and npm test to the checks
aryanjasala Oct 1, 2026
52ed2a9
fix(dev-server): read port settings as whole numbers only
aryanjasala Oct 1, 2026
722998f
fix(tailwind): put the entry's imports first and accept Tailwind at-r…
aryanjasala Oct 1, 2026
f4e4b11
fix(patterns): exit when a pattern file is loaded outside WordPress
aryanjasala Oct 1, 2026
ddfcbde
fix(graphify): report only an installed graphify
aryanjasala Oct 1, 2026
40bbf12
chore(graph): regenerate the committed knowledge graph
aryanjasala Oct 1, 2026
2525451
Merge remote-tracking branch 'origin/theme-elementary-v2' into golive…
aryanjasala Oct 1, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions .claude/skills/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,15 +4,17 @@ Skills for AI assistants (Claude Code, Cursor, and any tool that reads the Claud

| Skill | Invoke | What it does |
|---|---|---|
| [`init/`](init/SKILL.md) | `/init` | Turn this cloned theme into a named theme and manage it afterwards: rename the starter tokens, keep/remove the example sets, toggle optional features (Tailwind, HMR). Drives `npm run init`. |
| [`init/`](init/SKILL.md) | `/init` | Turn this cloned theme into a named theme and manage it afterwards: rename the starter tokens, keep/remove the example sets, toggle optional features (Tailwind, HMR, Dev Tools). Drives `npm run init`. |
| [`scaffold/`](scaffold/SKILL.md) | `/scaffold` | Add one feature (dynamic block, shortcode, settings/admin page, service, CI workflow - plus CPT/taxonomy/REST/CLI/cron for a companion plugin) via `npx wp-tooling add`, TDD-first, wiring it into `Main::CLASSES`. |

`init` is theme-specific. `scaffold` tracks `@rtcamp/wp-tooling` and introspects the project, so it stays correct as the layout evolves. [`setup/`](setup/SKILL.md) (`/setup`) is the natural-language bootstrapper: from one brief it applies tooling and chains a sequence of feature scaffolds.
`init` is theme-specific. `scaffold` tracks `@rtcamp/wp-tooling` and introspects the project, so it stays correct as the layout evolves. [`setup/`](setup/SKILL.md) (`/setup`) is the generic natural-language tooling bootstrapper for empty/existing projects. Use `/init` to personalize this skeleton; `/setup` does not replace its identity and capability flow.

**Copilot parity:** `init` and `scaffold` also exist for GitHub Copilot as prompt files in [`.github/prompts/`](../../.github/prompts/) (`/init`, `/scaffold`), kept consistent with these skills. Shared conventions and the knowledge-graph (graphify) policy live in [`AGENTS.md`](../../AGENTS.md).
**Copilot parity:** `init` and `scaffold` also exist for GitHub Copilot as prompt files in [the maintained Copilot prompts](https://github.com/rtCamp/theme-elementary/tree/theme-elementary-v2/.github/prompts) (`/init`, `/scaffold`), kept consistent with these skills. Shared conventions and the knowledge-graph (graphify) policy live in [`AGENTS.md`](../../AGENTS.md).

## Safety

These skills are opinionated about safety and never: run a package manager or `npm run build` without consent; read, log, or transmit secret values; apply cross-file wiring without showing the diff and getting consent; or commit, push, or open PRs without approval. `init` additionally never runs a destructive setup without confirming the resolved values against a clean working tree.
These skills are opinionated about safety and never: run a package manager or `npm run build` without consent; read, log, or transmit secret values; apply cross-file wiring without showing the diff and getting consent; or commit, push, or open PRs. `init` additionally never runs a destructive setup without confirming the resolved values against a clean working tree.

Two consented exceptions to the package-manager rule: `npm run init` (the theme's own setup script), and the **pilot bootstrap** `init` runs on request (sibling clone of the tooling engine + local `file:` ref + `composer update`/`npm install`). After any code change, the skills refresh the local graph with `graphify update .`.
Dependency installation and `npm run init` require consent. The init skill uses the declared dependencies; Composer's install hook already runs npm. Sibling dependency checkouts are maintainer work. After file changes, refresh the local graph with `graphify update .`.

Cleanup removes the Copilot-specific files under `.github` (`copilot-instructions.md`, `prompts/`, `instructions/`); issue templates, the PR template, `dependabot.yml`, `release.yml`, and workflows stay. `sync-ai` restores only generated framework instructions. The Claude skills remain. Review these removals before personalizing a clone.
63 changes: 26 additions & 37 deletions .claude/skills/init/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,16 +1,16 @@
---
name: init
description: Set up this cloned theme-elementary into a named theme, or manage its identity and capabilities later. During the pilot it can also run the local bootstrap (sibling clone of the tooling engine, local package ref, composer + npm install). Drives `npm run init`. Always confirms before destructive or install steps; expects a clean working tree.
description: Set up this cloned theme-elementary into a named theme, or manage its identity and capabilities later. Installs the declared dependencies, accounting for the Composer npm hook. Drives `npm run init`. Always confirms before destructive or install steps; expects a clean working tree.
---

# init

Two jobs: **bootstrap + setup** a fresh clone into a real theme, or **manage** an already-set-up project. Always interactive: gather inputs first, confirm the resolved plan, then act.

## Use for
- First run: optional pilot bootstrap (deps), rename starter tokens, pick which example sets to keep.
- First run: install declared dependencies, rename starter tokens, pick which example sets to keep.
- First run WITH a feature brief: after rename + capabilities, implement the described features by chaining to the **scaffold** skill (TDD), replacing the matching `Example*`/demo placeholders (step 8).
- Later: rename / re-prefix, toggle features (Tailwind, HMR).
- Later: rename / re-prefix, toggle features (Tailwind, HMR, Dev Tools).

## Do not use for
- Adding a feature class → the **scaffold** skill (`npx wp-tooling add`).
Expand All @@ -23,7 +23,7 @@ Ask the developer for every input the chosen path needs, in ONE batched message,
## Plan and announce (required) - developer experience first
Keep the developer oriented at every moment; great DX is the goal even through an AI skill.

1. **State the plan up front** in one short message: the mode (setup / manage) and the ordered steps you will run for THIS request. For a setup-with-brief, that is: detect mode -> (offer) bootstrap deps -> gather + confirm identity and capabilities -> run init (which also removes the example sets the brief does not need) -> hand each feature to the scaffold skill.
1. **State the plan up front** in one short message: the mode (setup / manage) and the ordered steps you will run for THIS request. For a setup-with-brief, that is: detect mode -> install deps -> gather + confirm identity and capabilities -> run init (which also removes the example sets the brief does not need) -> hand each feature to the scaffold skill.
2. **Maintain a live TODO list** on the host's task surface (`TodoWrite` in Claude Code): one entry per planned step, exactly one `in_progress` at a time, marked `completed` the moment it is done. Add entries as the work reveals them (a missing dep, each feature to scaffold).
3. **Announce each step with a short title** as you start it (e.g. "Running init", "Removing the shortcode example", "Handing the Testimonial block to scaffold") and report its outcome in one line. Never go silent during a long step.
4. **Confirm before anything destructive or installing** (the init rewrite, dependency installs), showing the exact resolved values.
Expand All @@ -36,61 +36,51 @@ test -f .wp-scaffold.json && echo manage || echo setup
```
No `.wp-scaffold.json` → **setup**. Present → **manage** (read it for current identity; `npm run init -- --list` shows feature status).

### 2. Setup: offer the pilot bootstrap
The rtCamp tooling packages are private/unpublished during the pilot. If `npm install` can resolve `@rtcamp/wp-tooling` from the registry and `composer install` resolves `rtcamp/wp-primitives` from its VCS repo, no bootstrap is needed - skip to step 3. Otherwise ask: "Bootstrap local dependencies now? (clones the tooling engine, points npm at it, installs). y/n". On **yes**, with consent, run in order (tell the developer each step in <=30 words):
### 2. Install dependencies
Skip installation when both dependency trees are already current. Otherwise, with installation consent, run from the theme directory:

```bash
nvm use # Node from .nvmrc

# Sibling clone for the npm engine (skip if it already exists):
git clone git@github.com:rtCamp/wp-tooling.git ../wp-tooling
( cd ../wp-tooling && git checkout release/v1.0.0 ) # init/scaffold engine landed here

# Local-only npm ref: this theme's only @rtcamp/* dependency is @rtcamp/wp-tooling.
npm pkg set devDependencies.@rtcamp/wp-tooling=file:../wp-tooling/node-packages/wp-tooling

# wp-primitives already resolves from the VCS "repositories" entry in composer.json (dev-main);
# composer update pulls it. For local framework development, optionally add a path repo instead:
# { "type": "path", "url": "../wp-primitives", "options": { "symlink": false } }
composer update rtcamp/wp-primitives
# --install-links is REQUIRED: it copies the file: @rtcamp package into node_modules instead of
# symlinking, so its peer deps resolve from this theme. Add --legacy-peer-deps on ERESOLVE.
npm install --install-links
nvm use
composer install
```
The `file:` edit is local-only. Note: init ALSO writes identity changes (name, namespace, pot path) into `package.json`/`composer.json`, so a blanket `git checkout package.json composer.json` would discard the rename. Before committing, revert ONLY the dependency-source line (the `@rtcamp/wp-tooling` `file:` ref, plus any path `repositories` entry and `composer.lock` you added) - keep every identity change. On **no**, skip to step 3 and surface installs as developer actions instead.

This theme's Composer `post-install-cmd` runs `npm i`; do not immediately repeat `npm install`. If Composer dependencies are already current but npm dependencies are missing or stale, run `npm install` with consent. If Composer was installed with `--no-scripts`, npm installation is still required. Check both dependencies before continuing. If consent is declined, print the missing installation command and stop.

### 3. Preconditions (verify; do not silently fix)
- `node_modules/@rtcamp/wp-tooling` exists (the engine needs it). If missing and bootstrap was declined, surface `npm install` as a developer action.
- `node_modules/@rtcamp/wp-tooling` exists (the engine needs it). If missing, surface the required installation command and stop.
- Clean working tree (`git status`). Init rewrites files irreversibly; a clean tree is the only undo. If dirty, ask to commit/stash.
- Confirm this is a fresh clone meant to become a new theme, not the skeleton repo itself.
- Setup only: confirm this is a clone meant to become a new theme, not the maintained starter theme. Manage mode operates on an already-personalized project.

### 4. Gather inputs
**Setup:** theme name (required, e.g. `Acme Blog` → namespace `rtCamp\Theme\Acme_Blog`, package `rtcamp/acme-blog`, text domain, constant/function/CSS prefixes, the `style.css` + `functions.php` headers; show these back); version (default `1.0.0`); which example sets to remove and which features to enable (defaults: keep all sets, hmr on, tailwind off). The engine derives the tokens itself; do not read the engine source to work them out - the mapping above is the contract, and the graph answers any deeper question (see the graphify policy in `AGENTS.md`).
**Setup:** theme name (required, e.g. `Acme Blog` → namespace `rtCamp\Theme\Acme_Blog`, package `rtcamp/acme-blog`, text domain, constant/function/CSS prefixes, the `style.css` + `functions.php` headers; show these back); version (default `1.0.0`); which example sets to remove and which features to enable (defaults: keep all sets, hmr on, tailwind and dev-tools off). The engine derives the tokens itself; do not read the engine source to work them out - the mapping above is the contract, and the graph answers any deeper question (see the graphify policy in `AGENTS.md`).
**Manage:** which of identity / features to change.

### 5. Confirm
Show the exact resolved values and the exact command. Get explicit consent; init is destructive.

### 6. Run init (with consent)
`npm run init` also runs `npm run sync-ai`; that is expected.
Successful init changes also run `npm run sync-ai`; `--list`, help, failed runs, and interrupted runs do not.
```bash
# Setup:
npm run init -- --name="Acme Blog" --version=1.0.0 --yes \
--remove-examples=shortcode,patterns --features=hmr,tailwind
# Manage:
npm run init -- --list
npm run init -- --enable=tailwind --yes
npm run init -- --enable=dev-tools --yes
npm run init -- --features=hmr --yes # exact enabled set (empty = none)
```
- `--keep-examples` keeps all; `--remove-examples` (no value) removes all; `--remove-examples=a,b` removes listed keys.
- `--features=a,b` sets the exact enabled set; `--enable`/`--disable` are deltas.
- `--yes` requires `--name`. For the guided wizard, run bare `npm run init` (space toggles, enter confirms).
- `--features=a,b` sets the exact enabled set; `--enable`/`--disable` are deltas. Do not combine an exact set with delta flags.
- `--yes` requires `--name` in setup mode; feature toggles in manage mode do not require a name. For the guided wizard, run bare `npm run init` (space toggles, enter confirms).

**Setup WITH a feature brief - remove the example sets in THIS step (do not make it a separate round-trip):** remove every example set (`--remove-examples` with all keys, or the no-value form). Unlike a plugin's per-kind `AbstractModule` with a `get_classes()` array to keep-and-empty, this theme lists every class directly in `Main::CLASSES`, so there is nothing to keep-and-empty: the scaffold skill builds each briefed feature from scratch and wires its new `::class` line into `Main::CLASSES` itself (step 8). Example: brief = a custom Testimonial block + a footer credits shortcode -> `--remove-examples=block-extension,settings,shortcode,components,patterns`, then let scaffold build the two real features.

### 7. After init
- Tailwind enabled → it added `src/css/frontend/tailwind.css` + `postcss.config.js` and pinned `@rtcamp/tailwind-config`; developer runs `npm install` (re-apply the `file:` ref first during the pilot).
- `composer dump-autoload` (engine runs it when `composer.json` is present).
- Tailwind enabled → it added `src/css/frontend/tailwind.css` + `postcss.config.js` and pinned `@rtcamp/tailwind-config`; developer runs `npm install` (the feature changes declarations; it does not install packages).
- Dev Tools enabled → developer runs `composer update rtcamp/wp-dev-tools -W`, starts/restarts wp-env, activates the theme using the exact mounted directory name printed by the engine (`npm run wp-env run cli -- wp theme activate <directory-name>`), then runs `npm run dev:connect`. This optional package is private and requires repository access; WordPress 6.9+ and PHP 8.2+ are required. The feature writes a gitignored `.wp-env.override.json` with Query Monitor, MCP Adapter, local gates, and host/theme-container paths; it does not modify committed `.wp-env.json` or the tests environment.
- Dev Tools disable → disconnect first (`npm run dev:disconnect`), then disable and follow the engine’s Composer update instruction.
- `composer dump-autoload` runs during setup when `composer.json` is present.
- Trust the engine's own output to verify (it reports the removed sets, drops their `Main::CLASSES` lines and tests, and regenerates the autoloader). To confirm a symbol or reference, run a single `graphify query`/`affected` against the graph - never grep `Main.php`/`inc/` to check removal.
- If you hand-edited PHP and are NOT handing off to scaffold (e.g. a manage-mode dangling `Main::CLASSES` cleanup), run `composer phpcs` on the change and fix it. When a brief follows (step 8), leave the phpcs/PHPStan/test gates to the scaffold skill - init does not run them.
- **Refresh the LOCAL graph** with `graphify update .` (theme slice, tree-sitter, no API, seconds). The committed `graphify-out/graph.json` is a maintained baseline; your local refresh keeps queries accurate after a rename. If graphify is not installed, say so in one line; do not block.
Expand All @@ -112,26 +102,25 @@ ONE "Select the example sets to include" prompt. Each is keep-or-remove; removin
|---|---|
| Editor & Frontend | `block-extension`, `shortcode`, `components`, `patterns`, `tailwind` (feature) |
| Admin | `settings` |
| Dev | `hmr` (feature) |
| Dev | `hmr`, `dev-tools` (features) |

- `block-extension` - Media-text block render-filter extension.
- `shortcode` - Author-bio shortcode.
- `components` - Example components (button, card).
- `patterns` - Page-creation block pattern.
- `settings` - Theme options settings page.

Sets are kept by default; pass keys to `--remove-examples` to drop. Features: `hmr` on, `tailwind` off; toggle via `--features`/`--enable`/`--disable`.
Sets are kept by default; pass keys to `--remove-examples` to drop. Features: `hmr` on, `tailwind` and `dev-tools` off; toggle via `--features`/`--enable`/`--disable`.

### Changing capabilities after setup
Add later → scaffold skill / `npx wp-tooling add <category>/<slug>` (writes the class, wires it into `Main::CLASSES`). Remove later → delete its class file(s) under `inc/Modules/<Kind>/` plus its `Main::CLASSES` line and `use` import by hand. Do not re-run init to change the set.

## Hard rules
- **BASE (see AGENTS.md guardrails):** never run history/remote `git`/`gh` (commit, push, `branch -D`, `reset --hard`, PR, issue comment, `gh secret set`) - print them as developer actions. `git clone`/`checkout` for setup are fine. Never do a destructive operation outside this theme directory; cloning a NEW sibling is additive and OK, deleting/overwriting existing out-of-repo files is not.
- Package managers only with consent: `npm run init`, and the pilot bootstrap of step 2 (sibling clone + local ref + `composer update`/`npm install`). Outside those, surface install commands as developer actions.
- Never run a destructive init without confirming resolved values, on a clean tree.
- Package managers and init only with consent. Step 2 describes the normal dependency installation; feature dependency updates require consent too.
- Never run a destructive init without confirming resolved values, on a clean tree. Non-interactive setup with `--yes` skips optional Git initialization.
- Never commit, push, open PRs, or edit `.wp-scaffold.json` by hand.
- Never leave local-only `file:`/`path` edits uncommunicated: tell the developer to revert ONLY the dependency-source lines before commit (the `@rtcamp/wp-tooling` `file:` ref, any path `repositories` entry, `composer.lock`), keeping all identity changes init wrote into those files.
- Never invent flags. Supported: `--name`, `--version`, `--yes`, `--keep-examples`, `--remove-examples[=...]`, `--features`, `--enable`, `--disable`, `--reinit`, `--list`, `--clean`, `--help`. Run `npm run init -- --help` if unsure.
- Never invent flags. Supported: `--name`, `--version`, `--yes`, `--keep-examples`, `--remove-examples[=...]`, `--features`, `--enable`, `--disable`, `--reinit`, `--list` (optionally `--json`), `--clean`, `--help`. Run `npm run init -- --help` if unsure.

## Reference
- Engine: `@rtcamp/wp-tooling/init` (via `bin/init.js`). Capability map: `bin/scaffold.config.js`.
Expand Down
Loading
Loading