// This skill should be used when starting a new Rockets SDK project, setting up a fresh API, or initializing from the rockets-starter template. Automates clone, env setup, dependency install, and build/test verification.
This skill should be used when adding ACL to an existing module, modifying role-based access rules, debugging 403 errors, configuring ownership checks, or writing Access Query Services manually. For new modules, use rockets-crud-generator with ACL config instead — it generates all ACL wiring automatically.
This skill should be used when generating an entire Rockets SDK project from a spec, bootstrapping multiple entities at once, or when the user has a plan.json file. Orchestrates wave-based generation with dependency ordering and validation gates. Works sequentially by default; supports Agent Teams for parallel execution. Requires rockets-crud-generator.
This skill should be used when implementing business logic beyond standard CRUD — state machines, approval workflows, event-driven automation, notifications, file uploads, external API integration, or cross-entity orchestration. Use after CRUD modules are generated. Also covers the foundational rule that application services must inject model services, never repositories.
This skill should be used when the user asks to generate a CRUD module, create a new entity, scaffold a domain object, add a new resource with endpoints, or create a junction table. Generates complete Rockets SDK modules including TypeORM entities, NestJS modules, controllers, services, DTOs, interfaces, and ACL wiring using generate.js, integrate.js, and validate.js scripts.
Diagnose common Rockets SDK startup/build/security wiring issues with executable checks and fix-ready output. Use when an app fails to boot, build, or enforce ACL as expected.
| name | rockets-project-bootstrap |
| description | This skill should be used when starting a new Rockets SDK project, setting up a fresh API, or initializing from the rockets-starter template. Automates clone, env setup, dependency install, and build/test verification. |
Use this skill to start a new Rockets project with deterministic setup commands.
Default template repository:
git@github.com:btwld/rockets-starter.git
# Full bootstrap (clone + env + install + build/test)
node skills/rockets-project-bootstrap/scripts/bootstrap.js \
--repo git@github.com:btwld/rockets-starter.git \
--dest ../rockets-starter-app \
--install --run-build --run-test
# Bootstrap existing local folder (skip clone)
node skills/rockets-project-bootstrap/scripts/bootstrap.js \
--skip-clone \
--dest /path/to/existing/project \
--install --run-build --run-test
# Dry run
node skills/rockets-project-bootstrap/scripts/bootstrap.js --dest ../rockets-starter-app --dry-run
--skip-clone)..env exists (copies from .env.example when available).yarn/pnpm/npm) from lockfile.--install is provided.build and test scripts when requested and available.The starter template must be correct out of the box. The generators add to it — they never fix it.
Run validate.js --project <path> after bootstrap to verify compliance.
apps/api/src/
├── main.ts # Swagger with project-specific title
├── app.module.ts # RocketsAuthModule + CrudModule.forRoot({})
├── app.acl.ts # AppRole + AppResource enums, base grants
├── access-control.service.ts # Implements AccessControlServiceInterface
├── config/
│ ├── typeorm.settings.ts # Postgres config, entities array
│ ├── rockets-auth.settings.ts # Auth config, project-specific email
│ └── rockets.settings.ts # App config
├── entities/
│ ├── index.ts # Barrel export for all entities
│ ├── user.entity.ts # extends UserPostgresEntity
│ ├── role.entity.ts # extends RolePostgresEntity
│ ├── user-otp.entity.ts # extends OtpPostgresEntity or CommonPostgresEntity
│ ├── user-metadata.entity.ts # extends CommonPostgresEntity
│ ├── user-role.entity.ts # extends CommonPostgresEntity
│ ├── federated.entity.ts # extends FederatedPostgresEntity or CommonPostgresEntity
│ └── invitation.entity.ts # extends InvitationPostgresEntity or CommonPostgresEntity
├── adapters/
│ ├── user.adapter.ts # @InjectRepository(UserEntity)
│ └── user-metadata.adapter.ts # @InjectRepository(UserMetadataEntity)
├── modules/
│ ├── user/dto/ # User DTOs (used by RocketsAuthModule)
│ └── role/ # Role CRUD (adapter, DTO)
└── migrations/ # Initial migration for all auth tables
*PostgresEntity or CommonPostgresEntity. NO *SqliteEntity base classes anywhere.src/entities/. NO duplicate entity files in modules/*/entities/.main.ts Swagger title, typeorm.settings.ts DB name, rockets-auth.settings.ts email MUST match the project name. NO placeholder names from other projects.app.module.ts imports (required before any CrudModule.forFeature()).uuid, timestamp, NOT datetime)..env.example — MUST exist with all required environment variables documented.The generators (generate.js + integrate.js) assume:
src/entities/index.ts exists (adds exports)src/config/typeorm.settings.ts or src/typeorm.settings.ts has an entities: [...] arraysrc/app.module.ts has @Module({ imports: [...] }) with bracket structuresrc/app.acl.ts has AppResource enum and acRules variable (if using ACL)If any of these are missing or malformed, integrate.js will warn but not fail.
node skills/rockets-project-bootstrap/scripts/smoke-test.js
The smoke test validates setup logic on a local temporary fixture (no network).