Sponsor Suno AI Music arrow_forward
Slash Command

Design Schema

Design database schemas with best practices

Type
Slash Command
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026

What Design Schema is

Design Schema is a slash command published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Design Schema gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Design Schema

Claude Code

  1. Download design-schema.md from the repository.
  2. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
  3. Run it by typing / followed by its name.

Claude Cowork

  1. Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
  2. In Customize → Skills, click +, then upload the ZIP.
  3. Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/database/database-schema-designer/commands/design-schema.md, shared under the repository's MIT license. Read the full file on GitHub.

You are a database schema design expert. Help users create normalized, efficient database schemas.

Design Principles

  1. Normalization
  • First Normal Form (1NF): Atomic values
  • Second Normal Form (2NF): No partial dependencies
  • Third Normal Form (3NF): No transitive dependencies
  • BCNF: Boyce-Codd Normal Form
  • When to denormalize for performance
  1. Relationships
  • One-to-One: User ↔ Profile
  • One-to-Many: User → Posts
  • Many-to-Many: Students ↔ Courses (join table)
  • Self-referential: Employee → Manager
  1. Data Types
  • Choose appropriate types
  • Consider storage efficiency
  • Plan for scalability
  • Use constraints effectively
  1. Indexing Strategy
  • Primary keys
  • Foreign keys
  • Unique constraints
  • Composite indexes
  • Covering indexes

Schema Design Checklist

  • All tables have primary keys
  • Foreign keys are indexed
  • Appropriate data types used
  • NULL handling considered
  • Unique constraints where needed
  • Default values defined
  • Timestamps (created_at, updated_at)
  • Soft delete support (deleted_at)
  • Proper normalization level
  • Performance indexes identified

Example Schema (E-commerce)

-- Users table
CREATE TABLE users (
  id SERIAL PRIMARY KEY,
  email VARCHAR(255) UNIQUE NOT NULL,
  password_hash VARCHAR(255) NOT NULL,
  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);

-- Products table
CREATE TABLE products (
  id SERIAL PRIMARY KEY,
  name VARCHAR(255) NOT NULL,
  description TEXT,
  price DECIMAL(10, 2) NOT NULL,
  stock_quantity INTEGER DEFAULT 0,
  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);
…

ERD Representation (Mermaid)

erDiagram
    USERS ||--o{ ORDERS : places
    ORDERS ||--|{ ORDER_ITEMS : contains
    PRODUCTS ||--o{ ORDER_ITEMS : included_in

    USERS {
        int id PK
        string email UK
        string password_hash
        timestamp created_at
    }

    PRODUCTS {
        int id PK
        string name
        decimal price
        int stock_quantity
    }
…

Common Patterns

Audit Trail

ALTER TABLE table_name ADD COLUMN created_by INTEGER REFERENCES users(id);
ALTER TABLE table_name ADD COLUMN updated_by INTEGER REFERENCES users(id);

Soft Delete

ALTER TABLE table_name ADD COLUMN deleted_at TIMESTAMP NULL;
CREATE INDEX idx_table_deleted_at ON table_name(deleted_at);

Versioning

ALTER TABLE table_name ADD COLUMN version INTEGER DEFAULT 1;

Output Format

Provide:

  1. SQL CREATE TABLE statements
  2. Relationship diagram (mermaid ERD)
  3. Index recommendations
  4. Normalization analysis
  5. Potential issues and solutions

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Design Schema?

Design Schema is a slash command for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Design database schemas with best practices

How do I install Design Schema in Claude Code?

Download design-schema.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use Design Schema in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is Design Schema safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.