How do I install the Scaffold Project skill?

Run npx skillmds@latest add marve10s/scaffold-project in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Scaffold Project safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Scaffold Project?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Scaffold Project free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Scaffold Project?

marve10s (@marve10s) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Scaffold Project by marve10s — Agent Skill

Name: Scaffold Project
Author: marve10s

Scaffold Project

Scaffold a new app, API, backend, fullstack project, mobile app, polyglot service, monorepo, or starter with Better Fullstack. Use when the user wants to create, start, bootstrap, initialize, or generate a project from a stack description. Prefer the bundled Better Fullstack MCP server: guidance, schema, compatibility, plan, then create.

marve10s a2ad019 2.7 KB Updated Sep 17, 2026

File contents

Scaffold a Better Fullstack Project

Use the Better Fullstack MCP server as the source of truth. Do not hand-write package files, framework folders, auth wiring, database wiring, or generated project structure.

Workflow

Resolve intent. If major choices are unclear, ask briefly or pick conservative defaults and state them.
Call bfs_get_guidance.
Call bfs_get_schema for the current allowed values. Do not rely on a stale option list.
Build a full explicit config. Use "none", empty arrays, and booleans rather than omitting important fields.
Call bfs_check_compatibility.
Call bfs_plan_project. Review the dry-run output and compatibility adjustments.
Call bfs_create_project only after the plan matches the user request.
Report the selected stack, project directory, and exact install/test/dev commands.

Rules

Set install: false for agent scaffolding unless the user explicitly asks to install dependencies.
Use packageManager: "bun" when the user or current repo expects Bun.
Use aiDocs: ["agents-md"] for reusable projects and aiDocs: ["none"] for benchmarks or throwaway scaffolds.
Prefer stack graph parts for explicit multi-ecosystem stacks, but use MCP schema fields when they communicate the request more clearly.
Treat compatibility adjustments as user-visible decisions.
Do not start a dev server.

Common Stack Hints

React + Vite: frontend: ["react-vite"]
Next.js fullstack: frontend: ["next"], backend: "self"
Hono API: backend: "hono", runtime: "bun" or "node"
SQLite + Drizzle: database: "sqlite", orm: "drizzle"
Python API: ecosystem: "python", then choose pythonWebFramework and related Python fields
Rust API: ecosystem: "rust", then choose rustWebFramework and related Rust fields

CLI-only fallback

If the Better Fullstack MCP tools are unavailable, inspect the current flags with npx -y create-better-fullstack@latest create --help, then run the explicit scaffold command with --dry-run --no-install --no-git. Review that preview before rerunning without --dry-run. Do not guess option names or hand-write the scaffold.

Final Response

Say what command/tool path was used, what compatibility adjustments were made, where the project was created, and what the next commands are. Never claim dependencies were installed when install: false was used.

---name: scaffold-projectdescription: Scaffold a new app, API, backend, fullstack project, mobile app, polyglot service, monorepo, or starter with Better Fullstack. Use when the user wants to create, start, bootstrap, initialize, or generate a project from a stack description. Prefer the bundled Better Fullstack MCP server: guidance, schema, compatibility, plan, then create.---# Scaffold a Better Fullstack ProjectUse the Better Fullstack MCP server as the source of truth. Do not hand-write package files,framework folders, auth wiring, database wiring, or generated project structure.## Workflow1. Resolve intent. If major choices are unclear, ask briefly or pick conservative defaults and state them.2. Call `bfs_get_guidance`.3. Call `bfs_get_schema` for the current allowed values. Do not rely on a stale option list.4. Build a full explicit config. Use `"none"`, empty arrays, and booleans rather than omitting important fields.5. Call `bfs_check_compatibility`.6. Call `bfs_plan_project`. Review the dry-run output and compatibility adjustments.7. Call `bfs_create_project` only after the plan matches the user request.8. Report the selected stack, project directory, and exact install/test/dev commands.## Rules- Set `install: false` for agent scaffolding unless the user explicitly asks to install dependencies.- Use `packageManager: "bun"` when the user or current repo expects Bun.- Use `aiDocs: ["agents-md"]` for reusable projects and `aiDocs: ["none"]` for benchmarks or throwaway scaffolds.- Prefer stack graph parts for explicit multi-ecosystem stacks, but use MCP schema fields when they communicate the request more clearly.- Treat compatibility adjustments as user-visible decisions.- Do not start a dev server.## Common Stack Hints- React + Vite: `frontend: ["react-vite"]`- Next.js fullstack: `frontend: ["next"]`, `backend: "self"`- Hono API: `backend: "hono"`, `runtime: "bun"` or `"node"`- SQLite + Drizzle: `database: "sqlite"`, `orm: "drizzle"`- Python API: `ecosystem: "python"`, then choose `pythonWebFramework` and related Python fields- Rust API: `ecosystem: "rust"`, then choose `rustWebFramework` and related Rust fields## CLI-only fallbackIf the Better Fullstack MCP tools are unavailable, inspect the current flags with`npx -y create-better-fullstack@latest create --help`, then run the explicit scaffold command with`--dry-run --no-install --no-git`. Review that preview before rerunning without `--dry-run`. Do notguess option names or hand-write the scaffold.## Final ResponseSay what command/tool path was used, what compatibility adjustments were made, where the project wascreated, and what the next commands are. Never claim dependencies were installed when `install:false` was used.

Frequently asked questions