feature-scaffolder — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited feature-scaffolder (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Before generating any output, read config/defaults.md and adapt all patterns, imports, and code examples to the user's configured stack.
This agent scaffolds a complete feature with shared types between backend and frontend. Follow this sequence:
Ask the user: feature name, entity/resource name, fields (or read from existing Prisma model if available).
Create a types.ts file with the entity interface, create/update input types, and API response types. All subsequent files import from this. This is the single source of truth.
// src/types/{feature}.ts
export interface {Entity} { ... }
export interface Create{Entity}Input { ... }
export interface Update{Entity}Input { ... }
export interface {Entity}ListResponse {
data: {Entity}[];
pagination: { page: number; limit: number; total: number; totalPages: number };
}Run the zod-schema-generator skill to create validation schemas from the shared types. Schemas import and align with the types from step 2.
Run the nextjs-route-generator skill to create the API route, importing the Zod schemas for validation and shared types for response typing.
Routes import from:
Run the react-component-generator skill to create the frontend component, importing shared types for props and API response handling.
Components import from:
Run the typescript-refactorer skill on all generated files as a final quality pass.
Check that all imports resolve correctly across generated files. If any file references a type or schema that doesn't exist, fix it before delivering.
Produce a file manifest showing all generated files and their dependency relationships:
# Feature Scaffolding Complete: {feature-name}
## File Manifest
src/types/{feature}.ts ← shared types (source of truth)
src/schemas/{feature}.ts ← Zod schemas (imports types)
app/api/{feature}/route.ts ← list + create (imports schemas + types)
app/api/{feature}/[id]/route.ts ← get + update + delete (imports schemas + types)
src/components/{feature}/ ← UI components (imports types)
## Dependency Graph
types.ts → schemas.ts → route.ts
types.ts → Component.tsxskills/zod-schema-generatorskills/nextjs-route-generatorskills/react-component-generatorskills/typescript-refactorer~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.