Data Systems Architecture
Use when designing databases for data-heavy applications, making schema decisions for performance, choosing between normalization and denormalization, selecting storage/indexing strategies, planning for scale, or evaluating OLTP vs OLAP trade-offs. Also use when encountering N+1 queries, ORM issues, or concurrency problems.
Install
npx skills add ratacat/claude-skills --skill data-systems-architecturegit clone --depth 1 https://github.com/ratacat/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/data-systems-architecture ~/.claude/skills/data-systems-architecturePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Data Systems Architecture ## Overview **Core principle:** Good data system architecture balances reliability (correct operation under faults), scalability (handling growth gracefully), and maintainability (enabling productive change over time). Every architectural decision involves trade-offs between these concerns. This skill synthesizes knowledge from three foundational texts: - *Designing Data-Intensive Applications* (Kleppmann) - distributed systems, storage engines, scaling - *The Art of PostgreSQL* (Fontaine) - PostgreSQL-specific patterns, SQL as programming - *PostgreSQL Query Optimization* (Dombrovskaya et al.) - execution plans, performance tuning ## When to Use | Symptom | Start With | |---------|------------| | Designing a new database/schema | `01-foundational-principles.md` | | Normalization vs denormalization decisions | `02-data-modeling.md` | | Need to understand OLTP vs OLAP | `03-storage-engines.md` | | Slow queries, index selection | `04-indexing.md` | | Planning for growth, read replicas | `05-scaling-patterns.md` | | Race conditions, deadlocks, isolation issues | `06-transactions-concurrency.md` | | N+1 queries, ORM problems, application integration | `07-application-integration.md` | ## Navigation ### Reference Files (Load as needed)
Details
- Skill name
data-systems-architecture- Repository
- ratacat/claude-skills
- Path
skills/data-systems-architecture/SKILL.md- Repo updated
- 11 February 2026
FAQ
What does the Data Systems Architecture skill do?
Use when designing databases for data-heavy applications, making schema decisions for performance, choosing between normalization and denormalization, selecting storage/indexing strategies, planning for scale, or evaluating OLTP vs OLAP trade-offs. Also use when encountering N+1 queries, ORM issues, or concurrency problems.
How do I install the Data Systems Architecture skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ratacat/claude-skills --skill data-systems-architecture. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Data Systems Architecture popular?
It lives in ratacat/claude-skills, which has 59 GitHub stars and 10 forks.
Related skills
Skill Creator
59ratacat/claude-skills
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
Skill Installer
59ratacat/claude-skills
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
Agent Browser
59ratacat/claude-skills
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click button", "take screenshot", "scrape page", "web automation".
Debugging
59ratacat/claude-skills
Systematic debugging that identifies root causes rather than treating symptoms. Uses sequential thinking for complex analysis, web search for research, and structured investigation to avoid circular reasoning and whack-a-mole fixes.
Code Simplicity Reviewer
59ratacat/claude-skills
Use this agent when you need a final review pass to ensure code changes are as simple and minimal as possible. This agent should be invoked after implementation is complete but before finalizing changes, to identify opportunities for simplification, remove unnecessary complexity, and ensure adherence to YAGNI principles. Examples: <example>Context: The user has just implemented a new feature and wants to ensure it's as simple as possible. user: "I've finished implementing the user authentication system" assistant: "Great! Let me review the implementation for simplicity and minimalism using the
Design Patterns
59ratacat/claude-skills
Use when designing software architecture, refactoring code structure, solving recurring design problems, or when code exhibits symptoms like tight coupling, rigid hierarchies, scattered responsibilities, or difficult-to-test components. Also use when choosing between architectural approaches or reviewing code for structural improvements.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.