agentleFS
Sign inStart free
DongDuong2001DongDuong2001/pudo-code-system/skills/plan/database/SKILL.md

database-plan

Skill5 starsChanged 5 months agoMITView on GitHub

Database architecture, schema design, and index planning

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    When determining whether to use SQL vs NoSQL vs Time-Series databases.

    line 11
  2. Distinctive:

    When designing entity-relationship diagrams (ERD) schemas.

    line 12
  3. Distinctive:

    When planning indexing, partitioning, or sharding strategies.

    line 13
  4. Distinctive:

    Avoid using UUIDs/GUIDs as primary clustered keys in massive tables where sequential inserts are critical for performance, unless mitigated …

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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 Planning Skill

This skill is essential when designing data storage solutions and defining schema boundaries.

When to use this skill

  • When determining whether to use SQL vs NoSQL vs Time-Series databases.
  • When designing entity-relationship diagrams (ERD) schemas.
  • When planning indexing, partitioning, or sharding strategies.

Guidelines

  • Normalize data by default to reduce redundancy, but denormalize strategically for read-heavy performance bottlenecks.
  • Plan indexes based on expected query patterns, not just foreign keys. Remember that excessive indexing slows down write operations.
  • Avoid using UUIDs/GUIDs as primary clustered keys in massive tables where sequential inserts are critical for performance, unless mitigated by the DB engine.

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.

Reviews can't be read right now.

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