ReddRadar
Topic: orchestration
1,040 skills in this topic.
-
design-system-patterns
Build scalable design systems with design tokens, theming infrastructure, and component architecture patterns. Use when creating design tokens, implementing theme switching, building component libraries, or establishing design system foundations.
wshobson/agents 32,911
-
interaction-design
Design and implement microinteractions, motion design, transitions, and user feedback patterns. Use when adding polish to UI interactions, implementing loading states, or creating delightful user experiences.
wshobson/agents 32,911
-
mobile-android-design
Master Material Design 3 and Jetpack Compose patterns for building native Android apps. Use when designing Android interfaces, implementing Compose UI, or following Google's Material Design guidelines.
wshobson/agents 32,911
-
mobile-ios-design
Master iOS Human Interface Guidelines and SwiftUI patterns for building native iOS apps. Use when designing iOS interfaces, implementing SwiftUI views, or ensuring apps follow Apple's design principles.
wshobson/agents 32,911
-
react-native-design
Master React Native styling, navigation, and Reanimated animations for cross-platform mobile development. Use when building React Native apps, implementing navigation patterns, or creating performant animations.
wshobson/agents 32,911
-
responsive-design
Implement modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first breakpoint strategies. Use when building adaptive interfaces, implementing fluid layouts, or creating component-level responsive behavior.
wshobson/agents 32,911
-
visual-design-foundations
Apply typography, color theory, spacing systems, and iconography principles to create cohesive visual designs. Use when establishing design tokens, building style guides, or improving visual hierarchy and consistency.
wshobson/agents 32,911
-
web-component-design
Master React, Vue, and Svelte component patterns including CSS-in-JS, composition strategies, and reusable component architecture. Use when building UI component libraries, designing component APIs, or implementing frontend design systems.
wshobson/agents 32,911
-
maestro:debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
ReinaMacCredy/maestro 26
-
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.
ReinaMacCredy/maestro 26
-
maestro:status
Interpret feature progress, detect problems, and recommend next actions based on maestro status output.
ReinaMacCredy/maestro 26
-
maestro:agents-md
Use when bootstrapping, updating, or reviewing AGENTS.md — teaches what makes effective agent memory, how to structure sections, signal vs noise filtering, and when to prune stale entries
ReinaMacCredy/maestro 26
-
maestro:brainstorming
Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
ReinaMacCredy/maestro 26
-
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 a standard feature but far richer. Use for multi-component systems, regulated domains, or unclear requirements.
ReinaMacCredy/maestro 26
-
maestro:dispatching
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
ReinaMacCredy/maestro 26
-
maestro:docker
Use when working with Docker containers — debugging container failures, writing Dockerfiles, docker-compose for integration tests, image optimization, or deploying containerized applications
ReinaMacCredy/maestro 26
-
maestro:implement
Execute feature tasks following TDD workflow. Single-agent by default, --team for parallel Agent Teams, Sub Agent Parallels. Use when ready to implement a planned feature.
ReinaMacCredy/maestro 26
-
maestro:new-feature
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.
ReinaMacCredy/maestro 26
-
maestro:next-move
Strategic analysis of a project to identify the single highest-leverage, most innovative addition. Use when the user asks what to build next, what the most impactful improvement would be, what's missing, or any question about strategic direction and priorities. Also use when stuck choosing between competing features.
ReinaMacCredy/maestro 26
-
maestro:plan-review-loop
Deep-review any plan (maestro, Codex, Claude Code plan mode, or plain markdown) using iterative subagent review loops with BMAD-inspired adversarial edge-case discovery. Spawns reviewer subagents that find issues using pre-mortem, inversion, and red-team techniques, auto-fixes them with structured fix strategies, and re-reviews until the plan passes with zero actionable issues. Use when the user says 'review the plan', 'deep review', 'check the plan thoroughly', 'review loop', 'validate before approving', or wants rigorous plan validation before execution. Also use proactively before plan-approve when the plan is complex or high-risk.
ReinaMacCredy/maestro 26
-
maestro:prompt-leverage
Strengthen a raw user prompt into an execution-ready instruction set for Claude Code, Amp, Codex, or another AI agent. Use when the user wants to improve an existing prompt, build a reusable prompting framework, wrap the current request with better structure, add clearer tool rules, or create a hook that upgrades prompts before execution.
ReinaMacCredy/maestro 26
-
maestro:revert
Git-aware revert of feature, phase, or individual task. Safely undoes implementation with task state rollback.
ReinaMacCredy/maestro 26
-
maestro:review
Code review for a feature against its spec and plan. Verifies implementation matches requirements, checks code quality and security.
ReinaMacCredy/maestro 26
-
maestro:simplify
Review changed code for reuse, quality, and efficiency, then fix issues found. Use after implementing a task or feature -- catches duplication, hacky patterns, and wasted work before review.
ReinaMacCredy/maestro 26