agentleFS
Sign inStart free
45ck45ck/backend-persistence-skills/.claude/skills/schema-normalizer/SKILL.md

schema-normalizer

Skill1 starsChanged 8 months agoMITView on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Prefer concrete operational behavior over abstract framework enthusiasm.

    line 34
  2. Distinctive:

    Prefer explicit tradeoffs over single-answer absolutism.

    line 47
  3. Distinctive:

    Use severity or priority where useful.

    line 48
  4. Distinctive:

    Do not blur domain logic, persistence logic, and transport concerns.

    line 51
  5. Distinctive:

    Do not describe happy-path behavior only.

    line 52
  6. Distinctive:

    Do not hide uncertainty behind ORM or framework jargon.

    line 53
  7. Distinctive:

    Do not recommend migrations or transactions without discussing rollback and compatibility.

    line 54

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

schema-normalizer

Purpose

Review a relational schema for redundancy, dependency issues, naming consistency, key design, and normalization tradeoffs.

Expected inputs

  • current backend or persistence context
  • data model or schema details
  • constraints or stack context
  • known risks or unresolved decisions

Deliverables

  • structured recommendation
  • design notes
  • risks or gaps
  • recommended next artifact

Trigger this skill when

  • You are designing or reviewing backend behavior, persistence, or API structure rather than only UI flow.
  • Data modeling, transactions, migration, or access-layer choices materially affect correctness or maintainability.
  • A team needs sharper boundaries between domain logic, persistence logic, and API contracts.

Operating procedure

  1. Clarify the domain, data lifecycle, and current or intended persistence approach.
  2. Separate facts, assumptions, constraints, and unresolved backend-specific risks.
  3. Prefer concrete operational behavior over abstract framework enthusiasm.
  4. Explicitly handle invalid, missing, conflict, and rollback cases where relevant.
  5. Recommend the next most useful backend, persistence, or testing skill.

Quality gates

  • The recommendation respects real data lifecycle and consistency needs.
  • Failure and conflict cases are not ignored.
  • Assumptions and unresolved decisions are visible.
  • Output is specific enough to influence implementation, schema, or testing.

Output style

  • Be concrete and structured.
  • Separate findings, assumptions, and recommendations.
  • Prefer explicit tradeoffs over single-answer absolutism.
  • Use severity or priority where useful.

Failure modes to avoid

  • Do not blur domain logic, persistence logic, and transport concerns.
  • Do not describe happy-path behavior only.
  • Do not hide uncertainty behind ORM or framework jargon.
  • Do not recommend migrations or transactions without discussing rollback and compatibility.

Minimum output skeleton

## Summary
## Findings or proposal
## Evidence vs assumptions
## Risks or tradeoffs
## Recommended next skill

Handoff targets

  • index-suggestion-writer
  • data-migration-planner
  • repository-layer-designer

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