crispy-data-provider
Data Provider architecture rules for Crispy CRM. Use when creating data handlers, adding new resources, modifying unifiedDataProvider, implementing CRUD operations, or working with React Admin handlers and Supa...
Discover testing security architecture patterns skills, compare source repositories and read the instructions for each workflow.
Data Provider architecture rules for Crispy CRM. Use when creating data handlers, adding new resources, modifying unifiedDataProvider, implementing CRUD operations, or working with React Admin handlers and Supa...
Feature-Sliced Design 아키텍처 패턴을 검증하고 적용합니다. "FSD 검증", "아키텍처 검토", "레이어 구조 확인", "슬라이스 분리", "의존성 검사" 요청 시 사용합니다.
Expert guide for Jean Claude CLI - a sophisticated AI orchestration framework featuring two-agent workflows, event sourcing, coordinator pattern with ntfy.sh, agent note-taking, mailbox communication, and real-...
Development guide for working on the Jean Claude project itself. Use this skill when making changes to Jean Claude's source code, tests, documentation, or architecture. This skill provides project-specific test...
Use when reviewing code for architectural consistency, designing backend systems, or evaluating structural changes
Use when optimizing performance, profiling bottlenecks, or architecting for scale
Reuse existing Prospect ID code instead of creating new abstractions
Extract business rules (BR-*) from requirements - validation rules, business logic, error handling, and decision criteria. Use when disambiguating requirements to identify specific rules that can be autogenerat...
Autogenerate production code from disambiguated business rules (BR-*). Converts BR-* specifications into validators, constants, and logic. Use when requirements have been disambiguated into BR-*, C-*, F-* forma...
Extract technical constraints (C-*) from ecosystem E(t) - timeouts, API limits, compliance requirements, platform dependencies. Acknowledges given constraints, not design choices. Use to document ecosystem real...
Create technical solution architecture from requirements with REQ-* traceability. Designs components, APIs, data models, and interactions. Tags all design artifacts with requirement keys. Use after requirements...
Create Architecture Decision Records (ADRs) documenting strategic technical decisions while acknowledging ecosystem E(t) constraints. Use when choosing cloud providers, languages, frameworks, databases, or arch...
Break vague requirements into precise business rules (BR-*), constraints (C-*), and formulas (F-*) for code generation. Orchestrates extraction of BR-*, C-*, F-* from REQ-*. Use after requirement-extraction to...
Expert-level site reliability engineering, SLOs, incident management, and operational excellence
Expert-level IoT systems, embedded devices, edge computing, and IoT protocols
Expert-level C# development with .NET 8+, ASP.NET Core, LINQ, async/await, and enterprise patterns
Expert-level system design, architecture patterns, scalability, and distributed systems
Expert-level data mesh architecture, domain-oriented ownership, data products, federated governance, and self-serve platforms
Expert-level Scala, functional programming, Akka, and reactive systems
Expert-level Linkerd service mesh management, traffic control, reliability, and production operations
Expert-level API design principles, REST, GraphQL, versioning, and API best practices
Expert-level gRPC, Protocol Buffers, microservices communication, and streaming
Expert-level microservices architecture, patterns, service mesh, and distributed systems
Expert-level Rust development with ownership, lifetimes, async, error handling, and production-grade patterns
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.