StackFit Skills

StackFit is a provider-neutral Agent Skills repository for making production service decisions when an application is ready to launch. It inspects the repository, checks what production requires, then composes current guidance from official provider skills such as Cloudflare, Neon, Supabase, and Vercel.

StackFit does not maintain a provider catalog, copy volatile prices, or replace provider-specific skills. It owns the neutral recommendation workflow: current-state discovery, production requirements, hard constraints, evidence quality, service composition, and release verification.

Skills

• ship-check audits release readiness and routes every unresolved production decision to the StackFit skill that owns it. Start here.
• prod-db recommends one production database for a project that is about to ship.
• deploy-plan recommends a minimal production deployment topology and the services needed to operate it.
• auth-plan assesses the current authentication and recommends one production auth approach.
• storage-plan finds file handling that will not survive production compute and recommends one object storage service.
• env-secrets inventories configuration, detects exposed secrets, and designs development, preview, and production separation.
• cost-fit estimates monthly launch cost, judges free-tier fitness, and specifies spending guardrails.

Install

Install every StackFit skill from a clone:

npx skills add .

Or install one skill:

npx skills add . --skill ship-check
npx skills add . --skill prod-db

Or copy a directory such as skills/prod-db into the skills directory used by your agent.

Install the official provider skills that are relevant to the comparison:

npx skills add cloudflare/skills --skill cloudflare
npx skills add cloudflare/skills --skill wrangler
npx skills add neondatabase/agent-skills --skill neon-postgres
npx skills add supabase/agent-skills --skill supabase
npx skills add vercel-labs/agent-skills --skill vercel-optimize
npx skills add vercel-labs/agent-skills --skill deploy-to-vercel

Provider skills are optional. When one is unavailable, StackFit uses current official documentation and identifies the missing provider skill rather than silently installing it.

Use

Example prompts:

Use $ship-check to tell me everything that must be decided or fixed before I can release this project.

Use $prod-db to recommend a production database before I release this project.

We are ready to deploy. Check whether the current development database is safe for production and recommend what to use.

Choose between Neon Postgres, Supabase Postgres, and Cloudflare D1 for this project's production release.

Use $deploy-plan to inspect this project and suggest the production services and deployment topology for release.

Should this app ship on Cloudflare, Vercel, or another platform? Recommend a stack but do not deploy it yet.

Is my login and session handling safe to ship, or should I move to a managed auth provider?

Use $storage-plan to check whether my file uploads will survive production and recommend where they should live.

Use $env-secrets to find anything secret committed to this repo and design my production environment configuration.

Use $cost-fit to estimate what this stack costs per month at launch and which free tiers are safe.

The current database is retained when it is production-safe and fits the release requirements. A local or development-only database is treated as implementation evidence, not as a production default.

Repository layout

Every skill follows the same shape:

skills/
  <skill>/
    SKILL.md            # rules and workflow
    agents/openai.yaml  # agent interface metadata
    references/         # readiness gates and provider evidence routing
scripts/
  validate_skills.py

Validate

python3 scripts/validate_skills.py

StackFit is recommendation-only by default. It must not connect to production, read secret values, create provider resources, deploy, or change application code unless the user explicitly requests implementation.