cue-ai 0.3.0 → 0.4.1

package/resources/claude-plugins-official/plugins/plugin-dev/skills/agent-development/scripts/validate-agent.sh

@@ -1,217 +0,0 @@
-#!/bin/bash
-# Agent File Validator
-# Validates agent markdown files for correct structure and content
-
-set -euo pipefail
-
-# Usage
-if [ $# -eq 0 ]; then
-  echo "Usage: $0 <path/to/agent.md>"
-  echo ""
-  echo "Validates agent file for:"
-  echo "  - YAML frontmatter structure"
-  echo "  - Required fields (name, description, model, color)"
-  echo "  - Field formats and constraints"
-  echo "  - System prompt presence and length"
-  echo "  - Example blocks in description"
-  exit 1
-fi
-
-AGENT_FILE="$1"
-
-echo "🔍 Validating agent file: $AGENT_FILE"
-echo ""
-
-# Check 1: File exists
-if [ ! -f "$AGENT_FILE" ]; then
-  echo "❌ File not found: $AGENT_FILE"
-  exit 1
-fi
-echo "✅ File exists"
-
-# Check 2: Starts with ---
-FIRST_LINE=$(head -1 "$AGENT_FILE")
-if [ "$FIRST_LINE" != "---" ]; then
-  echo "❌ File must start with YAML frontmatter (---)"
-  exit 1
-fi
-echo "✅ Starts with frontmatter"
-
-# Check 3: Has closing ---
-if ! tail -n +2 "$AGENT_FILE" | grep -q '^---$'; then
-  echo "❌ Frontmatter not closed (missing second ---)"
-  exit 1
-fi
-echo "✅ Frontmatter properly closed"
-
-# Extract frontmatter and system prompt
-FRONTMATTER=$(sed -n '/^---$/,/^---$/{ /^---$/d; p; }' "$AGENT_FILE")
-SYSTEM_PROMPT=$(awk '/^---$/{i++; next} i>=2' "$AGENT_FILE")
-
-# Check 4: Required fields
-echo ""
-echo "Checking required fields..."
-
-error_count=0
-warning_count=0
-
-# Check name field
-NAME=$(echo "$FRONTMATTER" | grep '^name:' | sed 's/name: *//' | sed 's/^"\(.*\)"$/\1/')
-
-if [ -z "$NAME" ]; then
-  echo "❌ Missing required field: name"
-  ((error_count++))
-else
-  echo "✅ name: $NAME"
-
-  # Validate name format
-  if ! [[ "$NAME" =~ ^[a-zA-Z0-9][a-zA-Z0-9-]*[a-zA-Z0-9]$ ]]; then
-    echo "❌ name must start/end with alphanumeric and contain only letters, numbers, hyphens"
-    ((error_count++))
-  fi
-
-  # Validate name length
-  name_length=${#NAME}
-  if [ $name_length -lt 3 ]; then
-    echo "❌ name too short (minimum 3 characters)"
-    ((error_count++))
-  elif [ $name_length -gt 50 ]; then
-    echo "❌ name too long (maximum 50 characters)"
-    ((error_count++))
-  fi
-
-  # Check for generic names
-  if [[ "$NAME" =~ ^(helper|assistant|agent|tool)$ ]]; then
-    echo "⚠️  name is too generic: $NAME"
-    ((warning_count++))
-  fi
-fi
-
-# Check description field
-DESCRIPTION=$(echo "$FRONTMATTER" | grep '^description:' | sed 's/description: *//')
-
-if [ -z "$DESCRIPTION" ]; then
-  echo "❌ Missing required field: description"
-  ((error_count++))
-else
-  desc_length=${#DESCRIPTION}
-  echo "✅ description: ${desc_length} characters"
-
-  if [ $desc_length -lt 10 ]; then
-    echo "⚠️  description too short (minimum 10 characters recommended)"
-    ((warning_count++))
-  elif [ $desc_length -gt 5000 ]; then
-    echo "⚠️  description very long (over 5000 characters)"
-    ((warning_count++))
-  fi
-
-  # Check for example blocks
-  if ! echo "$DESCRIPTION" | grep -q '<example>'; then
-    echo "⚠️  description should include <example> blocks for triggering"
-    ((warning_count++))
-  fi
-
-  # Check for "Use this agent when" pattern
-  if ! echo "$DESCRIPTION" | grep -qi 'use this agent when'; then
-    echo "⚠️  description should start with 'Use this agent when...'"
-    ((warning_count++))
-  fi
-fi
-
-# Check model field
-MODEL=$(echo "$FRONTMATTER" | grep '^model:' | sed 's/model: *//')
-
-if [ -z "$MODEL" ]; then
-  echo "❌ Missing required field: model"
-  ((error_count++))
-else
-  echo "✅ model: $MODEL"
-
-  case "$MODEL" in
-    inherit|sonnet|opus|haiku)
-      # Valid model
-      ;;
-    *)
-      echo "⚠️  Unknown model: $MODEL (valid: inherit, sonnet, opus, haiku)"
-      ((warning_count++))
-      ;;
-  esac
-fi
-
-# Check color field
-COLOR=$(echo "$FRONTMATTER" | grep '^color:' | sed 's/color: *//')
-
-if [ -z "$COLOR" ]; then
-  echo "❌ Missing required field: color"
-  ((error_count++))
-else
-  echo "✅ color: $COLOR"
-
-  case "$COLOR" in
-    blue|cyan|green|yellow|magenta|red)
-      # Valid color
-      ;;
-    *)
-      echo "⚠️  Unknown color: $COLOR (valid: blue, cyan, green, yellow, magenta, red)"
-      ((warning_count++))
-      ;;
-  esac
-fi
-
-# Check tools field (optional)
-TOOLS=$(echo "$FRONTMATTER" | grep '^tools:' | sed 's/tools: *//')
-
-if [ -n "$TOOLS" ]; then
-  echo "✅ tools: $TOOLS"
-else
-  echo "💡 tools: not specified (agent has access to all tools)"
-fi
-
-# Check 5: System prompt
-echo ""
-echo "Checking system prompt..."
-
-if [ -z "$SYSTEM_PROMPT" ]; then
-  echo "❌ System prompt is empty"
-  ((error_count++))
-else
-  prompt_length=${#SYSTEM_PROMPT}
-  echo "✅ System prompt: $prompt_length characters"
-
-  if [ $prompt_length -lt 20 ]; then
-    echo "❌ System prompt too short (minimum 20 characters)"
-    ((error_count++))
-  elif [ $prompt_length -gt 10000 ]; then
-    echo "⚠️  System prompt very long (over 10,000 characters)"
-    ((warning_count++))
-  fi
-
-  # Check for second person
-  if ! echo "$SYSTEM_PROMPT" | grep -q "You are\|You will\|Your"; then
-    echo "⚠️  System prompt should use second person (You are..., You will...)"
-    ((warning_count++))
-  fi
-
-  # Check for structure
-  if ! echo "$SYSTEM_PROMPT" | grep -qi "responsibilities\|process\|steps"; then
-    echo "💡 Consider adding clear responsibilities or process steps"
-  fi
-
-  if ! echo "$SYSTEM_PROMPT" | grep -qi "output"; then
-    echo "💡 Consider defining output format expectations"
-  fi
-fi
-
-echo ""
-echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-
-if [ $error_count -eq 0 ] && [ $warning_count -eq 0 ]; then
-  echo "✅ All checks passed!"
-  exit 0
-elif [ $error_count -eq 0 ]; then
-  echo "⚠️  Validation passed with $warning_count warning(s)"
-  exit 0
-else
-  echo "❌ Validation failed with $error_count error(s) and $warning_count warning(s)"
-  exit 1
-fi

package/resources/claude-plugins-official/plugins/plugin-dev/skills/command-development/README.md

@@ -1,272 +0,0 @@
-# Command Development Skill
-
-Comprehensive guidance on creating Claude Code slash commands, including file format, frontmatter options, dynamic arguments, and best practices.
-
-## Overview
-
-This skill provides knowledge about:
-- Slash command file format and structure
-- YAML frontmatter configuration fields
-- Dynamic arguments ($ARGUMENTS, $1, $2, etc.)
-- File references with @ syntax
-- Bash execution with !` syntax
-- Command organization and namespacing
-- Best practices for command development
-- Plugin-specific features (${CLAUDE_PLUGIN_ROOT}, plugin patterns)
-- Integration with plugin components (agents, skills, hooks)
-- Validation patterns and error handling
-
-## Skill Structure
-
-### SKILL.md (~2,470 words)
-
-Core skill content covering:
-
-**Fundamentals:**
-- Command basics and locations
-- File format (Markdown with optional frontmatter)
-- YAML frontmatter fields overview
-- Dynamic arguments ($ARGUMENTS and positional)
-- File references (@ syntax)
-- Bash execution (!` syntax)
-- Command organization patterns
-- Best practices and common patterns
-- Troubleshooting
-
-**Plugin-Specific:**
-- ${CLAUDE_PLUGIN_ROOT} environment variable
-- Plugin command discovery and organization
-- Plugin command patterns (configuration, template, multi-script)
-- Integration with plugin components (agents, skills, hooks)
-- Validation patterns (argument, file, resource, error handling)
-
-### References
-
-Detailed documentation:
-
-- **frontmatter-reference.md**: Complete YAML frontmatter field specifications
-  - All field descriptions with types and defaults
-  - When to use each field
-  - Examples and best practices
-  - Validation and common errors
-
-- **plugin-features-reference.md**: Plugin-specific command features
-  - Plugin command discovery and organization
-  - ${CLAUDE_PLUGIN_ROOT} environment variable usage
-  - Plugin command patterns (configuration, template, multi-script)
-  - Integration with plugin agents, skills, and hooks
-  - Validation patterns and error handling
-
-### Examples
-
-Practical command examples:
-
-- **simple-commands.md**: 10 complete command examples
-  - Code review commands
-  - Testing commands
-  - Deployment commands
-  - Documentation generators
-  - Git integration commands
-  - Analysis and research commands
-
-- **plugin-commands.md**: 10 plugin-specific command examples
-  - Simple plugin commands with scripts
-  - Multi-script workflows
-  - Template-based generation
-  - Configuration-driven deployment
-  - Agent and skill integration
-  - Multi-component workflows
-  - Validated input commands
-  - Environment-aware commands
-
-## When This Skill Triggers
-
-Claude Code activates this skill when users:
-- Ask to "create a slash command" or "add a command"
-- Need to "write a custom command"
-- Want to "define command arguments"
-- Ask about "command frontmatter" or YAML configuration
-- Need to "organize commands" or use namespacing
-- Want to create commands with file references
-- Ask about "bash execution in commands"
-- Need command development best practices
-
-## Progressive Disclosure
-
-The skill uses progressive disclosure:
-
-1. **SKILL.md** (~2,470 words): Core concepts, common patterns, and plugin features overview
-2. **References** (~13,500 words total): Detailed specifications
-   - frontmatter-reference.md (~1,200 words)
-   - plugin-features-reference.md (~1,800 words)
-   - interactive-commands.md (~2,500 words)
-   - advanced-workflows.md (~1,700 words)
-   - testing-strategies.md (~2,200 words)
-   - documentation-patterns.md (~2,000 words)
-   - marketplace-considerations.md (~2,200 words)
-3. **Examples** (~6,000 words total): Complete working command examples
-   - simple-commands.md
-   - plugin-commands.md
-
-Claude loads references and examples as needed based on task.
-
-## Command Basics Quick Reference
-
-### File Format
-
-```markdown
----
-description: Brief description
-argument-hint: [arg1] [arg2]
-allowed-tools: Read, Bash(git:*)
----
-
-Command prompt content with:
-- Arguments: $1, $2, or $ARGUMENTS
-- Files: @path/to/file
-- Bash: !`command here`
-```
-
-### Locations
-
-- **Project**: `.claude/commands/` (shared with team)
-- **Personal**: `~/.claude/commands/` (your commands)
-- **Plugin**: `plugin-name/commands/` (plugin-specific)
-
-### Key Features
-
-**Dynamic arguments:**
-- `$ARGUMENTS` - All arguments as single string
-- `$1`, `$2`, `$3` - Positional arguments
-
-**File references:**
-- `@path/to/file` - Include file contents
-
-**Bash execution:**
-- `!`command`` - Execute and include output
-
-## Frontmatter Fields Quick Reference
-
-| Field | Purpose | Example |
-|-------|---------|---------|
-| `description` | Brief description for /help | `"Review code for issues"` |
-| `allowed-tools` | Restrict tool access | `Read, Bash(git:*)` |
-| `model` | Specify model | `sonnet`, `opus`, `haiku` |
-| `argument-hint` | Document arguments | `[pr-number] [priority]` |
-| `disable-model-invocation` | Manual-only command | `true` |
-
-## Common Patterns
-
-### Simple Review Command
-
-```markdown
----
-description: Review code for issues
----
-
-Review this code for quality and potential bugs.
-```
-
-### Command with Arguments
-
-```markdown
----
-description: Deploy to environment
-argument-hint: [environment] [version]
----
-
-Deploy to $1 environment using version $2
-```
-
-### Command with File Reference
-
-```markdown
----
-description: Document file
-argument-hint: [file-path]
----
-
-Generate documentation for @$1
-```
-
-### Command with Bash Execution
-
-```markdown
----
-description: Show Git status
-allowed-tools: Bash(git:*)
----
-
-Current status: !`git status`
-Recent commits: !`git log --oneline -5`
-```
-
-## Development Workflow
-
-1. **Design command:**
-   - Define purpose and scope
-   - Determine required arguments
-   - Identify needed tools
-
-2. **Create file:**
-   - Choose appropriate location
-   - Create `.md` file with command name
-   - Write basic prompt
-
-3. **Add frontmatter:**
-   - Start minimal (just description)
-   - Add fields as needed (allowed-tools, etc.)
-   - Document arguments with argument-hint
-
-4. **Test command:**
-   - Invoke with `/command-name`
-   - Verify arguments work
-   - Check bash execution
-   - Test file references
-
-5. **Refine:**
-   - Improve prompt clarity
-   - Handle edge cases
-   - Add examples in comments
-   - Document requirements
-
-## Best Practices Summary
-
-1. **Single responsibility**: One command, one clear purpose
-2. **Clear descriptions**: Make discoverable in `/help`
-3. **Document arguments**: Always use argument-hint
-4. **Minimal tools**: Use most restrictive allowed-tools
-5. **Test thoroughly**: Verify all features work
-6. **Add comments**: Explain complex logic
-7. **Handle errors**: Consider missing arguments/files
-
-## Status
-
-**Completed enhancements:**
-- ✓ Plugin command patterns (${CLAUDE_PLUGIN_ROOT}, discovery, organization)
-- ✓ Integration patterns (agents, skills, hooks coordination)
-- ✓ Validation patterns (input, file, resource validation, error handling)
-
-**Remaining enhancements (in progress):**
-- Advanced workflows (multi-step command sequences)
-- Testing strategies (how to test commands effectively)
-- Documentation patterns (command documentation best practices)
-- Marketplace considerations (publishing and distribution)
-
-## Maintenance
-
-To update this skill:
-1. Keep SKILL.md focused on core fundamentals
-2. Move detailed specifications to references/
-3. Add new examples/ for different use cases
-4. Update frontmatter when new fields added
-5. Ensure imperative/infinitive form throughout
-6. Test examples work with current Claude Code
-
-## Version History
-
-**v0.1.0** (2025-01-15):
-- Initial release with basic command fundamentals
-- Frontmatter field reference
-- 10 simple command examples
-- Ready for plugin-specific pattern additions