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
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.