agentsclimarketplace

Forge fullstack

Skill ForgeyClap/claude-forge/plugins/forge/skills/forge-fullstack

Zero-dependency multi-agent build, automation and review system for Claude Code. 18 agents, 23 skills, a live per-project dashboard, and a /setup-forge onboarding wizard. One command: /forge.

Install
npx -y skills add ForgeyClap/claude-forge --skill forge-fullstack

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.5 KB, 517 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most databases sql skills give in 517 tokens

Counted across 589 of the 662 authors here whose files we hold, read 2026-08-07

  • Use parameterized queriesin 37 of 589, across 34 files
  • Use timestamptz for timestampsin 30 of 589, across 14 files
  • Index foreign keysin 29 of 589, across 18 files
  • Create indexes concurrentlyin 29 of 589, across 24 files
  • Use numeric type for moneyin 25 of 589, across 8 files
  • Use cursor pagination instead of offsetin 24 of 589, across 17 files
  • Select only required columnsin 24 of 589, across 20 files
  • Add indexes manually on foreign key columnsin 22 of 589, across 12 files
  • Normalize to third normal formin 19 of 589, across 10 files
  • Configure connection poolingin 19 of 589, across 17 files
  • Put equality columns before range columns in indexesin 18 of 589, across 10 files
  • Read individual rule files for detailed explanationsin 18 of 589, across 4 files

Said here and by no other author read

  • enforce server-side auth on every protected route
  • force adversarial review on auth and database changes
  • plan database schema and API contracts before integration
  • build frontend and backend in separate worktrees
  • test the complete auth flow
  • run migrations clean on a fresh database

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.