Portable Web Toolkit
Use the project contract and deterministic toolkit commands without creating a
parallel workflow.
If one narrow skill clearly owns the request, use it directly and do not load
this router merely because toolkit management is established.
Confirm toolkit management
Require at least one authoritative signal:
- repository instructions establish Portable Web Toolkit
- package scripts invoke
Web_Toolkit commands
- a compatible toolkit site profile governs the site
- an established
Web_Toolkit link is corroborated by configuration or docs
- the user explicitly selects the toolkit
A folder name alone is not proof. If management is uncertain, inspect and
report the evidence before imposing toolkit conventions.
Read project contract whenever instructions,
profiles, brand guidance, environment values, or generic skills may conflict.
Establish current state
- Resolve the active client repository and applicable instructions.
- Preserve unrelated and uncommitted work.
- Locate the toolkit source, site profile, package manager, and supported
project commands.
- Run
site-readiness when beginning material site work, after scaffolding,
before release preparation, or when project state is uncertain.
- Read its structured report before choosing fixes.
Use --skip-network when policy or environment disallows external checks.
Readiness findings do not authorize dependency installation, infrastructure
mutation, deployment, or toolkit updates.
Route to the narrow owner
| Need |
Owner |
| New toolkit-managed site |
site-starter |
| Project readiness and next actions |
site-readiness |
| Public Instagram fallback |
instagram-clone |
| Wordmark or raster-to-SVG candidate |
vectorize-pipeline |
| Toolkit and skill version comparison |
toolkit-update |
| Existing deterministic operation |
Relevant Web_Toolkit CLI |
Read operations routing only after the task and
deployment target are known.
Preserve mutation boundaries
- Use repository-approved package, build, and deploy commands.
- Audit and dry-run Cloudflare, DNS, cache, registrar, header, and hardening
changes before an authorized apply.
- Treat staging and production as separate authorization boundaries.
- Keep secrets out of command output, committed files, profiles, and reports.
- Do not install host software, update the toolkit, reinstall skills, deploy,
publish, or release merely because ordinary site work was requested.
- Stop on unexplained profile conflicts, destructive generated-file churn, or
incompatible toolkit versions.
Complete with evidence
Report the management evidence, project authority followed, readiness state,
toolkit commands used, files and environments changed, dry-run and live
evidence, warnings, skipped checks, rollback path, and unresolved uncertainty.
Read toolkit maintenance only for toolkit updates,
host setup, skill distribution, or toolkit publication.
1---2name: portable-web-toolkit3description: Coordinate multi-capability work, deployment or release sequencing, and ambiguous operations in Astro and Cloudflare projects managed by Portable Web Toolkit. Use when the task crosses toolkit owners or needs routing and safety gates. Defer directly to a narrow skill when readiness, scaffolding, updating, Instagram fallback, or vectorization clearly owns the request. Do not use for unrelated or merely generic web work.4---56# Portable Web Toolkit78Use the project contract and deterministic toolkit commands without creating a9parallel workflow.1011If one narrow skill clearly owns the request, use it directly and do not load12this router merely because toolkit management is established.1314## Confirm toolkit management1516Require at least one authoritative signal:1718- repository instructions establish Portable Web Toolkit19- package scripts invoke `Web_Toolkit` commands20- a compatible toolkit site profile governs the site21- an established `Web_Toolkit` link is corroborated by configuration or docs22- the user explicitly selects the toolkit2324A folder name alone is not proof. If management is uncertain, inspect and25report the evidence before imposing toolkit conventions.2627Read [project contract](references/project-contract.md) whenever instructions,28profiles, brand guidance, environment values, or generic skills may conflict.2930## Establish current state31321. Resolve the active client repository and applicable instructions.332. Preserve unrelated and uncommitted work.343. Locate the toolkit source, site profile, package manager, and supported35 project commands.364. Run `site-readiness` when beginning material site work, after scaffolding,37 before release preparation, or when project state is uncertain.385. Read its structured report before choosing fixes.3940Use `--skip-network` when policy or environment disallows external checks.41Readiness findings do not authorize dependency installation, infrastructure42mutation, deployment, or toolkit updates.4344## Route to the narrow owner4546| Need | Owner |47|---|---|48| New toolkit-managed site | `site-starter` |49| Project readiness and next actions | `site-readiness` |50| Public Instagram fallback | `instagram-clone` |51| Wordmark or raster-to-SVG candidate | `vectorize-pipeline` |52| Toolkit and skill version comparison | `toolkit-update` |53| Existing deterministic operation | Relevant `Web_Toolkit` CLI |5455Read [operations routing](references/operations.md) only after the task and56deployment target are known.5758## Preserve mutation boundaries5960- Use repository-approved package, build, and deploy commands.61- Audit and dry-run Cloudflare, DNS, cache, registrar, header, and hardening62 changes before an authorized apply.63- Treat staging and production as separate authorization boundaries.64- Keep secrets out of command output, committed files, profiles, and reports.65- Do not install host software, update the toolkit, reinstall skills, deploy,66 publish, or release merely because ordinary site work was requested.67- Stop on unexplained profile conflicts, destructive generated-file churn, or68 incompatible toolkit versions.6970## Complete with evidence7172Report the management evidence, project authority followed, readiness state,73toolkit commands used, files and environments changed, dry-run and live74evidence, warnings, skipped checks, rollback path, and unresolved uncertainty.7576Read [toolkit maintenance](references/maintenance.md) only for toolkit updates,77host setup, skill distribution, or toolkit publication.
ImYourBoyRoy