code-design-schema
Design data models, database schemas, and ORM definitions.
Process
-
Identify context:
- Identify the database technology (Postgres, MySQL, SQLite, Mongo, etc.)
- Identify the ORM/Framework (Prisma, TypeORM, SQLAlchemy, Django, etc.)
- Understand the entity relationships (1:1, 1:N, M:N)
-
Research and design:
- Lookup framework best practices for defining models and relationships (use WebSearch/WebFetch)
- Design the schema/entity relationship considering scalability and normalization
-
Execute based on goal:
- New Schema: Generate SQL DDL or ORM model definitions
- Modification: Analyze current schema vs desired state, generate migration steps
- Validation: Check for normalization issues or N+1 query risks in relationships
Output
More from sirn/dotfiles
code-explain
Explain code, triage changes, or map project structure. Use when user asks to explain, understand, triage, or explore project structure.
19code-plan
Generate comprehensive implementation plan based on analysis. Use when user asks to plan this, create a plan, how should I implement, or wants implementation guidance.
19code-commit
Commit current changes using jj. Analyzes changes, suggests commit messages following repository conventions, proposes splits if needed, and creates commits. Use ONLY when user explicitly asks to commit changes or create commits.
18gemini-reference
Reference for calling the Gemini CLI agent from other agents. ALWAYS read BEFORE invoking Gemini to ensure correct JSON protocol, session management, and subtask delegation patterns.
18code-quality
Run comprehensive quality checks by orchestrating review, verification, testing, and linting. Use when user asks to check code quality, run full checks, or verify code health.
18context7
Retrieve up-to-date documentation context for libraries using the Context7 API. Use when needing current library documentation (React, Python stdlib, Rust, etc.) BEFORE implementing or writing code.
17