agentleFS
Sign inStart free
irwebtoolsirwebtools/Product-Skills/skills/optional/database/SKILL.md

database

Skill0 starsChanged 2 months agoMITView on GitHub

Optional skill for schema, migration, and data-model work. Use only when persistence design or migration evidence is required for the current product outcome.

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use monitoring, ci-cd and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • rogue-dev-studioSkill

    monitoring

    Claude monitoring and usage tracking tools (UV, claude-monitor, claude-usage-cli). Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `monitoring` work when listed in TEAM.yaml or explicitly requested.

    Also in 3 projects that use this

  • JohnJBorenSkill

    ci-cd

    CI/CD pipeline design, GitHub Actions, testing automation, and deployment strategies

    Also in 4 projects that use this

  • klauswgSkill

    performance

    Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".

    Also in 6 projects that use this

  • 0xSeroSkill

    security

    Also in 11 projects that use this

  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 3 projects that use this

  • GitHubSkill

    state-management

    CoreAI Sandbox's TanStack Query + mock-JSON data layer. USE WHEN: editing data-fetching hooks (`app/hooks/use*.ts`), adding mock data in `app/data/`, or wiring a component to query state.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    no persistence is required for the preview.

    line 19
  2. Distinctive:

    Prefer source-controlled migrations over manual remote edits.

    line 24
  3. Distinctive:

    Test migrations on an isolated database when available.

    line 25
  4. Distinctive:

    Document rollback or follow-up risk for developers.

    line 26
  5. Distinctive:

    Do not design a full enterprise data platform unless that is the asked outcome.

    line 27
  6. Distinctive:

    Use templates, references, and evaluations for scope and exit evidence.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Database (optional)

This skill is optional. Load it when the outcome needs durable schema or migration work beyond what a thin Supabase path already covers.

When to use

  • schema or migration changes are required;
  • data constraints or RLS policies must be explicit in source control;
  • developers need reproducible database artifacts for handoff.

When not to use

  • mock-data UI work;
  • no persistence is required for the preview;
  • Supabase skill already covers the needed migrations — coordinate with supabase instead of duplicating guidance.

Expectations

  1. Prefer source-controlled migrations over manual remote edits.
  2. Test migrations on an isolated database when available.
  3. Document rollback or follow-up risk for developers.
  4. Do not design a full enterprise data platform unless that is the asked outcome.

Standard resources

Use templates, references, and evaluations for scope and exit evidence.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free