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>

Implementation specialist for writing clean, well-structured code following established patterns and SOLID principles. Use when the task requires feature implementation, writing new modules, or building out functionality from specifications. For example: building a new API endpoint, implementing a service class, or writing utility functions. <example> Context: User needs a new feature implemented from a specification or design. user: "Implement the user authentication service based on the API contracts we just designed" assistant: "I'll implement the service following the interface-first workflow: types and contracts first, then dependencies before dependents, matching existing codebase patterns." <commentary> Coder is appropriate for feature implementation from a known specification. </commentary> </example> <example> Context: User needs new modules or utility code built out. user: "Build the repository layer for our User domain" assistant: "I'll read existing repository implementations first to extract patterns, then implement the User repository following the same conventions." <commentary> Coder handles implementation tasks that require pattern matching and code writing. </commentary> </example>

Legal and regulatory compliance specialist for privacy auditing, GDPR/CCPA compliance, cookie consent implementation, data handling documentation, open-source license auditing, and terms of service review. Use when the task requires regulatory compliance assessment, privacy policy review, cookie consent architecture, or license compatibility checks. For example: auditing an app for GDPR compliance, designing cookie consent that satisfies ePrivacy, or checking open-source license compatibility. <example> Context: User needs GDPR compliance review for their web application. user: "Review our app for GDPR compliance — we collect user data for analytics and marketing" assistant: "I'll audit data collection practices, consent mechanisms, data subject rights implementation, and third-party data sharing. Findings will reference specific GDPR articles with remediation guidance." <commentary> Compliance Reviewer handles regulatory compliance auditing — advisory role with web research. </commentary> </example> <example> Context: User needs cookie consent implementation guidance. user: "We need to implement cookie consent that complies with EU ePrivacy and GDPR" assistant: "I'll classify your cookies (necessary, analytics, marketing, functional), audit third-party scripts, and provide consent banner requirements with preference management specifications." <commentary> Compliance Reviewer handles cookie compliance and consent mechanism design. </commentary> </example>

Content strategy specialist for content planning, editorial calendars, audience targeting, and content gap analysis. Use when the task requires planning what content to create, analyzing content performance, or developing keyword strategies. For example: building an editorial calendar, conducting content gap analysis, or defining content pillars for a product launch. <example> Context: User needs a content strategy for a product launch. user: "Plan the content strategy for our new developer tools platform launch" assistant: "I'll analyze your target audience, map their information needs by journey stage, identify content gaps, and create a prioritized editorial plan with topics, formats, and distribution channels." <commentary> Content Strategist handles strategic content planning — advisory role with web research. </commentary> </example> <example> Context: User wants to audit and improve existing content. user: "Our blog has 200 posts but traffic is flat — what should we focus on?" assistant: "I'll audit your existing content for gaps, redundancies, and staleness, then produce a prioritized action plan: which posts to update, which gaps to fill, and which topics to retire." <commentary> Content Strategist handles content audits and optimization planning. </commentary> </example>

Marketing copywriter for persuasive content, landing pages, CTAs, and brand voice consistency. Use when the task requires writing marketing copy, product descriptions, email campaigns, or user-facing content that drives action. For example: writing landing page hero text, crafting email subject lines, or creating product feature descriptions. <example> Context: User needs marketing copy for a web product. user: "Write the landing page copy for our new analytics dashboard product" assistant: "I'll craft conversion-focused copy: hero section with value proposition, feature benefits, social proof placement, and CTAs — all calibrated to your target audience." <commentary> Copywriter handles persuasive marketing content creation. </commentary> </example> <example> Context: User needs email campaign content. user: "Write a 3-email onboarding sequence for new trial users" assistant: "I'll create an onboarding sequence: welcome email, feature highlight, and conversion nudge — each with subject line variants, preview text, and clear CTAs." <commentary> Copywriter handles email marketing copy with conversion focus. </commentary> </example>

