setup

Read host portability before resolving plugin files, invoking sibling skills, or persisting project guidance.

sc-php Setup

Scaffold-from-zero counterpart to sc-php:sniff (which detects/audits an already-configured project). Covers exactly the three frameworks sniff detects: WordPress, Laravel, Symfony.

Available actions

#	Action	Role	Input
01	detect-framework	Resolve which framework to scaffold (explicit request, ask if ambiguous), abort if project already configured	project root, user request
02	scaffold-wordpress	WordPress FSE theme + custom plugin + Docker/wp-env	resolved framework = wordpress
03	scaffold-laravel	Laravel via composer create-project + Docker Compose	resolved framework = laravel
04	scaffold-symfony	Symfony via composer create-project + Docker Compose	resolved framework = symfony
05	wire-deploy	Compatibility route to sc-php:cd server; never a second producer	framework, target(s) info from user
06	verify	Post-scaffold and native CD facade sanity checks	framework, project root

Default flow

01 → (02 | 03 | 04 depending on resolved framework) → 06. 05 is optional, proposed after scaffold but never assumed — only run it if the user wants a deploy target wired now.

Trigger-to-action mapping for 01:

• Framework named explicitly ("scaffold a WordPress", "set up Laravel with Docker") → skip the question, go straight to the matching scaffold action.
• No framework named, or ambiguous → ask (WordPress / Laravel / Symfony), never guess.

References

• references/pitfalls.md — Docker Compose project-naming trap (generic, all frameworks), WP-specific CSS cache-busting and wp-cli-via-Docker rules.
• references/compose-project-name-guard.md — start.ps1/stop.ps1/wp.ps1 template shared by all three scaffolds.
• references/wp-env-json.md, references/theme-plugin-skeleton.md — WordPress scaffold content.
• references/docker-compose-laravel.md, references/docker-compose-symfony.md — Docker Compose content for the other two frameworks.
• references/deploy-pipeline.md — legacy pipeline recognition and migration rules; new delivery belongs to sc-php:cd.

Transversal rules

• Never scaffold onto an already-configured project — 01 aborts and redirects to sniff/audit if composer.json or a sentinel file already exists.
• Never invent deploy target credentials (host, user, path) — ask, or leave a commented example.
• Never auto-run a database import against a remote target — that step stays manual and explicit, always.
• Never let Docker Compose derive its project name implicitly — every scaffold wires the COMPOSE_PROJECT_NAME guard from compose-project-name-guard.md.
• WordPress is the reference-quality flow (real production lineage); Laravel/Symfony are thinner (official installer + standard compose) — say so rather than implying equal depth.
• Report every file written, per action, same as sniff/overcode:service do.