# Skills

> Supacharger includes agent skills under `.agents/skills/`. A skill is a focused set of engineering instructions and supporting references that helps a compatible coding agent work safely in a particular area of the project.

# Supacharger skills

Supacharger includes agent skills under `.agents/skills/`. A skill is a focused set of engineering instructions and supporting references that helps a compatible coding agent work safely in a particular area of the project.

The starter currently includes:

- `supabase` for Auth, Database, Storage, Edge Functions, migrations, RLS and Supabase CLI work;
- `supabase-postgres-best-practices` for schema design, query performance, indexes, locking, connections and PostgreSQL security.

## Use a skill

Open your coding agent in the project root. You can name a skill directly in a request, for example:

```text
Use $supabase to add a forward migration for this feature, test it locally,
and document the hosted deployment step.
```

Compatible agents may also select a skill automatically when your task matches its description. Naming it explicitly is useful when you want to make the working method unambiguous.

The agent reads the complete `SKILL.md`, follows the project `AGENTS.md`, and loads only the references needed for the task. Project rules remain authoritative when a general skill and the repository differ.

## Keep skills aligned

Core owns the supplied skill packages. The CLI copies the managed skill directories to consumers so improvements reach every application. Do not edit a managed skill independently in one consumer. Promote a reusable improvement to Core, release it, and update consumers through the normal Core lock flow.

Product-specific skills may live beside the supplied skills in a developer-owned path. Give each one a narrow trigger, a complete `SKILL.md`, and only the references or scripts it actually needs. Never put secrets or environment credentials in a skill.

## A useful request pattern

Tell the agent the outcome, environment and verification boundary:

```text
Use $supabase. Add organisation invitations to the local schema, preserve RLS,
run the database tests, generate a forward migration, and list the separate
hosted release steps. Do not deploy until I approve the dry run.
```

This keeps the task concrete while the skill supplies current Supabase-specific safety and verification guidance.