ns-proto-creator — Claude Code skill: prototyping and install
ns-proto-creator — a Claude Code skill that captures live interfaces with Playwright and builds or updates a prototype. It runs for URL-based prototyping, screen reconstruction, and changes to an existing prototype/.
Apache-2.0 106 installs updated 2026-10-24
npx skills add nextstage-brasil/skills --skill ns-proto-creator -a claude-codeWhat ns-proto-creator does
The skill uses Playwright to inspect a live interface, record what it finds, and create or update the project’s prototype/. It first gathers the target URL, roles, screens, and requested changes. Then it writes AS-IS notes under docs/ and builds from observed screens, fields, and states.
When prototype/ is missing, the skill creates it; otherwise, it edits the existing tree in place and leaves version history to Git. Playwright MCP is required for capture. The workflow also calls on ns-harness, ns-frontend-design, ns-best-practices, ns-living-spec, and ns-proto-visual-guide. Bare code fixes and full SDD work are routed to other skills.
What it helps with
- capture screens from a live app with Playwright
- document current pages and flows under
docs/ - build a prototype from an observed interface
- evolve one prototype without creating
vN/copies
Example prompts for the agent
- Capture the app at this URL and build its prototype in
prototype/. - Document the current screens and roles, then update the existing prototype.
- Inspect this page’s fields and states with Playwright and reflect them in the prototype.
How to install ns-proto-creator
1Skills CLI (Vercel)
npx skills add nextstage-brasil/skills --skill ns-proto-creator -a claude-code2Manually: put the files in place
~/.claude/skills/ns-proto-creator/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ns-proto-creator/
1Skills CLI (Vercel)
npx skills add nextstage-brasil/skills --skill ns-proto-creator -a codex2Manually: put the files in place
.agents/skills/ns-proto-creator/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nextstage-brasil/skills --skill ns-proto-creator -a cursor2Manually: put the files in place
.cursor/skills/ns-proto-creator/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nextstage-brasil/skills skills/ns-proto-creator2Manually: put the files in place
.github/skills/ns-proto-creator/SKILL.md1Skills CLI (Vercel)
npx skills add nextstage-brasil/skills --skill ns-proto-creator -a gemini-cli2Platform CLI
gemini skills install https://github.com/nextstage-brasil/skills --path skills/ns-proto-creatorManually: put the files in place
.devin/skills/ns-proto-creator/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add nextstage-brasil/skills --skill ns-proto-creator -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ns-proto-creator
How do I install ns-proto-creator in Claude Code?
Run npx skills add nextstage-brasil/skills --skill ns-proto-creator -a claude-code. The skill file is installed at ~/.claude/skills/ns-proto-creator/SKILL.md.
What does ns-proto-creator do?
It captures a live interface with Playwright, records its current state, and creates or updates a single prototype in prototype/. Git tracks its evolution.
What does ns-proto-creator need to run?
Playwright MCP is required. The workflow also uses ns-harness, ns-frontend-design, ns-best-practices, ns-living-spec, and ns-proto-visual-guide.
Source text
SKILL.md · Apache-2.0
--- name: ns-proto-creator description: "(NS) Playwright reverse-prototyping — capture live UI; create/evolve single prototype/ (git history; never v1/v2). Use when prototyping from a URL, reversing a screen into prototype/, evolving a prototype, AS-IS flows/fields, or \"prototype this app/page\". Do NOT use for appearance MDs only (ns-proto-visual-guide), full SDD (ns-spec-driven), bare code fixes (ns-coder), or /ns-harness prepare." license: Apache-2.0 metadata: author: nextstage-brasil version: "1.0" depends: - ns-harness - ns-frontend-design - ns-best-practices - ns-living-spec - ns-proto-visual-guide --- # Proto Creator **Delivery face:** Playwright reverse prototyping. Capture → AS-IS docs → create/evolve one `prototype/` → quality → living appearance → optional visual guides. **Orchestrate.** Load worker `SKILL.md` at delegation. No inline full design checklists or Element|How tables. ## Layout (locked) ``` prototype/ # THE prototype — create once, evolve forever docs/ # AS-IS briefs, screenshots, appearance guides docs/specs/ # Living domain specs (when consolidating) ``` - Missing `prototype/` → **create**. - Existing `prototype/` → **evolve in place**. - Never scaffold `vN/prototype/` or ask version-folder name. Versioning = **git**. Optional: remind commit after meaningful evolve. ## Harness See `../../ns-harness/references/session-boot.md` and `../../ns-harness/references/artifact-layout.md`. ## Near-miss routing | User wants | Redirect | | ---------- | -------- | | Only `*-visual.md` / descrição normativa / guia de aparência | `ns-proto-visual-guide` | | Full SDD version / requirements / tasks | `ns-spec-driven` | | Bare bugfix, no prototype scope | `ns-coder` | | Brownfield architecture map only | Tell user run `/ns-harness prepare` | ## Boot (mandatory, once per session) Short natural-language questions. No giant questionnaire. 1. **Base URL** — login / which Playwright MCP profile if multiple. 2. **Scope** — screens, roles, add/change. 3. **Prototype mode** — detect `prototype/`: - absent → **create** - present → **evolve in place** No version-id / `v1` folder question. ## Journey ```mermaid flowchart TB boot[Boot questions] capture[Capture Playwright] asis[AS-IS docs] build[Build or evolve prototype] quality[Best practices + guidelines] living[Living appearance] handoff[Offer visual guide] boot --> capture --> asis --> build --> quality --> living --> handoff ``` | Phase | Reference / worker | Behavior | | ----- | ------------------ | -------- | | Capture | `references/capture-playwright.md` | Discover Playwright MCP; navigate; screenshots; note structure, fonts, icons, density | | AS-IS | `references/as-is-docs.md` | Write/update `docs/` briefs from evidence | | Build / Evolve | `references/build-prototype.md` + `ns-frontend-design` | Only under `prototype/`; mirror flows/fields/states; modern stack — no legacy clone | | Quality | `ns-best-practices` | Hygiene + Web Interface Guidelines review on prototype surfaces | | Living | `ns-living-spec` **appearance** | Create `docs/specs/` + INDEX if missing; SHALL for visible product behavior only | | Handoff | `ns-proto-visual-guide` | Offer / run for implementation appearance MDs | ## Hard rules - One prototype tree; evolve in place; never parallel `vN/` copies - Fidelity from live Playwright evidence; no invented screens - Stack-free modern UI under `prototype/` — load `ns-frontend-design` - English for this skill's artifacts; project docs language follows repo - Versioning = git; optional commit remind after meaningful evolve - No hardcoded product-specific login — project rules / user credentials path ## Related skills - `ns-proto-visual-guide` — normative appearance MDs - `/ns-harness` `codebase-reverse-spec.md` — business reverse from code (complement URL capture) - `ns-frontend-design` / `ns-best-practices` — design + quality workers
© nextstage-brasil · Apache-2.0 · nextstage-brasil/skills