database-design-document SKILL.md skillA
database-design-document from fattain-naime/engineering-docs is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add fattain-naime/engineering-docs/database-design-document@git:20260717.2f82174Pins git:20260717.2f82174 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- fattain-naime/engineering-docs
- Path
skills/database-design-document/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260717.2f82174, committed Jul 17, 2026
- First version recorded
- Jul 8, 2026
- Size
- 15,523 bytes
- Repository stars
- 6
- License
- MIT
Design a production database schema including ERD, table definitions, data dictionary, indexing strategy, normalization decisions, and migration plan. Use when designing a new database, adding major entities, or documenting an existing schema.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## Purpose Produce a database design document that specifies the complete logical and physical data model, including entity relationships, table definitions, column constraints, indexing strategy, and migration plan. **Database schema is the hardest type of technical debt to remediate.** Changing a column name on a 50M-row table is a 4-hour maintenance window. Designing it correctly upfront is a 2-hour design session. ## Input **Works best with:** The domain or system being modeled. **Also valuable:** Business rules, cardinality constraints, known query patterns, performance requirements, existing tables that must integrate. **Example invocation:** `Design the database schema for PayFlow's merchant management system. Merchants have multiple brands, each with their own settings, domains, and staff users. Users have roles with specific permissions. Brands can have multiple currencies and payment methods.` ## Key Concepts ### Normalization - **1NF:** Atomic values. No repeating groups. Single value per cell. - **2NF:** No partial dependencies. Non-key columns depend on the full primary key. - **3NF:** No transitive dependencies. Non-key columns depend only on the primary key. …
Read the whole file at its exact version.
How to install
mdr add fattain-naime/engineering-docs/database-design-document@sha256:1fb82d4a04f85943The line at the top of this page pins the label git:20260717.2f82174, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2ssasvnww44yei6h)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 8, 2026 and Jul 17, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260717.2f82174 latest | 2026-07-17 | 2f82174 | 15,523 B | A | view · diff |
| git:20260712.59c5852 | 2026-07-12 | 59c5852 | 5,457 B | A | view · diff |
| git:20260712.7e3d1bb | 2026-07-12 | 7e3d1bb | 5,541 B | A | view · diff |
| git:20260709.03fe43c | 2026-07-09 | 03fe43c | 5,338 B | A | view · diff |
| git:20260708.a309efd | 2026-07-08 | a309efd | 4,509 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15523 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
fattain-naime/engineering-docs · 6 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2ssasvnww44yei6h GET https://markdownregistry.com/api/v1/resolve?ref=fattain-naime/engineering-docs/database-design-document GET https://markdownregistry.com/api/v1/blob/1fb82d4a04f85943ed9ecd055921f52ef8f521e3747ee0848c23a5c3907a3728
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.