evaluate-schema
Comprehensive database schema analysis using 5-expert panel evaluation. PROACTIVELY activate for: (1) schema review, (2) data modeling decisions, (3) database design evaluation, (4) migration planning, (5) normalization analysis. Triggers: "evaluate schema", "review schema", "database design", "data model review", "schema analysis", "evaluate database"
What this skill does
# Evaluate Schema
Comprehensive database schema analysis using a 5-perspective expert panel.
## When to Use
Use this skill when you need to:
- Review a database schema for quality and best practices
- Evaluate data modeling decisions before implementation
- Plan schema migrations with risk assessment
- Analyze normalization and denormalization trade-offs
- Assess schema scalability and performance implications
## Workflow
Invoke the `database-schema-evaluator` skill for:
$ARGUMENTS
### Default Parameters
| Parameter | Value | Rationale |
|-----------|-------|-----------|
| `evaluation_depth` | comprehensive | Full 5-perspective analysis |
| `include_alternatives` | false | Focus on current schema; enable for redesign |
| `scoring_rubric` | standard | Balanced across all dimensions |
### Expert Panel Composition
The evaluation assembles 5 domain experts:
| Expert | Focus Area | Key Questions |
|--------|-----------|---------------|
| **Data Architect** | Normalization, patterns, relationships | Is the schema properly normalized? Are relationships clear? |
| **Performance Engineer** | Indexing, query optimization, scalability | Will this scale? Are indexes appropriate? |
| **Data Integrity Guardian** | Constraints, referential integrity, validation | Can invalid data enter? Are constraints complete? |
| **Evolution Strategist** | Migrations, extensibility, versioning | How hard will changes be? Is it future-proof? |
| **Operations Specialist** | Backup, maintenance, monitoring | Can we maintain this? Recovery implications? |
### Evaluation Dimensions
Each expert scores on their primary dimensions:
**Data Architect:**
- Normalization level (1NF-BCNF appropriateness)
- Relationship clarity
- Naming conventions
- Domain modeling accuracy
**Performance Engineer:**
- Index coverage
- Query pattern support
- Partitioning strategy
- Denormalization trade-offs
**Data Integrity Guardian:**
- Primary key design
- Foreign key completeness
- Check constraints
- NULL handling
**Evolution Strategist:**
- Additive change ease
- Breaking change risk
- Schema versioning support
- Migration complexity
**Operations Specialist:**
- Backup/restore complexity
- Monitoring surface area
- Maintenance windows required
- Disaster recovery impact
## Output Format
The schema evaluation produces:
```xml
<schema-evaluation>
<header>
<id>[unique identifier]</id>
<schema_name>[schema identifier]</schema_name>
<evaluation_depth>comprehensive</evaluation_depth>
<overall_score>[1-10]</overall_score>
</header>
<expert-assessments>
<assessment expert="Data Architect">
<score>[1-10]</score>
<findings>
<finding severity="[critical|high|medium|low]">
[Specific issue or observation]
</finding>
</findings>
<recommendations>
<recommendation priority="[1-n]">
[Specific improvement suggestion]
</recommendation>
</recommendations>
</assessment>
<!-- ... more expert assessments ... -->
</expert-assessments>
<consensus-findings>
<strengths>
<strength>[What the schema does well]</strength>
</strengths>
<concerns>
<concern severity="[critical|high|medium|low]" experts="[which experts flagged]">
[Shared concern across experts]
</concern>
</concerns>
</consensus-findings>
<prioritized-recommendations>
<recommendation priority="1" effort="[low|medium|high]" impact="[low|medium|high]">
<description>[What to change]</description>
<rationale>[Why this matters]</rationale>
<example>[Concrete example if applicable]</example>
</recommendation>
</prioritized-recommendations>
<migration-considerations>
[If changes recommended, migration implications]
</migration-considerations>
</schema-evaluation>
```
## Quality Gates
- [ ] All 5 expert perspectives represented
- [ ] Scores calibrated consistently across experts
- [ ] Critical issues flagged with severity
- [ ] Recommendations are specific and actionable
- [ ] Migration implications considered for recommended changes
- [ ] Trade-offs explicitly documented
## Related Skills
After schema evaluation, consider:
- Run `/compare-options` if multiple schema designs exist
- Run `/write-reference` to document the final schema
- Run `/research-brief` for technology-specific best practices
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.