agentleFS
RichardMcQuiston01RichardMcQuiston01/unofficial-claude-skill-examples/skills/database-conventions/SKILL.md

database-conventions

Skill1 starsChanged 3 months agoApache-2.0View on GitHub

My database naming and schema conventions — models, tables, columns, required audit fields, and transaction usage. Use whenever designing or editing database schemas, models, or migrations.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If UUID is not supported by database type, use auto-incremented Integer as PK instead

    line 12
  2. Distinctive:

    Always use database transactions for multi-step writes

    line 14

≈ “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

Database Conventions

  • Model names: singular PascalCase (e.g., User, MakerShop, MachineType)
  • Table names: singular snake_case via @@map("snake_case") — existing tables from crafterkit keep their names
  • Column names: snake_case in DB, camelCase in ORM via @map("snake_case")
  • Required on all tables: id (UUID PK), created_at, updated_at
  • If UUID is not supported by database type, use auto-incremented Integer as PK instead
  • Required on user-modifiable tables: created_by_user_id, updated_by_user_id
  • Always use database transactions for multi-step writes

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.