design-system-patterns
Best practices for building reusable UI components. Use when creating atoms, molecules, or updating the theme.
Discover Blockchain skills, compare source repositories and read the instructions for each workflow.
Best practices for building reusable UI components. Use when creating atoms, molecules, or updating the theme.
Writes complete OpenAPI 3.0 specifications for API endpoints following RESTful conventions. Use when creating new API endpoints, documenting API contracts, or defining request/response schemas for GloboTicket A...
Establishes patterns for creating test data in Entity Framework Core integration tests for multi-tenant applications. Use when writing integration tests that involve tenant isolation, foreign key relationships,...
Use this skill when implementing or modifying multi-tenant data isolation and security.
Use this skill when configuring Entity Framework Core entities using the Fluent API.
Provides unit testing patterns for .NET applications using EF Core In-Memory Provider, AAA structure, test data helpers, and TDD workflows. Use when writing unit tests for services, repositories, or domain logi...
Manages Entity Framework Core migrations using project scripts. Use when creating, applying, listing, or removing database migrations.
ASP.NET Core Minimal APIs patterns for endpoints, DTOs, validation, and service integration. Use when implementing API endpoints, defining request/response contracts, or structuring API projects with clean sepa...
Use this skill when implementing domain entities and their properties in .NET.
Use this skill when implementing data access, repositories, or query logic with Entity Framework Core.
Database schema specification using Mermaid ER diagrams, table structures, constraints, and indexes for multi-tenant applications.
Multi-tenancy implementation patterns for row level security, tenant isolation, and data segregation in SaaS applications.
Frontend architecture patterns for React apps (React Router 7, TanStack Query). Use when planning features, defining routes, data strategies, and component gaps.
Best practices for frontend architecture. Use when planning new features, defining routes, or designing data strategies.
User story writing patterns with comprehensive acceptance criteria categories and quality standards. Use when creating user stories, defining acceptance criteria, or reviewing story completeness for multi-tenan...
Best practices for E2E testing. Use when writing or debugging Playwright tests.
Test-Driven Development workflow for task implementation. Use when implementing tasks that require the Red-Green-Refactor cycle, quality gates, commit guidelines, or phase verification protocols.
Synchronize project documentation after track completion. Use when a track reaches completed status and product, tech-stack, or guidelines documents may need updates.
Track lifecycle management patterns. Use when creating tracks, updating track status, generating track IDs, parsing plan files, or managing track metadata.
Scans code and data for Protected Health Information (PHI) to ensure HIPAA compliance. Use when reviewing code that handles patient data, healthcare records, or medical information.
Autonomously run quality checks (RuboCop, RSpec) to establish baseline or detect regressions. Triggers before starting development work, after completing changes, when checking code quality, or when explicitly...
Job restart workflow for Slack-MM2 Sync (POST /api/jobs/{job_id}/restart), including backend behavior, UI conditions, and test expectations. Use when implementing or debugging retry of failed/skipped exports.
Docker Compose workflows for Slack-MM2 Sync (dev full-stack, prod stack, .env.dev/.env.prod, ports, log inspection). Use when starting/stopping services, reproducing bugs, or running integration flows.
Database + Alembic workflow for Slack-MM2 Sync (migrations, collapsed history, NEVER CANCEL guidance, and troubleshooting queries). Use when changing schema, debugging DB state, or dealing with migration failur...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.