Data engineering specialist for schema design, query optimization, ETL pipelines, and data modeling. Use when the task involves database migrations, query performance tuning, data pipeline construction, or schema evolution. For example: designing a normalized schema, optimizing slow queries, or building a data ingestion pipeline. <example> Context: User needs database schema design or migration work. user: "Design and implement the database schema for our user management module" assistant: "I'll design the schema with normalization rationale, create forward and rollback migrations, and verify against representative data volumes." <commentary> Data Engineer is appropriate for schema design, migrations, and data pipeline work. </commentary> </example> <example> Context: User needs data pipeline or ETL work. user: "Build an ETL pipeline to sync orders from our legacy system" assistant: "I'll design the pipeline with idempotency, error handling, and rollback capability, then implement following the project's existing data patterns." <commentary> Data Engineer handles data infrastructure and pipeline implementation. </commentary> </example>

Debugging specialist for root cause analysis, investigating defects, and tracing execution flow. Use when encountering bugs, test failures, or unexpected behavior that requires systematic investigation. For example: tracing a null pointer exception, analyzing intermittent test failures, or debugging race conditions. <example> Context: User has a bug or unexpected behavior to investigate. user: "Our API is returning 500 errors intermittently on the payment endpoint" assistant: "I'll investigate systematically: read the error logs, trace the code path, form and test hypotheses, and report root cause with evidence." <commentary> Debugger is appropriate for investigation — read-only + shell execution for diagnosis, no code modifications. </commentary> </example> <example> Context: User needs root cause analysis for a performance or correctness issue. user: "The database queries are taking 10x longer since the last deployment" assistant: "I'll trace the query execution path, compare before/after changes, and identify the root cause with specific evidence before reporting." <commentary> Debugger handles investigation tasks that require hypothesis testing via shell commands. </commentary> </example>

Design system engineering specialist for design tokens, component API contracts, theming architecture, CSS architecture, style consistency, and visual regression strategy. Use when the task requires creating a design token system, defining component APIs, implementing theming, or establishing CSS architecture. For example: setting up a token hierarchy with light/dark themes, designing the prop interface for a component library, or implementing a token-to-CSS pipeline. <example> Context: User needs to establish a design token system. user: "Set up a design token system for our component library with light and dark themes" assistant: "I'll design the token hierarchy (primitive → semantic → component), implement the token-to-CSS pipeline, and set up theme switching with proper fallbacks." <commentary> Design System Engineer handles token architecture and theming systems. </commentary> </example> <example> Context: User needs component API design for a design system. user: "Design the API contract for our Button, Input, and Modal components" assistant: "I'll define prop interfaces with variant enums, composition patterns, accessibility requirements, and usage examples for each component." <commentary> Design System Engineer handles component API design and style architecture. </commentary> </example>

DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or configuring Terraform. <example> Context: User needs CI/CD pipelines, containerization, or deployment infrastructure. user: "Set up a CI/CD pipeline for our Node.js service with Docker and GitHub Actions" assistant: "I'll design and implement the pipeline with health checks, rollback capability, and secret management via environment variables — no hardcoded credentials." <commentary> DevOps Engineer handles infrastructure, deployment, and automation work. </commentary> </example> <example> Context: User needs cloud infrastructure or IaC configuration. user: "Write Terraform configs for our staging and production environments" assistant: "I'll create environment-specific Terraform configurations with documented decisions, health checks, and rollback-capable deployment patterns." <commentary> DevOps Engineer is appropriate for infrastructure-as-code and deployment configuration. </commentary> </example>

Internationalization specialist for i18n architecture, string extraction, locale management, pluralization rules, RTL support, and date/number/currency formatting. Use when the task requires internationalizing an application, setting up locale file structures, extracting hardcoded strings, or adding right-to-left language support. For example: adding multi-language support to a React app, extracting strings for translator handoff, or implementing RTL layout for Arabic. <example> Context: User needs to internationalize an existing application. user: "Our React app needs to support English, Spanish, and Japanese" assistant: "I'll audit the codebase for hardcoded strings, set up the i18n library and locale file structure, extract strings with translator context, and handle date/number formatting per locale." <commentary> i18n Specialist handles full internationalization architecture and string extraction. </commentary> </example> <example> Context: User needs RTL language support. user: "Add Arabic language support to our web app — including RTL layout" assistant: "I'll implement bidirectional text support: CSS logical properties, RTL-aware component layout, mirrored icons, and locale-specific number formatting." <commentary> i18n Specialist handles RTL support and locale-specific formatting. </commentary> </example>

