maestro:cpp-coding-standards
C++ coding standards based on C++ Core Guidelines for modern, safe, idiomatic C++. Use during maestro:implement for C++ code quality and maestro:review for C++ review criteria.
maestro:cost-aware-llm-pipeline
Cost optimization for LLM API usage with model routing, budget tracking, retry logic, and prompt caching. Use during maestro:implement when building LLM-powered features.
maestro:continuous-learning
Auto-extract reusable patterns from Claude Code sessions as learned skills. Use across all maestro phases to capture and reuse session learnings.
maestro:content-hash-cache-pattern
SHA-256 content hash caching for expensive file processing. Use during maestro:implement when adding caching layers with path-independent, auto-invalidating cache keys.
maestro:content-engine
Multi-platform content creation for X, LinkedIn, TikTok, YouTube, and newsletters. Use in any maestro phase when producing social media content or marketing materials.
maestro:python-patterns
Pythonic idioms, PEP 8 standards, type hints, and best practices for Python applications. Use during maestro:implement when writing Python code -- naming, structure, and idiomatic patterns.
maestro:search-first
Research-before-coding workflow. Use during maestro:design to find existing tools, libraries, and patterns before writing custom code.
maestro:python-testing
Python testing with pytest, TDD methodology, fixtures, mocking, and parametrization. Use during maestro:implement when writing Python tests following TDD.
maestro:skill-stocktake
Audit Claude skills and commands for quality with Quick Scan or Full Stocktake modes. Use during maestro:review to assess skill quality and consistency.
maestro:strategic-compact
Strategic context compaction for long sessions. Use during maestro:design for multi-phase sessions approaching context limits, suggesting /compact at logical breakpoints.
maestro-status
Show track progress overview with phase/task completion stats, next actions, and blockers.
maestro-setup
Scaffolds project context (product, tech stack, coding guidelines, product guidelines, workflow) and initializes track registry. Use for first-time project onboarding.
maestro-review
Code review for a track against its spec and plan. Verifies implementation matches requirements, checks code quality and security.
maestro-revert
Git-aware revert of track, phase, or individual task. Safely undoes implementation with plan state rollback.
maestro-note
Capture decisions, constraints, and context to persistent notepad. Priority notes are injected into every session and implementation run.
maestro-new-track
Create a new feature/bug track with spec and implementation plan. Interactive interview generates requirements spec, then phased TDD plan. Use when starting work on a new feature, bug fix, or chore.
maestro:swift-actor-persistence
Thread-safe data persistence using Swift actors with in-memory cache and file-backed storage. Use during maestro:implement when building persistence layers in Swift.
maestro-design
Deep discovery and specification for ambitious features. Full BMAD-inspired interview with classification, vision, journeys, domain analysis, and FR synthesis. Same output contract (spec.md + plan.md) as new-track but far richer. Use for multi-component systems, regulated domains, or unclear requirements.
init
Generates AGENTS.md and CLAUDE.md files using the WHAT/WHY/HOW framework. Explores the codebase and produces minimal (<100 line) context files with progressive disclosure.
maestro:visa-doc-translate
Translate visa application documents (images) to English and create bilingual PDFs. Use in any maestro phase when translating documents for visa applications.
maestro:verification-loop
Comprehensive post-change verification system with build, test, lint, and quality gates. Use during maestro:review as the core verification workflow before PRs or releases.
maestro:tdd-workflow
Test-driven development workflow enforcing Red-Green-Refactor with 80%+ coverage. Use during maestro:implement as the core TDD methodology for all code changes.
maestro:swiftui-patterns
SwiftUI architecture with @Observable state management, view composition, navigation, and performance optimization. Use during maestro:implement when building SwiftUI views and features.
maestro:swift-protocol-di-testing
Protocol-based dependency injection for testable Swift code with mock strategies and Swift Testing. Use during maestro:implement when writing testable Swift with DI.
maestro-implement
Execute track tasks following TDD workflow. Single-agent by default, --team for parallel Agent Teams, Sub Agent Parallels. Use when ready to implement a planned track.
maestro:swift-concurrency-6-2
Swift 6.2 Approachable Concurrency with single-threaded default, @concurrent offloading, and isolated conformances. Use during maestro:implement when writing async Swift code.
maestro:springboot-verification
Verification loop for Spring Boot: build, static analysis, tests with coverage, security scans, and diff review. Use during maestro:review before Spring Boot releases or PRs.
maestro:article-writing
Long-form content writing for articles, guides, blog posts, and tutorials with distinctive voice. Use in any maestro phase when producing written content longer than a paragraph.
maestro:autonomous-loops
Patterns for autonomous Claude Code loops from simple pipelines to multi-agent DAG systems. Use during maestro:design when architecting automated workflows or multi-agent orchestration.
maestro:backend-patterns
Backend architecture patterns for Node.js, Express, and Next.js API routes. Use during maestro:implement when building server-side code, API routes, or backend services.
maestro:clickhouse-io
ClickHouse query optimization, analytics patterns, and data engineering for high-performance analytical workloads. Use during maestro:implement when building analytics queries or data pipelines with ClickHouse.
maestro:coding-standards
TypeScript/JavaScript/React/Node.js coding standards and best practices. Use during maestro:implement for code quality and maestro:review for review criteria on TS/JS projects.
maestro:configure-ecc
Interactive installer for Everything Claude Code skills and rules. Use during maestro:setup or project initialization to install and configure ECC skills.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
maestro:api-design
REST API design patterns for resource naming, status codes, pagination, error responses, and versioning. Use during maestro:design when specifying API contracts, and maestro:implement when building endpoints.
laravel-api-resource-patterns
Best practices for Laravel API Resources including resource transformation, collection handling, conditional attributes, and relationship loading.
laravel-authorization-patterns
Best practices for Laravel authorization including Gates, Policies, middleware auth, and Blade directives for access control.
laravel-blade-component-patterns
Best practices for Laravel Blade components including class-based and anonymous components, slots, attribute bags, and reusable UI patterns.
laravel-brainstorming
Use when creating or developing Laravel features, before writing code or implementation plans - refines rough ideas into fully-formed Laravel designs through collaborative questioning, alternative exploration, and incremental validation.
eloquent-best-practices
Best practices for Laravel Eloquent ORM including query optimization, relationship management, and avoiding common pitfalls like N+1 queries.
laravel-validation-patterns
Best practices for Laravel validation including Form Requests, custom rules, conditional validation, and input sanitization.
laravel-systematic-debugging
Systematic debugging process for Laravel applications - ensures root cause investigation before attempting fixes. Use for any Laravel issue (test failures, bugs, unexpected behavior, performance problems).
laravel-event-driven-architecture
Best practices for Laravel events and listeners including event discovery, queued listeners, subscribers, and model events for decoupled architecture.
laravel-tdd
Test-Driven Development specifically for Laravel applications using Pest PHP. Use when implementing any Laravel feature or bugfix - write the test first, watch it fail, write minimal code to pass.
laravel-feature-flags
Best practices for Laravel Pennant feature flags including defining features, checking activation, scoping, rich values for A/B testing, and gradual rollouts.
laravel-queue-patterns
Best practices for Laravel queues including job structure, batching, chaining, middleware, retry strategies, and error handling.
laravel-notification-patterns
Best practices for Laravel notifications including multi-channel delivery, mail and database notifications, queueing, and on-demand recipients.
laravel-middleware-patterns
Best practices for Laravel middleware including before/after patterns, terminable middleware, groups, parameters, and common middleware implementations.
laravel-caching-strategies
Best practices for Laravel caching including cache patterns, tags, atomic locks, flexible cache, and cache invalidation strategies.
laravel-task-scheduling
Best practices for Laravel task scheduling including defining schedules, frequency constraints, overlap prevention, and monitoring hooks.
Page 935 of 1698 · 84852 results
