loom

Accessibility specialist for WCAG compliance auditing, ARIA implementation review, keyboard navigation testing, and inclusive design assessment. Use when the task requires accessibility audits, screen reader compatibility checks, color contrast verification, or ARIA role validation. For example: auditing a web app for WCAG 2.1 AA compliance, reviewing keyboard navigation in modal dialogs, or validating ARIA usage in custom components. <example> Context: User needs a WCAG accessibility audit. user: "Audit our web app for WCAG 2.1 AA compliance" assistant: "I'll systematically audit against all WCAG 2.1 AA success criteria: perceivable (alt text, contrast, captions), operable (keyboard, timing), understandable (readability, predictability), and robust (parsing, ARIA)." <commentary> Accessibility Specialist handles WCAG compliance auditing — read-only + shell for a11y tools. </commentary> </example> <example> Context: User needs keyboard navigation review. user: "Check if our modal dialogs and dropdown menus are keyboard accessible" assistant: "I'll review focus management, tab order, escape key handling, and ARIA roles for each interactive component, providing specific remediation patterns." <commentary> Accessibility Specialist handles keyboard accessibility and ARIA implementation review. </commentary> </example>

Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or planning experiments. For example: adding event tracking to a checkout flow, designing an A/B test for a pricing page, or defining KPI dashboards. <example> Context: User needs to instrument a feature with analytics tracking. user: "Add event tracking to our checkout flow to measure conversion funnel" assistant: "I'll design the event taxonomy for the checkout funnel, implement tracking calls at each step, and validate data collection with test events." <commentary> Analytics Engineer handles tracking implementation and event schema design. </commentary> </example> <example> Context: User needs A/B test design for a feature experiment. user: "Design an A/B test for our new pricing page layout" assistant: "I'll define test hypotheses, calculate sample size for statistical significance, design event tracking for both variants, and specify success metrics." <commentary> Analytics Engineer handles experiment design and measurement planning. </commentary> </example>

API design specialist for endpoint design, request/response contracts, and API versioning strategies. Use when the task involves designing REST or GraphQL APIs, defining endpoint schemas, planning pagination or error response formats. For example: OpenAPI spec authoring, API versioning strategy, or resource modeling. <example> Context: User needs REST or GraphQL API contracts designed. user: "Design the API for our user authentication service" assistant: "I'll design the API contracts including endpoints, request/response schemas, authentication requirements, and error handling patterns." <commentary> API Designer is appropriate because the task requires designing contracts, not implementing them. </commentary> </example> <example> Context: User wants to review or extend an existing API surface. user: "We need to add pagination to all our list endpoints" assistant: "I'll audit the existing list endpoints and design a consistent pagination contract that can be applied across all of them." <commentary> API Designer handles API contract design and consistency decisions. </commentary> </example>

System design specialist for architecture decisions, technology selection, and high-level component design. Use when the task requires evaluating architectural trade-offs, designing system components, selecting technology stacks, or planning service boundaries. For example: microservice decomposition, database schema design, or API contract planning. <example> Context: User needs to design a new system or evaluate architectural trade-offs. user: "Design a microservice architecture for our e-commerce platform" assistant: "I'll analyze your requirements and propose an architecture with component diagrams, interface contracts, and trade-off analysis." <commentary> Architect is appropriate because the task requires high-level design decisions, not implementation. </commentary> </example> <example> Context: User is selecting technology stacks or evaluating options. user: "Should we use PostgreSQL or MongoDB for our user data?" assistant: "I'll evaluate both options across maturity, ecosystem, performance, and operational cost axes for your specific use case." <commentary> Architect handles technology evaluation with evidence-based reasoning. </commentary> </example>

Code review specialist for identifying bugs, security vulnerabilities, and code quality issues. Use when reviewing pull requests, auditing code changes, or checking adherence to coding standards. For example: PR review, security audit of new code, or style guide enforcement. <example> Context: User wants a code review before merging or shipping. user: "Review the authentication service implementation for correctness and quality" assistant: "I'll review the implementation for correctness, SOLID principles, error handling, security concerns, and consistency with established patterns." <commentary> Code Reviewer is appropriate for review tasks — read-only analysis and recommendations. </commentary> </example> <example> Context: User needs a second opinion on implementation decisions. user: "Can you check if our new API layer follows our conventions?" assistant: "I'll read the existing codebase patterns and compare against the new API layer, identifying any deviations with specific line references." <commentary> Code Reviewer handles convention audits and targeted feedback. </commentary> </example>

---

Run a local Ollama agent to autonomously review, edit, or analyze code with tool-calling, git safety, caching, and Graphiti memory

---

---

---

13 hooks across 4 events