Agent skill

System Design Data Architecture

by HoangNguyen0403 in HoangNguyen0403/agent-skills-standard

Choose and scale the data layer: SQL versus NoSQL per access pattern, single data ownership, replication and read scaling, partition key choice, hot partition and celebrity key mitigation.

MITAuto-check passedDatabases

Install System Design Data Architecture

skills CLI
$ npx skills add HoangNguyen0403/agent-skills-standard --skill system-design-data-architecture -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HoangNguyen0403/agent-skills-standard system-design-data-architecture --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/system-design/system-design-data-architecture .claude/skills/system-design-data-architecture && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
system-design-data-architecture
GitHub stars
572
Token cost
~910 tokens
SKILL.md length
435 words
Files
3 (incl. references)
Skills in repo
211
Repo updated
First seen
Licence
MIT

At a glance

Choose and scale the data layer: SQL versus NoSQL per access pattern, single data ownership, replication and read scaling, partition key choice, hot partition and celebrity key mitigation.

  • Works in 5 steps: List every read and write access pattern… → Default to a relational store. It wins… → Move a pattern to a specialized store… → …
  • Selecting a store
  • SKILL.md covers Priority: P1 (HIGH), Store Selection, Ownership and Consistency and Scaling Order, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

System Design Data Architecture is an agent skill from HoangNguyen0403/agent-skills-standard. Choose and scale the data layer: SQL versus NoSQL per access pattern, single data ownership, replication and read scaling, partition key choice, hot partition and celebrity key mitigation. Use when selecting a store, planning sharding, or fixing a data-tier bottleneck.

Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `evals/evals.json` and `references/database-scaling.md`).

It sits in Databases, covering Database administration and NoSQL databases. It works with SQL. The repository describes itself as: A collection of Agent Skills Standard and Best Practice for Programming Languages, Frameworks that help our AI Agent follow best practies on frameworks and programming laguages. The licence is MIT.

When your agent uses it

  • Selecting a store
  • Planning sharding
  • Fixing a data-tier bottleneck

Example prompts

  • “/system-design-data-architecture”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. List every read and write access pattern with its QPS, latency target, and consistency need.
  2. Default to a relational store. It wins until a specific pattern proves it cannot serve.
  3. Move a pattern to a specialized store only when the relational store fails that named pattern
  4. Every additional store adds sync lag, dual-write risk, and one more operational surface. Justify it.
  5. Blobs never live in the primary database; store bytes in object storage and keep the reference.

What it can do on your machine

Read from SKILL.md and the folder at commit b529c2d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

System Design Data Architecture loads about 910 tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 75 tokens; SKILL.md has 435 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~910
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HoangNguyen0403/agent-skills-standard at commit b529c2d, republished under its MIT licence (© HoangNguyen0403). 435 words, ~910 tokens.

Download SKILL.mdSave it as .claude/skills/system-design-data-architecture/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
system-design-data-architecture
description
Choose and scale the data layer: SQL versus NoSQL per access pattern, single data ownership, replication and read scaling, partition key choice, hot partition and celebrity key mitigation. Use when selecting a store, planning sharding, or fixing a data-tier bottleneck.

Data Architecture

Priority: P1 (HIGH)

Access patterns choose the store. Ownership precedes schema. Shard last, not first.

Store Selection

  1. List every read and write access pattern with its QPS, latency target, and consistency need.
  2. Default to a relational store. It wins until a specific pattern proves it cannot serve.
  3. Move a pattern to a specialized store only when the relational store fails that named pattern: key-value for hot lookups, wide-column for massive ordered writes, document for schema-variant aggregates, graph for multi-hop traversal, search index for text and facets, object store for blobs.
  4. Every additional store adds sync lag, dual-write risk, and one more operational surface. Justify it.
  5. Blobs never live in the primary database; store bytes in object storage and keep the reference.

Ownership and Consistency

  • One writer owns each entity. Cross-service reads use an API or an event stream, never a shared table.
  • Classify each flow before choosing replication: money, stock, and identity need strong consistency; feeds, counters, and analytics tolerate eventual.
  • Read replicas serve reads only, and replica lag is visible to users. Route read-after-write to the primary or pin the session.
  • Cross-entity atomicity across services needs a saga with compensations, not a distributed transaction.

