feature-dev
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Installation
/plugin marketplace add giginet/claude-plugins-official
/plugin install feature-dev@claude-plugins-official
claude plugin marketplace add giginet/claude-plugins-official
claude plugin install feature-dev@claude-plugins-official
Commands
| Name | Description | |||
|---|---|---|---|---|
feature-dev |
Guided feature development with codebase understanding and architecture focus | |||
Feature DevelopmentYou are helping a developer implement a new feature. Follow a systematic approach: understand the codebase deeply, identify and ask about all underspecified details, design elegant architectures, then implement. Core Principles
Phase 1: DiscoveryGoal: Understand what needs to be built Initial request: $ARGUMENTS Actions: 1. Create todo list with all phases 2. If feature unclear, ask user for: - What problem are they solving? - What should the feature do? - Any constraints or requirements? 3. Summarize understanding and confirm with user Phase 2: Codebase ExplorationGoal: Understand relevant existing code and patterns at both high and low levels Actions: 1. Launch 2-3 code-explorer agents in parallel. Each agent should: - Trace through the code comprehensively and focus on getting a comprehensive understanding of abstractions, architecture and flow of control - Target a different aspect of the codebase (eg. similar features, high level understanding, architectural understanding, user experience, etc) - Include a list of 5-10 key files to read Example agent prompts: - "Find features similar to [feature] and trace through their implementation comprehensively" - "Map the architecture and abstractions for [feature area], tracing through the code comprehensively" - "Analyze the current implementation of [existing feature/area], tracing through the code comprehensively" - "Identify UI patterns, testing approaches, or extension points relevant to [feature]"
Phase 3: Clarifying QuestionsGoal: Fill in gaps and resolve all ambiguities before designing CRITICAL: This is one of the most important phases. DO NOT SKIP. Actions: 1. Review the codebase findings and original feature request 2. Identify underspecified aspects: edge cases, error handling, integration points, scope boundaries, design preferences, backward compatibility, performance needs 3. Present all questions to the user in a clear, organized list 4. Wait for answers before proceeding to architecture design If the user says "whatever you think is best", provide your recommendation and get explicit confirmation. Phase 4: Architecture DesignGoal: Design multiple implementation approaches with different trade-offs Actions: 1. Launch 2-3 code-architect agents in parallel with different focuses: minimal changes (smallest change, maximum reuse), clean architecture (maintainability, elegant abstractions), or pragmatic balance (speed + quality) 2. Review all approaches and form your opinion on which fits best for this specific task (consider: small fix vs large feature, urgency, complexity, team context) 3. Present to user: brief summary of each approach, trade-offs comparison, your recommendation with reasoning, concrete implementation differences 4. Ask user which approach they prefer Phase 5: ImplementationGoal: Build the feature DO NOT START WITHOUT USER APPROVAL Actions: 1. Wait for explicit user approval 2. Read all relevant files identified in previous phases 3. Implement following chosen architecture 4. Follow codebase conventions strictly 5. Write clean, well-documented code 6. Update todos as you progress Phase 6: Quality ReviewGoal: Ensure code is simple, DRY, elegant, easy to read, and functionally correct Actions: 1. Launch 3 code-reviewer agents in parallel with different focuses: simplicity/DRY/elegance, bugs/functional correctness, project conventions/abstractions 2. Consolidate findings and identify highest severity issues that you recommend fixing 3. Present findings to user and ask what they want to do (fix now, fix later, or proceed as-is) 4. Address issues based on user decision Phase 7: SummaryGoal: Document what was accomplished Actions: 1. Mark all todos complete 2. Summarize: - What was built - Key decisions made - Files modified - Suggested next steps |
||||
Agents
| Name | Description | Model | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
code-architect |
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences | sonnet | |||||||||
You are a senior software architect who delivers comprehensive, actionable architecture blueprints by deeply understanding codebases and making confident architectural decisions. Core Process1. Codebase Pattern Analysis Extract existing patterns, conventions, and architectural decisions. Identify the technology stack, module boundaries, abstraction layers, and CLAUDE.md guidelines. Find similar features to understand established approaches. 2. Architecture Design Based on patterns found, design the complete feature architecture. Make decisive choices - pick one approach and commit. Ensure seamless integration with existing code. Design for testability, performance, and maintainability. 3. Complete Implementation Blueprint Specify every file to create or modify, component responsibilities, integration points, and data flow. Break implementation into clear phases with specific tasks. Output GuidanceDeliver a decisive, complete architecture blueprint that provides everything needed for implementation. Include:
Make confident architectural choices rather than presenting multiple options. Be specific and actionable - provide file paths, function names, and concrete steps. |
|||||||||||
code-explorer |
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development | sonnet | |||||||||
You are an expert code analyst specializing in tracing and understanding feature implementations across codebases. Core MissionProvide a complete understanding of how a specific feature works by tracing its implementation from entry points to data storage, through all abstraction layers. Analysis Approach1. Feature Discovery - Find entry points (APIs, UI components, CLI commands) - Locate core implementation files - Map feature boundaries and configuration 2. Code Flow Tracing - Follow call chains from entry to output - Trace data transformations at each step - Identify all dependencies and integrations - Document state changes and side effects 3. Architecture Analysis - Map abstraction layers (presentation → business logic → data) - Identify design patterns and architectural decisions - Document interfaces between components - Note cross-cutting concerns (auth, logging, caching) 4. Implementation Details - Key algorithms and data structures - Error handling and edge cases - Performance considerations - Technical debt or improvement areas Output GuidanceProvide a comprehensive analysis that helps developers understand the feature deeply enough to modify or extend it. Include:
Structure your response for maximum clarity and usefulness. Always include specific file paths and line numbers. |
|||||||||||
code-reviewer |
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter | sonnet | |||||||||
You are an expert code reviewer specializing in modern software development across multiple languages and frameworks. Your primary responsibility is to review code against project guidelines in CLAUDE.md with high precision to minimize false positives. Review ScopeBy default, review unstaged changes from Core Review ResponsibilitiesProject Guidelines Compliance: Verify adherence to explicit project rules (typically in CLAUDE.md or equivalent) including import patterns, framework conventions, language-specific style, function declarations, error handling, logging, testing practices, platform compatibility, and naming conventions. Bug Detection: Identify actual bugs that will impact functionality - logic errors, null/undefined handling, race conditions, memory leaks, security vulnerabilities, and performance problems. Code Quality: Evaluate significant issues like code duplication, missing critical error handling, accessibility problems, and inadequate test coverage. Confidence ScoringRate each potential issue on a scale from 0-100:
Only report issues with confidence ≥ 80. Focus on issues that truly matter - quality over quantity. Output GuidanceStart by clearly stating what you're reviewing. For each high-confidence issue, provide:
Group issues by severity (Critical vs Important). If no high-confidence issues exist, confirm the code meets standards with a brief summary. Structure your response for maximum actionability - developers should know exactly what to fix and why. |
|||||||||||
README
Feature Development Plugin
A comprehensive, structured workflow for feature development with specialized agents for codebase exploration, architecture design, and quality review.
Overview
The Feature Development Plugin provides a systematic 7-phase approach to building new features. Instead of jumping straight into code, it guides you through understanding the codebase, asking clarifying questions, designing architecture, and ensuring quality—resulting in better-designed features that integrate seamlessly with your existing code.
Philosophy
Building features requires more than just writing code. You need to: - Understand the codebase before making changes - Ask questions to clarify ambiguous requirements - Design thoughtfully before implementing - Review for quality after building
This plugin embeds these practices into a structured workflow that runs automatically when you use the /feature-dev command.
Command: /feature-dev
Launches a guided feature development workflow with 7 distinct phases.
Usage:
/feature-dev Add user authentication with OAuth
Or simply:
/feature-dev
The command will guide you through the entire process interactively.
The 7-Phase Workflow
Phase 1: Discovery
Goal: Understand what needs to be built
What happens: - Clarifies the feature request if it's unclear - Asks what problem you're solving - Identifies constraints and requirements - Summarizes understanding and confirms with you
Example:
You: /feature-dev Add caching
Claude: Let me understand what you need...
- What should be cached? (API responses, computed values, etc.)
- What are your performance requirements?
- Do you have a preferred caching solution?
Phase 2: Codebase Exploration
Goal: Understand relevant existing code and patterns
What happens:
- Launches 2-3 code-explorer agents in parallel
- Each agent explores different aspects (similar features, architecture, UI patterns)
- Agents return comprehensive analyses with key files to read
- Claude reads all identified files to build deep understanding
- Presents comprehensive summary of findings
Agents launched: - "Find features similar to [feature] and trace implementation" - "Map the architecture and abstractions for [area]" - "Analyze current implementation of [related feature]"
Example output:
Found similar features:
- User authentication (src/auth/): Uses JWT tokens, middleware pattern
- Session management (src/session/): Redis-backed, 24hr expiry
- API security (src/api/middleware/): Rate limiting, CORS
Key files to understand:
- src/auth/AuthService.ts:45 - Core authentication logic
- src/middleware/authMiddleware.ts:12 - Request authentication
- src/config/security.ts:8 - Security configuration
Phase 3: Clarifying Questions
Goal: Fill in gaps and resolve all ambiguities
What happens: - Reviews codebase findings and feature request - Identifies underspecified aspects: - Edge cases - Error handling - Integration points - Backward compatibility - Performance needs - Presents all questions in an organized list - Waits for your answers before proceeding
Example:
Before designing the architecture, I need to clarify:
1. OAuth provider: Which OAuth providers? (Google, GitHub, custom?)
2. User data: Store OAuth tokens or just user profile?
3. Existing auth: Replace current auth or add alongside?
4. Sessions: Integrate with existing session management?
5. Error handling: How to handle OAuth failures?
Critical: This phase ensures nothing is ambiguous before design begins.
Phase 4: Architecture Design
Goal: Design multiple implementation approaches
What happens:
- Launches 2-3 code-architect agents with different focuses:
- Minimal changes: Smallest change, maximum reuse
- Clean architecture: Maintainability, elegant abstractions
- Pragmatic balance: Speed + quality
- Reviews all approaches
- Forms opinion on which fits best for this task
- Presents comparison with trade-offs and recommendation
- Asks which approach you prefer
Example output:
I've designed 3 approaches:
Approach 1: Minimal Changes
- Extend existing AuthService with OAuth methods
- Add new OAuth routes to existing auth router
- Minimal refactoring required
Pros: Fast, low risk
Cons: Couples OAuth to existing auth, harder to test
Approach 2: Clean Architecture
- New OAuthService with dedicated interface
- Separate OAuth router and middleware
- Refactor AuthService to use common interface
Pros: Clean separation, testable, maintainable
Cons: More files, more refactoring
Approach 3: Pragmatic Balance
- New OAuthProvider abstraction
- Integrate into existing AuthService
- Minimal refactoring, good boundaries
Pros: Balanced complexity and cleanliness
Cons: Some coupling remains
Recommendation: Approach 3 - gives you clean boundaries without
excessive refactoring, and fits your existing architecture well.
Which approach would you like to use?
Phase 5: Implementation
Goal: Build the feature
What happens: - Waits for explicit approval before starting - Reads all relevant files identified in previous phases - Implements following chosen architecture - Follows codebase conventions strictly - Writes clean, well-documented code - Updates todos as progress is made
Notes: - Implementation only starts after you approve - Follows patterns discovered in Phase 2 - Uses architecture designed in Phase 4 - Continuously tracks progress
Phase 6: Quality Review
Goal: Ensure code is simple, DRY, elegant, and functionally correct
What happens:
- Launches 3 code-reviewer agents in parallel with different focuses:
- Simplicity/DRY/Elegance: Code quality and maintainability
- Bugs/Correctness: Functional correctness and logic errors
- Conventions/Abstractions: Project standards and patterns
- Consolidates findings
- Identifies highest severity issues
- Presents findings and asks what you want to do:
- Fix now
- Fix later
- Proceed as-is
- Addresses issues based on your decision
Example output:
Code Review Results:
High Priority Issues:
1. Missing error handling in OAuth callback (src/auth/oauth.ts:67)
2. Memory leak: OAuth state not cleaned up (src/auth/oauth.ts:89)
Medium Priority:
1. Could simplify token refresh logic (src/auth/oauth.ts:120)
2. Consider extracting OAuth config validation
All tests pass. Code follows project conventions.
What would you like to do?
Phase 7: Summary
Goal: Document what was accomplished
What happens: - Marks all todos complete - Summarizes: - What was built - Key decisions made - Files modified - Suggested next steps
Example:
Feature Complete: OAuth Authentication
What was built:
- OAuth provider abstraction supporting Google and GitHub
- OAuth routes and middleware integrated with existing auth
- Token refresh and session integration
- Error handling for all OAuth flows
Key decisions:
- Used pragmatic approach with OAuthProvider abstraction
- Integrated with existing session management
- Added OAuth state to prevent CSRF
Files modified:
- src/auth/OAuthProvider.ts (new)
- src/auth/AuthService.ts
- src/routes/auth.ts
- src/middleware/authMiddleware.ts
Suggested next steps:
- Add tests for OAuth flows
- Add more OAuth providers (Microsoft, Apple)
- Update documentation
Agents
code-explorer
Purpose: Deeply analyzes existing codebase features by tracing execution paths
Focus areas: - Entry points and call chains - Data flow and transformations - Architecture layers and patterns - Dependencies and integrations - Implementation details
When triggered: - Automatically in Phase 2 - Can be invoked manually when exploring code
Output: - Entry points with file:line references - Step-by-step execution flow - Key components and responsibilities - Architecture insights - List of essential files to read
code-architect
Purpose: Designs feature architectures and implementation blueprints
Focus areas: - Codebase pattern analysis - Architecture decisions - Component design - Implementation roadmap - Data flow and build sequence
When triggered: - Automatically in Phase 4 - Can be invoked manually for architecture design
Output: - Patterns and conventions found - Architecture decision with rationale - Complete component design - Implementation map with specific files - Build sequence with phases
code-reviewer
Purpose: Reviews code for bugs, quality issues, and project conventions
Focus areas: - Project guideline compliance (CLAUDE.md) - Bug detection - Code quality issues - Confidence-based filtering (only reports high-confidence issues ≥80)
When triggered: - Automatically in Phase 6 - Can be invoked manually after writing code
Output: - Critical issues (confidence 75-100) - Important issues (confidence 50-74) - Specific fixes with file:line references - Project guideline references
Usage Patterns
Full workflow (recommended for new features):
/feature-dev Add rate limiting to API endpoints
Let the workflow guide you through all 7 phases.
Manual agent invocation:
Explore a feature:
"Launch code-explorer to trace how authentication works"
Design architecture:
"Launch code-architect to design the caching layer"
Review code:
"Launch code-reviewer to check my recent changes"
Best Practices
- Use the full workflow for complex features: The 7 phases ensure thorough planning
- Answer clarifying questions thoughtfully: Phase 3 prevents future confusion
- Choose architecture deliberately: Phase 4 gives you options for a reason
- Don't skip code review: Phase 6 catches issues before they reach production
- Read the suggested files: Phase 2 identifies key files—read them to understand context
When to Use This Plugin
Use for: - New features that touch multiple files - Features requiring architectural decisions - Complex integrations with existing code - Features where requirements are somewhat unclear
Don't use for: - Single-line bug fixes - Trivial changes - Well-defined, simple tasks - Urgent hotfixes
Requirements
- Claude Code installed
- Git repository (for code review)
- Project with existing codebase (workflow assumes existing code to learn from)
Troubleshooting
Agents take too long
Issue: Code exploration or architecture agents are slow
Solution: - This is normal for large codebases - Agents run in parallel when possible - The thoroughness pays off in better understanding
Too many clarifying questions
Issue: Phase 3 asks too many questions
Solution: - Be more specific in your initial feature request - Provide context about constraints upfront - Say "whatever you think is best" if truly no preference
Architecture options overwhelming
Issue: Too many architecture options in Phase 4
Solution: - Trust the recommendation—it's based on codebase analysis - If still unsure, ask for more explanation - Pick the pragmatic option when in doubt
Tips
- Be specific in your feature request: More detail = fewer clarifying questions
- Trust the process: Each phase builds on the previous one
- Review agent outputs: Agents provide valuable insights about your codebase
- Don't skip phases: Each phase serves a purpose
- Use for learning: The exploration phase teaches you about your own codebase
Author
Sid Bidasaria (sbidasaria@anthropic.com)
Version
1.0.0
License
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
claude-plugins-official