USP
Its unique granular plugin architecture ensures minimal token usage and high composability, allowing users to install only specific agents, commands, and skills needed for a task, unlike monolithic solutions. It also features a new PluginE…
Use cases
- 01Full-stack development orchestration
- 02Security scanning and auditing
- 03Multi-agent team collaboration
- 04Code review and quality analysis
- 05Infrastructure setup and operations
Detected files (8)
plugins/agent-teams/skills/parallel-feature-development/SKILL.mdskillShow content (6667 bytes)
--- name: parallel-feature-development description: Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system simultaneously, when establishing file ownership to prevent merge conflicts in a shared codebase, when designing interface contracts so parallel implementers can build against each other's APIs before they are ready, or when deciding whether to use vertical slices versus horizontal layers for a full-stack feature. version: 1.0.2 --- # Parallel Feature Development Strategies for decomposing features into parallel work streams, establishing file ownership boundaries, avoiding conflicts, and integrating results from multiple implementer agents. ## When to Use This Skill - Decomposing a feature for parallel implementation - Establishing file ownership boundaries between agents - Designing interface contracts between parallel work streams - Choosing integration strategies (vertical slice vs horizontal layer) - Managing branch and merge workflows for parallel development ## File Ownership Strategies ### By Directory Assign each implementer ownership of specific directories: ``` implementer-1: src/components/auth/ implementer-2: src/api/auth/ implementer-3: tests/auth/ ``` **Best for**: Well-organized codebases with clear directory boundaries. ### By Module Assign ownership of logical modules (which may span directories): ``` implementer-1: Authentication module (login, register, logout) implementer-2: Authorization module (roles, permissions, guards) ``` **Best for**: Feature-oriented architectures, domain-driven design. ### By Layer Assign ownership of architectural layers: ``` implementer-1: UI layer (components, styles, layouts) implementer-2: Business logic layer (services, validators) implementer-3: Data layer (models, repositories, migrations) ``` **Best for**: Traditional MVC/layered architectures. ## Conflict Avoidance Rules ### The Cardinal Rule **One owner per file.** No file should be assigned to multiple implementers. ### When Files Must Be Shared If a file genuinely needs changes from multiple implementers: 1. **Designate a single owner** — One implementer owns the file 2. **Other implementers request changes** — Message the owner with specific change requests 3. **Owner applies changes sequentially** — Prevents merge conflicts 4. **Alternative: Extract interfaces** — Create a separate interface file that the non-owner can import without modifying ### Interface Contracts When implementers need to coordinate at boundaries: ```typescript // src/types/auth-contract.ts (owned by team-lead, read-only for implementers) export interface AuthResponse { token: string; user: UserProfile; expiresAt: number; } export interface AuthService { login(email: string, password: string): Promise<AuthResponse>; register(data: RegisterData): Promise<AuthResponse>; } ``` Both implementers import from the contract file but neither modifies it. ## Integration Patterns ### Vertical Slice Each implementer builds a complete feature slice (UI + API + tests): ``` implementer-1: Login feature (login form + login API + login tests) implementer-2: Register feature (register form + register API + register tests) ``` **Pros**: Each slice is independently testable, minimal integration needed. **Cons**: May duplicate shared utilities, harder with tightly coupled features. ### Horizontal Layer Each implementer builds one layer across all features: ``` implementer-1: All UI components (login form, register form, profile page) implementer-2: All API endpoints (login, register, profile) implementer-3: All tests (unit, integration, e2e) ``` **Pros**: Consistent patterns within each layer, natural specialization. **Cons**: More integration points, layer 3 depends on layers 1 and 2. ### Hybrid Mix vertical and horizontal based on coupling: ``` implementer-1: Login feature (vertical slice — UI + API + tests) implementer-2: Shared auth infrastructure (horizontal — middleware, JWT utils, types) ``` **Best for**: Most real-world features with some shared infrastructure. ## Branch Management ### Single Branch Strategy All implementers work on the same feature branch: - Simple setup, no merge overhead - Requires strict file ownership to avoid conflicts - Best for: small teams (2-3), well-defined boundaries ### Multi-Branch Strategy Each implementer works on a sub-branch: ``` feature/auth ├── feature/auth-login (implementer-1) ├── feature/auth-register (implementer-2) └── feature/auth-tests (implementer-3) ``` - More isolation, explicit merge points - Higher overhead, merge conflicts still possible in shared files - Best for: larger teams (4+), complex features ## Troubleshooting **Implementers are blocking each other waiting for shared code.** Extract the shared piece into its own interface contract file owned by the team-lead and have implementers import from it. Neither implementer modifies the contract — they only implement against it. **Merge conflicts appear even with clear ownership rules.** A file was assigned to two agents, or a config/index file (e.g., `index.ts`, `__init__.py`) that auto-imports everything was modified by both. Designate one owner for all barrel/index files, or have the lead merge them at the end. **An implementer finishes early but the integration step is blocked.** Use a staging interface: the finished implementer writes a stub or mock of the downstream dependency so the other implementer can continue working. Replace with the real implementation at integration time. **The feature decomposition turned out wrong mid-stream.** Stop new work, have the lead redistribute files, and communicate the change via broadcast. Sunk cost on partially written code is acceptable — continuing with the wrong split is worse. **Tests written by one implementer fail against code written by another.** Interface contracts drifted: the implementer who owns the API changed a signature without notifying the test implementer. Enforce the rule that contract files require a broadcast before modification. ## Related Skills - [team-composition-patterns](../team-composition-patterns/SKILL.md) — Choose the right team size and agent types before decomposing work - [team-communication-protocols](../team-communication-protocols/SKILL.md) — Coordinate integration handoffs and plan approvals between implementersplugins/agent-teams/skills/team-communication-protocols/SKILL.mdskillShow content (6975 bytes)
--- name: team-communication-protocols description: Structured messaging protocols for agent team communication including message type selection, plan approval, shutdown procedures, and anti-patterns to avoid. Use this skill when establishing communication norms for a newly spawned team, when deciding whether to send a direct message or a broadcast, when a team-lead needs to review and approve an implementer's plan before work begins, when orchestrating a graceful team shutdown after all tasks are complete, or when debugging why teammates are not coordinating correctly at integration points. version: 1.0.2 --- # Team Communication Protocols Protocols for effective communication between agent teammates, including message type selection, plan approval workflows, shutdown procedures, and common anti-patterns to avoid. ## When to Use This Skill - Establishing communication norms for a new team - Choosing between message types (message, broadcast, shutdown_request) - Handling plan approval workflows - Managing graceful team shutdown - Discovering teammate identities and capabilities ## Message Type Selection ### `message` (Direct Message) — Default Choice Send to a single specific teammate: ```json { "type": "message", "recipient": "implementer-1", "content": "Your API endpoint is ready. You can now build the frontend form.", "summary": "API endpoint ready for frontend" } ``` **Use for**: Task updates, coordination, questions, integration notifications. ### `broadcast` — Use Sparingly Send to ALL teammates simultaneously: ```json { "type": "broadcast", "content": "Critical: shared types file has been updated. Pull latest before continuing.", "summary": "Shared types updated" } ``` **Use ONLY for**: Critical blockers affecting everyone, major changes to shared resources. **Why sparingly?**: Each broadcast sends N separate messages (one per teammate), consuming API resources proportional to team size. ### `shutdown_request` — Graceful Termination Request a teammate to shut down: ```json { "type": "shutdown_request", "recipient": "reviewer-1", "content": "Review complete, shutting down team." } ``` The teammate responds with `shutdown_response` (approve or reject with reason). ## Communication Anti-Patterns | Anti-Pattern | Problem | Better Approach | | --------------------------------------- | ---------------------------------------- | -------------------------------------- | | Broadcasting routine updates | Wastes resources, noise | Direct message to affected teammate | | Sending JSON status messages | Not designed for structured data | Use TaskUpdate to update task status | | Not communicating at integration points | Teammates build against stale interfaces | Message when your interface is ready | | Micromanaging via messages | Overwhelms teammates, slows work | Check in at milestones, not every step | | Using UUIDs instead of names | Hard to read, error-prone | Always use teammate names | | Ignoring idle teammates | Wasted capacity | Assign new work or shut down | ## Plan Approval Workflow When a teammate is spawned with `plan_mode_required`: 1. Teammate creates a plan using read-only exploration tools 2. Teammate calls `ExitPlanMode` which sends a `plan_approval_request` to the lead 3. Lead reviews the plan 4. Lead responds with `plan_approval_response`: **Approve**: ```json { "type": "plan_approval_response", "request_id": "abc-123", "recipient": "implementer-1", "approve": true } ``` **Reject with feedback**: ```json { "type": "plan_approval_response", "request_id": "abc-123", "recipient": "implementer-1", "approve": false, "content": "Please add error handling for the API calls" } ``` ## Shutdown Protocol ### Graceful Shutdown Sequence 1. **Lead sends shutdown_request** to each teammate 2. **Teammate receives request** as a JSON message with `type: "shutdown_request"` 3. **Teammate responds** with `shutdown_response`: - `approve: true` — Teammate saves state and exits - `approve: false` + reason — Teammate continues working 4. **Lead handles rejections** — Wait for teammate to finish, then retry 5. **After all teammates shut down** — Call `TeamDelete` to remove team resources ### Handling Rejections If a teammate rejects shutdown: - Check their reason (usually "still working on task") - Wait for their current task to complete - Retry shutdown request - If urgent, user can force shutdown ## Teammate Discovery Find team members by reading the config file: **Location**: `~/.claude/teams/{team-name}/config.json` **Structure**: ```json { "members": [ { "name": "security-reviewer", "agentId": "uuid-here", "agentType": "team-reviewer" }, { "name": "perf-reviewer", "agentId": "uuid-here", "agentType": "team-reviewer" } ] } ``` **Always use `name`** for messaging and task assignment. Never use `agentId` directly. ## Troubleshooting **A teammate is not responding to messages.** Check the teammate's task status. If it is idle, it may have completed its task and is waiting to be assigned new work or shut down. If it is still active, it may be mid-execution and will process messages once the current operation finishes. **The lead is sending broadcasts for every status update.** This is a common anti-pattern. Broadcasts are expensive — each one sends N messages. Use direct messages (`type: "message"`) for point-to-point updates. Reserve broadcasts for critical shared-resource changes like an updated interface contract. **A teammate rejected a shutdown request unexpectedly.** The teammate is still working. Check the rejection reason in the `shutdown_response` content field, wait for the work to finish, then retry. Never force-terminate a teammate that has unsaved work. **A plan_approval_request arrived but the request_id is missing.** The teammate called `ExitPlanMode` without the required request context. Have the teammate re-enter plan mode, complete exploration, and call `ExitPlanMode` again. The `request_id` is generated automatically by the plan mode system. **Two teammates are waiting on each other and neither is making progress.** This is a deadlock: both are blocked waiting for the other to finish first. The lead should send a direct message to one teammate with a stub or partial result so it can unblock and proceed. ## Related Skills - [team-composition-patterns](../team-composition-patterns/SKILL.md) — Select agent types and team size before establishing communication norms - [parallel-feature-development](../parallel-feature-development/SKILL.md) — Use communication protocols to coordinate integration handoffs between parallel implementersplugins/agent-teams/skills/task-coordination-strategies/SKILL.mdskillShow content (4690 bytes)
--- name: task-coordination-strategies description: Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress. version: 1.0.2 --- # Task Coordination Strategies Strategies for decomposing complex tasks into parallelizable units, designing dependency graphs, writing effective task descriptions, and monitoring workload across agent teams. ## When to Use This Skill - Breaking down a complex task for parallel execution - Designing task dependency relationships (blockedBy/blocks) - Writing task descriptions with clear acceptance criteria - Monitoring and rebalancing workload across teammates - Identifying the critical path in a multi-task workflow ## Task Decomposition Strategies ### By Layer Split work by architectural layer: - Frontend components - Backend API endpoints - Database migrations/models - Test suites **Best for**: Full-stack features, vertical slices ### By Component Split work by functional component: - Authentication module - User profile module - Notification module **Best for**: Microservices, modular architectures ### By Concern Split work by cross-cutting concern: - Security review - Performance review - Architecture review **Best for**: Code reviews, audits ### By File Ownership Split work by file/directory boundaries: - `src/components/` — Implementer 1 - `src/api/` — Implementer 2 - `src/utils/` — Implementer 3 **Best for**: Parallel implementation, conflict avoidance ## Dependency Graph Design ### Principles 1. **Minimize chain depth** — Prefer wide, shallow graphs over deep chains 2. **Identify the critical path** — The longest chain determines minimum completion time 3. **Use blockedBy sparingly** — Only add dependencies that are truly required 4. **Avoid circular dependencies** — Task A blocks B blocks A is a deadlock ### Patterns **Independent (Best parallelism)**: ``` Task A ─┐ Task B ─┼─→ Integration Task C ─┘ ``` **Sequential (Necessary dependencies)**: ``` Task A → Task B → Task C ``` **Diamond (Mixed)**: ``` ┌→ Task B ─┐ Task A ─┤ ├→ Task D └→ Task C ─┘ ``` ### Using blockedBy/blocks ``` TaskCreate: { subject: "Build API endpoints" } → Task #1 TaskCreate: { subject: "Build frontend components" } → Task #2 TaskCreate: { subject: "Integration testing" } → Task #3 TaskUpdate: { taskId: "3", addBlockedBy: ["1", "2"] } → #3 waits for #1 and #2 ``` ## Task Description Best Practices Every task should include: 1. **Objective** — What needs to be accomplished (1-2 sentences) 2. **Owned Files** — Explicit list of files/directories this teammate may modify 3. **Requirements** — Specific deliverables or behaviors expected 4. **Interface Contracts** — How this work connects to other teammates' work 5. **Acceptance Criteria** — How to verify the task is done correctly 6. **Scope Boundaries** — What is explicitly out of scope ### Template ``` ## Objective Build the user authentication API endpoints. ## Owned Files - src/api/auth.ts - src/api/middleware/auth-middleware.ts - src/types/auth.ts (shared — read only, do not modify) ## Requirements - POST /api/login — accepts email/password, returns JWT - POST /api/register — creates new user, returns JWT - GET /api/me — returns current user profile (requires auth) ## Interface Contract - Import User type from src/types/auth.ts (owned by implementer-1) - Export AuthResponse type for frontend consumption ## Acceptance Criteria - All endpoints return proper HTTP status codes - JWT tokens expire after 24 hours - Passwords are hashed with bcrypt ## Out of Scope - OAuth/social login - Password reset flow - Rate limiting ``` ## Workload Monitoring ### Indicators of Imbalance | Signal | Meaning | Action | | -------------------------- | ------------------- | --------------------------- | | Teammate idle, others busy | Uneven distribution | Reassign pending tasks | | Teammate stuck on one task | Possible blocker | Check in, offer help | | All tasks blocked | Dependency issue | Resolve critical path first | | One teammate has 3x others | Overloaded | Split tasks or reassign | ### Rebalancing Steps 1. Call `TaskList` to assess current state 2. Identify idle or overloaded teammates 3. Use `TaskUpdate` to reassign tasks 4. Use `SendMessage` to notify affected teammates 5. Monitor for improved throughputplugins/accessibility-compliance/skills/screen-reader-testing/SKILL.mdskillShow content (12034 bytes)
--- name: screen-reader-testing description: Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support. --- # Screen Reader Testing Practical guide to testing web applications with screen readers for comprehensive accessibility validation. ## When to Use This Skill - Validating screen reader compatibility - Testing ARIA implementations - Debugging assistive technology issues - Verifying form accessibility - Testing dynamic content announcements - Ensuring navigation accessibility ## Core Concepts ### 1. Major Screen Readers | Screen Reader | Platform | Browser | Usage | | ------------- | --------- | -------------- | ----- | | **VoiceOver** | macOS/iOS | Safari | ~15% | | **NVDA** | Windows | Firefox/Chrome | ~31% | | **JAWS** | Windows | Chrome/IE | ~40% | | **TalkBack** | Android | Chrome | ~10% | | **Narrator** | Windows | Edge | ~4% | ### 2. Testing Priority ``` Minimum Coverage: 1. NVDA + Firefox (Windows) 2. VoiceOver + Safari (macOS) 3. VoiceOver + Safari (iOS) Comprehensive Coverage: + JAWS + Chrome (Windows) + TalkBack + Chrome (Android) + Narrator + Edge (Windows) ``` ### 3. Screen Reader Modes | Mode | Purpose | When Used | | ------------------ | ---------------------- | ----------------- | | **Browse/Virtual** | Read content | Default reading | | **Focus/Forms** | Interact with controls | Filling forms | | **Application** | Custom widgets | ARIA applications | ## VoiceOver (macOS) ### Setup ``` Enable: System Preferences → Accessibility → VoiceOver Toggle: Cmd + F5 Quick Toggle: Triple-press Touch ID ``` ### Essential Commands ``` Navigation: VO = Ctrl + Option (VoiceOver modifier) VO + Right Arrow Next element VO + Left Arrow Previous element VO + Shift + Down Enter group VO + Shift + Up Exit group Reading: VO + A Read all from cursor Ctrl Stop speaking VO + B Read current paragraph Interaction: VO + Space Activate element VO + Shift + M Open menu Tab Next focusable element Shift + Tab Previous focusable element Rotor (VO + U): Navigate by: Headings, Links, Forms, Landmarks Left/Right Arrow Change rotor category Up/Down Arrow Navigate within category Enter Go to item Web Specific: VO + Cmd + H Next heading VO + Cmd + J Next form control VO + Cmd + L Next link VO + Cmd + T Next table ``` ### Testing Checklist ```markdown ## VoiceOver Testing Checklist ### Page Load - [ ] Page title announced - [ ] Main landmark found - [ ] Skip link works ### Navigation - [ ] All headings discoverable via rotor - [ ] Heading levels logical (H1 → H2 → H3) - [ ] Landmarks properly labeled - [ ] Skip links functional ### Links & Buttons - [ ] Link purpose clear - [ ] Button actions described - [ ] New window/tab announced ### Forms - [ ] All labels read with inputs - [ ] Required fields announced - [ ] Error messages read - [ ] Instructions available - [ ] Focus moves to errors ### Dynamic Content - [ ] Alerts announced immediately - [ ] Loading states communicated - [ ] Content updates announced - [ ] Modals trap focus correctly ### Tables - [ ] Headers associated with cells - [ ] Table navigation works - [ ] Complex tables have captions ``` ### Common Issues & Fixes ```html <!-- Issue: Button not announcing purpose --> <button><svg>...</svg></button> <!-- Fix --> <button aria-label="Close dialog"><svg aria-hidden="true">...</svg></button> <!-- Issue: Dynamic content not announced --> <div id="results">New results loaded</div> <!-- Fix --> <div id="results" role="status" aria-live="polite">New results loaded</div> <!-- Issue: Form error not read --> <input type="email" /> <span class="error">Invalid email</span> <!-- Fix --> <input type="email" aria-invalid="true" aria-describedby="email-error" /> <span id="email-error" role="alert">Invalid email</span> ``` ## NVDA (Windows) ### Setup ``` Download: nvaccess.org Start: Ctrl + Alt + N Stop: Insert + Q ``` ### Essential Commands ``` Navigation: Insert = NVDA modifier Down Arrow Next line Up Arrow Previous line Tab Next focusable Shift + Tab Previous focusable Reading: NVDA + Down Arrow Say all Ctrl Stop speech NVDA + Up Arrow Current line Headings: H Next heading Shift + H Previous heading 1-6 Heading level 1-6 Forms: F Next form field B Next button E Next edit field X Next checkbox C Next combo box Links: K Next link U Next unvisited link V Next visited link Landmarks: D Next landmark Shift + D Previous landmark Tables: T Next table Ctrl + Alt + Arrows Navigate cells Elements List (NVDA + F7): Shows all links, headings, form fields, landmarks ``` ### Browse vs Focus Mode ``` NVDA automatically switches modes: - Browse Mode: Arrow keys navigate content - Focus Mode: Arrow keys control interactive elements Manual switch: NVDA + Space Watch for: - "Browse mode" announcement when navigating - "Focus mode" when entering form fields - Application role forces forms mode ``` ### Testing Script ```markdown ## NVDA Test Script ### Initial Load 1. Navigate to page 2. Let page finish loading 3. Press Insert + Down to read all 4. Note: Page title, main content identified? ### Landmark Navigation 1. Press D repeatedly 2. Check: All main areas reachable? 3. Check: Landmarks properly labeled? ### Heading Navigation 1. Press Insert + F7 → Headings 2. Check: Logical heading structure? 3. Press H to navigate headings 4. Check: All sections discoverable? ### Form Testing 1. Press F to find first form field 2. Check: Label read? 3. Fill in invalid data 4. Submit form 5. Check: Errors announced? 6. Check: Focus moved to error? ### Interactive Elements 1. Tab through all interactive elements 2. Check: Each announces role and state 3. Activate buttons with Enter/Space 4. Check: Result announced? ### Dynamic Content 1. Trigger content update 2. Check: Change announced? 3. Open modal 4. Check: Focus trapped? 5. Close modal 6. Check: Focus returns? ``` ## JAWS (Windows) ### Essential Commands ``` Start: Desktop shortcut or Ctrl + Alt + J Virtual Cursor: Auto-enabled in browsers Navigation: Arrow keys Navigate content Tab Next focusable Insert + Down Read all Ctrl Stop speech Quick Keys: H Next heading T Next table F Next form field B Next button G Next graphic L Next list ; Next landmark Forms Mode: Enter Enter forms mode Numpad + Exit forms mode F5 List form fields Lists: Insert + F7 Link list Insert + F6 Heading list Insert + F5 Form field list Tables: Ctrl + Alt + Arrows Table navigation ``` ## TalkBack (Android) ### Setup ``` Enable: Settings → Accessibility → TalkBack Toggle: Hold both volume buttons 3 seconds ``` ### Gestures ``` Explore: Drag finger across screen Next: Swipe right Previous: Swipe left Activate: Double tap Scroll: Two finger swipe Reading Controls (swipe up then right): - Headings - Links - Controls - Characters - Words - Lines - Paragraphs ``` ## Common Test Scenarios ### 1. Modal Dialog ```html <!-- Accessible modal structure --> <div role="dialog" aria-modal="true" aria-labelledby="dialog-title" aria-describedby="dialog-desc" > <h2 id="dialog-title">Confirm Delete</h2> <p id="dialog-desc">This action cannot be undone.</p> <button>Cancel</button> <button>Delete</button> </div> ``` ```javascript // Focus management function openModal(modal) { // Store last focused element lastFocus = document.activeElement; // Move focus to modal modal.querySelector("h2").focus(); // Trap focus modal.addEventListener("keydown", trapFocus); } function closeModal(modal) { // Return focus lastFocus.focus(); } function trapFocus(e) { if (e.key === "Tab") { const focusable = modal.querySelectorAll( 'button, [href], input, select, textarea, [tabindex]:not([tabindex="-1"])', ); const first = focusable[0]; const last = focusable[focusable.length - 1]; if (e.shiftKey && document.activeElement === first) { last.focus(); e.preventDefault(); } else if (!e.shiftKey && document.activeElement === last) { first.focus(); e.preventDefault(); } } if (e.key === "Escape") { closeModal(modal); } } ``` ### 2. Live Regions ```html <!-- Status messages (polite) --> <div role="status" aria-live="polite" aria-atomic="true"> <!-- Content updates will be announced after current speech --> </div> <!-- Alerts (assertive) --> <div role="alert" aria-live="assertive"> <!-- Content updates interrupt current speech --> </div> <!-- Progress updates --> <div role="progressbar" aria-valuenow="75" aria-valuemin="0" aria-valuemax="100" aria-label="Upload progress" ></div> <!-- Log (additions only) --> <div role="log" aria-live="polite" aria-relevant="additions"> <!-- New messages announced, removals not --> </div> ``` ### 3. Tab Interface ```html <div role="tablist" aria-label="Product information"> <button role="tab" id="tab-1" aria-selected="true" aria-controls="panel-1"> Description </button> <button role="tab" id="tab-2" aria-selected="false" aria-controls="panel-2" tabindex="-1" > Reviews </button> </div> <div role="tabpanel" id="panel-1" aria-labelledby="tab-1"> Product description content... </div> <div role="tabpanel" id="panel-2" aria-labelledby="tab-2" hidden> Reviews content... </div> ``` ```javascript // Tab keyboard navigation tablist.addEventListener("keydown", (e) => { const tabs = [...tablist.querySelectorAll('[role="tab"]')]; const index = tabs.indexOf(document.activeElement); let newIndex; switch (e.key) { case "ArrowRight": newIndex = (index + 1) % tabs.length; break; case "ArrowLeft": newIndex = (index - 1 + tabs.length) % tabs.length; break; case "Home": newIndex = 0; break; case "End": newIndex = tabs.length - 1; break; default: return; } tabs[newIndex].focus(); activateTab(tabs[newIndex]); e.preventDefault(); }); ``` ## Debugging Tips ```javascript // Log what screen reader sees function logAccessibleName(element) { const computed = window.getComputedStyle(element); console.log({ role: element.getAttribute("role") || element.tagName, name: element.getAttribute("aria-label") || element.getAttribute("aria-labelledby") || element.textContent, state: { expanded: element.getAttribute("aria-expanded"), selected: element.getAttribute("aria-selected"), checked: element.getAttribute("aria-checked"), disabled: element.disabled, }, visible: computed.display !== "none" && computed.visibility !== "hidden", }); } ``` ## Best Practices ### Do's - **Test with actual screen readers** - Not just simulators - **Use semantic HTML first** - ARIA is supplemental - **Test in browse and focus modes** - Different experiences - **Verify focus management** - Especially for SPAs - **Test keyboard only first** - Foundation for SR testing ### Don'ts - **Don't assume one SR is enough** - Test multiple - **Don't ignore mobile** - Growing user base - **Don't test only happy path** - Test error states - **Don't skip dynamic content** - Most common issues - **Don't rely on visual testing** - Different experienceplugins/accessibility-compliance/skills/wcag-audit-patterns/SKILL.mdskillShow content (12248 bytes)
--- name: wcag-audit-patterns description: Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns. --- # WCAG Audit Patterns Comprehensive guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies. ## When to Use This Skill - Conducting accessibility audits - Fixing WCAG violations - Implementing accessible components - Preparing for accessibility lawsuits - Meeting ADA/Section 508 requirements - Achieving VPAT compliance ## Core Concepts ### 1. WCAG Conformance Levels | Level | Description | Required For | | ------- | ---------------------- | ----------------- | | **A** | Minimum accessibility | Legal baseline | | **AA** | Standard conformance | Most regulations | | **AAA** | Enhanced accessibility | Specialized needs | ### 2. POUR Principles ``` Perceivable: Can users perceive the content? Operable: Can users operate the interface? Understandable: Can users understand the content? Robust: Does it work with assistive tech? ``` ### 3. Common Violations by Impact ``` Critical (Blockers): ├── Missing alt text for functional images ├── No keyboard access to interactive elements ├── Missing form labels └── Auto-playing media without controls Serious: ├── Insufficient color contrast ├── Missing skip links ├── Inaccessible custom widgets └── Missing page titles Moderate: ├── Missing language attribute ├── Unclear link text ├── Missing landmarks └── Improper heading hierarchy ``` ## Audit Checklist ### Perceivable (Principle 1) ````markdown ## 1.1 Text Alternatives ### 1.1.1 Non-text Content (Level A) - [ ] All images have alt text - [ ] Decorative images have alt="" - [ ] Complex images have long descriptions - [ ] Icons with meaning have accessible names - [ ] CAPTCHAs have alternatives Check: ```html <!-- Good --> <img src="chart.png" alt="Sales increased 25% from Q1 to Q2" /> <img src="decorative-line.png" alt="" /> <!-- Bad --> <img src="chart.png" /> <img src="decorative-line.png" alt="decorative line" /> ``` ```` ## 1.2 Time-based Media ### 1.2.1 Audio-only and Video-only (Level A) - [ ] Audio has text transcript - [ ] Video has audio description or transcript ### 1.2.2 Captions (Level A) - [ ] All video has synchronized captions - [ ] Captions are accurate and complete - [ ] Speaker identification included ### 1.2.3 Audio Description (Level A) - [ ] Video has audio description for visual content ## 1.3 Adaptable ### 1.3.1 Info and Relationships (Level A) - [ ] Headings use proper tags (h1-h6) - [ ] Lists use ul/ol/dl - [ ] Tables have headers - [ ] Form inputs have labels - [ ] ARIA landmarks present Check: ```html <!-- Heading hierarchy --> <h1>Page Title</h1> <h2>Section</h2> <h3>Subsection</h3> <h2>Another Section</h2> <!-- Table headers --> <table> <thead> <tr> <th scope="col">Name</th> <th scope="col">Price</th> </tr> </thead> </table> ``` ### 1.3.2 Meaningful Sequence (Level A) - [ ] Reading order is logical - [ ] CSS positioning doesn't break order - [ ] Focus order matches visual order ### 1.3.3 Sensory Characteristics (Level A) - [ ] Instructions don't rely on shape/color alone - [ ] "Click the red button" → "Click Submit (red button)" ## 1.4 Distinguishable ### 1.4.1 Use of Color (Level A) - [ ] Color is not only means of conveying info - [ ] Links distinguishable without color - [ ] Error states not color-only ### 1.4.3 Contrast (Minimum) (Level AA) - [ ] Text: 4.5:1 contrast ratio - [ ] Large text (18pt+): 3:1 ratio - [ ] UI components: 3:1 ratio Tools: WebAIM Contrast Checker, axe DevTools ### 1.4.4 Resize Text (Level AA) - [ ] Text resizes to 200% without loss - [ ] No horizontal scrolling at 320px - [ ] Content reflows properly ### 1.4.10 Reflow (Level AA) - [ ] Content reflows at 400% zoom - [ ] No two-dimensional scrolling - [ ] All content accessible at 320px width ### 1.4.11 Non-text Contrast (Level AA) - [ ] UI components have 3:1 contrast - [ ] Focus indicators visible - [ ] Graphical objects distinguishable ### 1.4.12 Text Spacing (Level AA) - [ ] No content loss with increased spacing - [ ] Line height 1.5x font size - [ ] Paragraph spacing 2x font size - [ ] Letter spacing 0.12x font size - [ ] Word spacing 0.16x font size ```` ### Operable (Principle 2) ```markdown ## 2.1 Keyboard Accessible ### 2.1.1 Keyboard (Level A) - [ ] All functionality keyboard accessible - [ ] No keyboard traps - [ ] Tab order is logical - [ ] Custom widgets are keyboard operable Check: ```javascript // Custom button must be keyboard accessible <div role="button" tabindex="0" onkeydown="if(event.key === 'Enter' || event.key === ' ') activate()"> ```` ### 2.1.2 No Keyboard Trap (Level A) - [ ] Focus can move away from all components - [ ] Modal dialogs trap focus correctly - [ ] Focus returns after modal closes ## 2.2 Enough Time ### 2.2.1 Timing Adjustable (Level A) - [ ] Session timeouts can be extended - [ ] User warned before timeout - [ ] Option to disable auto-refresh ### 2.2.2 Pause, Stop, Hide (Level A) - [ ] Moving content can be paused - [ ] Auto-updating content can be paused - [ ] Animations respect prefers-reduced-motion ```css @media (prefers-reduced-motion: reduce) { * { animation: none !important; transition: none !important; } } ``` ## 2.3 Seizures and Physical Reactions ### 2.3.1 Three Flashes (Level A) - [ ] No content flashes more than 3 times/second - [ ] Flashing area is small (<25% viewport) ## 2.4 Navigable ### 2.4.1 Bypass Blocks (Level A) - [ ] Skip to main content link present - [ ] Landmark regions defined - [ ] Proper heading structure ```html <a href="#main" class="skip-link">Skip to main content</a> <main id="main">...</main> ``` ### 2.4.2 Page Titled (Level A) - [ ] Unique, descriptive page titles - [ ] Title reflects page content ### 2.4.3 Focus Order (Level A) - [ ] Focus order matches visual order - [ ] tabindex used correctly ### 2.4.4 Link Purpose (In Context) (Level A) - [ ] Links make sense out of context - [ ] No "click here" or "read more" alone ```html <!-- Bad --> <a href="report.pdf">Click here</a> <!-- Good --> <a href="report.pdf">Download Q4 Sales Report (PDF)</a> ``` ### 2.4.6 Headings and Labels (Level AA) - [ ] Headings describe content - [ ] Labels describe purpose ### 2.4.7 Focus Visible (Level AA) - [ ] Focus indicator visible on all elements - [ ] Custom focus styles meet contrast ```css :focus { outline: 3px solid #005fcc; outline-offset: 2px; } ``` ### 2.4.11 Focus Not Obscured (Level AA) - WCAG 2.2 - [ ] Focused element not fully hidden - [ ] Sticky headers don't obscure focus ```` ### Understandable (Principle 3) ```markdown ## 3.1 Readable ### 3.1.1 Language of Page (Level A) - [ ] HTML lang attribute set - [ ] Language correct for content ```html <html lang="en"> ```` ### 3.1.2 Language of Parts (Level AA) - [ ] Language changes marked ```html <p>The French word <span lang="fr">bonjour</span> means hello.</p> ``` ## 3.2 Predictable ### 3.2.1 On Focus (Level A) - [ ] No context change on focus alone - [ ] No unexpected popups on focus ### 3.2.2 On Input (Level A) - [ ] No automatic form submission - [ ] User warned before context change ### 3.2.3 Consistent Navigation (Level AA) - [ ] Navigation consistent across pages - [ ] Repeated components same order ### 3.2.4 Consistent Identification (Level AA) - [ ] Same functionality = same label - [ ] Icons used consistently ## 3.3 Input Assistance ### 3.3.1 Error Identification (Level A) - [ ] Errors clearly identified - [ ] Error message describes problem - [ ] Error linked to field ```html <input aria-describedby="email-error" aria-invalid="true" /> <span id="email-error" role="alert">Please enter valid email</span> ``` ### 3.3.2 Labels or Instructions (Level A) - [ ] All inputs have visible labels - [ ] Required fields indicated - [ ] Format hints provided ### 3.3.3 Error Suggestion (Level AA) - [ ] Errors include correction suggestion - [ ] Suggestions are specific ### 3.3.4 Error Prevention (Level AA) - [ ] Legal/financial forms reversible - [ ] Data checked before submission - [ ] User can review before submit ```` ### Robust (Principle 4) ```markdown ## 4.1 Compatible ### 4.1.1 Parsing (Level A) - Obsolete in WCAG 2.2 - [ ] Valid HTML (good practice) - [ ] No duplicate IDs - [ ] Complete start/end tags ### 4.1.2 Name, Role, Value (Level A) - [ ] Custom widgets have accessible names - [ ] ARIA roles correct - [ ] State changes announced ```html <!-- Accessible custom checkbox --> <div role="checkbox" aria-checked="false" tabindex="0" aria-labelledby="label"> </div> <span id="label">Accept terms</span> ```` ### 4.1.3 Status Messages (Level AA) - [ ] Status updates announced - [ ] Live regions used correctly ```html <div role="status" aria-live="polite">3 items added to cart</div> <div role="alert" aria-live="assertive">Error: Form submission failed</div> ``` ```` ## Automated Testing ```javascript // axe-core integration const axe = require('axe-core'); async function runAccessibilityAudit(page) { await page.addScriptTag({ path: require.resolve('axe-core') }); const results = await page.evaluate(async () => { return await axe.run(document, { runOnly: { type: 'tag', values: ['wcag2a', 'wcag2aa', 'wcag21aa', 'wcag22aa'] } }); }); return { violations: results.violations, passes: results.passes, incomplete: results.incomplete }; } // Playwright test example test('should have no accessibility violations', async ({ page }) => { await page.goto('/'); const results = await runAccessibilityAudit(page); expect(results.violations).toHaveLength(0); }); ```` ```bash # CLI tools npx @axe-core/cli https://example.com npx pa11y https://example.com lighthouse https://example.com --only-categories=accessibility ``` ## Remediation Patterns ### Fix: Missing Form Labels ```html <!-- Before --> <input type="email" placeholder="Email" /> <!-- After: Option 1 - Visible label --> <label for="email">Email address</label> <input id="email" type="email" /> <!-- After: Option 2 - aria-label --> <input type="email" aria-label="Email address" /> <!-- After: Option 3 - aria-labelledby --> <span id="email-label">Email</span> <input type="email" aria-labelledby="email-label" /> ``` ### Fix: Insufficient Color Contrast ```css /* Before: 2.5:1 contrast */ .text { color: #767676; } /* After: 4.5:1 contrast */ .text { color: #595959; } /* Or add background */ .text { color: #767676; background: #000; } ``` ### Fix: Keyboard Navigation ```javascript // Make custom element keyboard accessible class AccessibleDropdown extends HTMLElement { connectedCallback() { this.setAttribute("tabindex", "0"); this.setAttribute("role", "combobox"); this.setAttribute("aria-expanded", "false"); this.addEventListener("keydown", (e) => { switch (e.key) { case "Enter": case " ": this.toggle(); e.preventDefault(); break; case "Escape": this.close(); break; case "ArrowDown": this.focusNext(); e.preventDefault(); break; case "ArrowUp": this.focusPrevious(); e.preventDefault(); break; } }); } } ``` ## Best Practices ### Do's - **Start early** - Accessibility from design phase - **Test with real users** - Disabled users provide best feedback - **Automate what you can** - 30-50% issues detectable - **Use semantic HTML** - Reduces ARIA needs - **Document patterns** - Build accessible component library ### Don'ts - **Don't rely only on automated testing** - Manual testing required - **Don't use ARIA as first solution** - Native HTML first - **Don't hide focus outlines** - Keyboard users need them - **Don't disable zoom** - Users need to resize - **Don't use color alone** - Multiple indicators neededplugins/agent-teams/skills/multi-reviewer-patterns/SKILL.mdskillShow content (5192 bytes)
--- name: multi-reviewer-patterns description: Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results. version: 1.0.2 --- # Multi-Reviewer Patterns Patterns for coordinating parallel code reviews across multiple quality dimensions, deduplicating findings, calibrating severity, and producing consolidated reports. ## When to Use This Skill - Organizing a multi-dimensional code review - Deciding which review dimensions to assign - Deduplicating findings from multiple reviewers - Calibrating severity ratings consistently - Producing a consolidated review report ## Review Dimension Allocation ### Available Dimensions | Dimension | Focus | When to Include | | ----------------- | --------------------------------------- | ------------------------------------------- | | **Security** | Vulnerabilities, auth, input validation | Always for code handling user input or auth | | **Performance** | Query efficiency, memory, caching | When changing data access or hot paths | | **Architecture** | SOLID, coupling, patterns | For structural changes or new modules | | **Testing** | Coverage, quality, edge cases | When adding new functionality | | **Accessibility** | WCAG, ARIA, keyboard nav | For UI/frontend changes | ### Recommended Combinations | Scenario | Dimensions | | ---------------------- | -------------------------------------------- | | API endpoint changes | Security, Performance, Architecture | | Frontend component | Architecture, Testing, Accessibility | | Database migration | Performance, Architecture | | Authentication changes | Security, Testing | | Full feature review | Security, Performance, Architecture, Testing | ## Finding Deduplication When multiple reviewers report issues at the same location: ### Merge Rules 1. **Same file:line, same issue** — Merge into one finding, credit all reviewers 2. **Same file:line, different issues** — Keep as separate findings 3. **Same issue, different locations** — Keep separate but cross-reference 4. **Conflicting severity** — Use the higher severity rating 5. **Conflicting recommendations** — Include both with reviewer attribution ### Deduplication Process ``` For each finding in all reviewer reports: 1. Check if another finding references the same file:line 2. If yes, check if they describe the same issue 3. If same issue: merge, keeping the more detailed description 4. If different issue: keep both, tag as "co-located" 5. Use highest severity among merged findings ``` ## Severity Calibration ### Severity Criteria | Severity | Impact | Likelihood | Examples | | ------------ | --------------------------------------------- | ---------------------- | -------------------------------------------- | | **Critical** | Data loss, security breach, complete failure | Certain or very likely | SQL injection, auth bypass, data corruption | | **High** | Significant functionality impact, degradation | Likely | Memory leak, missing validation, broken flow | | **Medium** | Partial impact, workaround exists | Possible | N+1 query, missing edge case, unclear error | | **Low** | Minimal impact, cosmetic | Unlikely | Style issue, minor optimization, naming | ### Calibration Rules - Security vulnerabilities exploitable by external users: always Critical or High - Performance issues in hot paths: at least Medium - Missing tests for critical paths: at least Medium - Accessibility violations for core functionality: at least Medium - Code style issues with no functional impact: Low ## Consolidated Report Template ```markdown ## Code Review Report **Target**: {files/PR/directory} **Reviewers**: {dimension-1}, {dimension-2}, {dimension-3} **Date**: {date} **Files Reviewed**: {count} ### Critical Findings ({count}) #### [CR-001] {Title} **Location**: `{file}:{line}` **Dimension**: {Security/Performance/etc.} **Description**: {what was found} **Impact**: {what could happen} **Fix**: {recommended remediation} ### High Findings ({count}) ... ### Medium Findings ({count}) ... ### Low Findings ({count}) ... ### Summary | Dimension | Critical | High | Medium | Low | Total | | ------------ | -------- | ----- | ------ | ----- | ------ | | Security | 1 | 2 | 3 | 0 | 6 | | Performance | 0 | 1 | 4 | 2 | 7 | | Architecture | 0 | 0 | 2 | 3 | 5 | | **Total** | **1** | **3** | **9** | **5** | **18** | ### Recommendation {Overall assessment and prioritized action items} ```plugins/agent-teams/skills/parallel-debugging/SKILL.mdskillShow content (4748 bytes)
--- name: parallel-debugging description: Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration. Use this skill when debugging bugs with multiple potential causes, performing root cause analysis, or organizing parallel investigation workflows. version: 1.0.2 --- # Parallel Debugging Framework for debugging complex issues using the Analysis of Competing Hypotheses (ACH) methodology with parallel agent investigation. ## When to Use This Skill - Bug has multiple plausible root causes - Initial debugging attempts haven't identified the issue - Issue spans multiple modules or components - Need systematic root cause analysis with evidence - Want to avoid confirmation bias in debugging ## Hypothesis Generation Framework Generate hypotheses across 6 failure mode categories: ### 1. Logic Error - Incorrect conditional logic (wrong operator, missing case) - Off-by-one errors in loops or array access - Missing edge case handling - Incorrect algorithm implementation ### 2. Data Issue - Invalid or unexpected input data - Type mismatch or coercion error - Null/undefined/None where value expected - Encoding or serialization problem - Data truncation or overflow ### 3. State Problem - Race condition between concurrent operations - Stale cache returning outdated data - Incorrect initialization or default values - Unintended mutation of shared state - State machine transition error ### 4. Integration Failure - API contract violation (request/response mismatch) - Version incompatibility between components - Configuration mismatch between environments - Missing or incorrect environment variables - Network timeout or connection failure ### 5. Resource Issue - Memory leak causing gradual degradation - Connection pool exhaustion - File descriptor or handle leak - Disk space or quota exceeded - CPU saturation from inefficient processing ### 6. Environment - Missing runtime dependency - Wrong library or framework version - Platform-specific behavior difference - Permission or access control issue - Timezone or locale-related behavior ## Evidence Collection Standards ### What Constitutes Evidence | Evidence Type | Strength | Example | | ----------------- | -------- | --------------------------------------------------------------- | | **Direct** | Strong | Code at `file.ts:42` shows `if (x > 0)` should be `if (x >= 0)` | | **Correlational** | Medium | Error rate increased after commit `abc123` | | **Testimonial** | Weak | "It works on my machine" | | **Absence** | Variable | No null check found in the code path | ### Citation Format Always cite evidence with file:line references: ``` **Evidence**: The validation function at `src/validators/user.ts:87` does not check for empty strings, only null/undefined. This allows empty email addresses to pass validation. ``` ### Confidence Levels | Level | Criteria | | ------------------- | ----------------------------------------------------------------------------------- | | **High (>80%)** | Multiple direct evidence pieces, clear causal chain, no contradicting evidence | | **Medium (50-80%)** | Some direct evidence, plausible causal chain, minor ambiguities | | **Low (<50%)** | Mostly correlational evidence, incomplete causal chain, some contradicting evidence | ## Result Arbitration Protocol After all investigators report: ### Step 1: Categorize Results - **Confirmed**: High confidence, strong evidence, clear causal chain - **Plausible**: Medium confidence, some evidence, reasonable causal chain - **Falsified**: Evidence contradicts the hypothesis - **Inconclusive**: Insufficient evidence to confirm or falsify ### Step 2: Compare Confirmed Hypotheses If multiple hypotheses are confirmed, rank by: 1. Confidence level 2. Number of supporting evidence pieces 3. Strength of causal chain 4. Absence of contradicting evidence ### Step 3: Determine Root Cause - If one hypothesis clearly dominates: declare as root cause - If multiple hypotheses are equally likely: may be compound issue (multiple contributing causes) - If no hypotheses confirmed: generate new hypotheses based on evidence gathered ### Step 4: Validate Fix Before declaring the bug fixed: - [ ] Fix addresses the identified root cause - [ ] Fix doesn't introduce new issues - [ ] Original reproduction case no longer fails - [ ] Related edge cases are covered - [ ] Relevant tests are added or updated.claude-plugin/marketplace.jsonmarketplaceShow content (38960 bytes)
{ "name": "claude-code-workflows", "owner": { "name": "Seth Hobson", "email": "seth@major7apps.com", "url": "https://github.com/wshobson" }, "metadata": { "description": "Production-ready workflow orchestration with 79 focused plugins, 184 specialized agents, and 150 skills - optimized for granular installation and minimal token usage", "version": "1.6.0" }, "plugins": [ { "name": "documentation-standards", "source": "./plugins/documentation-standards", "description": "HADS (Human-AI Document Standard) — semantic tagging convention for writing docs that work efficiently for both humans and AI models. Reduces token consumption by separating machine-critical facts from human context.", "version": "1.0.0", "author": { "name": "Niksa Barlovic", "url": "https://github.com/catcam" }, "homepage": "https://github.com/catcam/hads", "license": "MIT", "category": "documentation" }, { "name": "code-documentation", "source": "./plugins/code-documentation", "description": "Documentation generation, code explanation, and technical writing with automated doc generation and tutorial creation", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "documentation" }, { "name": "debugging-toolkit", "source": "./plugins/debugging-toolkit", "description": "Interactive debugging, developer experience optimization, and smart debugging workflows", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "development" }, { "name": "git-pr-workflows", "source": "./plugins/git-pr-workflows", "description": "Git workflow automation, pull request enhancement, and team onboarding processes", "version": "1.3.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "workflows" }, { "name": "backend-development", "source": "./plugins/backend-development", "description": "Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development", "version": "1.3.1", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "development" }, { "name": "frontend-mobile-development", "source": "./plugins/frontend-mobile-development", "description": "Frontend UI development and mobile application implementation across platforms", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "development" }, { "name": "full-stack-orchestration", "source": "./plugins/full-stack-orchestration", "description": "End-to-end feature orchestration with testing, security, performance, and deployment", "version": "1.3.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "workflows" }, { "name": "unit-testing", "source": "./plugins/unit-testing", "description": "Unit and integration test automation for Python and JavaScript with debugging support", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "testing" }, { "name": "tdd-workflows", "source": "./plugins/tdd-workflows", "description": "Test-driven development methodology with red-green-refactor cycles and code review", "version": "1.3.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "workflows" }, { "name": "code-refactoring", "source": "./plugins/code-refactoring", "description": "Code cleanup, refactoring automation, and technical debt management with context restoration", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "utilities" }, { "name": "dependency-management", "source": "./plugins/dependency-management", "description": "Dependency auditing, version management, and security vulnerability scanning", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "utilities" }, { "name": "error-debugging", "source": "./plugins/error-debugging", "description": "Error analysis, trace debugging, and multi-agent problem diagnosis", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "utilities" }, { "name": "team-collaboration", "source": "./plugins/team-collaboration", "description": "Team workflows, issue management, standup automation, and developer experience optimization", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "utilities" }, { "name": "llm-application-dev", "description": "LLM application development with LangGraph, RAG systems, vector search, and AI agent architectures for Claude 4.6 and GPT-5.4", "version": "2.0.5", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/llm-application-dev", "category": "ai-ml", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "agent-orchestration", "source": "./plugins/agent-orchestration", "description": "Multi-agent system optimization, agent improvement workflows, and context management", "version": "1.2.1", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "ai-ml" }, { "name": "context-management", "source": "./plugins/context-management", "description": "Context persistence, restoration, and long-running conversation management", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "ai-ml" }, { "name": "machine-learning-ops", "description": "ML model training pipelines, hyperparameter tuning, model deployment automation, experiment tracking, and MLOps workflows", "version": "1.2.1", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/machine-learning-ops", "category": "ai-ml", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "data-engineering", "description": "ETL pipeline construction, data warehouse design, batch processing workflows, and data-driven feature development", "version": "1.3.1", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/data-engineering", "category": "data", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "incident-response", "description": "Production incident management, triage workflows, and automated incident resolution", "version": "1.3.1", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/incident-response", "category": "operations", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "error-diagnostics", "description": "Error tracing, root cause analysis, and smart debugging for production systems", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/error-diagnostics", "category": "operations", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "distributed-debugging", "description": "Distributed system tracing and debugging across microservices", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/distributed-debugging", "category": "operations", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "observability-monitoring", "description": "Metrics collection, logging infrastructure, distributed tracing, SLO implementation, and monitoring dashboards", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/observability-monitoring", "category": "operations", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "deployment-strategies", "description": "Deployment patterns, rollback automation, and infrastructure templates", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/deployment-strategies", "category": "infrastructure", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "deployment-validation", "description": "Pre-deployment checks, configuration validation, and deployment readiness assessment", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/deployment-validation", "category": "infrastructure", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "kubernetes-operations", "description": "Kubernetes manifest generation, networking configuration, security policies, observability setup, GitOps workflows, and auto-scaling", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/kubernetes-operations", "category": "infrastructure", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "cloud-infrastructure", "description": "Cloud architecture design for AWS/Azure/GCP/OCI, Kubernetes cluster configuration, Terraform infrastructure-as-code, hybrid cloud networking, and multi-cloud cost optimization", "version": "1.3.1", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/cloud-infrastructure", "category": "infrastructure", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "cicd-automation", "description": "CI/CD pipeline configuration, GitHub Actions/GitLab CI workflow setup, and automated deployment pipeline orchestration", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/cicd-automation", "category": "infrastructure", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "application-performance", "source": "./plugins/application-performance", "description": "Application profiling, performance optimization, and observability for frontend and backend systems", "version": "1.3.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "performance" }, { "name": "database-cloud-optimization", "source": "./plugins/database-cloud-optimization", "description": "Database query optimization, cloud cost optimization, and scalability improvements", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "performance" }, { "name": "comprehensive-review", "source": "./plugins/comprehensive-review", "description": "Multi-perspective code analysis covering architecture, security, and best practices", "version": "1.3.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "quality" }, { "name": "performance-testing-review", "source": "./plugins/performance-testing-review", "description": "Performance analysis, test coverage review, and AI-powered code quality assessment", "version": "1.2.1", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "quality" }, { "name": "framework-migration", "source": "./plugins/framework-migration", "description": "Framework updates, migration planning, and architectural transformation workflows", "version": "1.3.1", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "modernization" }, { "name": "codebase-cleanup", "source": "./plugins/codebase-cleanup", "description": "Technical debt reduction, dependency updates, and code refactoring automation", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "modernization" }, { "name": "database-design", "source": "./plugins/database-design", "description": "Database architecture, schema design, and SQL optimization for production systems", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "database" }, { "name": "database-migrations", "source": "./plugins/database-migrations", "description": "Database migration automation, observability, and cross-database migration strategies", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "database" }, { "name": "security-scanning", "description": "SAST analysis, dependency vulnerability scanning, OWASP Top 10 compliance, container security scanning, and automated security hardening", "version": "1.3.1", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/security-scanning", "category": "security", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "security-compliance", "description": "SOC2, HIPAA, and GDPR compliance validation, secrets scanning, compliance checklists, and regulatory documentation", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/security-compliance", "category": "security", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "backend-api-security", "description": "API security hardening, authentication implementation, authorization patterns, rate limiting, and input validation", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/backend-api-security", "category": "security", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "frontend-mobile-security", "description": "XSS prevention, CSRF protection, content security policies, mobile app security, and secure storage patterns", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/frontend-mobile-security", "category": "security", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "data-validation-suite", "description": "Schema validation, data quality monitoring, streaming validation pipelines, and input validation for backend APIs", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/data-validation-suite", "category": "data", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "api-scaffolding", "source": "./plugins/api-scaffolding", "description": "REST and GraphQL API scaffolding, framework selection, backend architecture, and API generation", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "api" }, { "name": "api-testing-observability", "source": "./plugins/api-testing-observability", "description": "API testing automation, request mocking, OpenAPI documentation generation, observability setup, and monitoring", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "api" }, { "name": "seo-content-creation", "source": "./plugins/seo-content-creation", "description": "SEO content writing, planning, and quality auditing with E-E-A-T optimization", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "marketing" }, { "name": "seo-technical-optimization", "source": "./plugins/seo-technical-optimization", "description": "Technical SEO optimization including meta tags, keywords, structure, and featured snippets", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "marketing" }, { "name": "seo-analysis-monitoring", "source": "./plugins/seo-analysis-monitoring", "description": "Content freshness analysis, cannibalization detection, and authority building for SEO", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "marketing" }, { "name": "documentation-generation", "source": "./plugins/documentation-generation", "description": "OpenAPI specification generation, Mermaid diagram creation, tutorial writing, API reference documentation", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "documentation" }, { "name": "c4-architecture", "source": "./plugins/c4-architecture", "description": "Comprehensive C4 architecture documentation workflow with bottom-up code analysis, component synthesis, container mapping, and context diagram generation", "version": "1.0.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "documentation" }, { "name": "multi-platform-apps", "source": "./plugins/multi-platform-apps", "description": "Cross-platform application development coordinating web, iOS, Android, and desktop implementations", "version": "1.3.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "development" }, { "name": "business-analytics", "source": "./plugins/business-analytics", "description": "Business metrics analysis, KPI tracking, financial reporting, and data-driven decision making", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "business" }, { "name": "startup-business-analyst", "description": "Comprehensive startup business analysis with market sizing (TAM/SAM/SOM), financial modeling, team planning, and strategic research for early-stage companies", "version": "1.0.5", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/startup-business-analyst", "category": "business", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "hr-legal-compliance", "source": "./plugins/hr-legal-compliance", "description": "HR policy documentation, legal compliance templates (GDPR/SOC2/HIPAA), employment contracts, and regulatory documentation", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "business" }, { "name": "customer-sales-automation", "source": "./plugins/customer-sales-automation", "description": "Customer support workflow automation, sales pipeline management, email campaigns, and CRM integration", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "business" }, { "name": "content-marketing", "source": "./plugins/content-marketing", "description": "Content marketing strategy, web research, and information synthesis for marketing operations", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "marketing" }, { "name": "blockchain-web3", "source": "./plugins/blockchain-web3", "description": "Smart contract development with Solidity, DeFi protocol implementation, NFT platforms, and Web3 application architecture", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "blockchain" }, { "name": "quantitative-trading", "source": "./plugins/quantitative-trading", "description": "Quantitative analysis, algorithmic trading strategies, financial modeling, portfolio risk management, and backtesting", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "finance" }, { "name": "payment-processing", "source": "./plugins/payment-processing", "description": "Payment gateway integration with Stripe, PayPal, checkout flow implementation, subscription billing, and PCI compliance", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "payments" }, { "name": "game-development", "source": "./plugins/game-development", "description": "Unity game development with C# scripting, Minecraft server plugin development with Bukkit/Spigot APIs", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "gaming" }, { "name": "accessibility-compliance", "source": "./plugins/accessibility-compliance", "description": "WCAG accessibility auditing, compliance validation, UI testing for screen readers, keyboard navigation, and inclusive design", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "accessibility" }, { "name": "python-development", "source": "./plugins/python-development", "description": "Modern Python development with Python 3.12+, Django, FastAPI, async patterns, and production best practices", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "languages" }, { "name": "javascript-typescript", "source": "./plugins/javascript-typescript", "description": "JavaScript and TypeScript development with ES6+, Node.js, React, and modern web frameworks", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "languages" }, { "name": "systems-programming", "source": "./plugins/systems-programming", "description": "Systems programming with Rust, Go, C, and C++ for performance-critical and low-level development", "version": "1.2.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "languages" }, { "name": "jvm-languages", "source": "./plugins/jvm-languages", "description": "JVM language development including Java, Scala, and C# with enterprise patterns and frameworks", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "languages" }, { "name": "web-scripting", "source": "./plugins/web-scripting", "description": "Web scripting with PHP and Ruby for web applications, CMS development, and backend services", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "languages" }, { "name": "functional-programming", "source": "./plugins/functional-programming", "description": "Functional programming with Elixir, OTP patterns, Phoenix framework, and distributed systems", "version": "1.2.0", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "languages" }, { "name": "julia-development", "source": "./plugins/julia-development", "description": "Modern Julia development with Julia 1.10+, package management, scientific computing, high-performance numerical code, and production best practices", "version": "1.0.0", "author": { "name": "Community Contribution", "url": "https://github.com/exAClior" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "languages" }, { "name": "arm-cortex-microcontrollers", "source": "./plugins/arm-cortex-microcontrollers", "description": "ARM Cortex-M firmware development for Teensy, STM32, nRF52, and SAMD with peripheral drivers and memory safety patterns", "version": "1.2.0", "author": { "name": "Ryan Snodgrass", "url": "https://github.com/rsnodgrass" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "languages" }, { "name": "shell-scripting", "source": "./plugins/shell-scripting", "description": "Production-grade Bash scripting with defensive programming, POSIX compliance, and comprehensive testing", "version": "1.2.2", "author": { "name": "Ryan Snodgrass", "url": "https://github.com/rsnodgrass" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "languages" }, { "name": "developer-essentials", "source": "./plugins/developer-essentials", "description": "Essential developer skills including Git workflows, SQL optimization, error handling, code review, E2E testing, authentication, debugging, and monorepo management", "version": "1.0.3", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "development" }, { "name": "reverse-engineering", "source": "./plugins/reverse-engineering", "description": "Binary reverse engineering, malware analysis, firmware security, and software protection research for authorized security research, CTF competitions, and defensive security", "version": "1.0.0", "author": { "name": "Dávid Balatoni", "url": "https://github.com/balcsida" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "security" }, { "name": "conductor", "description": "Context-Driven Development plugin that transforms Claude Code into a project management tool with structured workflow: Context → Spec & Plan → Implement", "version": "1.2.1", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/conductor", "category": "workflows", "homepage": "https://github.com/wshobson/agents", "license": "Apache-2.0" }, { "name": "ui-design", "description": "Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns", "version": "1.0.4", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/ui-design", "category": "development", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "agent-teams", "description": "Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams", "version": "1.0.2", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "source": "./plugins/agent-teams", "category": "workflows", "homepage": "https://github.com/wshobson/agents", "license": "MIT" }, { "name": "dotnet-contribution", "source": "./plugins/dotnet-contribution", "description": "Comprehensive .NET backend development with C#, ASP.NET Core, Entity Framework Core, and Dapper for production-grade applications", "version": "1.0.1", "author": { "name": "Seth Hobson", "email": "seth@major7apps.com" }, "homepage": "https://github.com/wshobson/agents", "license": "MIT", "category": "languages" }, { "name": "meigen-ai-design", "source": "./plugins/meigen-ai-design", "description": "AI image generation with creative workflow orchestration, prompt engineering, and curated inspiration library via MCP server", "version": "1.0.5", "author": { "name": "MeiGen", "url": "https://github.com/jau123" }, "homepage": "https://github.com/jau123/MeiGen-AI-Design-MCP", "license": "MIT", "category": "creative" }, { "name": "brand-landingpage", "source": "./plugins/brand-landingpage", "description": "Guides developers from brand discovery through iterative design to deployment-ready HTML via Stitch.", "version": "1.0.0", "author": { "name": "Travis D. Elliott", "url": "https://github.com/travis-d-elliott" }, "license": "MIT", "category": "creative" }, { "name": "plugin-eval", "source": "./plugins/plugin-eval", "description": "Three-layer quality evaluation framework for Claude Code plugins with Elo ranking", "version": "0.1.0", "author": { "name": "Seth Hobson" }, "license": "MIT", "category": "quality" }, { "name": "block-no-verify", "source": "./plugins/block-no-verify", "description": "PreToolUse hook that prevents AI agents from using --no-verify, --no-gpg-sign, and other bypass flags that skip git hooks", "version": "1.0.0", "author": { "name": "cskwork" }, "homepage": "https://github.com/cskwork", "license": "MIT", "category": "security" }, { "name": "qa-orchestra", "source": { "source": "git-subdir", "url": "https://github.com/Anasss/qa-orchestra.git", "path": "." }, "description": "Multi-agent QA toolkit with 10 specialized agents covering the full QA lifecycle — orchestrator, environment-manager, functional-reviewer, test-scenario-designer, browser-validator, automation-writer, manual-validator, bug-reporter, release-analyzer, and smart-test-selector. Stack-agnostic, output-chained, designed around live validation via Chrome MCP.", "version": "1.0.0", "author": { "name": "Anass Rach", "url": "https://github.com/Anasss" }, "homepage": "https://github.com/Anasss/qa-orchestra", "license": "MIT", "category": "testing" }, { "name": "protect-mcp", "source": "./plugins/protect-mcp", "description": "Cedar policy enforcement + Ed25519 signed receipts for every Claude Code tool call. First cryptographic governance plugin — decisions are policy-gated before they run and every decision produces a tamper-evident receipt verifiable offline.", "version": "0.1.0", "author": { "name": "Tom Farley", "email": "tommy@scopeblind.com", "url": "https://github.com/tomjwxf" }, "homepage": "https://veritasacta.com", "license": "MIT", "category": "governance", "keywords": ["cedar", "receipts", "ed25519", "policy", "governance", "audit", "compliance"] }, { "name": "signed-audit-trails", "source": "./plugins/signed-audit-trails", "description": "Teaching skill: cookbook-style walkthrough for signed audit trails on every Claude Code tool call. Cedar policy, Ed25519 receipts, offline verification, CI/CD integration, SLSA composition. Pairs with the protect-mcp runtime plugin.", "version": "0.1.0", "author": { "name": "Tom Farley", "email": "tommy@scopeblind.com", "url": "https://github.com/tomjwxf" }, "homepage": "https://veritasacta.com", "license": "MIT", "category": "governance", "keywords": ["tutorial", "skill", "recipe", "audit", "governance", "cedar", "receipts", "ed25519"] }, { "name": "review-agent-governance", "source": "./plugins/review-agent-governance", "description": "Require a human approval signal before an AI agent can post PR reviews, comments, merges, or writes to CI configuration. Joins protect-mcp and signed-audit-trails in the governance category; composes with protect-mcp for runtime enforcement.", "version": "0.1.0", "author": { "name": "Tom Farley", "email": "tommy@scopeblind.com", "url": "https://github.com/tomjwxf" }, "homepage": "https://veritasacta.com", "license": "MIT", "category": "governance", "keywords": ["review", "governance", "cedar", "receipts", "human-approval", "pr-review", "ci-guard"] } ] }
README
Claude Code Plugins: Orchestration and Automation
⚡ Updated for Opus 4.7, Sonnet 4.6 & Haiku 4.5 — Three-tier model strategy for optimal performance
🎯 Agent Skills Enabled — 153 specialized skills extend Claude's capabilities across plugins with progressive disclosure
A comprehensive production-ready system combining 185 specialized AI agents, 16 multi-agent workflow orchestrators, 153 agent skills, and 100 commands organized into 80 focused, single-purpose plugins for Claude Code.
Overview
This unified repository provides everything needed for intelligent automation and multi-agent orchestration across modern software development:
- 80 Focused Plugins - Granular, single-purpose plugins optimized for minimal token usage and composability
- 185 Specialized Agents - Domain experts with deep knowledge across architecture, languages, infrastructure, quality, data/AI, documentation, business operations, and SEO
- 153 Agent Skills - Modular knowledge packages with progressive disclosure for specialized expertise
- 16 Workflow Orchestrators - Multi-agent coordination systems for complex operations like full-stack development, security hardening, ML pipelines, and incident response
- 100 Commands - Optimized utilities including project scaffolding, security scanning, test automation, and infrastructure setup
Key Features
- Granular Plugin Architecture: 80 focused plugins optimized for minimal token usage
- Comprehensive Tooling: 100 commands including test generation, scaffolding, and security scanning
- 100% Agent Coverage: All plugins include specialized agents
- Agent Skills: 153 specialized skills following for progressive disclosure and token efficiency
- Clear Organization: 25 categories with 1-10 plugins each for easy discovery
- Efficient Design: Average 3.6 components per plugin (follows Anthropic's 2-8 pattern)
How It Works
Each plugin is completely isolated with its own agents, commands, and skills:
- Install only what you need - Each plugin loads only its specific agents, commands, and skills
- Minimal token usage - No unnecessary resources loaded into context
- Mix and match - Compose multiple plugins for complex workflows
- Clear boundaries - Each plugin has a single, focused purpose
- Progressive disclosure - Skills load knowledge only when activated
Example: Installing python-development loads 3 Python agents, 1 scaffolding tool, and makes 16 skills available (~1000 tokens), not the entire marketplace.
Quick Start
Step 1: Add the Marketplace
Add this marketplace to Claude Code:
/plugin marketplace add wshobson/agents
This makes all 80 plugins available for installation, but does not load any agents or tools into your context.
Step 2: Install Plugins
Browse available plugins:
/plugin
Install the plugins you need:
# Essential development plugins
/plugin install python-development # Python with 16 specialized skills
/plugin install javascript-typescript # JS/TS with 4 specialized skills
/plugin install backend-development # Backend APIs with 3 architecture skills
# Infrastructure & operations
/plugin install kubernetes-operations # K8s with 4 deployment skills
/plugin install cloud-infrastructure # AWS/Azure/GCP with 4 cloud skills
# Security & quality
/plugin install security-scanning # SAST with security skill
/plugin install comprehensive-review # Multi-perspective code analysis
# Full-stack orchestration
/plugin install full-stack-orchestration # Multi-agent workflows
Each installed plugin loads only its specific agents, commands, and skills into Claude's context.
Plugins vs Agents
You install plugins, which bundle agents:
| Plugin | Agents |
|---|---|
comprehensive-review | architect-review, code-reviewer, security-auditor |
javascript-typescript | javascript-pro, typescript-pro |
python-development | python-pro, django-pro, fastapi-pro |
blockchain-web3 | blockchain-developer |
# ❌ Wrong - can't install agents directly
/plugin install typescript-pro
# ✅ Right - install the plugin
/plugin install javascript-typescript@claude-code-workflows
Troubleshooting
"Plugin not found" → Use plugin names, not agent names. Add @claude-code-workflows suffix.
Plugins not loading → Clear cache and reinstall:
rm -rf ~/.claude/plugins/cache/claude-code-workflows && rm ~/.claude/plugins/installed_plugins.json
Documentation
Core Guides
- Plugin Reference - Complete catalog of all 80 plugins
- Agent Reference - All 185 agents organized by category
- Agent Skills - 153 specialized skills with progressive disclosure
- Usage Guide - Commands, workflows, and best practices
- Architecture - Design principles and patterns
- PluginEval - Quality evaluation framework (layers, dimensions, scoring)
Quick Links
- Installation - Get started in 2 steps
- Essential Plugins - Top plugins for immediate productivity
- Command Reference - All slash commands organized by category
- Multi-Agent Workflows - Pre-configured orchestration examples
- Model Configuration - Haiku/Sonnet hybrid orchestration
What's New
PluginEval — Quality Evaluation Framework (NEW)
A three-layer evaluation framework for measuring and certifying plugin/skill quality:
/plugin install plugin-eval@claude-code-workflows
- Three Evaluation Layers — Static analysis (instant), LLM judge (semantic), Monte Carlo simulation (statistical)
- 10 Quality Dimensions — Triggering accuracy, orchestration fitness, output quality, scope calibration, progressive disclosure, token efficiency, robustness, structural completeness, code template quality, ecosystem coherence
- Quality Badges — Platinum (★★★★★), Gold (★★★★), Silver (★★★), Bronze (★★)
- Anti-Pattern Detection — OVER_CONSTRAINED, EMPTY_DESCRIPTION, MISSING_TRIGGER, BLOATED_SKILL, ORPHAN_REFERENCE, DEAD_CROSS_REF
- Statistical Rigor — Wilson score CI, bootstrap CI, Clopper-Pearson exact CI, Elo ranking
- CLI + Claude Code —
uv run plugin-eval score/certify/compareor/eval,/certify,/comparecommands - CI Gate —
--thresholdflag exits non-zero below a minimum score
# Quick evaluation (static only, instant)
uv run plugin-eval score path/to/skill --depth quick
# Standard evaluation (static + LLM judge)
uv run plugin-eval score path/to/skill --depth standard
# Full certification (all layers + Elo)
uv run plugin-eval certify path/to/skill
→ View PluginEval documentation
Agent Teams Plugin
Orchestrate multi-agent teams for parallel workflows using Claude Code's experimental Agent Teams feature:
/plugin install agent-teams@claude-code-workflows
- 7 Team Presets —
review,debug,feature,fullstack,research,security,migration - Parallel Code Review —
/team-review src/ --reviewers security,performance,architecture - Hypothesis-Driven Debugging —
/team-debug "API returns 500" --hypotheses 3 - Parallel Feature Development —
/team-feature "Add OAuth2 auth" --plan-first - Research Teams — Parallel investigation across codebase and web sources
- Security Audits — 4 reviewers covering OWASP, auth, dependencies, and secrets
- Migration Support — Coordinated migration with parallel streams and correctness verification
Includes 4 specialized agents, 7 commands, and 6 skills with reference documentation.
→ View agent-teams documentation
Conductor Plugin — Context-Driven Development
Transforms Claude Code into a project management tool with a structured Context → Spec & Plan → Implement workflow:
/plugin install conductor@claude-code-workflows
- Interactive Setup —
/conductor:setupcreates product vision, tech stack, workflow rules, and style guides - Track-Based Development —
/conductor:new-trackgenerates specifications and phased implementation plans - TDD Workflow —
/conductor:implementexecutes tasks with verification checkpoints - Semantic Revert —
/conductor:revertundoes work by logical unit (track, phase, or task) - State Persistence — Resume setup across sessions with persistent project context
- 3 Skills — Context-driven development, track management, workflow patterns
→ View Conductor documentation
Agent Skills (153 skills across 40 plugins)
Specialized knowledge packages following Anthropic's progressive disclosure architecture:
Language Development:
- Python (5 skills): async patterns, testing, packaging, performance, UV package manager
- JavaScript/TypeScript (4 skills): advanced types, Node.js patterns, testing, modern ES6+
Infrastructure & DevOps:
- Kubernetes (4 skills): manifests, Helm charts, GitOps, security policies
- Cloud Infrastructure (4 skills): Terraform, multi-cloud, hybrid networking, cost optimization
- CI/CD (4 skills): pipeline design, GitHub Actions, GitLab CI, secrets management
Development & Architecture:
- Backend (3 skills): API design, architecture patterns, microservices
- LLM Applications (8 skills): LangGraph, prompt engineering, RAG, evaluation, embeddings, similarity search, vector tuning, hybrid search
Blockchain & Web3 (4 skills): DeFi protocols, NFT standards, Solidity security, Web3 testing
Project Management:
- Conductor (3 skills): context-driven development, track management, workflow patterns
And more: Framework migration, observability, payment processing, ML operations, security scanning
→ View complete skills documentation
Three-Tier Model Strategy
Strategic model assignment for optimal performance and cost:
| Tier | Model | Agents | Use Case |
|---|---|---|---|
| Tier 1 | Opus 4.7 | 42 | Critical architecture, security, ALL code review, production coding (language pros, frameworks) |
| Tier 2 | Inherit | 42 | Complex tasks - user chooses model (AI/ML, backend, frontend/mobile, specialized) |
| Tier 3 | Sonnet | 51 | Support with intelligence (docs, testing, debugging, network, API docs, DX, legacy, payments) |
| Tier 4 | Haiku | 18 | Fast operational tasks (SEO, deployment, simple docs, sales, content, search) |
Why Opus 4.7 for Critical Agents?
- 80.8% on SWE-bench (industry-leading)
- 65% fewer tokens for complex tasks
- Best for architecture decisions and security audits
Tier 2 Flexibility (inherit):
Agents marked inherit use your session's default model, letting you balance cost and capability:
- Set via
claude --model opusorclaude --model sonnetwhen starting a session - Falls back to Sonnet 4.6 if no default specified
- Perfect for frontend/mobile developers who want cost control
- AI/ML engineers can choose Opus for complex model work
Cost Considerations:
- Opus 4.7: $5/$25 per million input/output tokens - Premium for critical work
- Sonnet 4.6: $3/$15 per million tokens - Balanced performance/cost
- Haiku 4.5: $1/$5 per million tokens - Fast, cost-effective operations
- Opus's 65% token reduction on complex tasks often offsets higher rate
- Use
inherittier to control costs for high-volume use cases
Orchestration patterns combine models for efficiency:
Opus (architecture) → Sonnet (development) → Haiku (deployment)
→ View model configuration details
Popular Use Cases
Full-Stack Feature Development
/full-stack-orchestration:full-stack-feature "user authentication with OAuth2"
Coordinates 7+ agents: backend-architect → database-architect → frontend-developer → test-automator → security-auditor → deployment-engineer → observability-engineer
Security Hardening
/security-scanning:security-hardening --level comprehensive
Multi-agent security assessment with SAST, dependency scanning, and code review.
Python Development with Modern Tools
/python-development:python-scaffold fastapi-microservice
Creates production-ready FastAPI project with async patterns, activating skills:
async-python-patterns- AsyncIO and concurrencypython-testing-patterns- pytest and fixturesuv-package-manager- Fast dependency management
Kubernetes Deployment
# Activates k8s skills automatically
"Create production Kubernetes deployment with Helm chart and GitOps"
Uses kubernetes-architect agent with 4 specialized skills for production-grade configs.
Plugin Categories
25 categories, 80 plugins:
- 🎨 Development (6) - debugging, backend, frontend, multi-platform
- 📚 Documentation (4) - code docs, API specs, diagrams, C4 architecture, HADS (Human-AI Document Standard)
- 🔄 Workflows (5) - git, full-stack, TDD, Conductor (context-driven development), Agent Teams (multi-agent orchestration)
- ✅ Testing (2) - unit testing, qa-orchestra (multi-agent QA toolkit with Chrome MCP validation)
- 🔍 Quality (3) - comprehensive review, performance
- 🤖 AI & ML (4) - LLM apps, agent orchestration, context, MLOps
- 📊 Data (2) - data engineering, data validation
- 🗄️ Database (2) - database design, migrations
- 🚨 Operations (4) - incident response, diagnostics, distributed debugging, observability
- ⚡ Performance (2) - application performance, database/cloud optimization
- ☁️ Infrastructure (5) - deployment, validation, Kubernetes, cloud, CI/CD
- 🔒 Security (6) - scanning, compliance, backend/API, frontend/mobile, block-no-verify (git hook bypass guard)
- 🛡️ Governance (1) - protect-mcp (Cedar policy enforcement + Ed25519 signed receipts)
- 💻 Languages (10) - Python, JS/TS, systems, JVM, scripting, functional, embedded
- 🔗 Blockchain (1) - smart contracts, DeFi, Web3
- 💰 Finance (1) - quantitative trading, risk management
- 💳 Payments (1) - Stripe, PayPal, billing
- 🎮 Gaming (1) - Unity, Minecraft plugins
- 🎨 Creative (1) - creative tooling
- ♿ Accessibility (1) - WCAG and a11y
- 📢 Marketing (4) - SEO content, technical SEO, SEO analysis, content marketing
- 💼 Business (4) - analytics, HR/legal, customer/sales
- 🔌 API (2) - API tooling
- 🛠️ Utilities (4) - general-purpose helpers
- 🔧 Modernization (2) - legacy migration and refactoring
→ View complete plugin catalog
Related Plugins
Plugins hosted in their own marketplaces — install from the source for the latest releases:
-
Pensyve — Universal memory runtime with cross-session cognitive memory for Claude Code. Intelligent capture, entity-aware recall, 6 commands, 4 skills, 2 agents, and 6 lifecycle hooks.
/plugin marketplace add major7apps/pensyve /plugin install pensyve@major7apps-pensyve
Architecture Highlights
Granular Design
- Single responsibility - Each plugin does one thing well
- Minimal token usage - Average 3.6 components per plugin
- Composable - Mix and match for complex workflows
- 100% coverage - All 185 agents accessible across plugins
Progressive Disclosure (Skills)
Three-tier architecture for token efficiency:
- Metadata - Name and activation criteria (always loaded)
- Instructions - Core guidance (loaded when activated)
- Resources - Examples and templates (loaded on demand)
Repository Structure
claude-agents/
├── .claude-plugin/
│ └── marketplace.json # 81 plugins (80 local + 1 external)
├── plugins/
│ ├── python-development/
│ │ ├── agents/ # 3 Python experts
│ │ ├── commands/ # Scaffolding tool
│ │ └── skills/ # 5 specialized skills
│ ├── kubernetes-operations/
│ │ ├── agents/ # K8s architect
│ │ ├── commands/ # Deployment tools
│ │ └── skills/ # 4 K8s skills
│ └── ... (67 more plugins)
├── docs/ # Comprehensive documentation
└── README.md # This file
Contributing
To add new agents, skills, or commands:
- Identify or create the appropriate plugin directory in
plugins/ - Create
.mdfiles in the appropriate subdirectory:agents/- For specialized agentscommands/- For tools and workflowsskills/- For modular knowledge packages
- Follow naming conventions (lowercase, hyphen-separated)
- Write clear activation criteria and comprehensive content
- Update the plugin definition in
.claude-plugin/marketplace.json
See Architecture Documentation for detailed guidelines.
Resources
Documentation
This Repository
License
MIT License - see LICENSE file for details.