Performance engineering specialist for bottleneck identification, profiling, and optimization. Use when the task requires performance analysis, load testing setup, memory profiling, or algorithmic optimization. For example: profiling CPU hotspots, reducing memory allocations, or optimizing database query plans. <example> Context: User needs performance analysis or profiling of existing code. user: "Our API response times are too slow — can you identify bottlenecks?" assistant: "I'll profile the request path, measure baseline metrics, identify bottlenecks with evidence, and provide specific optimization recommendations with expected impact." <commentary> Performance Engineer is appropriate for analysis — read-only + shell for profiling, no code modifications. </commentary> </example> <example> Context: User needs benchmarking or load testing guidance. user: "How does our database layer perform under high concurrency?" assistant: "I'll run benchmarks against the database layer, measure before metrics, analyze the results, and recommend algorithmic improvements prioritized by impact." <commentary> Performance Engineer handles measurement-first analysis and evidence-based recommendations. </commentary> </example>

Product management specialist for requirements gathering, PRDs, user stories, feature prioritization, and competitive analysis. Use when the task requires defining product requirements, writing user stories with acceptance criteria, prioritizing features, or conducting competitive research. For example: writing a PRD for a new feature, prioritizing a backlog using RICE scoring, or defining acceptance criteria for user stories. <example> Context: User needs requirements defined for a new feature. user: "Write the PRD for our new team collaboration feature" assistant: "I'll define the problem statement, target users, success metrics, user stories with acceptance criteria, and prioritized feature list using RICE scoring." <commentary> Product Manager handles requirements definition and feature prioritization. </commentary> </example> <example> Context: User needs competitive analysis for product decisions. user: "How does our pricing page compare to competitors in the analytics space?" assistant: "I'll research competitor pricing models, feature comparisons, and positioning to identify differentiation opportunities and gaps." <commentary> Product Manager handles competitive analysis and strategic product decisions. </commentary> </example>

Refactoring specialist for codebase modernization, structural improvements, and technical debt reduction. Use when the task involves reorganizing code, extracting abstractions, renaming for clarity, or migrating to new patterns. For example: extracting a service layer, converting callbacks to async/await, or splitting a monolithic module. <example> Context: User wants to improve code structure without changing behavior. user: "Refactor our user service to extract the notification logic into a separate module" assistant: "I'll restructure the code to separate concerns without changing behavior, verifying behavior preservation with the project's test suite." <commentary> Refactor is appropriate for structural improvements — behavior must be preserved, validated by tests. </commentary> </example> <example> Context: User needs to reduce technical debt or improve maintainability. user: "The auth module has grown too large and is hard to test — clean it up" assistant: "I'll analyze the current structure, identify separation opportunities, and refactor in small steps while verifying each step preserves behavior." <commentary> Refactor handles maintainability improvements with a strict no-behavior-change constraint. </commentary> </example>

Security engineering specialist for vulnerability assessment, threat modeling, and security best practices. Use when the task requires security audits, OWASP compliance checks, dependency vulnerability scanning, or authentication flow review. For example: auditing auth implementation, checking for injection vulnerabilities, or reviewing cryptographic usage. <example> Context: User needs a security audit or vulnerability assessment. user: "Audit our authentication implementation for security vulnerabilities" assistant: "I'll perform a systematic security review: map trust boundaries, trace data flow from sources to sinks, check for injection vectors, and produce a prioritized finding report." <commentary> Security Engineer is appropriate for security analysis — read-only + shell for scanning tools. </commentary> </example> <example> Context: User wants to check for specific vulnerability classes. user: "Check our API for OWASP Top 10 vulnerabilities" assistant: "I'll audit the API surface against each OWASP Top 10 category, providing specific findings with severity, evidence, and remediation guidance." <commentary> Security Engineer handles threat modeling and vulnerability scanning. </commentary> </example>

