Elite Software Architect governance framework that enforces architectural discipline, persistent project memory, and specialized skill orchestration.
Works with
Mandatory initialization protocol reads governance files ( SKILL.md ), personas ( agents/ ), and domain expertise ( skills/ ) in strict sequence to maintain architectural continuity across sessions
Persistent \"Brain\" system in .maestro/brain.jsonl stores long-term memory, tech stack audits, and decision history to enable cross-session pr
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmaestroExecute the skills CLI command in your project's root directory to begin installation:
Fetches maestro from xenitv1/claude-code-maestro and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate maestro. Access via /maestro in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
206
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
206
stars
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.
SKILL.md (Governance), 2. agents/ (Persona), 3. skills/ (Domain Expertise).implementation_plan.md (RFC-Lite). Do not write production code on assumptions.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.Maestro maintains a long-term memory system in .maestro/brain.jsonl.
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.
skills/frontend-design/SKILL.md. Enforce physics-based animations and anti-AI aesthetics.skills/backend-design/SKILL.md. Enforce zero-trust architecture and strict API contracts.skills/debug-mastery/SKILL.md. Use 4-phase systematic diagnostics.planning-mastery.// TODO comments or lazy placeholders.Philosophy: "Urgency is never an excuse for bad architecture. Trust the protocol. Orchestrate the future."
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
Registry listing for maestro matched our evaluation — installs cleanly and behaves as described in the markdown.
maestro reduced setup friction for our internal harness; good balance of opinion and flexibility.
maestro reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in maestro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend maestro for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend maestro for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in maestro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in maestro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend maestro for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
maestro fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 38