agentsclimarketplace
Sign in

Db physical design

Skill planifest/planifest-framework/planifest-framework/external-skills/db-physical-design

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.From its SKILL.md

Install
npx -y skills add planifest/planifest-framework --skill db-physical-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 315 tokens by cl100k_base, as published. Nobody here has run it

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

  1. Profile data growth, access skew, and latency bottlenecks.
  2. Evaluate physical layout options against workload and operations cost.
  3. Select partition and storage strategies with explicit trade-offs.
  4. Define maintenance cadence for statistics and storage health.
  5. 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.

What ships with it: 1 file

11.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,852. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.