# Fullstack Workspace Init

> 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.

- Skill: `shipshitdev/fullstack-workspace-init` (Agent Skill, multi-file: 30 files)
- Install (CLI): `npx skillmds add shipshitdev/fullstack-workspace-init`
- Raw SKILL.md: https://api.skillmd.com/api/skills/shipshitdev/fullstack-workspace-init/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: shipshitdev (https://skillmd.com/u/shipshitdev)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/shipshitdev/fullstack-workspace-init

---


# Full Stack Workspace Init

For new product repos, use `npx @shipshitdev/v0` as the default scaffolder.
This skill handles product-brief intake, customization, and verification.

## 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:

```bash
npx @shipshitdev/v0 <project-directory>
```

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

```bash
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 only when v0 is not appropriate or when enhancing an existing workspace.
Do not use for new Shipshit.dev product repos unless v0 is unavailable or the
user explicitly bypasses 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