bundles/workspace/skills/fullstack-workspace-init/SKILL.md
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.
npx skillsauth add shipshitdev/library fullstack-workspace-initInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
For new product repos, use npx @shipshitdev/v0 as the default scaffolder.
This skill handles product-brief intake, customization, and verification.
Inputs:
Outputs:
Creates/Modifies:
.agents/skills, .agents/memory, .claude, .codex, apps, packages, and .v0 files generated by v0External Side Effects:
apps/webConfirmation Required:
Delegates To:
project-init-orchestrator for route selectionagent-folder-init only for existing repos not generated by v0testing-cicd-init, linter-formatter-init, and shadcn-setup for repair/customizationscaffold for incremental modules inside the generated workspaceFor 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.
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/templates/ - Code generation templates
service.spec.template.ts - NestJS service unit test templatecontroller.spec.template.ts - NestJS controller unit test templatee2e.spec.template.ts - E2E test template with supertest + MongoDB Memory Servercomponent.spec.template.tsx - React component test templatehook.spec.template.ts - React hook test templatetest-setup.template.ts - Frontend test setup with Clerk mocksreferences/vitest.config.ts - Backend Vitest configuration (80% coverage)references/vitest.config.frontend.ts - Frontend Vitest configuration (jsdom)references/github-actions/ci.yml - CI/CD workflowreferences/architecture-guide.md - Architectural decisionsreferences/coding-standards.md - Coding rulesdevelopment
TypeScript refactoring and modernization guidelines from a principal specialist perspective. This skill should be used when refactoring, reviewing, or modernizing TypeScript code to ensure type safety, compiler performance, and idiomatic patterns. Triggers on tasks involving TypeScript type architecture, narrowing, generics, error handling, or migration to modern TypeScript features.
tools
Resolves TypeScript and JavaScript problems across type-level programming, performance, monorepo management, migration, and modern tooling. Invoke when diagnosing "type instantiation excessively deep" errors, migrating JS to TS, configuring strict tsconfig, debugging module resolution, or choosing between Biome/ESLint/Turborepo/Nx.
tools
Turborepo monorepo build system guidance. Triggers on: `turbo.json`, task pipelines, `dependsOn`, caching, remote cache, the `turbo` CLI, `--filter`, `--affected`, CI optimization, environment variables, internal packages, monorepo structure, and package boundaries. Use when the user configures tasks or workflows, creates packages, sets up a monorepo, shares code between apps, runs changed packages, debugs cache behavior, or works in an `apps/` plus `packages/` workspace.
tools
Provides Tailwind CSS v4 performance optimization and best practices guidelines. Triggers when writing, reviewing, or refactoring Tailwind CSS v4 code; when working with Tailwind configuration, @theme directive, utility classes, responsive design, dark mode, container queries, or CSS generation optimization.