Skills

What skills are

supastack ships Agent Skills: short, task-focused instructions your coding agent loads when a job matches. Instead of guessing the kit's conventions on every prompt, the agent follows the same steps for features, payments, database changes and tests. Skills follow the open Agent Skills format, so they work in Claude Code, Cursor, Codex, GitHub Copilot, Gemini CLI and other compatible agents.

Where skills live

Skills live in .agents/skills/, one folder per skill with a SKILL.md file inside. Identical copies sit in .claude/skills/ for Claude Code.

Which agents read them

Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode read .agents/skills/. Claude Code reads .claude/skills/. Your agent picks a skill automatically when your request matches its description, or you can name it — say “use the database-schema-change skill”.

Which repositories ship them

The all-platforms repository includes every skill. The web, mobile and desktop repositories include the skills that apply to them; end-to-end testing and CI skills ship only with the all-platforms repository.

Setup & environment

Skills for getting the kit running, deployed and configured.

• Local environment setup (local-environment-setup) — use when bootstrapping or repairing the local environment: first clone, a missing or broken .env, Postgres, migrations or ports.
• Deploy and env vars (deploy-and-env-vars) — use when deploying, choosing a hosting target, or adding or changing an environment variable.
• Adding a dependency (adding-a-dependency) — use when adding, upgrading, moving or removing an npm dependency, or when CI fails the license or audit check.
• Upgrading from upstream (upgrading-from-upstream) — use when pulling a newer supastack release into a product built on it.

Building features

Skills for adding product surface area on each platform.

• Add a web feature (add-a-web-feature) — use when adding a product page or section with its own data, server actions, navigation and tests.
• Add an API endpoint (add-an-api-endpoint) — use when adding or changing a public /api/v1 endpoint, its OpenAPI documentation or API-key scopes.
• Add a UI component (add-a-ui-component) — use when building a section, block, form control or reusable component that follows the kit's styling rules.
• Change the theme or style (change-the-theme-or-style) — use when changing how the product looks: a design style, color pack, density, radius, font or layout.
• Add a marketing page or blog post (add-a-marketing-page-or-blog-post) — use when adding or editing a public page, pricing page, legal page, blog post or docs guide.
• Add a mobile screen (add-a-mobile-screen) — use when adding or changing a screen in the Expo mobile app.
• Add a desktop capability (add-a-desktop-capability) — use when changing the Tauri desktop app: window, tray, global shortcut or auto-updates.
• Add a notification (add-a-notification) — use when adding an in-app notification, push notification or digest item.

Auth & payments

Skills for sign-in, billing and plans.

• Add an auth method (add-an-auth-method) — use when changing sign-in: social providers, magic links, email codes, passkeys or two-factor.
• Add a payment provider (add-a-payment-provider) — use when activating a billing provider or writing a new billing adapter with checkout, customer portal and webhooks.
• Change plans and pricing (change-plans-and-pricing) — use when adding, renaming or repricing a plan: prices, trials, seats, entitlements, usage limits or credits.

Data & integrations

Skills for the schema, AI, jobs, email, storage and translations.

• Database schema change (database-schema-change) — use when adding or changing a table, column, index or relation and generating the migration.
• Add an AI feature (add-an-ai-feature) — use when adding a model call, chat or agent tool, a durable AI task, budgets or bring-your-own-key.
• Add a background job (add-a-background-job) — use when adding work that runs after a request, on a timer or per workspace.
• Add or edit an email (add-or-edit-an-email) — use when adding or changing a transactional email or switching the provider that delivers it.
• Use file storage (use-file-storage) — use when adding uploads or stored files such as avatars, logos or attachments.
• Add translations (add-translations) — use when adding or changing user-facing text, translating it or adding a locale.

Quality & shipping

Skills for tests, verification, reviews and CI.

• Writing unit tests (writing-unit-tests) — use when writing or fixing Vitest unit or integration tests.
• Writing e2e tests (writing-e2e-tests) — use when adding or fixing Playwright end-to-end tests, locally or in CI.
• Verify changes (verify-changes) — use before handing off, committing or opening a pull request to pick and run the right checks.
• Debugging a failing CI run (debugging-a-failing-ci-run) — use when a GitHub Actions run fails and you need to find and fix the cause.
• Reviewing a PR (reviewing-a-pr) — use when reviewing a pull request or diff for correctness, workspace isolation and conventions.

Add your own

Add a folder whose name matches the name in its frontmatter, with a name and a description that says when to use it. Copy it to .claude/skills/ too, so every agent can find it.