Scaling Order

Apply in order and stop as soon as headroom is sufficient: index and query fixes, then read replicas, then caching, then vertical scale, then partition or archive cold data, then shard. Sharding is last because it costs cross-shard queries, rebalancing, and a permanent partition key commitment.

Show full SKILL.md (185 more words)Show less

Partitioning

  • Choose a partition key that is high-cardinality, present in the hottest query, and evenly distributed.
  • Hash partitioning spreads load but kills range scans; range partitioning keeps scans but creates a moving hot partition on time-ordered keys.
  • Mitigate a celebrity key by salting the key, replicating the record, or serving it from a dedicated cache.
  • Plan resharding before launch: virtual buckets mapped to physical shards let you move buckets without rewriting keys.

Anti-Patterns

  • No premature sharding: an unindexed query at 300 QPS is not a sharding problem.
  • No shared database between services: it silently couples deploy and schema lifecycles.
  • No dual writes without reconciliation: use an event log or CDC, then reconcile.
  • No unbounded table growth: define retention, archival tier, and deletion at design time.
  • No denormalization without an update path: every copy needs an owner and a refresh trigger.

Verify

  • Every access pattern mapped to exactly one store with a stated reason
  • Single writer named per entity
  • Consistency class stated per flow
  • Partition key chosen with a hot-partition mitigation
  • Retention and archival defined

References

  • Database Scaling - store comparison, replication topologies, sharding mechanics, migration patterns

© HoangNguyen0403, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/system-design/system-design-data-architecture of HoangNguyen0403/agent-skills-standard.

  • SKILL.md
  • evals/evals.json
  • references/database-scaling.md

Open the folder on GitHubat commit b529c2d

Compare with similar skills

System Design Data Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

System Design Data Architecture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
System Design Data Architecture this skillHoangNguyen0403/agent-skills-standard572—~910Automated safety check: PassMIT
Database Architecture InterviewerPrepLabsAI/InterviewMentor112—~2.4kAutomated safety check: PassMIT
Ddia Systemswondelai/skills2.4k—~4.2kAutomated safety check: PassMIT
DB SculptorEliasOulkadi/shokunin114—~3.1kAutomated safety check: NotesMIT
Discover Databaserand/cc-polymath181—~2kAutomated safety check: PassMIT
DatabasesMicrock/ordinary-claude-skills404—~1.9kAutomated safety check: NotesMIT

Similar skills

  • Database Architecture Interviewer

    PrepLabsAI/InterviewMentor

    A Principal Database Engineer interviewer. An agent skill from PrepLabsAI/InterviewMentor.

    112 GitHub stars~2.4k tokensUpdated 4 days ago
    DatabasesAuto-check passed
  • Ddia Systems

    wondelai/skills

    Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models.

    2.4k GitHub stars~4.2k tokensUpdated 1 mo ago
    DatabasesAuto-check passed
  • DB Sculptor

    EliasOulkadi/shokunin

    Design database schemas with Prisma/Drizzle, PostgreSQL index strategy (B-tree, GIN, GiST, BRIN, Hash), query optimization (EXPLAIN ANALYZE), migration safety (expand/contract, zero-downtime), and…

    114 GitHub stars~3.1k tokensUpdated 6 days ago
    DatabasesAuto-check: notes
  • Discover Database

    rand/cc-polymath

    Automatically discover database skills when working with SQL, PostgreSQL, MongoDB, Redis, database schema design, query optimization, migrations, connection pooling, ORMs, or database selection.

    181 GitHub stars~2k tokensUpdated 7 mo ago
    DatabasesAuto-check passed
  • Databases

    Microck/ordinary-claude-skills

    Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin).

    404 GitHub stars~1.9k tokensUpdated 1 mo ago
    DatabasesAuto-check: notes
  • Mongodb

    sickn33/agentic-awesome-skills

    Administer MongoDB databases. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~2.7k tokens
    DatabasesAuto-check: notes

More from HoangNguyen0403/agent-skills-standard

