How do I install the Add To Project skill?

Run npx skillmds@latest add marve10s/add-to-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 Add To 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 Add To 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 Add To Project free to use?

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

Who published Add To Project?

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

Add To Project by marve10s — Agent Skill

Name: Add To Project
Author: marve10s

Add To Project

Add capabilities, addons, deployment targets, generated CI, services, or stack updates to an existing Better Fullstack project. Use when the current repo has bts.jsonc or the user asks to extend a generated project. Prefer bfs_plan_stack_update and bfs_apply_stack_update; use legacy addon tools only for addon/deploy-only flows.

marve10s Updated Sep 17, 2026

File contents

Add to an Existing Better Fullstack Project

Use the Better Fullstack MCP server for existing-project updates. Do not hand-edit generated stack metadata or guess which template files belong to a capability.

Workflow

Confirm the project directory and ensure it contains bts.jsonc.
Call bfs_get_guidance and bfs_get_schema.
For capability changes, call bfs_plan_stack_update with the target projectDir and requested stack fields.
Review the preview, including blockers, file changes, dependency changes, env changes, and compatibility adjustments.
Call bfs_apply_stack_update only when the plan is acceptable.
For legacy addon/deploy-only changes, call bfs_plan_addition before bfs_add_feature.
Report changed files and the exact install/test commands.

Rules

Keep update semantics preview-first.
Prefer additive updates first: generated CI, docs, observability, email, search, vector DB, file storage, rate limiting, and mobile capabilities.
Treat database, ORM, auth, API, and payment-provider swaps as risky and make compatibility changes explicit.
Set installs disabled unless the user asks for dependency installation.
Do not start a dev server.

CLI-only fallback

If the Better Fullstack MCP tools are unavailable, inspect the current flags with npx -y create-better-fullstack@latest add --help, then run the explicit add command with --project-dir <path> --dry-run --no-install. Review that preview before rerunning without --dry-run. Do not guess option names or hand-edit generated stack metadata.

Frequently asked questions