development▌

Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns. \n \n Provides three file ownership models (by directory, module, or layer) and enforces the cardinal rule: one owner per file to prevent merge conflicts \n Defines interface contracts as read-only coordination points between implementers, allowing shared boundaries without direct file conflicts \n Covers two integration patterns (vertical slice for independent features, ho

Create, debug, and deploy serverless cloud programs for web scraping, automation, and data processing. \n \n Supports JavaScript, TypeScript, and Python templates with integrated Crawlee, Playwright, and Cheerio libraries for HTTP and browser-based crawling \n Includes local testing via apify run with isolated storage, schema validation for inputs/outputs, and deployment to Apify platform via apify push \n Requires Apify CLI authentication and mandatory generatedBy metadata in .actor/actor.json

Event-driven automation for Claude Code plugins using prompt-based and command hooks. \n \n Supports 9 hook events (PreToolUse, PostToolUse, Stop, SubagentStop, UserPromptSubmit, SessionStart, SessionEnd, PreCompact, Notification) for validation, policy enforcement, and workflow automation \n Prompt-based hooks use LLM reasoning for context-aware decisions; command hooks execute bash scripts for deterministic checks \n Includes matchers for filtering by tool name (exact, regex, wildcard) and par

Role: Voice AI Architect

Markdown-based slash commands for defining reusable prompts with dynamic arguments, file references, and bash execution. \n \n Commands are instructions written for Claude (not users), stored as .md files in .claude/commands/ , ~/.claude/commands/ , or plugin directories \n YAML frontmatter configures description, allowed tools, model selection, and argument hints; use $ARGUMENTS , $1 , $2 for dynamic substitution and @file-path syntax for file inclusion \n Bash execution via backticks gathers d

Guidance for creating effective, discoverable skills for Claude Code plugins with progressive disclosure and strong triggering. \n \n Create skills in the plugin's skills/ directory with SKILL.md (required) and optional references/ , examples/ , and scripts/ subdirectories for progressive context loading \n Write frontmatter descriptions in third person with specific trigger phrases users would say (e.g., \"This skill should be used when the user asks to 'create a hook', 'validate tool use'...\"

$22

Structured project context management through persistent, synchronized documentation artifacts. \n \n Creates and maintains five core artifacts in a conductor/ directory: product.md (vision/goals), tech-stack.md (dependencies/architecture), workflow.md (development practices), tracks.md (work unit registry), and product-guidelines.md (communication standards) \n Scaffolds new projects interactively or extracts context from existing codebases, pre-populating artifacts based on discovered patterns

$22

Write tests first, watch them fail, then implement minimal code to pass. \n \n Follows the red-green-refactor cycle: write a failing test, verify it fails correctly, implement minimal code to pass, then refactor while keeping tests green \n Requires deleting any production code written before tests exist; no exceptions for \"reference\" or \"adaptation\" \n Emphasizes watching tests fail as proof they actually test the right thing; tests that pass immediately prove nothing \n Covers common ratio