Discover testing security architecture patterns skills, compare source repositories and read the instructions for each workflow.
Backend development patterns for TanStack Start with server functions, middleware, Zod validation, and Nitro. Use when creating API endpoints, server functions, handling authentication, processing webhooks, fil...
Security best practices for TanStack Start applications with React 19, Drizzle ORM, PostgreSQL, Stripe, OAuth, and AWS S3/R2. Use when writing secure code, implementing authentication, handling payments, protec...
This skill should be used when capturing reusable workflows from conversations, codifying decision heuristics, or when "patternify", "capture", or "codify workflow" are mentioned.
This skill should be used when coordinating agents, delegating tasks to specialists, or when "dispatch agents", "which agent", or "multi-agent" are mentioned.
This skill should be used when designing systems, evaluating architectures, making technology decisions, or planning for scale. Provides technology selection frameworks, scalability planning, and architectural...
This skill should be used when recognizing recurring themes, codifying best practices, extracting reusable workflows, or when "pattern", "recurring", or "repeated" are mentioned.
Deep structural analysis of @Fake annotated interfaces examining method signatures, property definitions, generic type parameters, suspend functions, complexity assessment, and generation strategy recommendatio...
Use when you need to plan technical solutions that are scalable, secure, and maintainable.
AWS serverless and event-driven architecture expert based on Well-Architected Framework. Use when building serverless APIs, Lambda functions, REST APIs, microservices, or async workflows. Covers Lambda with Typ...
Integrate Dapr for pub/sub messaging and scheduled jobs. Use this skill when implementing event-driven architectures with Dapr, handling CloudEvent message formats, setting up pub/sub subscriptions, or scheduli...
Creates blueprint-driven skills for infrastructure and deployment tasks. This skill should be used when creating new skills that require templates, patterns, or reference configurations (e.g., Dockerfiles, Helm...
SRE patterns for production service reliability: SLOs, error budgets, postmortems, and incident response. Use when defining reliability targets, writing postmortems, implementing SLO alerting, or establishing o...
自动化的记忆管理中间件，执行 Retrieve-Respond-Save 闭环以维持长期记忆。
Create Architecture Decision Records (ADRs) to document significant technical decisions, their context, alternatives considered, and consequences. Use when making architectural choices, selecting libraries/fram...
Production ETL patterns orchestrator. Routes to core reliability patterns and incremental load strategies.
Implement business logic with ActiveInteraction and AASM state machines. Routes to specialized skills for typed operations and state management.
Implement state machines with AASM for workflow management. Covers state transitions, guards, callbacks, and testing.
Implement typed business operations with ActiveInteraction. Covers input types, composition, controller patterns, and testing.
dbt (data build tool) patterns for model organization, incremental strategies, and testing.
Use when implementing real-time features requiring reliability, especially LLM streaming. Applies AnyCable patterns for message delivery guarantees, presence tracking, and Action Cable migration.
Jobs-to-be-Done framework for understanding customer motivations and building solutions that get "hired".
Expert guidance on modern React patterns including hooks, composition, state management, and concurrent features. Use when implementing React components or refactoring existing code.
Record domain events and dispatch to inbox handlers for side effects, audit trails, and activity feeds. Use when building activity logs, syncing external services, or decoupling event creation from processing....
Core ETL reliability patterns including idempotency, checkpointing, error handling, chunking, retry logic, and logging.
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.