Web accessibility implementation and audit patterns conforming to WCAG 2.1 AA. Covers semantic HTML, ARIA roles and properties, keyboard navigation, focus management, screen reader compatibility, color contrast, and accessible component patterns for modals, menus, forms, and live regions. Use when implementing UI…
Delegate bounded research, summarization, support, and advisory reviews to Antigravity CLI through agy for large files, broad exploration, long logs, diffs, or second opinions. Do not use for main coding, security-sensitive logic, or final reviews.
API contract design, versioning, and breaking change management for HTTP APIs. Covers OpenAPI specification as source of truth, backward compatibility rules, deprecation lifecycle, consumer-driven contract principles, and API design standards. Use when designing new API endpoints, reviewing API changes, managing API…
C programming patterns for embedded systems. Covers memory management, fixed-width types, bitwise operations, volatile and const correctness, interrupt-safe code, hardware register access, and defensive coding for resource-constrained environments. Use when writing or reviewing C code targeting microcontrollers…
Generate structured CHANGELOG entries from git history, PR descriptions, or session handoffs. Use when preparing a release, closing a sprint, or documenting changes for end users.
CI/CD pipeline design and implementation patterns for automated build, test, and deployment workflows. Covers GitHub Actions, quality gates, environment promotion, secret management in CI, Docker image publishing, and deployment safety patterns. Use when setting up or reviewing CI/CD pipelines, adding quality gates…
Perform code review. Quality analysis. Acceptance criteria verification. Best practices review. Includes security lens for backend code — covers OWASP Top 10 patterns, injection, auth/authZ, and secrets hygiene as part of every review.
Domain-driven data modeling patterns covering aggregate design, entity boundaries, value objects, and event sourcing fundamentals. Use when designing the domain model for a new service, reviewing existing data structures for DDD correctness, or deciding how to structure complex business logic around data.
Enforce structured root cause analysis before writing any fix. Use for any bug, error, crash, or unexpected behavior — prevents surface-level patches on deeper problems.
Build structured engineering documentation and execution flow artifacts by composing existing dev skills. Use when the user asks for docs + flow outputs, asks for /docs-flow, explicitly names dev-docs-flow, or needs one consolidated artifact from research/planning/implementation/review context.
Dockerfile and Docker Compose implementation and review patterns for containerized applications. Use when Codex needs to build, refactor, debug, or review Dockerfile, docker-compose.yml, compose.yaml, multi-stage builds, runtime images, service definitions, or Turborepo-compatible container workflows, especially for…
E2E testing patterns, verification procedures, and CI readiness checklists. Use for writing, debugging, or reviewing end-to-end tests, fixing flaky tests, creating Page Objects, and mocking external APIs.
Embedded build system patterns using CMake and GCC cross-compilation toolchain. Covers arm-none-eabi and riscv toolchain setup, CMake cross-compilation configuration, linker scripts, startup files, memory maps, and flashing with OpenOCD. Use when setting up a new embedded project from scratch, reviewing build…
Cross-cutting error handling patterns for production backend systems. Covers error boundary design, retry strategies, circuit breakers, graceful degradation, and error observability. Use when designing error handling for new services, reviewing error propagation across system boundaries, or hardening a service against…
Feature flag implementation and lifecycle management patterns. Covers flag types, rollout strategies, kill switches, flag hygiene, and integration patterns for backend and frontend. Use when implementing gradual rollouts, A/B tests, kill switches for risky features, or managing flag lifecycle from creation to cleanup.
Frontend implementation patterns, accessibility requirements, design system usage, and web performance guidelines. Use for implementing UI components, working with design tokens, ensuring a11y compliance, optimizing Core Web Vitals, and building reusable frontend code.
GraphQL schema design, resolver implementation, and performance patterns. Covers type system design, mutation patterns, N+1 problem with DataLoader, subscriptions, error handling, and security considerations. Use when designing or implementing a GraphQL API, reviewing resolver code, or solving N+1 query problems.
Web internationalization (i18n) implementation patterns using i18next and react-i18next. Covers translation file structure, pluralization, ICU message format, locale routing in Next.js/Nuxt, date and number formatting, RTL support, and missing translation handling. Use when adding multi-language support to a web…
Retrieve a small, bounded set of relevant prior notes from the Obsidian vault (concepts, patterns, playbooks, comparisons, ADRs, debug traces, experiments) before planning or implementing, instead of re-discovering decisions the vault already recorded. Returns a context pack of 3-7 notes with an explicit token budget…
★not rated 5 5d agoA94 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: