Results for “patterns”

Apache Airflow DAG Patterns workflow skill. Use this skill when the user needs Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

The English summary is being prepared. Showing the original description.

Use when asked about UX patterns, interaction best practices, form design, navigation patterns, or loading states. Examples: "best practice for form validation", "navigation pattern for dashboard", "loading state UX"

The English summary is being prepared. Showing the original description.

Flask-specific delta on top of python-foundation:sqlalchemy-patterns: Flask-SQLAlchemy extension setup, db.Model declarative models (3.x Mapped style and 2.x legacy db.Column), synchronous db.session lifecycle bound to the app context, Flask-Migrate integration. Used by flask-architect (model definitions) and flask-migrate-specialist (column finalization and migration). Activated automatically by flask-plugin/stack.md. Use this skill to: - Set up the SQLAlchemy and Migrate extensions with the app-factory pattern. - Write Flask-SQLAlchemy models with the db.Model base. - Query with db.session and manage the request-scoped session lifecycle. - Integrate Flask-Migrate for Alembic-based migrations managed via flask db commands. Do NOT use this skill for: - Framework-agnostic model, column, relationship, and querying rules — see python-foundation:sqlalchemy-patterns (load it first). - Flask routing and template/API patterns — see flask-plugin:flask-conventions. - Migration execution (flask db migrate, flask db upgrade) — that's flask-migrate-specialist's job.

The English summary is being prepared. Showing the original description.

Node.js backend conventions: project layout, configuration, logging, routing, and error handling patterns. Apply when implementing or modifying Node.js backend code in projects matching the nodejs stack profile. Use this skill to: - Pick conventional file/folder structure for a new module. - Wire configuration through env vars correctly. - Use the project's existing logger style. - Implement error handling that matches the framework (Express/Fastify/Koa). - Follow async/await patterns consistently. Do NOT use this skill for: - Frontend code (React/Vue/RN have their own conventions). - NestJS-specific patterns (decorators, DI, modules) — nest-plugin owns those. - Database schema design (call out as a sub-task; npm-patterns covers package management, not DB).

The English summary is being prepared. Showing the original description.

ORM patterns for NestJS: TypeORM, Prisma, Mongoose. Covers entities, repositories, transactions, migrations, common pitfalls (N+1, cascade deletes, transaction boundaries). Use this skill to: - Detect which ORM the project uses and apply matching patterns. - Define entities/schemas with the right decorators. - Inject repositories or Prisma client correctly. - Run transactions at the service boundary. - Write migrations that round-trip cleanly. Do NOT use this skill for: - Module/DI patterns (see nest-conventions). - Decorator usage broadly (see decorator-patterns). - Non-ORM raw SQL (rare; flag in BLOCKERS if needed).

The English summary is being prepared. Showing the original description.

Django web framework conventions: app layout, settings split (base/local/production), URLconf with app namespacing, CBV and DRF ViewSets, DRF serializers and permissions, form validation, signals, Django admin registration, and middleware. Activated automatically by django-plugin/stack.md. Works alongside python-foundation:python-conventions and django-plugin:django-orm-patterns. Use this skill to: - Structure a Django project with multiple apps and correct URLconf hierarchy. - Write CBVs and DRF ViewSets with appropriate permissions and serializers. - Configure settings correctly for different environments. - Use signals for decoupled event handling between apps. - Register models in Django admin with useful list_display and search_fields. Do NOT use this skill for: - Django ORM model field finalization and migration patterns — see django-plugin:django-orm-patterns. - Python language idioms (type hints, dataclasses, enums) — see python-foundation:python-conventions. - Testing patterns — see python-foundation:pytest-testing.

The English summary is being prepared. Showing the original description.

Research UI component patterns across the component.gallery corpus — 60 canonical component types, ~95 production design systems, 2,600+ examples — plus an AI-era overlay (prompt inputs, tool-call cards, streaming status, citations) and composite patterns (command palette, app shell, agent console). Compare implementations, find alternative component names, ground frontend decisions in real-world precedent. Pairs with minoan-frontend-design for research-then-build workflows. Triggers on component patterns, how do others implement X, design system research, component comparison, AI chat components, agent UI patterns.

The English summary is being prepared. Showing the original description.

Review custom components and layouts against shadcn design patterns, visual style conventions (Vega, Nova, Maia, Lyra, Mira), composition rules, design token usage, and Radix/Base UI composition patterns. Use PROACTIVELY after writing or modifying any custom UI component, page layout, or variant of a shadcn component. Use when the user says "review this component", "check my spacing", "does this follow shadcn patterns", "audit this layout", "is this shadcn-idiomatic", or shares a component for feedback. Catches spacing drift, hardcoded colors, missing data-slot attributes, inconsistent theme application, and composition anti-patterns that shipping-fast-with-AI tools often miss.

The English summary is being prepared. Showing the original description.

Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).

The English summary is being prepared. Showing the original description.

Cloud design patterns for distributed systems architecture covering 42 industry-standard patterns across reliability, performance, messaging, security, and deployment categories. Use when choosing architecture patterns for reliability, performance, messaging, or security in a distributed cloud system.

