Loading...
Loading...
Found 277 Skills
Dimensional modeling and schema design for data products. Star schema patterns, slowly changing dimensions, denormalization decisions, and architecture decision records. Use when designing data models, reviewing schema designs, choosing between normalization strategies, or when someone asks "how should I model this data?" or "should I denormalize?" For OMOP CDM patterns specifically, see healthcare-data-domain.
Agent skill for arch-system-design - invoke with $agent-arch-system-design
Choose system boundaries, architectural patterns, and tradeoffs. USE when deciding overall software shape, domain boundaries, or major technical direction.
Reviews code for quality — architecture conformance, anti-patterns, performance issues, maintainability. Read-only analysis that detects circular dependencies, N+1 queries, dead code, naming violations, and layering breaches. Use when the user asks for a code review, wants feedback on code quality, PR review, tech debt analysis, or architecture conformance checks.
Curated guide for implementing design patterns, architecture decisions, and verified design rules in software projects
Designs system architecture and selects technology stack based on vision analysis. Use after vision analysis for technical decisions. Triggers on: design architecture, select tech stack, choose framework.
Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution-design.md files in docs/specs/. Includes validation checklist, consistency verification, and overlap detection.
Collaborative design phase for feature lifecycle: explore requirements, discuss trade-offs, produce design document. Use when starting a new feature that needs design before implementation. Use for "design feature", "let's think through", "explore approaches", or "/feature-design". Do NOT use for simple bug fixes or tasks that don't need design discussion.
Use when a Beat change is implemented and ready to archive — not for verifying implementation
Use when starting a Beat change to create spec artifacts — not for task breakdown, implementation, or exploration
LP, MILP, and QP (beta) with cuOpt — C API only. Use when the user is embedding LP, MILP, or QP in C/C++.
Architecture-aware project initialization combining online research with archetype selection. project initialization, new project, architecture decision, project setup, which architecture, choose architecture, project architecture Use when: initializing a new project and need to select an appropriate architecture based on project type, team size, domain complexity, and current best practices DO NOT use when: architecture is already decided - use project-init instead.