azrole 3.0.0

package/templates/commands/dream.md

@@ -0,0 +1,13 @@
+I want to build a project. Here's my idea:
+
+$ARGUMENTS
+
+Orchestrator — analyze this project idea, detect the tech stack, scan my current
+environment level (0-10), then build everything I need progressively:
+CLAUDE.md, MCP config, skills, commands, memory system, and specialized dev agents.
+
+Show me progress at each level and what was created when done.
+
+If the project idea above is blank or empty, ask me: "What do you want to build? Give me your idea and the technologies you want to use."
+
+If no tech stack was mentioned above, ask me ONE question: "What technologies do you want to use?"

package/templates/commands/evolve.md

@@ -0,0 +1,3 @@
+Use the orchestrator agent to run an evolution cycle on my development environment.
+Find gaps in my agents, skills, commands, and memory. Fix what's weak.
+Show me the before/after score.

package/templates/commands/explain.md

@@ -0,0 +1,13 @@
+Explain this to me like I'm not a developer:
+
+$ARGUMENTS
+
+Rules:
+- Use simple, everyday language — no jargon
+- If I pasted code, explain what it does step by step
+- If I pasted an error, explain what went wrong and how to fix it
+- If I named a file or folder, read it and explain what it's for
+- If I asked a concept question, explain it with an analogy
+- Keep it short — 2-3 paragraphs max unless I ask for more detail
+
+If nothing was provided above, ask: "What would you like me to explain? You can paste code, an error message, a file name, or ask about any concept."

package/templates/commands/fix.md

@@ -0,0 +1,15 @@
+Something is broken. Here's what I see:
+
+$ARGUMENTS
+
+Find the bug, fix it, and explain what went wrong in plain English.
+
+Steps:
+1. Read the error message or description above
+2. Search the codebase for the relevant files
+3. Identify the root cause
+4. Fix it
+5. Verify the fix works (run the app/tests if possible)
+6. Explain what happened and what you changed — assume I'm not a developer
+
+If no error or description was provided above, ask: "What's going wrong? Paste the error or describe what you expected to happen."

package/templates/commands/level-up.md

@@ -0,0 +1,3 @@
+Use the orchestrator agent to scan my current Claude Code environment.
+Show me what level I'm at (0-10), what I have, what I'm missing.
+Then offer to build the next level for me.

package/templates/commands/setup.md

@@ -0,0 +1,26 @@
+Scan my existing project and build the AI coding environment for it.
+
+Orchestrator — this is an EXISTING project with code already written. Do NOT ask what I want to build. Instead:
+
+1. Scan the current directory thoroughly:
+   - Read package.json, pyproject.toml, requirements.txt, Cargo.toml, go.mod, etc.
+   - Look at the directory structure to understand the architecture
+   - Read any existing project rules file (CLAUDE.md, AGENTS.md, GEMINI.md, .cursorrules)
+   - Check for existing config dirs (.claude/, .gemini/, .opencode/, .codex/, .cursor/)
+   - Identify the tech stack, frameworks, and patterns from actual code
+
+2. Run the environment scanner to detect my current level (0-10)
+
+3. Build everything I'm missing up to Level 5:
+   - Project rules file based on what actually exists in the codebase
+   - MCP servers for the detected technologies
+   - Skills based on the actual patterns found in the code
+   - Memory system with a real codebase map
+   - Specialized agents matched to the actual directory structure
+
+4. Show me what was detected and what was built
+
+If $ARGUMENTS is provided, use it as additional context about the project.
+Otherwise, figure everything out from the code.
+
+$ARGUMENTS

package/templates/commands/ship.md

@@ -0,0 +1,14 @@
+Save my work and push it to GitHub.
+
+Steps:
+1. Run `git status` to see what changed
+2. If this isn't a git repo yet, run `git init` and create an initial commit
+3. Stage all changed files (but NEVER stage .env, credentials, secrets, or API keys)
+4. Generate a clear commit message describing what changed
+5. Commit the changes
+6. If a remote is set up, push to the current branch
+7. If no remote exists, tell me how to connect to GitHub
+
+Show me a summary of what was shipped.
+
+If there are no changes to ship, say: "Nothing to ship — your code is already up to date."

package/templates/commands/status.md

@@ -0,0 +1,14 @@
+Give me a quick overview of my project right now.
+
+Check and report:
+1. **Project health** — does the app run? Any obvious errors?
+   - Try to detect the start command (package.json scripts, pyproject.toml, Makefile, etc.)
+   - Check for common issues (missing dependencies, env vars, config files)
+
+2. **What's changed** — run `git status` and `git diff --stat` to show recent changes
+
+3. **Current level** — if .devteam/blueprint.json exists, scan the Claude Code environment level (0-10)
+
+4. **Next steps** — based on what you see, suggest 2-3 things I could work on next
+
+Keep the output short and visual. Use checkmarks and X marks. No walls of text.