The English summary is being prepared. Showing the original description.

Canonical patterns for writing custom MSBuild targets. Only activate in MSBuild/.NET build context. USE FOR: diagnosing and fixing custom target authoring anti-patterns, reviewing MSBuild target definitions for correctness, diagnosing broken SDK target chains across files (e.g., Directory.Build.targets silently redefining SDK targets), fixing targets that replace CompileDependsOn instead of extending it with $(CompileDependsOn), fixing query targets that return stale results due to Outputs vs Returns misuse, fixing missing Inputs/Outputs causing unnecessary rebuilds, fixing missing FileWrites registration. Covers DependsOnTargets vs BeforeTargets vs AfterTargets, the Build→CoreBuild three-level pattern, hooking into the build pipeline, the $(XxxDependsOn) chain-extension pattern. DO NOT USE FOR: incremental build tuning (use incremental-build), parallelization (use build-parallelism), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.

The English summary is being prepared. Showing the original description.

Choose and compare cloud design patterns for distributed systems. Use when reviewing architecture, selecting workload patterns, or mapping reliability, performance, messaging, security, and migration concerns to concrete design options.

The English summary is being prepared. Showing the original description.

Expert en revue de code (PR reviews, patterns, anti-patterns, security, performance, readability)

The English summary is being prepared. Showing the original description.

Architect scalable backend services using layered architecture, dependency injection, middleware patterns, service classes, and separation of concerns. Use when building API services, implementing business logic layers, creating service classes, setting up middleware chains, implementing dependency injection, designing controller-service-repository patterns, handling cross-cutting concerns, creating domain models, implementing CQRS patterns, or establishing backend architecture standards.

The English summary is being prepared. Showing the original description.

Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).

The English summary is being prepared. Showing the original description.

front-end-design-patterns を使い、指定されたフロントエンド範囲に対して サブエージェント調査（必要時は複数スコープに分割した独立 fresh audit） → メインセッション修正 → 必要時のみ性能計測 → simple-add → 再調査を NO_FINDINGS まで繰り返す、機能変更なしの内部リファクタリングループ。 Trigger: front-end-refactor-loop, front-end-design-patterns リファクタリングループ, フロントエンドリファクタリングループ, Reactリファクタリングループ, サブエージェントでフロントエンド調査, NO_FINDINGSまでリファクタ, 性能計測つきフロントエンドリファクタ

The English summary is being prepared. Showing the original description.

Review database schema design and detect anti-patterns. Based on common RDB design knowledge and best practices. Supports Prisma, Drizzle, Rails, Django, Laravel, TypeORM, Sequelize, SQLAlchemy, and raw SQL (DDL). Use when the user says "review DB design", "check schema", "review table design", "review migration", "check for anti-patterns", "DB設計をレビューして", "スキーマを見て", "テーブル設計を確認して", "マイグレーションをレビューして", "アンチパターンがないか調べて", "この設計で問題ないか見て".

The English summary is being prepared. Showing the original description.

Stability Patterns knowledge base. Provides patterns, antipatterns, and PHP-specific guidelines for Circuit Breaker, Retry, Rate Limiter, Bulkhead, and resilience audits.

The English summary is being prepared. Showing the original description.

Design patterns and architectural guidance for .NET applications. Navigation skill covering vertical slices, domain modeling, messaging patterns, resilience, caching, and system design. For building scalable, maintainable applications. Keywords: architecture, patterns, vertical slices, domain modeling, messaging, resilience, caching, design patterns

The English summary is being prepared. Showing the original description.

Build and review server-side APIs with Node.js, Express, and Next.js. The skill provides patterns for separating responsibilities, reducing database queries, caching results, checking access permissions, and handling background work and errors.

• Designing API endpoints and separating responsibilities
• Reducing excessive database queries
• Adding caching to data retrieval

Build React Native and Expo screens with guidance on navigation, state management, and data fetching. Apply patterns for long lists, validated forms, device features, and secure token storage when developing or reviewing mobile apps.

• Building screens and navigation in Expo
• Separating remote data from interface state
• Improving long-list rendering

Build Redis caching, request limits, locks that coordinate multiple workers, and messaging. Use concrete implementation patterns to choose data structures, set key expiration, manage connections, and review common production pitfalls.

• Add response caching to an API
• Limit API requests per user
• Prevent workers from running the same job simultaneously

Build or review Java services with Quarkus 3.x using patterns for REST APIs, database access with Panache, and messaging with Apache Camel. Examples cover layered code structure, validation, transactions, and asynchronous processing, where work completes separately from the main flow.

• Designing a REST API with separate service and repository layers
• Connecting services through Camel and RabbitMQ
• Reviewing Panache database access and transactions

Guides electronic medical record development, covering visit workflows, prescriptions, and clinical data entry. Provides patterns for medication interaction alerts, abnormal result displays, audit trails, and accessible interfaces that keep patient information visible during care.

• Designing a patient visit workflow
• Adding medication interaction alerts
• Displaying abnormal laboratory results