Analyze a codebase and generate Project_Architecture_Blueprint.md — detected stacks and architecture patterns, diagrams, layers, cross-cutting concerns, extension guidance. Use to document, map, or blueprint a project's architecture or keep it consistent.

2026-07-040

backend-delivery-loop

jgamaraalv/delivery-loop

Continuous backend delivery loop — cycles subagents through test → diagnose → fix → review → secure → re-test until the suite, quality, and security gates are clean. Use to develop, fix, harden, or finish a backend feature/service/endpoint.

2026-07-040

backend-design

jgamaraalv/delivery-loop

Design backend systems — REST/GraphQL/gRPC APIs, microservices, database schemas, auth, caching, message queues, scalability. Use when designing backend services, APIs, data models, distributed systems, or auth flows.

2026-07-040

backend-dev-guidelines

jgamaraalv/delivery-loop

Shared backend guide for Langfuse's Next.js/tRPC/BullMQ/TypeScript monorepo — tRPC routers, public REST endpoints, BullMQ processors, services, Prisma/ClickHouse access, Zod validation, and backend tests across web/worker/shared.

2026-07-040

backend-testing

jgamaraalv/delivery-loop

Turn backend test ambiguity into one practical test packet — API/service/repo/auth coverage, fixture & seed/reset strategy, mock-vs-container choices, contract checks, and flaky-suite stabilization across local and CI.

2026-07-040

backend-to-frontend-handoff-docs

jgamaraalv/delivery-loop

Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'.

2026-07-040

name	accessibility-a11y
description	Build inclusive, WCAG-compliant UIs. Use for a11y, screen readers, ARIA, keyboard nav, contrast, or accessibility audits.

Accessibility (a11y) Best Practices

You are an expert in web accessibility and inclusive design. Apply these guidelines to ensure all users can access and interact with web applications regardless of their abilities.

Core Accessibility Principles

Follow WCAG (Web Content Accessibility Guidelines) standards
Use semantic HTML to improve accessibility and screen reader compatibility
Ensure high accessibility standards using ARIA roles and native accessibility props
Design for all users including those with visual, auditory, motor, and cognitive disabilities
Test with various assistive technologies

References

Each file is loaded on demand — read one only when the task needs that depth (progressive disclosure).

references/semantic-aria.md — semantic HTML (structural elements, form accessibility) and ARIA (when to use it, common patterns) · read when authoring markup, forms, or non-native interactive widgets.
references/visual-keyboard.md — visual accessibility (color, contrast, focus management) and keyboard navigation (requirements, interactive elements, touch targets) · read when styling visuals/focus or making interactions keyboard-operable.
references/content-responsive.md — content accessibility (images, media, text, typography) and responsive/adaptive design (mobile-first, user preferences like prefers-reduced-motion) · read when handling images/media/copy or building responsive, preference-aware layouts.
references/testing-css.md — testing & validation (automated tools, manual/screen-reader testing) and CSS best practices for accessibility · read when auditing/validating a11y or setting up styling conventions.