agentleFS
RichardMcQuiston01RichardMcQuiston01/unofficial-claude-skill-examples/skills/postgres-style/SKILL.md

postgres-style

Skill1 starsChanged 3 months agoApache-2.0View on GitHub

My Postgres database schema conventions — table/column naming, key strategy, and timestamp columns. Use whenever designing or editing database schemas, migrations, or tables.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer UUID over auto-increment integer for primary keys

    line 10
  2. Very specific:

    Add created_at and updated_at timestamp columns to tables unless otherwise specified

    line 11
  3. Distinctive:

    Check with the user before running any database migrations

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Postgres Style

  • Singular table names rather than plural (e.g. user, not users)
  • snake_case for column names
  • Prefer UUID over auto-increment integer for primary keys
  • Add created_at and updated_at timestamp columns to tables unless otherwise specified

Migration safety

  • Make copies or dumps of any databases prior to running any migrations
  • Check with the user before running any database migrations

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.