How do I install the Forge Fullstack skill?

Run npx skillmds@latest add forgeyclap/forge-fullstack-2 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 Forge Fullstack 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 Forge Fullstack?

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 Forge Fullstack free to use?

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

Who published Forge Fullstack?

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

Forge Fullstack by forgeyclap — Agent Skill

Name: Forge Fullstack
Author: ForgeyClap

Forge Fullstack

Forge playbook for full-stack apps with frontend + backend + database + auth. Use when building a complete application, web app, SaaS, CRUD app, or data-backed dashboard with a database and login — keywords: full-stack, app, SaaS, backend, API, database, Postgres, Supabase, auth, login, JWT, session, signup, CRUD, end-to-end. Coordinates frontend, backend, DB, and auth specialists across git worktrees.

ForgeyClap Updated Sep 22, 2026

File contents

Forge playbook — Full-stack app

Do not duplicate ECC skills — defer to: make-plan/do (planning+execution), using-git-worktrees (parallel isolation), subagent-driven-development. Orchestration only.

Hard rules

Auth on every protected route, enforced server-side (authn + authz).
Input validation on every endpoint; never trust client data.
Secrets in env + .env.example placeholders; no secrets in the client bundle.
DB migrations reviewed by database-reviewer and reversible.
Auth/secret/DB changes are a required Codex review area — force /codex:adversarial-review.

Team (conditional by stack/level)

Lead: architect + planner.
Frontend: react-reviewer / vue-reviewer.
Backend: fastapi-reviewer / django-reviewer (Python) or typescript-reviewer / go-reviewer (by stack).
Data: database-reviewer (Postgres/Supabase).
Cross-cutting: security-reviewer, tdd-guide, e2e-runner / production-validator.

Skills / commands / MCP

make-plan→do, using-git-worktrees, language build/test commands (/react-build, /python-review, etc.), /test-coverage, security-reviewer. Supabase/Shopify MCP via ToolSearch if relevant.

Fan-out & flow

L3 standard; L4 for a platform / prod client delivery (phased, review after each phase). Serial: plan → DB schema + API contract first → integration → e2e → security → review. Parallel: frontend ∥ backend ∥ schema in separate worktrees; you integrate. Don't let two agents write the same tree.

Domain gates

Auth flow tested (signup/login/logout/refresh); validation on all endpoints; migrations clean on a fresh DB; e2e green; no folder mixing.

Ship-readiness (unique)

Migrations run clean on a fresh DB; auth flow verified; .env.example complete; no secrets in repo; rollback/seed documented; dev/preview by default (production needs explicit user approval). The ship-readiness full-stack/auth checklist is advisory; optionally run codex-reviewer (Codex) on auth/migration code — not a blocker.

---name: forge-fullstack-2description: Forge playbook for full-stack apps with frontend + backend + database + auth. Use when building a complete application, web app, SaaS, CRUD app, or data-backed dashboard with a database and login — keywords: full-stack, app, SaaS, backend, API, database, Postgres, Supabase, auth, login, JWT, session, signup, CRUD, end-to-end. Coordinates frontend, backend, DB, and auth specialists across git worktrees.---# Forge playbook — Full-stack app**Do not duplicate ECC skills — defer to:** `make-plan`/`do` (planning+execution), `using-git-worktrees` (parallel isolation), `subagent-driven-development`. Orchestration only.## Hard rules- Auth on **every** protected route, enforced server-side (authn + authz).- Input validation on every endpoint; never trust client data.- Secrets in env + `.env.example` placeholders; no secrets in the client bundle.- DB migrations reviewed by `database-reviewer` and reversible.- Auth/secret/DB changes are a **required Codex review area** — force `/codex:adversarial-review`.## Team (conditional by stack/level)- Lead: `architect` + `planner`.- Frontend: `react-reviewer` / `vue-reviewer`.- Backend: `fastapi-reviewer` / `django-reviewer` (Python) or `typescript-reviewer` / `go-reviewer` (by stack).- Data: `database-reviewer` (Postgres/Supabase).- Cross-cutting: `security-reviewer`, `tdd-guide`, `e2e-runner` / `production-validator`.## Skills / commands / MCP`make-plan`→`do`, `using-git-worktrees`, language build/test commands (`/react-build`, `/python-review`, etc.), `/test-coverage`, `security-reviewer`. Supabase/Shopify MCP via ToolSearch if relevant.## Fan-out & flowL3 standard; L4 for a platform / prod client delivery (phased, review after each phase).**Serial:** plan → DB schema + API contract first → integration → e2e → security → review.**Parallel:** frontend ∥ backend ∥ schema in **separate worktrees**; you integrate. Don't let two agents write the same tree.## Domain gatesAuth flow tested (signup/login/logout/refresh); validation on all endpoints; migrations clean on a fresh DB; e2e green; no folder mixing.## Ship-readiness (unique)Migrations run clean on a fresh DB; auth flow verified; `.env.example` complete; no secrets in repo; rollback/seed documented; dev/preview by default (production needs explicit user approval). The `ship-readiness` full-stack/auth checklist is advisory; optionally run `codex-reviewer` (Codex) on auth/migration code — not a blocker.

Frequently asked questions