LAYER_08_DATA_STORE

Define physical database schemas with SQL DDL for PostgreSQL, MySQL, and SQLite.

1|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/tinkermonkey/documentation_robotics --skill layer-08-data-store
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: LAYER_08_DATA_STORE
Source: https://github.com/tinkermonkey/documentation_robotics/tree/main/cli-validation/test-project/baseline/.claude/skills/dr_08_dataset_layer
Command: npx skills add https://github.com/tinkermonkey/documentation_robotics --skill layer-08-data-store

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of precisely defining and managing the physical structure of databases, including tables, columns, and their constraints, ensuring data integrity and efficient storage.

Core Features & Use Cases

  • Database Schema Definition: Model databases, schemas, tables, and columns with detailed data types and constraints.
  • Index and Constraint Management: Define primary keys, unique constraints, foreign keys, and indexes for performance optimization.
  • Use Case: Define a users table with UUID primary key, email and username unique constraints, and an encrypted password hash column, linking it to a user_profile object in the data model layer.

Quick Start

Use the dr tool to add a new table named 'products' to the 'inventory' schema.

Frequently Asked Questions about LAYER_08_DATA_STORE

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define a physical database schema with SQL DDL for PostgreSQL, MySQL, or SQLite?

You define a physical database schema by modeling tables, columns, indexes, constraints, triggers, and views using specific RDBMS syntax for PostgreSQL, MySQL, or SQLite. It supports data types, nullability, default values, PII marking, and encryption.

Can I model indexes and constraints like primary keys and foreign keys for a database table?

Yes, you can model indexes and constraints for a database table. This includes defining primary keys, unique constraints, foreign keys, and indexes to ensure data integrity and optimize query performance.

Does this approach support marking columns as PII and configuring encryption?

Yes, this approach supports marking columns as PII and configuring encryption. You can define physical database schemas with detailed data types, nullability, default values, and security attributes like PII marking and encryption.

How do I add a new table to an existing database schema?

You add a new table to an existing database schema by using the dr tool to specify the table name and target schema. This models the physical structure including columns, constraints, and indexes.

What is physical database design and when do I need to model it?

Physical database design is the process of defining the actual storage structure of data, including tables, columns, and constraints. You need to model it when precisely managing data integrity and efficient storage in a specific RDBMS.

Can I define triggers and views alongside tables in my database schema?

Yes, you can define triggers and views alongside tables in your database schema. It manages these entities in addition to databases, columns, indexes, and constraints using SQL DDL concepts for PostgreSQL, MySQL, and SQLite.