Command Claude Code
Expert in Phase 5 implementation planning for the plan workflow. Use when creating detailed technical implementation plans with acceptance criteria, CRUD operations, and step-by-step action plans for each user story.
Command Claude Code
Ultimate meta-level feature workflow expert. Use when you need to autonomously execute the entire 6-phase feature workflow, create or optimize workflow artifacts, or provide meta-level analysis of feature development processes. Combines deep workflow knowledge with autonomous execution capabilities.
Command Claude Code
Expert Issue Management Architect. Use when creating, transforming, or updating issues across any domain (tech, operations, marketing, sales, finance, people). Specializes in intelligent domain detection, structured issue creation, and maintaining consistency across all issue types.
Command Claude Code
Expert prompt engineering specialist for Claude Code. Use when creating, refining, or optimizing prompts for Claude-based AI systems, especially for coding and development tasks. Specializes in structured prompting techniques following the modular prompt philosophy.
Command Claude Code
Expert in Phase 3 refinement and architecture for the plan workflow. Use when defining exact properties, behaviours, and system architecture for all components following the 5-layer refinement approach.
Command Claude Code
Expert in Phase 2 requirements elaboration for the plan workflow. Use when expanding high-level requirements into detailed activity flows and identifying all deliverables needed for implementation.
Command Claude Code
Expert in Phase 4 milestone and roadmap planning for the plan workflow. Use when organizing deliverables into releasable milestones, creating user stories, and generating effort estimates for sprint planning.
Command Claude Code
Expert in creating detailed user stories from milestone deliverables. Use when transforming high-level requirements into actionable stories with clear acceptance criteria, effort estimates, and technical specifications.
Command Claude Code
Ultimate meta-level agent for maintaining and evolving the PLX framework. Use for creating/updating any framework artifact or for expert guidance on the framework itself. Embodies the expertise of all other agents.
Command Claude Code
When this command is used, switch to the specified operational mode. Acknowledge the mode activation and proceed according to the mode's defined behaviors.
Command Claude Code
When this command is used, switch to the specified operational mode. Acknowledge the mode activation and proceed according to the mode's defined behaviors.
Command Claude Code
When this command is used, switch to the specified operational mode. Acknowledge the mode activation and proceed according to the mode's defined behaviors.
Instructions file
Claude Code instructions for appboypov/pew-pew-plx-old, covering claude.md, common development commands, core commands, sync all framework components to claude code and clean sync (removes and re-adds all components).
Cursor rule Cursor
Apply when implementing or discussing configuration management strategy for any CLI tool. Ensures a clear order of precedence (args > env > project config > user config > system config), use of standard config file locations (e.g., XDG Base Directory spec), support for environment variables, and secure persistence of…
Cursor rule Cursor
Apply when creating or updating user-facing documentation (README, help text) for a CLI tool. Ensures comprehensive and conventional help output (-h/--help), clear usage examples, a useful README quickstart, consistency between docs and behavior, informative output standards (including color and JSON options), and…
Cursor rule Cursor
Cursor rule "no-inline-comments-agent" from appboypov/pew-pew-cli, covering no inline code comments, critical rules and examples.
Cursor rule Cursor
This rule is essential for maintaining consistency and quality in rule creation across the codebase. It must be followed whenever: (1) A user requests a new rule to be created, (2) An existing rule needs modification, (3) The user asks to remember certain behaviors or patterns, or (4) Future behavior changes are…
Cursor rule Cursor
Apply when executing unit tests and reporting the results, especially when failures occur. Mandates running all new and existing project tests together and requires reporting every failed test using a specific structured format before proceeding with fixes.
Cursor rule Cursor
This rule mandates the use of the Jest testing framework for all unit tests in TypeScript CLI projects. Apply this rule when creating new tests, configuring the testing environment, or reviewing existing test suites to ensure consistency and leverage Jest's features.
Cursor rule Cursor
This rule mandates that the initial phase of writing unit tests for a feature should focus exclusively on the core 'happy path' functionality. Apply this rule when starting test development for new code or features. Edge cases and error handling tests should be deferred unless specifically requested.
Cursor rule Cursor
Apply when designing or refactoring CLI command implementations or writing unit tests for them. Promotes separating the core business logic of a command from I/O operations (argument parsing, console output, file system access, network requests) to enhance testability. Encourages testing the isolated logic functions…
Cursor rule Cursor
Apply when writing unit tests that involve functions or modules with side effects (e.g., file system access, network requests, database interactions, timers, complex dependencies). Guides the use of test doubles like mocks, spies, and stubs (using frameworks like Jest) to isolate the unit under test and control its…
Cursor rule Cursor
Apply when setting up, organizing, or adding unit tests to a project, particularly TypeScript projects using Jest. Guides towards placing test files logically alongside source code (e.g., tests/ or .test.ts), mirroring the source directory structure, and correctly configuring the test runner (e.g., jest.config.js) for…
Cursor rule Cursor
Apply when writing individual unit test cases, especially during initial feature development. Enforces the Arrange-Act-Assert pattern, mandates focusing only on the core happy path functionality initially, and requires keeping tests small, focused, fast, and independent. Defers edge case and error handling tests…