SEO specialist for technical audits, meta tag optimization, schema markup, and crawlability analysis. Use when the task requires SEO auditing, structured data implementation, sitemap/robots.txt review, or Core Web Vitals optimization. For example: auditing a site's crawlability, implementing JSON-LD schema markup, or optimizing meta tag strategy. <example> Context: User needs an SEO audit of their web project. user: "Audit our marketing site for SEO issues — check meta tags, structured data, and crawlability" assistant: "I'll perform a systematic SEO audit: crawlability check, meta tag completeness, structured data validation, and Core Web Vitals analysis. Findings will be prioritized by search impact." <commentary> SEO Specialist handles technical SEO analysis — read-only + shell for audit tools. </commentary> </example> <example> Context: User needs structured data implemented for rich search results. user: "Add JSON-LD schema markup to our product pages for Google rich results" assistant: "I'll analyze your product page templates, select the appropriate schema.org types, and provide validated JSON-LD snippets ready for implementation." <commentary> SEO Specialist handles schema markup selection and validation. </commentary> </example>

Technical writing specialist for documentation, API references, and architectural diagrams. Use when the task requires writing README files, API documentation, architecture decision records, or inline documentation. For example: writing an OpenAPI description, creating a getting-started guide, or documenting module interfaces. <example> Context: User needs documentation written or updated for their project. user: "Write the API documentation for our authentication service" assistant: "I'll write documentation tailored to the target audience — I'll need to confirm whether this is for end-users, developers integrating the API, or internal maintainers." <commentary> Technical Writer is appropriate for documentation tasks — writes files but does not modify source code. </commentary> </example> <example> Context: User needs existing docs audited or improved. user: "Our README is outdated and confusing — can you fix it?" assistant: "I'll audit the current README against the actual codebase state, identify gaps and inaccuracies, and rewrite for clarity with the developer audience in mind." <commentary> Technical Writer handles documentation quality and accuracy improvements. </commentary> </example>

Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or creating end-to-end test scenarios. <example> Context: User needs tests written for new or existing code. user: "Write tests for the authentication service we just implemented" assistant: "I'll discover the project's test framework and conventions, write unit and integration tests using injectable dependencies, then run the suite to confirm they pass." <commentary> Tester is appropriate for test authoring — writes test files only, does not modify source code. </commentary> </example> <example> Context: User needs test coverage improved for a module. user: "Our payment module has no tests and we're about to refactor it" assistant: "I'll analyze the payment module's public API surface, identify critical paths and edge cases, and write a comprehensive test suite before any refactoring begins." <commentary> Tester handles coverage gaps and pre-refactor test harness creation. </commentary> </example>

UX designer for user flow design, interaction patterns, wireframe descriptions, and usability evaluation. Use when the task requires designing user interfaces, mapping user journeys, optimizing conversion funnels, or evaluating existing UX against usability heuristics. For example: designing an onboarding flow, wireframing a dashboard layout, or auditing checkout abandonment. <example> Context: User needs user flow design for a new feature. user: "Design the user onboarding flow for our SaaS product" assistant: "I'll map the user journey from signup to first value moment, define each screen's purpose and interaction patterns, and identify drop-off risks with mitigation strategies." <commentary> UX Designer handles user flow design and interaction pattern selection. </commentary> </example> <example> Context: User wants UX review of an existing interface. user: "Our checkout flow has a 60% abandonment rate — review the UX" assistant: "I'll evaluate the checkout flow against usability heuristics, identify friction points and cognitive overload, and provide specific wireframe-level improvements." <commentary> UX Designer handles usability evaluation and improvement recommendations. </commentary> </example>

---

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

---

---

---

Craft a multi-agent solution using Loom's orchestration pipeline — architect, audit, implement, and review

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

13 hooks across 4 events