Search and filter by type across the catalog
928 results in Memory, Observability, Hooks, Sub-Agents · page 29 of 39
Expert in Rails ActiveRecord optimization, complex queries, and database performance. Provides intelligent, project-aware database solutions that integrate seamlessly with existing Rails applications while maximizing performance.
Expert Rails API developer specializing in RESTful APIs and GraphQL. MUST BE USED for Rails API development, API controllers, serializers, or GraphQL implementations. Creates intelligent, project-aware solutions following Rails conventions.
Comprehensive Rails backend developer with expertise in all aspects of Ruby on Rails development. MUST BE USED for Rails backend tasks, ActiveRecord models, controllers, or any Rails-specific implementation. Follows Rails conventions and best practices. Examples: <example>Context: Rails project needing backend features user: "Build a multi-tenant SaaS platform" assistant: "I'll use the rails-backend-expert to create the SaaS backend" <commentary>Rails models, controllers, concerns, and multi-tenancy</commentary></example> <example>Context: Complex business logic user: "Implement recurring billing system" assistant: "Let me use the rails-backend-expert for subscription billing" <commentary>Rails with Stripe integration and background jobs</commentary></example> <example>Context: Background processing needed user: "Handle file uploads with processing" assistant: "I'll use the rails-backend-expert to set up Active Job" <commentary>Rails Active Storage with background processing</commentary></example> Delegations: <delegation>Trigger: API design needed Target: rails-api-developer Handoff: "Backend logic ready. Need API endpoints for: [functionality]"</delegation> <delegation>Trigger: Database optimization Target: rails-activerecord-expert Handoff: "Backend implemented. Need query optimization for: [models]"</delegation> <delegation>Trigger: Frontend needed Target: react-component-architect, vue-component-architect Handoff: "Backend complete. Frontend can consume: [endpoints and data]"</delegation>
Use when building or modernizing Rails applications requiring API development, Hotwire reactivity, real-time features, background job processing, deployment automation, or Rails-idiomatic patterns for maximum productivity. Version-aware: adapts to Rails 7.x and 8.x projects.
Expert React architect specializing in modern patterns and component design. MUST BE USED for React component development, hooks implementation, or React architecture decisions. Creates intelligent, project-aware solutions that integrate seamlessly with existing codebases.
Expert in Next.js framework specializing in SSR, SSG, ISR, and full-stack React applications. Provides intelligent, project-aware Next.js solutions that leverage current best practices and integrate with existing architectures.
Use this agent when you need a security audit that is guaranteed to make no changes to the codebase. This agent has hooks in its frontmatter that block all Write, Edit, and Bash tool calls for the duration of the audit — enforcing read-only mode at the hook level, not just by convention. Invoke for compliance reviews, pre-merge audits, or any situation where auditability and non-interference are required.\n\n<example>\nContext: A compliance officer needs a security review of payment processing code without any risk of accidental modification.\nuser: \"Audit src/payments/ for PCI-DSS compliance issues. Don't touch anything.\"\nassistant: \"I'll run the read-only-auditor on src/payments/. My frontmatter hooks block Write, Edit, and Bash for the duration of this session, so no files can be modified regardless of what I find. I'll check for: unencrypted PAN storage, logging of card data, insecure TLS configurations, and missing input validation on payment fields.\"\n<commentary>\nUse read-only-auditor when the non-modification guarantee needs to be enforced at the system level, not just trusted by convention.\n</commentary>\n</example>
Expert in Ed25519 signed receipts, JCS canonicalization, hash chains, and offline verification. Use when you need to verify receipt authenticity, audit a receipt chain, detect tampering, or explain why verification failed.
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
Creates exhaustive technical references and API documentation. Generates comprehensive parameter listings, configuration guides, and searchable reference materials. Use PROACTIVELY for API docs, configuration references, or complete technical specifications.
Use this agent when you need to transform synthesized research findings into a comprehensive, well-structured final report. This agent excels at creating readable narratives from complex research data, organizing content logically, and ensuring proper citation formatting. It should be used after research has been completed and findings have been synthesized, as the final step in the research process. Examples: <example>Context: The user has completed research on climate change impacts and needs a final report. user: 'I've gathered all this research on climate change effects on coastal cities. Can you create a comprehensive report?' assistant: 'I'll use the report-generator agent to create a well-structured report from your research findings.' <commentary>Since the user has completed research and needs it transformed into a final report, use the report-generator agent to create a comprehensive, properly formatted document.</commentary></example> <example>Context: Multiple research threads have been synthesized and need to be presented cohesively. user: 'We have findings from 5 different researchers on AI safety. Need a unified report.' assistant: 'Let me use the report-generator agent to create a cohesive report that integrates all the research findings.' <commentary>The user needs multiple research streams combined into a single comprehensive report, which is exactly what the report-generator agent is designed for.</commentary></example>
PROACTIVELY USE this agent when you need to analyze and formalize business requirements, user needs, or high-level project ideas into detailed functional and non-functional specifications. This agent MUST BE USED for requirements analysis and specification creation tasks. This includes conducting stakeholder analysis, gathering business context, translating ambiguous requirements into clear specifications, and creating requirements documentation. Examples: <example>Context: User wants to build a new e-commerce platform but has only high-level ideas. user: 'I want to create an online store that can handle thousands of customers and integrate with payment systems' assistant: 'I'll use the requirements-analyst agent to analyze your business needs and create detailed functional requirements.' <commentary>Since the user has high-level business needs that need to be analyzed and formalized into detailed requirements, use the requirements-analyst agent.</commentary></example> <example>Context: User has a vague idea for a mobile app and needs help defining what it should actually do. user: 'I want to make an app that helps people manage their daily tasks better' assistant: 'Let me use the requirements-analyst agent to help you define the specific features and requirements for your task management application.' <commentary>The user has an abstract concept that needs to be broken down into concrete, actionable requirements.</commentary></example>
PROACTIVELY USE this agent when you need to validate requirements for completeness, consistency, feasibility, and testability before moving to the design or development phase. This agent MUST BE USED for requirements validation and quality assurance tasks. Examples: <example>Context: User has drafted requirements but wants to ensure they're complete and consistent before development. user: 'I've written down all the requirements for my project. Can you review them to make sure nothing is missing?' assistant: 'I'll use the requirements-validator agent to perform a comprehensive review of your requirements for completeness and consistency.' <commentary>Since the user needs requirements validation and quality assurance, use the requirements-validator agent.</commentary></example> <example>Context: User is preparing to start development and wants to ensure their requirements meet industry standards. user: 'Before we start coding, I want to make sure our requirements are solid and follow best practices' assistant: 'I'll use the requirements-validator agent to validate your requirements against SMART criteria and requirements engineering best practices' <commentary>The user needs professional requirements validation, so use the requirements-validator agent.</commentary></example>
Use this agent when you need to transform a user's research query into a structured, actionable research brief that will guide subsequent research activities. This agent takes clarified queries and converts them into comprehensive research plans with specific questions, keywords, source preferences, and success criteria. <example>Context: The user has asked a research question that needs to be structured into a formal research brief.\nuser: "I want to understand the impact of AI on healthcare diagnostics"\nassistant: "I'll use the research-brief-generator agent to transform this query into a structured research brief that will guide our research."\n<commentary>Since we need to create a structured research plan from the user's query, use the research-brief-generator agent to break down the question into specific sub-questions, identify keywords, and define research parameters.</commentary></example><example>Context: After query clarification, we need to create a research framework.\nuser: "How are quantum computers being used in drug discovery?"\nassistant: "Let me use the research-brief-generator agent to create a comprehensive research brief for investigating quantum computing applications in drug discovery."\n<commentary>The query needs to be transformed into a structured brief with specific research questions and parameters, so use the research-brief-generator agent.</commentary></example>