Skip to content

lidge-jun/codexclaw / plugins/codexclaw/skills/dev-scaffolding

cxc-dev-scaffolding

Verified

Use for project/module setup and docs. Triggers: scaffold, structure audit, architecture docs, API docs, monorepo setup, 스캐폴딩, 새 프로젝트, 새 기능, 구조 점검, 모듈 추가.

references/scaffold-verification.md

View on GitHub
## 12. Audit

Run the scaffold audit if one is available for the repo (e.g. `bash <SKILL_DIR>/scripts/scaffold-audit.sh [project-path]`) to check structural compliance. Audit checks should reflect the project's own conventions — covering feature-based structure, colocation, public boundary exports (dev-architecture §5), optional source-of-truth docs, `.env` safety, file length, and `AGENTS.md` where those apply.

## Scaffold Contract (SCAFFOLD-CONTRACT-01, DEFAULT)

Source: sol research (microsoft/apm, HoangNguyen0403/agent-skills-standard).

A scaffold operation must be deterministic and verifiable:

1. **Manifest**: before generating files, produce a list of files that will be
   created/modified with their purpose. Show it to the user or record it.
2. **Idempotency**: running the scaffold twice on the same input should not
   create duplicates or corrupt existing files.
3. **Template provenance**: record which template or pattern was used and its
   version/commit so the scaffold can be reproduced.
4. **Dry run**: for C3+ scaffolds, offer a dry-run mode that shows what would
   be created without writing files.

## Post-Scaffold Verification (SCAFFOLD-VERIFY-01, DEFAULT)

Apply the following only to a runnable project scaffold and only for supported commands.
Documentation scaffolds use link/structure/contract checks; module scaffolds use affected
checks. Do not install dependencies, start servers, or run a broad suite merely to validate prose.
For a runnable scaffold, verify usability within the authorized environment:

1. `npm install` / `pip install` / equivalent dependency installation succeeds
2. `npm run build` / `cargo build` / equivalent build succeeds
3. `npm test` / `pytest` / equivalent test suite passes (even if only a smoke test)
4. Linter runs clean (or with only pre-existing warnings)
5. Dev server starts and responds (for web projects)
6. A second scaffold run on the same input does not break the first (idempotency)

Failures in any of these steps mean the scaffold is incomplete. Fix before
claiming done.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall