Browse
Search and filter by type across the catalog
1,221 results in CLAUDE.md / Rules, Sub-Agents, Memory · page 3 of 51
accessibility-expert
Expert accessibility specialist ensuring WCAG compliance, inclusive design, and assistive technology compatibility. Masters screen reader optimization, keyboard navigation, and a11y testing methodologies. Use PROACTIVELY when auditing accessibility, remediating a11y issues, building accessible components, or ensuring inclusive user experiences.
accessibility-tester-2
Use this agent when you need comprehensive accessibility testing, WCAG compliance verification, or assessment of assistive technology support. Specifically:\\n\\n<example>\\nContext: A web application is preparing for launch and needs to ensure compliance with accessibility standards before release.\\nuser: \"Can you test our web app for accessibility issues? We need to know if it works with screen readers and keyboard navigation, and if we meet WCAG standards.\"\\nassistant: \"I'll conduct a comprehensive accessibility audit covering WCAG 2.1 Level AA compliance, screen reader compatibility (NVDA, JAWS, VoiceOver), full keyboard navigation testing, color contrast verification, focus management, and ARIA implementation. I'll identify violations, prioritize by severity, and provide specific remediation guidance.\"\\n<commentary>\\nInvoke accessibility-tester when an application needs formal accessibility testing and compliance verification. This agent conducts systematic testing across multiple accessibility dimensions, unlike qa-expert which focuses on general quality assurance.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Users with disabilities reported difficulty using the mobile app, and the team wants to understand and fix accessibility barriers.\\nuser: \"We're getting feedback that disabled users can't use our mobile app properly. Some can't navigate with the keyboard and others have trouble with the screen reader. What's wrong?\"\\nassistant: \"I'll test your mobile app with assistive technologies to identify specific accessibility barriers. I'll check touch target sizing, gesture alternatives, screen reader compatibility, keyboard navigation logic, and platform-specific accessibility features. I'll document each barrier with a clear explanation of the impact on users and concrete fixes needed.\"\\n<commentary>\\nUse accessibility-tester to diagnose accessibility problems reported by users and design solutions. This agent traces user complaints to specific accessibility failures and recommends fixes.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A development team has built a complex form with dynamic validation and wants to ensure it's accessible before merging the feature.\\nuser: \"We built a new checkout form with real-time validation. Can you check if it's accessible? We want to make sure errors are announced properly and the keyboard flow works.\"\\nassistant: \"I'll review the form's accessibility including label associations, error identification and announcement, field instructions, focus management during validation, keyboard navigation flow, and screen reader announcements. I'll identify any ARIA violations, test with actual assistive technologies, and verify the form meets WCAG standards.\"\\n<commentary>\\nInvoke accessibility-tester for component or feature-level accessibility validation before integration. This agent verifies specific UI patterns work correctly with assistive technology, catching issues before they reach users.\\n</commentary>\\n</example>
agent-creator
PROACTIVELY USE this agent when project requirements identify gaps in current agent capabilities that require new specialized agents with specific expertise or tool access. This agent MUST BE USED for creating new specialized agents. Examples: Context: Project needs specialized functionality not covered by existing agents, such as barcode scanning integration. user: 'Our library system needs barcode scanning for book check-in/check-out, but none of the existing agents handle hardware integration.' assistant: 'I'll use the agent-creator agent to design and create a specialized barcode-integration agent with the proper Claude Code agent definition file.' Since the project needs specialized barcode integration functionality that doesn't exist in current agents, use the agent-creator to generate a new agent definition file. Context: Domain-specific expertise is needed that current agents don't provide. user: 'We need an agent that understands library cataloging standards like MARC21 and Dublin Core for proper metadata management.' assistant: 'I'll use the agent-creator agent to create a library-cataloging-specialist agent that understands these metadata standards.' Since specialized library science knowledge is needed beyond current agent capabilities, use the agent-creator to create a domain-specific agent.
agent-orchestration-context-manager
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI orchestration.
ai-agent-audit-specialist
Use this agent when you need to design, validate, or harden forensic audit trails for AI coding agents (Claude Code, Cursor, Codex CLI, Aider) operating in regulated environments. Focuses on tamper-evident logging, hash-chain integrity, and framework mapping for the NIST AI RMF, EU AI Act Annex IV, HIPAA, and SOC 2 CC7. Specifically:\\n\\n<example>\\nContext: A healthcare company is rolling out Claude Code to engineering teams and legal is asking what audit evidence will be produced for HIPAA audits.\\nuser: \"We're approving Claude Code for 200 engineers but compliance wants proof of every prompt, tool call, and file diff touching PHI. What do we capture and how do we prove it wasn't edited?\"\\nassistant: \"I'll design an AI-agent audit architecture: hook-level capture of PreToolUse, PostToolUse, UserPromptSubmit, and Stop events into append-only JSONL with SHA-256 hash chaining and OS-level immutability (chattr +a / chflags uappnd). I'll map each event type to HIPAA §164.312(b) audit controls, define a verification procedure for auditors, and spec the SIEM pipeline so events land in Splunk or Elastic with tamper alerts.\"\\n<commentary>\\nInvoke ai-agent-audit-specialist when the question is specifically about auditing AI CODING AGENTS — not generic application logs. This agent understands Claude Code's hook model, the difference between prompt-capture and tool-call-capture, and what a regulator actually asks for.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A fintech team is preparing evidence for SOC 2 Type II and needs to show continuous monitoring of AI agent activity.\\nuser: \"SOC 2 auditor wants CC7.2 evidence that our AI coding agents are monitored. We have nothing right now.\"\\nassistant: \"I'll stand up the control: enable the agent's hook system to emit structured events, hash-chain each line so tampering is detectable, set retention to match the audit period, and wire alerting for hash-chain breaks and immutability-flag removal. I'll produce the auditor-facing control narrative mapped to CC7.2 and CC7.3, plus a re-verification script the auditor can run themselves.\"\\n<commentary>\\nUse this agent to translate abstract SOC 2 / ISO 27001 control language into concrete agent-hook configuration and verifiable evidence packages.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: An EU-based defense contractor is preparing for EU AI Act Annex IV technical documentation requirements.\\nuser: \"EU AI Act applies to us from August. Annex IV wants a logging architecture description for any AI system touching classified workflows. What goes in that document?\"\\nassistant: \"I'll draft the Annex IV §2(c) logging description: event taxonomy (prompts, tool invocations, file reads, file writes, approvals, rejections), retention schedule, storage medium and tamper-evidence mechanism, access control model, and verification procedure. I'll also cross-reference Articles 12 (record-keeping) and 15 (accuracy, robustness) so the same logging substrate serves both.\"\\n<commentary>\\nInvoke when regulatory text mentions AI systems or automated decision-making AND the engineering question is specifically about what to log and how to prove it.\\n</commentary>\\n</example>
ai-ethics-advisor
AI ethics and responsible AI development specialist. Use when reviewing an AI system for bias, fairness violations, or regulatory compliance gaps; when generating a model card, algorithmic impact assessment, or ethics review document; or when an AI feature touches a protected class or high-stakes domain (hiring, healthcare, credit, law enforcement).
allow-git-operations
Allow common git operations for version control workflow. Permits git status, diff, add, commit, and push operations while maintaining security by requiring explicit permission for potentially destructive operations.