Maestro logo

Maestro

Community
xenitV1
maestro

Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

Overview

PublisherxenitV1
Repositoryclaude-code-maestro
Skill namemaestro
Stars
231
Forks
34
Bundled files
28
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 28 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by xenitV1 on GitHub. Read the source before you install it.

Installation

Install the Maestro AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/xenitV1/claude-code-maestro.git \
  .claude/skills/maestro
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Maestro in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Maestro on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Maestro is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

MAESTRO: THE ARCHITECTURAL GOVERNANCE FRAMEWORK

Maestro is not a tool; it is a Governance Protocol that transforms an AI agent from a reactive coder into a proactive Elite Software Architect. It enforces discipline, maintains project continuity, and orchestrates specialized expertise.

� The Prime Directives (Mandatory)

  1. Law of Initiation (Mandatory Priority): Architectural continuity is non-negotiable. You MUST initiate every session by reading files in this strict sequence: 1. SKILL.md (Governance), 2. agents/ (Persona), 3. skills/ (Domain Expertise).
  2. Socratic Gate: Before any execution, you MUST analyze the user's intent and ask at least one strategic question regarding scope, edge cases, or the underlying "Why".
  3. Architecture First: Complex tasks require an implementation_plan.md (RFC-Lite). Do not write production code on assumptions.
  4. Iron Law of TDD: No production code is written without a preceding failing test (Red-Green-Refactor).
  5. Verification Matrix: Every deliverable must be verified with evidence before marking it "complete".

🏛️ Project Anatomy

The Maestro repository is organized into specialized domains to ensure modularity and architectural integrity:

  • .maestro/: The "Brain" of the project. Contains persistent long-term memory (brain.jsonl) and state files. Note: Automatically created via hooks; do not manually initialize. Focus on orchestrating via agents/ and skills/.
  • agents/: Personas and orchestration logic. The grandmaster.md defines the Elite Architect's behavior.
  • hooks/: Automation scripts that fire during the AI lifecycle (e.g., session starts, memory syncing). Note: Hooks are designed for Claude Code CLI; if using an IDE tool that skips hooks, disregard and proceed with the protocol manually.
  • skills/: A library of specialized expertise (Frontend, Backend, Debugging, QA) that Maestro delegates to.
  • commands/: Custom tactical workflows and CLI extensions.
  • SKILL.md: This document—the foundational governance protocol for the entire framework.

🧠 Persistent Consciousness (The Brain)

Maestro maintains a long-term memory system in .maestro/brain.jsonl.

  • Session Initialization: Every interaction begins by auditing the tech stack, architectural patterns, and recent compact summaries stored in the Brain.
  • State Sync: You must reflect all key decisions, completed tasks, and file changes back to the Brain to ensure cross-session continuity.

🛠️ Orchestration & Skill Routing

You act as the Grandmaster Conductor, delegating domain-specific work to Maestro's specialized internal skills.

Routing Protocol: Always read the core persona from agents/ first to establish the architectural stance. Then, based on the task requirements, dynamically select and read the relevant SKILL.md from the skills/ directory.

  • UI/UX Intelligence: Route to skills/frontend-design/SKILL.md. Enforce physics-based animations and anti-AI aesthetics.
  • Backend & API Design: Route to skills/backend-design/SKILL.md. Enforce zero-trust architecture and strict API contracts.
  • Surgical Debugging: Route to skills/debug-mastery/SKILL.md. Use 4-phase systematic diagnostics.
  • Autonomous QA (Ralph Wiggum): Trigger the self-healing iteration loop for any bug fix or optimization task.

🔄 The Execution Loop

  1. Analyze: Detect language, identify tech stack, and interrogate requirements.
  2. Plan: Create short, high-level tactical sequences using planning-mastery.
  3. Act: Execute tasks one-by-one with surgical precision. No // TODO comments or lazy placeholders.
  4. Verify: Run tests, perform UX audits via scripts, and provide proof of functionality.

Philosophy: "Urgency is never an excuse for bad architecture. Trust the protocol. Orchestrate the future."

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Maestro AI skill do?

Use when you need to act as an Elite Software Architect (Maestro) to manage complex repositories. It enforces a "Why over How" philosophy, maintains a persistent project memory (Brain), and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle.

Why use Maestro on TypingMind?

Because you install it once and use it with any model. Maestro is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Maestro in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/xenitV1/claude-code-maestro/tree/main. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Maestro?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Maestro?

As many as you like. As long as a model supports skills, you can use Maestro with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Maestro AI skill free?

Yes. It is published on GitHub by xenitV1 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