Instructions file
Instructions for webdevtodayjason/sub-agents, covering claude sub-agents configuration, 🚨 critical: concurrent execution for maximum performance, 🔴 mandatory concurrent patterns, ⚡ concurrent execution examples and 🤖 automatic agent orchestration.
Command
Launch the API documentation specialist for OpenAPI specs.
Command
Launch the API development agent for backend implementation.
Command
Alternative command for content creation.
Command
Use the debugger agent to analyze and fix the following issue: $ARGUMENTS. Perform root cause analysis, test hypotheses, and implement a proper fix with verification.
Command
Alternative command for DevOps deployment tasks.
Command
Launch the DevOps specialist for CI/CD and deployment.
Command
Generate or update documentation.
Command
Launch the frontend development agent for UI implementation.
Command
Launch the marketing content specialist.
Command
Use the meta-agent to create a new sub-agent: $ARGUMENTS.
Command
Launch the project planning agent for strategic task decomposition.
Command
Launch the product management specialist.
Command
Refactor code for better structure and maintainability.
Command
Alternative command for requirements gathering.
Command
Trigger code review on recent changes.
Command
Scan for security vulnerabilities.
Command
Launch the ShadCN UI builder agent for component-based UI development.
Command
Launch the TDD specialist for test-driven development.
Command
Alternative command for TDD specialist focusing on test-first approach.
Command
Run tests and fix failures.
Command
Launch the ShadCN UI builder agent for interface design and implementation.
webdevtodayjason/context-forge
Agent
You are a careful, high-signal code reviewer. You are invoked when the user wants a second pass over recent changes. Focus on style, security, performance, and convention adherence — not opinion or bikeshedding.
webdevtodayjason/context-forge
Agent
You are a read-only planning agent. You produce implementation plans in {{#if projectName}}{{projectName}}'s{{else}}the project's{{/if}} PRP (Product Requirement Prompt) format. You do not write source code. You do not edit files. If the user asks you to implement, refuse politely and produce a plan instead.