kentoshimizu/sw-agent-skills/db-physical-design
Claude Code and agent skill by kentoshimizu/sw-agent-skills
Trust tier 3
- community
Source check pending
Checking that the SKILL.md file is still in the repository.
Physical database design workflow for storage layout, partitioning, engine settings, and hardware-aware performance behavior. Use when sustained workload efficiency depends on physical data organization; do not use for conceptual modeling tasks.
Install
npx vskill@latest install kentoshimizu/sw-agent-skills/db-physical-designSKILL.md
DB Physical Design
Overview
Use this skill to align storage structures with workload shape, growth patterns, and operational constraints.
Scope Boundaries
- Data volume or access distribution creates storage and latency pressure.
- Partitioning or table layout decisions affect manageability.
- Engine-specific behavior requires deliberate configuration.
Core Judgments
- Partitioning strategy (range/hash/list/hybrid) and key choice.
- Hot/cold data tiering and archival layout.
- Table/index storage parameters by engine characteristics.
- Maintenance strategy for bloat, vacuum/reorg, and statistics.
Practitioner Heuristics
- Partition by access and lifecycle behavior, not by calendar habit.
- Keep partition count operationally manageable.
- Co-locate frequently joined data only when it materially improves hot paths.
- Engine tuning must follow measured workload and failure history, not defaults folklore.
Workflow
- Profile data growth, access skew, and latency bottlenecks.
- Evaluate physical layout options against workload and operations cost.
- Select partition and storage strategies with explicit trade-offs.
- Define maintenance cadence for statistics and storage health.
- Document scaling and re-partitioning triggers.
Common Failure Modes
- Partition key chosen without considering future rebalance complexity.
- Excessive small partitions degrade planner and maintenance performance.
- Storage tuning changes applied without workload baseline.
Failure Conditions
- Stop when physical layout has no clear workload rationale.
- Stop when partition strategy cannot support retention/archival requirements.
- Escalate when operational maintenance burden exceeds team capacity.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/db-physical-design/SKILL.md
Popularity
- Repository stars
- 5
- 7-day trend score
- 9
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 7 May 2026, 6 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/kentoshimizu/sw-agent-skills/db-physical-design)