A starting description of a product’s main kinds of data, such as users, orders, or projects, and the relationships between them. It creates shared names for the data but is not the final database design.

Use it to define or revise the product’s core entities and relationships in `/product/data-shape/data-shape.md`.

It gives different parts of a product a common vocabulary, reducing inconsistencies when creating sample data or designing screens.

How buildermethods/design-os configures Claude Code

About the project

Design OS is a product-planning and interface-design tool that guides an idea through product definition, data modeling, design-system choices, screen design, and implementation handoff. Teams use it to give coding agents a clear specification before development begins. Its catalogue add-ons support the guided planning and design workflow.

buildermethods/design-os · 1,876 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to buildermethods/design-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/buildermethods/design-os/main/.claude/commands/design-os/data-shape.md

Clone the repo

git clone --depth 1 https://github.com/buildermethods/design-os

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/buildermethods/design-os/data-shape/github.svg)](https://agentmods.dev/commands/buildermethods/design-os/data-shape)

Your own site

<a href="https://agentmods.dev/commands/buildermethods/design-os/data-shape"><img src="https://agentmods.dev/badge/commands/buildermethods/design-os/data-shape/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/buildermethods/design-os/data-shape"><img src="https://agentmods.dev/badge/commands/buildermethods/design-os/data-shape.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 839 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00839
Opus 5.5	$0.00000	$0.00336
Sonnet 5.5	$0.00000	$0.00168
Haiku 4.5	$0.00000	$0.00084

Measured 2mo ago against content hash ca87ad25a676, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

data-shape scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/design-os/data-shape.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Data Shape

You are helping the user create or update the general shape of their product's data — the core entities ("nouns") and how they relate to each other. This creates a shared vocabulary that ensures consistency across sections when generating sample data and screen designs. This is not the final data model — it's a starting point that the implementation agent will extend and refine.

Step 1: Check Current State

First, check if /product/data-shape/data-shape.md exists.

If Data Shape Already Exists (Updating)

Read:

/product/data-shape/data-shape.md
/product/product-overview.md (if it exists, for context)
/product/product-roadmap.md (if it exists, for context)

Present the current state and ask what to change:

"Your data shape currently defines these entities:

[Entity1] — [Description]
[Entity2] — [Description]

Relationships:

[Relationship 1]
[Relationship 2]

What would you like to change about the entities or relationships?"

Wait for the user's response describing what they want changed. Once you receive their notes, immediately proceed to update product/data-shape/data-shape.md based on their requested changes — do not present a draft for approval.

After updating, inform the user:

"I've updated the data shape based on your feedback. Review the changes and let me know if you'd like further adjustments."

Stop here — the remaining steps below are for generating a new data shape from scratch.

If No Data Shape Exists (Creating New)

Check Prerequisites

Read:

/product/product-overview.md to understand what the product does
/product/product-roadmap.md to understand the planned sections

If either file is missing, let the user know:

"Before defining your data shape, you'll need to establish your product vision. Please run /product-vision first."

Stop here if prerequisites are missing.

Analyze and Generate

Review the product overview and roadmap, then immediately proceed to create the data shape file — do not present a draft for approval.

Read the full file on GitHub · 113 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 113 lines · 0 tokens per session scan A ca87ad25a676

Subscribe to this mod's changes

data-shape is a command published in the GitHub repository buildermethods/design-os (1,876 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 839 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Databases Planning

data-shape next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
data-shapebuildermethods/design-os	Command	1.9k	1mo ago	MIT	A	0	Claude Code
initfcakyon/claude-codex-settings	Command	1.2k	yesterday	Apache-2.0	A	0	Claude Code
securityajitpratap0/GoSQLX	Command	124	2d ago	Apache-2.0	A	21	Claude Code
database-setupimsaif/design-with-claude	Command	11	yesterday	MIT	A	36	Claude Code
new-migrationRaNDoM6913/claude-code-superkit	Command	3	yesterday	MIT	A	22	Claude Code
json.batch_getstratalab/strata-core	Command	5	1mo ago	Apache-2.0	A	0	Claude Code
json.index.dropstratalab/strata-core	Command	5	1mo ago	Apache-2.0	A	0	Claude Code

design-os: Command for Claude Code