scaffold-pagesmith-docslisted

Stand up a brand-new Pagesmith documentation site from nothing — @pagesmith/docs wired to diagramkit, sample content, package skills installed, ending on a running preview. Triggers on "scaffold / bootstrap / stand up / start / create a new docs site", "new Pagesmith docs from scratch", "set up a docs site with diagrams". Writes to disk and runs local tooling (npm install, skills install, site build, dev server) — it configures a deploy target but NEVER deploys, pushes, or opens a PR; it prints the deploy command for a human to run. Confirms before touching an existing pagesmith.config. This is the greenfield counterpart to /adk:pagesmith (use that for an EXISTING site) and hands diagram-only work to /adk:diagramkit. It restates no package config schema, no engine flags, no palette — every version-sensitive authoring detail is delegated to the consumer's installed skills under node_modules.
sujeet-pro/agents-devkit · ★ 0 · API & Backend · score 75

Install: claude install-skill sujeet-pro/agents-devkit

# scaffold-pagesmith-docs — stand up a new Pagesmith docs site The flagship end-to-end scaffold. From an empty (or non-docs) directory it installs `@pagesmith/docs` + `diagramkit`, applies the package's own setup, materializes the package skills into the repo, seeds real sample content (one guide, one reference page, one diagram per requested engine), then validates and hands you a **running preview**. It stops at previewable and configured-for-deploy — it never deploys, pushes, or opens a PR. This skill is **greenfield only**. For an existing Pagesmith site — adding pages, restyling, deploying, package work — use `/adk:pagesmith`. For diagram-only work in any repo, use `/adk:diagramkit`. **Critical delegation rule:** this skill is a thin orchestrator. It does **not** carry Pagesmith's config schema, diagramkit's engine list, or any palette — those are version-sensitive and drift the instant a package ships. Every step that authors real content reads and follows the matching skill in the **consumer's** `node_modules` (`node_modules/@pagesmith/docs/skills/…`, `node_modules/diagramkit/skills/…`). If this skill and an installed skill ever disagree, the installed skill wins. The full operating contract lives in this skill folder — read these as you need them: | Aspect | File | |---|---| | How you scaffold (voice, discipline, output shape) | `persona.md` | | The phased process + Workflow orchestration | `workflow.md` | | Hard rules + refusals + safety | `rules.md` | ## Quick