القائمة
Maestro spec-driven development for Claude Code. Load this skill when invoking Maestro commands so workflows stay aligned with LeIndex and the Rust TUI.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Maestro spec-driven development for Gemini CLI. Load this skill when invoking Maestro commands so workflows stay aligned with LeIndex and the Rust TUI.
Maestro spec-driven development for Amp CLI. Load this skill when invoking Maestro commands so workflows stay aligned with LeIndex and the Rust TUI.
Show users how Maestro works - the opinionated setup with hooks, memory, and coordination
Full 5-layer analysis of a specific function for debugging or deep understanding
Get a token-efficient overview of any project using the TLDR stack
Maps questions to the optimal LeIndex command
| name | maestro |
| description | Maestro spec-driven development for Claude Code. Load this skill when invoking Maestro commands so workflows stay aligned with LeIndex and the Rust TUI. |
Use this skill whenever you run Maestro inside Claude Code. Keep it native to Claude Code and the Agent Skills standard.
/maestro, /maestro:setup, /maestro:newTrack, /maestro:implement, /maestro:orchestrate, /maestro:status, /maestro:revert, /maestro:leindex, /maestro:tui.~/.claude/skills/maestro/ (installed by the Maestro wizard).claude.mcpServers.leindex → { "command": "leindex", "args": ["mcp"], "type": "stdio" } so Claude Code reaches the standalone LeIndex binary directly. Do not point to any TLDR/legacy endpoints.~/.config/gemini, ~/.amp, or OpenCode paths./maestro setup — initialize/refresh product, tech stack, workflow, track registry./maestro newTrack "<goal>" — generate spec + plan with clarifying questions./maestro implement <track> — execute plan with LeIndex 5-phase analysis for scoped file access./maestro orchestrate — cockpit/orchestrator panel (Rust TUI pane)./maestro status — report progress and blockers.