Agent-Skills.md

Agent Skills: Full Stack Workspace Init

Scaffold a production-ready full-stack monorepo with working MVP features, tests, and CI/CD. Generates complete CRUD functionality, Clerk authentication, and quality gates that run immediately with `bun dev`.

UncategorizedID: shipshitdev/library/fullstack-workspace-init

Repository

shipshitdev/library
shipshitdev
151

Install this agent skill to your local

pnpm dlx add-skill https://github.com/shipshitdev/library/tree/HEAD/bundles/workspace/skills/fullstack-workspace-init

Skill Files

Browse the full folder contents for fullstack-workspace-init.

Download Skill

Loading file tree…

bundles/workspace/skills/fullstack-workspace-init/SKILL.md

Skill Metadata

Name
fullstack-workspace-init
Description
Initialize Shipshit.dev full-stack product workspaces through npx @shipshitdev/v0, then customize and verify the generated repo. Use for new product scaffolds or post-v0 workspace setup.

Full Stack Workspace Init

Create a Shipshit.dev product workspace. For new product repos, use npx @shipshitdev/v0 as the default scaffolder and treat this skill as the product-brief, customization, and verification layer.

Contract

Inputs:

  • Project directory and product name
  • Product scope or PRD-style brief
  • Selected app surfaces and product routes
  • Agent handoff preference: codex, claude, or skip-agent

Outputs:

  • v0 command or interactive route used
  • Generated workspace summary
  • Quality gate and startup status
  • Follow-up tasks for app-specific customization

Creates/Modifies:

  • New Bun/Turbo product repo when v0 runs
  • .agents/skills, .agents/memory, .claude, .codex, apps, packages, and .v0 files generated by v0
  • App-specific files only when customizing after v0 generation

External Side Effects:

  • May install dependencies and start apps/web
  • May create GitHub repo/issues only when GitHub flags are explicitly enabled

Confirmation Required:

  • Before creating a GitHub repo or issue
  • Before running in a non-empty directory
  • Before overwriting generated app files after v0 completes

Delegates To:

  • project-init-orchestrator for route selection
  • agent-folder-init only for existing repos not generated by v0
  • testing-cicd-init, linter-formatter-init, and shadcn-setup for repair/customization
  • scaffold for incremental modules inside the generated workspace

Default v0 Route

For new Shipshit.dev product repos, run:

npx @shipshitdev/v0 <project-directory>

Use non-interactive mode when the user gives enough detail:

npx @shipshitdev/v0 <project-directory> \
  --scope "<product scope>" \
  --agent codex \
  --apps web,app,desktop,mobile,extension,cli \
  --routes overview,new-task,search,inbox,activities \
  --no-github

Use --skip-agent, --no-install, and --no-start for CI/smoke tests or when the user only wants the scaffold written.

Legacy Manual Route

Use the manual guidance below only when v0 is not appropriate or when enhancing an existing workspace that already has its core scaffold.

Do not use this route for a new Shipshit.dev product repo unless v0 is unavailable or the user explicitly asks to bypass it.

Stack: Next.js 16 + React 19 + TypeScript + Tailwind + @agenticindiedev/ui (frontend), NestJS 11 + MongoDB + Clerk Auth + Swagger (backend), Vitest 80% coverage + Biome + Husky + GitHub Actions CI/CD, Bun package manager.

Load references/legacy-manual-route.md for the full step-by-step workflow, generated structure, key code patterns, and development commands.

References

  • references/templates/ - Code generation templates
    • service.spec.template.ts - NestJS service unit test template
    • controller.spec.template.ts - NestJS controller unit test template
    • e2e.spec.template.ts - E2E test template with supertest + MongoDB Memory Server
    • component.spec.template.tsx - React component test template
    • hook.spec.template.ts - React hook test template
    • test-setup.template.ts - Frontend test setup with Clerk mocks
  • references/vitest.config.ts - Backend Vitest configuration (80% coverage)
  • references/vitest.config.frontend.ts - Frontend Vitest configuration (jsdom)
  • references/github-actions/ci.yml - CI/CD workflow
  • references/architecture-guide.md - Architectural decisions
  • references/coding-standards.md - Coding rules