Imported from shipshitdev/skills (
skills/scaffold/SKILL.md). Install upstream withnpx skills add shipshitdev/skills --skill scaffold. Copyright stays with the author.
Scaffold
Generate incremental code inside an existing repository, following local codebase patterns.
Contract
Inputs:
- Scaffold target type and name
- Repository root
- Existing examples to follow
Outputs:
- Files created or modified
- Patterns copied from existing code
- Manual follow-up steps and tests to run
Creates/Modifies:
- Local source, test, and export files for the requested module/component/package
- Does not create a full product repo
External Side Effects:
- None
Confirmation Required:
- Before overwriting existing files
- Before introducing a new pattern when fewer than 3 matching examples exist
Delegates To:
project-init-orchestratorwhen the user needs a whole new projectfullstack-workspace-init/npx @shipshitdev/v0when the user needs a new Shipshit.dev product repo- Framework-specific skills such as
nestjs-expert,react-patterns,shadcn, ortypescript-expert
Steps
-
Determine what to scaffold from arguments:
endpoint [name]— New API endpoint (controller + service + module)module [name]— New backend module with full structurecomponent [name]— New UI component with proper typingpackage [name]— New shared packagecollection [name]— New database collection with schema + service
-
Find 3+ existing examples:
- Search for similar implementations in the codebase
- Identify the exact patterns used (imports, naming, file structure)
- Note any module-specific conventions
-
Scaffold based on type:
API Endpoint
- Controller, Service, Module in appropriate directory
- Follow: auth guards, tenant filtering, serializer response
UI Component
- Component file with proper typing
- Props interface in dedicated props file
- Export from barrel
Shared Package
- Directory with package.json
- Barrel export:
src/index.ts - TypeScript config
Database Collection
- Schema/model file
- Interface in shared interfaces package
- Serializer in shared serializers package (if applicable)
-
Apply critical rules:
- Interfaces in dedicated files, not inline
- Path aliases, not relative imports
- Tenant/organization filter in all queries (if applicable)
-
Report: List all files created and any manual steps needed
Arguments
- Required: what to scaffold (e.g., "endpoint tasks", "component ImageGrid", "collection workflows")