Initial commit

commands/add-agent.md

@@ -0,0 +1,11 @@
+---
+description: Create a new agent for a plugin
+---
+
+Use the agent-writer agent to create a new agent for a plugin.
+
+The agent-writer will:
+- List available plugins to choose from
+- Gather agent requirements and specifications
+- Create properly formatted agent markdown file in the plugin's agents/ directory
+- Follow agent-design skill patterns for autonomous delegation

commands/add-command.md

@@ -0,0 +1,13 @@
+---
+description: Create a new slash command in a plugin
+---
+
+Use the slash-command-writer agent to create a new slash command.
+
+The agent will:
+- List available plugins to choose from
+- Gather command requirements (name, purpose, arguments, tool restrictions)
+- Create the command markdown file in the appropriate plugin's commands directory
+- Validate the command follows best practices
+
+Provide the command name and purpose when ready.

commands/add-hook.md

@@ -0,0 +1,12 @@
+---
+description: Add a new hook to an existing plugin
+---
+
+Use the hooks-writer agent to create a new hook for a plugin.
+
+The hooks-writer will:
+- List available plugins to choose from
+- Gather hook requirements (event type, matcher, command/prompt)
+- Create or update hooks.json in the plugin's hooks/ directory
+- Update plugin.json if needed
+- Follow hook-design skill patterns for deterministic lifecycle integration

commands/add-plugin.md

@@ -0,0 +1,14 @@
+---
+description: Create a new Claude Code plugin with complete scaffolding
+---
+
+Delegate to the plugin-writer agent to create a new Claude Code plugin.
+
+The plugin-writer will:
+- Create proper directory structure with components at root (not in .claude-plugin/)
+- Generate plugin.json with comprehensive metadata
+- Write detailed README with installation and usage instructions
+- **MUST delegate** component creation to specialized writer agents (never create components directly)
+- Self-validate for Box Factory compliance before completing
+- Follow plugin-design skill patterns for production-ready plugins
+- Optionally register plugin in marketplace.json

commands/add-skill.md

@@ -0,0 +1,11 @@
+---
+description: Create a new skill for a plugin
+---
+
+Use the skill-writer agent to create a new skill for a plugin.
+
+The skill-writer will:
+- List available plugins to choose from
+- Gather skill requirements and specifications
+- Create properly formatted SKILL.md file in the plugin's skills/ directory
+- Follow skill-design patterns for progressive knowledge disclosure

commands/review-component.md

@@ -0,0 +1,15 @@
+---
+description: Review a Claude Code component for quality and best practices
+argument-hint: [component-path]
+---
+
+Use the component-reviewer agent to perform a comprehensive quality review of the specified Claude Code component.
+
+The component-reviewer agent will analyze the component against:
+- Relevant design skills (slash-command-design, agent-design, hook-design, plugin-design)
+- Official Claude Code documentation
+- Common anti-patterns and best practices
+
+Component to review: $1
+
+If no component path is provided, the agent will prompt for clarification or review the current file if it's a recognized component type.

commands/update-docs.md

@@ -0,0 +1,47 @@
+---
+description: Update or regenerate README and CLAUDE.md documentation for a plugin
+argument-hint: plugin-path
+---
+
+Update or regenerate comprehensive documentation for the plugin at $1 (or current directory if not specified).
+
+## Process
+
+1. **Read all plugin components:**
+   - plugin.json (metadata)
+   - All files in agents/, commands/, skills/, hooks/
+   - Existing README.md and CLAUDE.md (if present)
+
+2. **Analyze the plugin:**
+   - Core purpose and value proposition
+   - Features and capabilities
+   - Component architecture and relationships
+   - Usage patterns and workflows
+   - Development conventions and patterns
+
+3. **Generate/update README.md:**
+   - Plugin overview and description
+   - Features section (organize by component type)
+   - Installation instructions
+   - Quick start guide
+   - Usage examples for each component
+   - File structure reference
+   - Troubleshooting section
+   - Resources and links
+   - Follow existing Box Factory README patterns as reference
+
+4. **Generate/update CLAUDE.md:**
+   - Development philosophy and principles
+   - Component-specific patterns and conventions
+   - Decision frameworks (when to use what)
+   - Quality standards and checklists
+   - Anti-patterns (forbidden approaches)
+   - Architecture diagrams or patterns
+   - Follow existing Box Factory CLAUDE.md patterns as reference
+
+5. **Ensure quality:**
+   - Documentation matches actual implementation
+   - All components are documented
+   - Examples are accurate and tested
+   - Consistent tone and formatting
+   - No outdated or incorrect information

commands/validate-plugin.md

@@ -0,0 +1,15 @@
+---
+description: Validate a plugin's structure and components against official specs and best practices
+argument-hint: [plugin-path]
+---
+
+Use the validation-agent to perform comprehensive validation of the plugin at `$1`.
+
+The agent will validate:
+- plugin.json structure and required fields
+- Directory structure (components at plugin root, not in .claude-plugin/)
+- Component frontmatter and formatting
+- Forbidden patterns and anti-patterns
+- Best practices compliance
+
+If no path is provided, validate the current plugin context.