All 211 skills in this repo
  • Subagent-Driven Development

    HoangNguyen0403/agent-skills-standard

    Runs a multi-task implementation plan by sending each task to a fresh implementer subagent, reviewing it independently, then reviewing the whole branch.

    572 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • draw.io Architecture Diagramming

    HoangNguyen0403/agent-skills-standard

    Draws architecture diagrams as editable draw.io files from a JSON spec, with a fixed house style, one C4 level per diagram and evidence-tagged shapes.

    572 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Android Navigation 3 Guide

    HoangNguyen0403/agent-skills-standard

    Implements and migrates to Jetpack Navigation 3 in Compose: NavDisplay, typed route objects, a state-list back stack, deep links, multiple back stacks and dialog scenes.

    572 GitHub stars~687 tokensUpdated yesterday
    Auto-check passed
  • Angular HttpClient Standards

    HoangNguyen0403/agent-skills-standard

    Sets rules for Angular HTTP code: functional interceptors, typed requests, services that own every call, and httpResource for reactive data loading in Angular 17+.

    572 GitHub stars~652 tokensUpdated yesterday
    Auto-check passed
  • Angular Tooling

    HoangNguyen0403/agent-skills-standard

    Angular CLI usage, code generation, build configuration, and bundle optimization.

    572 GitHub stars~743 tokensUpdated yesterday
    Auto-check passed
  • Common Code Review

    HoangNguyen0403/agent-skills-standard

    Conduct high-quality, persona-driven code reviews. An agent skill from HoangNguyen0403/agent-skills-standard.

    572 GitHub stars~772 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about System Design Data Architecture

What does System Design Data Architecture do?

Choose and scale the data layer: SQL versus NoSQL per access pattern, single data ownership, replication and read scaling, partition key choice, hot partition and celebrity key mitigation. System Design Data Architecture is an agent skill from HoangNguyen0403/agent-skills-standard. Choose and scale the data layer: SQL versus NoSQL per access pattern, single data ownership, replication and read scaling, partition key choice, hot partition and celebrity key mitigation.

When should I use System Design Data Architecture?

System Design Data Architecture fits situations like: selecting a store; planning sharding; fixing a data-tier bottleneck.

How do I install System Design Data Architecture in Claude Code?

Run `npx skills add HoangNguyen0403/agent-skills-standard --skill system-design-data-architecture -a claude-code`. Or copy the skill folder (skills/system-design/system-design-data-architecture in HoangNguyen0403/agent-skills-standard) into .claude/skills/system-design-data-architecture in your project. Claude Code loads it when a task matches its description.

How do I install System Design Data Architecture in Codex?

Run `npx skills add HoangNguyen0403/agent-skills-standard --skill system-design-data-architecture -a codex`. Or copy the skill folder (skills/system-design/system-design-data-architecture in HoangNguyen0403/agent-skills-standard) into .agents/skills/system-design-data-architecture in your project. Codex loads it when a task matches its description.

Can I use System Design Data Architecture in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HoangNguyen0403/agent-skills-standard --skill system-design-data-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/system-design-data-architecture, .gemini/skills/system-design-data-architecture, .github/skills/system-design-data-architecture and .opencode/skills/system-design-data-architecture in your project.

What does System Design Data Architecture need to run?

SKILL.md names no scripts, command-line tools or credentials: System Design Data Architecture is instructions for the agent only.

Does System Design Data Architecture access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is System Design Data Architecture safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does System Design Data Architecture use?

System Design Data Architecture is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does System Design Data Architecture use?

About 910 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to System Design Data Architecture?

Skills that share tags, products or a category with System Design Data Architecture: Database Architecture Interviewer (PrepLabsAI/InterviewMentor, 112 stars), Ddia Systems (wondelai/skills, 2.4k stars), DB Sculptor (EliasOulkadi/shokunin, 114 stars) and Discover Database (rand/cc-polymath, 181 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains System Design Data Architecture?

HoangNguyen0403 (a GitHub user) maintains it in HoangNguyen0403/agent-skills-standard, which has 572 GitHub stars. The repository holds 211 skills in this directory. The repository was last updated on October 9, 2026.

Source: HoangNguyen0403/agent-skills-standard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.