Fullstack workspace init — scaffold Shipshit.dev product repos via the v0 generator (short listing)
Short listing — license not verifiable; scaffold new fullstack product workspaces through npx @shipshitdev/v0, then customize and verify: intake contract, default v0 route, legacy manual route
- What
- Short listing — license not verifiable; scaffold new fullstack product workspaces through npx @shipshitdev/v0, then customize and verify: intake contract, default v0 route, legacy manual route
- Cost
- Free
- Needs
- a product brief or scope for the new product repo; Node.js with npx for running the v0 generator
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Selected by Skill Harbor — short listing (the discovery manifest records no license for this skill — the manifest makes faith, so no content is reproduced beyond this summary; the repo frontmatter carries no license field): @shipshitdev's fullstack-workspace-init skill — a scaffolding workflow for new Shipshit.dev full-stack product repos: the default route runs the v0 generator (npx @shipshitdev/v0, with non-interactive flags for scope, agent choice, app surfaces, and routes), wrapped in a contract (inputs like product brief and agent-handoff preference, outputs like the generated workspace summary and quality gate status, confirmation gates before creating GitHub repos or touching non-empty directories), plus a legacy manual route (Next.js 16 + React 19 + TypeScript frontend, NestJS 11 + MongoDB + Clerk Auth backend, Vitest/Biome/Husky/GitHub Actions) for cases where v0 is unavailable, with references for templates, test configs, CI workflows, architecture, and coding standards. Honest caveats: license terms not verifiable — short listing with a link only; tied to the Shipshit.dev stack and its v0 tooling, not a generic scaffolder. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a product brief or scope for the new product repo; Node.js with npx for running the v0 generator Install "Fullstack workspace init — scaffold Shipshit.dev product repos via the v0 generator (short listing)" for me. It gives my agent @shipshitdev's workspace-scaffolding workflow: intake the product brief (project directory, name, scope, app surfaces, routes, agent handoff preference), run the default v0 route (npx @shipshitdev/v0 with scope/agent/apps/routes flags), customize and verify the generated Bun/Turbo workspace, respect the confirmation gates (GitHub repo creation, non-empty directories, overwriting generated files), and fall back to the legacy manual route (Next.js + NestJS + MongoDB + Clerk) when v0 is unavailable. IMPORTANT: the license terms were not verifiable (the discovery manifest records no license; the repo frontmatter carries no license field) — fetch from the link only, reproduce nothing beyond the link, and read the license terms yourself before reuse. Repository: https://github.com/shipshitdev/skills/blob/main/bundles/workspace/skills/fullstack-workspace-init/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "fullstack-workspace-init". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. read the license terms before reuse, prepare the product brief, choose codex/claude/skip-agent handoff). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.