메뉴
Smoke test a scaffold preset end-to-end. Runs init, install, build, test, explores output, and writes a structured report.json with quality scores. Use when scaffold testing, preset smoke test, or scaffold report are mentioned.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | scaffold-testing |
| version | 0.1.0 |
| description | Smoke test a scaffold preset end-to-end. Runs init, install, build, test, explores output, and writes a structured report.json with quality scores. Use when scaffold testing, preset smoke test, or scaffold report are mentioned. |
Smoke test a single scaffold preset end-to-end and produce a structured quality report.
Read the preset name and run directory from the prompt context. Confirm:
<run-dir>/<preset>/report.json)Run the scaffold command from the repo root:
bun ./apps/outfitter/src/cli.ts init <dir> --name scaffold-e2e-<preset> --preset <preset> --yes --skip-git --skip-commit
Note: Do NOT pass --skip-install — we want to test the real install flow in Phase 3.
Record: exit code, stdout, stderr, duration.
Run bun install in the scaffolded directory.
Record: exit code, stdout, stderr, duration, any warnings about peer deps or resolution issues.
Check if package.json has a build script. If yes, run bun run build. If no (e.g., minimal preset), mark as skipped with reason "no build script".
Record: exit code, stdout, stderr, duration.
Run bun run verify:ci if the script exists in package.json. Fall back to bun test if verify:ci is absent. If neither exists, mark as skipped.
Record: exit code, stdout, stderr, duration.
Read key files and apply the scoring rubric:
Load the outfitter-atlas skill to cross-check against documented patterns. Note any inconsistencies between what the docs say and what the scaffold produces.
Apply scoring rubric from references/scoring-rubric.md:
Every score MUST cite specific files, line numbers, or command output. No hand-waving.
Write report.json to the preset directory following the schema in references/report-schema.md.
Include:
skipped with reason, but still explore files and score what's observable.references/report-schema.md — Full JSON schema for report.jsonreferences/scoring-rubric.md — Behavioral anchors for each dimensionreferences/preset-expectations.md — Per-preset expected files and common issuesPatterns for @outfitter/daemon including lifecycle management, IPC communication, health checks, and PID files. Use when building background services, daemons, or when "daemon", "IPC", "health check", "background service", or "@outfitter/daemon" are mentioned.
Creates handlers, CLI commands, MCP tools, and daemon services following Outfitter Dev Kit conventions. Use when adding new components to a project, scaffolding code, or when "create handler", "new command", "add tool", or "daemon service" are mentioned.
Deep patterns for @outfitter/mcp including tool registration, Zod schemas, resources, and server configuration. Use when building MCP servers, registering tools, defining resources, or when "MCP server", "MCP tool", "registerTool", or "@outfitter/mcp" are mentioned.
Generates patterns, templates, and guides for @outfitter/* packages. Covers transport-agnostic handler systems, Result types, error taxonomy, and package APIs. Use when working with @outfitter/*, Result types, Handler contract, error taxonomy, or when Result, Handler, ValidationError, NotFoundError, OutfitterError, or package names like contracts, cli, mcp, schema, tui, daemon, config, logging are mentioned.
Verify Outfitter compliance in a codebase. Scans for anti-patterns (throws, console, hardcoded paths) and produces a severity-ranked compliance report. Use for pre-commit checks, code review, or migration validation.
Submit feedback to the Outfitter team via GitHub issues. Use after discovering bugs, missing features, unclear docs, or improvement opportunities in @outfitter/* packages.