database

Generate TypeScript entity definitions and data schemas from requirements.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/sizukutamago/blueprint-plugin --skill database-sizukutamago
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database
Source: https://github.com/sizukutamago/blueprint-plugin/tree/main/skills/database
Command: npx skills add https://github.com/sizukutamago/blueprint-plugin --skill database-sizukutamago

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams design data models, entity definitions, and TypeScript typings to create consistent, shareable data structures for Wave A workflows.

Core Features & Use Cases

  • Data model generation: convert requirements into structured entities with typed definitions.
  • Entity definition & TypeScript typings: produce interfaces and types that map to database schema and business rules.
  • Validation & conventions: apply naming rules, data classifications, and schema constraints to ensure consistency across projects.

Quick Start

Provide the user requirements and reference data_structure templates to generate docs/04_data_structure/data_structure.md with TypeScript typings for entities.

Frequently Asked Questions about database

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

FAQPage Schema
How do I generate TypeScript types and entity definitions from requirements?

To generate TypeScript types and entity definitions, provide your project requirements and reference templates. The skill transforms these inputs into structured entities with typed fields, producing a standardized data structure document for architecture tasks.

What is data model generation for Wave A workflows?

Data model generation for Wave A workflows is the process of converting requirements into structured entities and data schemas. It targets architecture-skeleton and design-inventory tasks to establish consistent data structures across projects.

Can I use this to define entity IDs and apply database schema constraints?

Yes, you can use this to define entity IDs and apply database schema constraints. It enforces validation rules, data classifications, and standardized naming conventions to ensure schema consistency and accurate TypeScript typings.

What's the best way to ensure consistent data structures and TypeScript typings across projects?

The best way to ensure consistent data structures and TypeScript typings is to apply standardized naming rules and schema constraints during entity definition. This approach maps interfaces directly to business rules and database schemas.

Do I need reference data structure templates to generate docs/04_data_structure/data_structure.md?

Yes, you need reference data structure templates to generate docs/04_data_structure/data_structure.md. Providing these templates alongside your requirements enables the creation of accurate TypeScript typings and structured entity definitions.