Agent Zero AI framework
remove frameworks
3clyp50f9545bf860f5
diff --git a/prompts/agent.system.framework.md b/prompts/agent.system.framework.mddeleted file mode 100644index 0cf7ec79b..000000000--- a/prompts/agent.system.framework.md+++ /dev/null@@ -1,16 +0,0 @@-# Active Framework: {{framework_name}}--{{framework_description}}--## Workflow Steps-Follow this structured workflow when working on development tasks:--{{workflow_steps}}--## Framework Usage Guidelines-- Use the `skills_tool` to load framework-specific skills when starting each workflow phase-- Skills with the `{{framework_prefix}}-` prefix are designed for this framework-- Guide the user through the appropriate workflow step based on where they are in the development process-- When the user asks to start a new feature or project, begin with step 1 of the workflow-- Provide clear transitions between workflow phases-- Reference the relevant skill for detailed instructions on each phasediff --git a/python/api/frameworks.py b/python/api/frameworks.pydeleted file mode 100644index 9ee735d89..000000000--- a/python/api/frameworks.py+++ /dev/null@@ -1,33 +0,0 @@-from dataclasses import asdict-from python.helpers.api import ApiHandler, Input, Output, Request-from python.helpers import frameworks---class Frameworks(ApiHandler):- """API handler for framework operations."""-- async def process(self, input: Input, request: Request) -> Output:- action = input.get("action", "list")- try:- if action == "list":- return {"ok": True, "data": self.list_frameworks()}- if action == "get":- framework_id = input.get("id", "")- data = self.get_framework(framework_id)- if data is None:- return {"ok": False, "error": "Framework not found"}- return {"ok": True, "data": data}- return {"ok": False, "error": "Invalid action"}- except Exception:- return {"ok": False, "error": "Internal error"}-- def list_frameworks(self) -> list[dict]:- """List all available frameworks."""- return [asdict(fw) for fw in frameworks.list_frameworks()]-- def get_framework(self, framework_id: str) -> dict | None:- """Get a specific framework by ID."""- fw = frameworks.get_framework(framework_id)- if fw is None:- return None- return asdict(fw)diff --git a/python/extensions/message_loop_prompts_after/_55_recall_skills.py b/python/extensions/message_loop_prompts_after/_55_recall_skills.pyindex 370fdadf2..89be65e89 100644--- a/python/extensions/message_loop_prompts_after/_55_recall_skills.py+++ b/python/extensions/message_loop_prompts_after/_55_recall_skills.py@@ -1,7 +1,7 @@from python.helpers.extension import Extensionfrom agent import LoopDatafrom python.helpers import skills as skills_helper-from python.helpers import projects, frameworks+from python.helpers import projectsclass RecallSkills(Extension):@@ -24,20 +24,17 @@ class RecallSkills(Extension):if not user_instruction or len(user_instruction) < 8:return- # Get active project + framework for scoped discovery+ # Get active project for scoped discoveryproject_name = (projects.get_context_project_name(self.agent.context)if self.agent.contextelse None)- framework = frameworks.get_active_framework(self.agent.context)- framework_id = framework.id if framework else Nonematches = skills_helper.search_skills(user_instruction,limit=6,project_name=project_name,- framework_id=framework_id,)if not matches:returndiff --git a/python/extensions/system_prompt/_10_system_prompt.py b/python/extensions/system_prompt/_10_system_prompt.pyindex 7dc2b2619..fc5c109d9 100644--- a/python/extensions/system_prompt/_10_system_prompt.py+++ b/python/extensions/system_prompt/_10_system_prompt.py@@ -3,7 +3,7 @@ from python.helpers.extension import Extensionfrom python.helpers.mcp_handler import MCPConfigfrom agent import Agent, LoopDatafrom python.helpers.settings import get_settings-from python.helpers import projects, frameworks+from python.helpers import projectsclass SystemPrompt(Extension):@@ -20,7 +20,6 @@ class SystemPrompt(Extension):mcp_tools = get_mcp_tools_prompt(self.agent)secrets_prompt = get_secrets_prompt(self.agent)project_prompt = get_project_prompt(self.agent)- framework_prompt = get_framework_prompt(self.agent)system_prompt.append(main)system_prompt.append(tools)@@ -30,8 +29,6 @@ class SystemPrompt(Extension):system_prompt.append(secrets_prompt)if project_prompt:system_prompt.append(project_prompt)- if framework_prompt:- system_prompt.append(framework_prompt)def get_main_prompt(agent: Agent):@@ -85,26 +82,3 @@ def get_project_prompt(agent: Agent):return result-def get_framework_prompt(agent: Agent):- """- Get the active framework prompt if one is selected.-- Returns empty string if no framework is active (framework_id == "none").- """- framework = frameworks.get_active_framework(agent.context)- if not framework:- return ""-- # Build workflow steps description- workflow_steps = "\n".join([- f"{w.sequence}. **{w.name}** (`{w.skill_name}`): {w.description}"- for w in framework.workflows- ])-- return agent.read_prompt(- "agent.system.framework.md",- framework_name=framework.name,- framework_description=framework.description,- framework_prefix=framework.skill_prefix,- workflow_steps=workflow_steps,- )diff --git a/python/helpers/frameworks.py b/python/helpers/frameworks.pydeleted file mode 100644index a6e53cafa..000000000--- a/python/helpers/frameworks.py+++ /dev/null@@ -1,623 +0,0 @@-"""-Framework Registry for Agent Zero.--This module defines the available frameworks that can be used-to guide agent workflows. Each framework provides structured methodologies-for software development tasks.--Frameworks are selected globally in settings or overridden per-project.-When a framework is active, its skills are prioritized in skill discovery-and framework context is injected into the system prompt.-"""--from __future__ import annotations--from dataclasses import dataclass, field-from typing import TYPE_CHECKING, List, Literal, Optional--if TYPE_CHECKING:- from agent import AgentContext--# Supported framework identifiers-FrameworkId = Literal[- "none",- "gsd",- "superpowers",- "bmad",- "bmad-builder",- "bmad-cis",- "bmad-gds",- "speckit",- "prp",- "agentos",- "amplihack",- "agent-zero-dev",-]--ALL_FRAMEWORK_IDS: List[str] = [- "none",- "gsd",- "superpowers",- "bmad",- "bmad-builder",- "bmad-cis",- "bmad-gds",- "speckit",- "prp",- "agentos",- "amplihack",- "agent-zero-dev",-]---@dataclass(slots=True)-class FrameworkWorkflow:- """A single workflow step within a framework."""-- name: str # e.g., "plan-phase"- skill_name: str # Maps to SKILL.md name, e.g., "gsd-plan-phase"- description: str- sequence: int # Order in workflow (1-based)---@dataclass(slots=True)-class Framework:- """A framework definition."""-- id: FrameworkId- name: str # Display name- description: str- skill_prefix: str # Namespace for skills, e.g., "gsd", "bmad"- workflows: List[FrameworkWorkflow] = field(default_factory=list)---# ─────────────────────────────────────────────────────────────────────────────-# Framework Registry-# ─────────────────────────────────────────────────────────────────────────────--FRAMEWORK_REGISTRY: dict[str, Framework] = {- "none": Framework(- id="none",- name="None",- description="No framework. Agent operates with standard skills only.",- skill_prefix="",- workflows=[],- ),- "gsd": Framework(- id="gsd",- name="GSD (Get Stuff Done)",- description="A structured methodology emphasizing planning before implementation. Features clear phases: project setup, discussion, planning, execution, verification, and milestone completion.",- skill_prefix="gsd",- workflows=[- FrameworkWorkflow(- name="New Project",- skill_name="gsd-new-project",- description="Initialize project structure, requirements, and roadmap",- sequence=1,- ),- FrameworkWorkflow(- name="Discuss Phase",- skill_name="gsd-discuss-phase",- description="Capture implementation decisions and preferences before planning",- sequence=2,- ),- FrameworkWorkflow(- name="Plan Phase",- skill_name="gsd-plan-phase",- description="Research, create atomic task plans, and verify against requirements",- sequence=3,- ),- FrameworkWorkflow(- name="Execute Phase",- skill_name="gsd-execute-phase",- description="Run plans in parallel waves with fresh context per task",- sequence=4,- ),- FrameworkWorkflow(- name="Verify Work",- skill_name="gsd-verify-work",- description="Manual user acceptance testing with automatic fix generation",- sequence=5,- ),- FrameworkWorkflow(- name="Complete Milestone",- skill_name="gsd-complete-milestone",- description="Archive milestone, tag release, prepare for next iteration",- sequence=6,- ),- ],- ),- "superpowers": Framework(- id="superpowers",- name="Superpowers",- description="A comprehensive development workflow framework for Claude Code. Emphasizes TDD, brainstorming, planning, subagent execution, code review, and proper branch management.",- skill_prefix="sp",- workflows=[- FrameworkWorkflow(- name="Brainstorming",- skill_name="sp-brainstorming",- description="Socratic design refinement before writing code",- sequence=1,- ),- FrameworkWorkflow(- name="Git Worktrees",- skill_name="sp-git-worktrees",- description="Create isolated workspace on new branch for development",- sequence=2,- ),- FrameworkWorkflow(- name="Writing Plans",- skill_name="sp-writing-plans",- description="Break work into bite-sized tasks (2-5 min each) with verification",- sequence=3,- ),- FrameworkWorkflow(- name="Test-Driven Development",- skill_name="sp-test-driven-development",- description="RED-GREEN-REFACTOR: test first, minimal code, commit",- sequence=4,- ),- FrameworkWorkflow(- name="Executing Plans",- skill_name="sp-executing-plans",- description="Dispatch subagents per task with two-stage review",- sequence=5,- ),- FrameworkWorkflow(- name="Code Review",- skill_name="sp-code-review",- description="Review against plan, report issues by severity",- sequence=6,- ),- FrameworkWorkflow(- name="Finishing Branch",- skill_name="sp-finishing-branch",- description="Verify tests, merge/PR options, cleanup worktree",- sequence=7,- ),- ],- ),- "bmad": Framework(- id="bmad",- name="BMAD (Business-Minded Agile Development)",- description="A business-focused agile methodology with 21 specialized agents. Features two paths: Quick (spec→dev→review) for small tasks, Full (brief→PRD→arch→epics→sprint→stories) for complex projects.",- skill_prefix="bmad",- workflows=[- FrameworkWorkflow(- name="Quick Spec",- skill_name="bmad-quick-spec",- description="(Quick Path) Analyze codebase and produce tech-spec with stories",- sequence=1,- ),- FrameworkWorkflow(- name="Product Brief",- skill_name="bmad-product-brief",- description="(Full Path) Define problem, users, and MVP scope",- sequence=2,- ),- FrameworkWorkflow(- name="Create PRD",- skill_name="bmad-create-prd",- description="Full requirements with personas, metrics, and risks",- sequence=3,- ),- FrameworkWorkflow(- name="Architecture",- skill_name="bmad-create-architecture",- description="Technical decisions and system design",- sequence=4,- ),- FrameworkWorkflow(- name="Create Epics",- skill_name="bmad-create-epics",- description="Break work into prioritized epics and stories",- sequence=5,- ),- FrameworkWorkflow(- name="Sprint Planning",- skill_name="bmad-sprint-planning",- description="Initialize sprint tracking and story selection",- sequence=6,- ),- FrameworkWorkflow(- name="Developer Story",- skill_name="bmad-dev-story",- description="Implement individual stories with guidance",- sequence=7,- ),- FrameworkWorkflow(- name="Code Review",- skill_name="bmad-code-review",- description="Validate quality and completeness",- sequence=8,- ),- ],- ),- "bmad-builder": Framework(- id="bmad-builder",- name="BMad Builder",- description="Meta-module for creating custom BMad agents, workflows, and domain-specific modules. Build specialized AI agents with custom expertise, structured workflows, and shareable module packages.",- skill_prefix="bmb",- workflows=[- FrameworkWorkflow(- name="Build Agent",- skill_name="bmb-agent",- description="Create specialized AI agents with custom expertise and tools",- sequence=1,- ),- FrameworkWorkflow(- name="Build Workflow",- skill_name="bmb-workflow",- description="Design structured workflows with steps and cross-workflow communication",- sequence=2,- ),- FrameworkWorkflow(- name="Build Module",- skill_name="bmb-module",- description="Package agents and workflows into shareable BMad modules",- sequence=3,- ),- ],- ),- "bmad-cis": Framework(- id="bmad-cis",- name="BMad Creative Intelligence Suite",- description="Tools for the fuzzy front-end of development—where ideas are born, problems are reframed, and solutions emerge through structured creativity. Features innovation, design thinking, and brainstorming workflows.",- skill_prefix="cis",- workflows=[- FrameworkWorkflow(- name="Brainstorm",- skill_name="cis-brainstorm",- description="Generate ideas with structured techniques (SCAMPER, Reverse Brainstorming)",- sequence=1,- ),- FrameworkWorkflow(- name="Design Thinking",- skill_name="cis-design-thinking",- description="Human-centered design through empathy, ideation, and prototyping",- sequence=2,- ),- FrameworkWorkflow(- name="Problem Solve",- skill_name="cis-problem-solve",- description="Systematic problem diagnosis and root cause analysis",- sequence=3,- ),- FrameworkWorkflow(- name="Innovation",- skill_name="cis-innovation",- description="Business model innovation and disruption opportunity analysis",- sequence=4,- ),- FrameworkWorkflow(- name="Storytelling",- skill_name="cis-storytelling",- description="Craft compelling narratives for products and features",- sequence=5,- ),- FrameworkWorkflow(- name="Presentation",- skill_name="cis-presentation",- description="Structure and deliver persuasive presentations",- sequence=6,- ),- ],- ),- "bmad-gds": Framework(- id="bmad-gds",- name="BMad Game Dev Studio",- description="Six specialized game development agents: Game Designer (Samus Shepard), Game Architect (Cloud Dragonborn), Game Developer (Link Freeman), Game Scrum Master (Max), Game QA (GLaDOS), and Game Solo Dev (Indie). Two paths: Full (brief→GDD→arch→sprint→stories) for team projects, Quick Flow for solo/indie dev.",- skill_prefix="gds",- workflows=[- FrameworkWorkflow(- name="Brainstorm Game",- skill_name="gds-brainstorm-game",- description="Guided game ideation with Game Designer (Samus Shepard)",- sequence=1,- ),- FrameworkWorkflow(- name="Create Game Brief",- skill_name="gds-create-brief",- description="Define game vision, core loop, and target experience",- sequence=2,- ),- FrameworkWorkflow(- name="Create GDD",- skill_name="gds-create-gdd",- description="Full Game Design Document with mechanics and systems",- sequence=3,- ),- FrameworkWorkflow(- name="Game Architecture",- skill_name="gds-create-architecture",- description="Technical architecture with Game Architect (Cloud Dragonborn)",- sequence=4,- ),- FrameworkWorkflow(- name="Sprint Planning",- skill_name="gds-sprint-planning",- description="Plan sprints with Game Scrum Master (Max)",- sequence=5,- ),- FrameworkWorkflow(- name="Dev Story",- skill_name="gds-dev-story",- description="Implement stories with Game Developer (Link Freeman)",- sequence=6,- ),- FrameworkWorkflow(- name="QA Framework",- skill_name="gds-qa-framework",- description="Set up testing with Game QA (GLaDOS)",- sequence=7,- ),- FrameworkWorkflow(- name="Quick Flow",- skill_name="gds-quick-flow",- description="Solo dev fast path with Game Solo Dev (Indie)",- sequence=8,- ),- ],- ),- "speckit": Framework(- id="speckit",- name="Spec Kit",- description="A specification-driven approach emphasizing upfront clarity. Starts with constitution definition, progresses through specification, planning, task generation, and implementation.",- skill_prefix="speckit",- workflows=[- FrameworkWorkflow(- name="Constitution",- skill_name="speckit-constitution",- description="Define project principles and constraints",- sequence=1,- ),- FrameworkWorkflow(- name="Specify",- skill_name="speckit-specify",- description="Create detailed specifications",- sequence=2,- ),- FrameworkWorkflow(- name="Plan",- skill_name="speckit-plan",- description="Generate implementation roadmap from specs",- sequence=3,- ),- FrameworkWorkflow(- name="Tasks",- skill_name="speckit-tasks",- description="Break plan into actionable tasks",- sequence=4,- ),- FrameworkWorkflow(- name="Implement",- skill_name="speckit-implement",- description="Execute tasks following specifications",- sequence=5,- ),- ],- ),- "prp": Framework(- id="prp",- name="PRP (Prompt-Response Protocol)",- description="A lightweight two-phase methodology: generate comprehensive PRPs (prompts) for tasks, then execute them. Ideal for well-defined, repeatable tasks.",- skill_prefix="prp",- workflows=[- FrameworkWorkflow(- name="Generate PRP",- skill_name="prp-generate",- description="Create detailed prompt specification for task",- sequence=1,- ),- FrameworkWorkflow(- name="Execute PRP",- skill_name="prp-execute",- description="Execute the generated prompt systematically",- sequence=2,- ),- ],- ),- "agentos": Framework(- id="agentos",- name="AgentOS",- description="A standards-based framework focusing on project initialization and adherence to coding standards. Emphasizes consistent project structure and quality gates.",- skill_prefix="agentos",- workflows=[- FrameworkWorkflow(- name="Project Install",- skill_name="agentos-project-install",- description="Initialize project with standard structure",- sequence=1,- ),- FrameworkWorkflow(- name="Standards",- skill_name="agentos-standards",- description="Apply and verify coding standards",- sequence=2,- ),- ],- ),- "amplihack": Framework(- id="amplihack",- name="AMPLIHACK",- description="A multi-agent orchestration framework with specialized agents. Features auto workflow selection, analysis, cascade patterns, debate workflows, fix workflows, and modular building.",- skill_prefix="amplihack",- workflows=[- FrameworkWorkflow(- name="Auto",- skill_name="amplihack-auto",- description="Automatic workflow selection based on task complexity",- sequence=1,- ),- FrameworkWorkflow(- name="Analyze",- skill_name="amplihack-analyze",- description="Deep code/requirements analysis with multiple perspectives",- sequence=2,- ),- FrameworkWorkflow(- name="Cascade",- skill_name="amplihack-cascade",- description="Sequential multi-agent processing for complex tasks",- sequence=3,- ),- FrameworkWorkflow(- name="Debate",- skill_name="amplihack-debate",- description="Multi-perspective debate for technical decisions",- sequence=4,- ),- FrameworkWorkflow(- name="Fix",- skill_name="amplihack-fix",- description="Systematic error resolution with pattern-specific context",- sequence=5,- ),- FrameworkWorkflow(- name="Modular Build",- skill_name="amplihack-modular-build",- description="Build code following brick philosophy with modules",- sequence=6,- ),- ],- ),- "agent-zero-dev": Framework(- id="agent-zero-dev",- name="Agent Zero Dev",- description="Development framework for extending and building features for Agent Zero. Provides patterns, templates, and code generators for creating tools, extensions, skills, API endpoints, subordinate profiles, and project configurations.",- skill_prefix="a0dev",- workflows=[- FrameworkWorkflow(- name="Quickstart",- skill_name="a0dev-quickstart",- description="5-minute guide to extending Agent Zero",- sequence=1,- ),- FrameworkWorkflow(- name="Create Tool",- skill_name="a0dev-create-tool",- description="Create new agent capabilities (tools)",- sequence=2,- ),- FrameworkWorkflow(- name="Create Extension",- skill_name="a0dev-create-extension",- description="Hook into agent lifecycle events",- sequence=3,- ),- FrameworkWorkflow(- name="Create Skill",- skill_name="a0dev-create-skill",- description="Build reusable instruction bundles (SKILL.md)",- sequence=4,- ),- FrameworkWorkflow(- name="Create API",- skill_name="a0dev-create-api",- description="Add Web UI / REST API endpoints",- sequence=5,- ),- FrameworkWorkflow(- name="Create Subordinate",- skill_name="a0dev-create-subordinate",- description="Create specialized agent profiles",- sequence=6,- ),- FrameworkWorkflow(- name="Create Project",- skill_name="a0dev-create-project",- description="Set up project-specific configuration",- sequence=7,- ),- FrameworkWorkflow(- name="Dev Workflow",- skill_name="a0dev-workflow",- description="Full Agent Zero development workflow",- sequence=8,- ),- ],- ),-}---# ─────────────────────────────────────────────────────────────────────────────-# Public API-# ─────────────────────────────────────────────────────────────────────────────---def get_framework(framework_id: str) -> Optional[Framework]:- """- Get a framework by its ID.-- Args:- framework_id: The framework identifier (e.g., "gsd", "bmad")-- Returns:- Framework object if found, None otherwise- """- return FRAMEWORK_REGISTRY.get(framework_id)---def list_frameworks() -> List[Framework]:- """- List all available frameworks.-- Returns:- List of all Framework objects in registry order- """- return [FRAMEWORK_REGISTRY[fid] for fid in ALL_FRAMEWORK_IDS if fid in FRAMEWORK_REGISTRY]---def get_active_framework(context: "AgentContext") -> Optional[Framework]:- """- Get the active framework for an agent context.-- Priority:- 1. Project-level override (if project has dev_framework set)- 2. Global setting (settings.dev_framework)- 3. None (no framework active)-- Args:- context: The agent context-- Returns:- Active Framework object, or None if "none" is selected- """- from python.helpers import projects- from python.helpers.settings import get_settings-- framework_id: str = "none"-- # Check project-level override first- project_name = projects.get_context_project_name(context)- if project_name:- try:- project_data = projects.load_basic_project_data(project_name)- project_fw = project_data.get("dev_framework", "")- if project_fw and project_fw != "":- framework_id = project_fw- except Exception:- pass-- # Fall back to global setting- if framework_id == "none" or not framework_id:- settings = get_settings()- framework_id = settings.get("dev_framework", "none")-- if framework_id == "none" or not framework_id:- return None-- return get_framework(framework_id)---def get_framework_options() -> List[dict]:- """- Get framework options formatted for settings UI select field.-- Returns:- List of dicts with 'value' and 'label' keys- """- return [- {"value": fw.id, "label": fw.name}- for fw in list_frameworks()- ]diff --git a/python/helpers/projects.py b/python/helpers/projects.pyindex 63dc7e58a..73deeba46 100644--- a/python/helpers/projects.py+++ b/python/helpers/projects.py@@ -37,7 +37,6 @@ class BasicProjectData(TypedDict):"own", "global"] # in the future we can add cutom and point to another existing folderfile_structure: FileStructureInjectionSettings- dev_framework: str # "" = use global setting, or specific framework IDclass EditProjectData(BasicProjectData):name: str@@ -113,7 +112,6 @@ def _normalizeBasicData(data: BasicProjectData):"file_structure",_default_file_structure_settings(),),- dev_framework=data.get("dev_framework", ""),)@@ -134,7 +132,6 @@ def _normalizeEditData(data: EditProjectData):_default_file_structure_settings(),),subagents=data.get("subagents", {}),- dev_framework=data.get("dev_framework", ""),)diff --git a/python/helpers/settings.py b/python/helpers/settings.pyindex 8c7233e38..02d0ff58d 100644--- a/python/helpers/settings.py+++ b/python/helpers/settings.py@@ -151,8 +151,6 @@ class Settings(TypedDict):update_check_enabled: bool- # Development framework selection- dev_framework: strclass PartialSettings(Settings, total=False):pass@@ -203,7 +201,6 @@ class SettingsOutputAdditional(TypedDict):agent_subdirs: list[FieldOption]knowledge_subdirs: list[FieldOption]stt_models: list[FieldOption]- framework_options: list[FieldOption]is_dockerized: boolruntime_settings: dict[str, Any]@@ -237,8 +234,6 @@ def _ensure_option_present(options: list[OptionT] | None, current_value: str | Nreturn optsdef convert_out(settings: Settings) -> SettingsOutput:- from python.helpers import frameworks-out = SettingsOutput(settings = settings.copy(),additional = SettingsOutputAdditional(@@ -260,7 +255,6 @@ def convert_out(settings: Settings) -> SettingsOutput:{"value": "turbo", "label": "Turbo (Multilingual)"},],runtime_settings={},- framework_options=cast(list[FieldOption], frameworks.get_framework_options()),),)@@ -287,7 +281,6 @@ def convert_out(settings: Settings) -> SettingsOutput:additional["agent_subdirs"] = _ensure_option_present(additional.get("agent_subdirs"), current.get("agent_profile"))additional["knowledge_subdirs"] = _ensure_option_present(additional.get("knowledge_subdirs"), current.get("agent_knowledge_subdir"))additional["stt_models"] = _ensure_option_present(additional.get("stt_models"), current.get("stt_model_size"))- additional["framework_options"] = _ensure_option_present(additional.get("framework_options"), current.get("dev_framework"))# masked api keysproviders = get_providers("chat") + get_providers("embedding")@@ -567,7 +560,6 @@ def get_default_settings() -> Settings:secrets="",litellm_global_kwargs=get_default_value("litellm_global_kwargs", {}),update_check_enabled=get_default_value("update_check_enabled", True),- dev_framework=get_default_value("dev_framework", "none"),)diff --git a/python/helpers/skills.py b/python/helpers/skills.pyindex 0fa2a5913..31c41d264 100644--- a/python/helpers/skills.py+++ b/python/helpers/skills.py@@ -14,7 +14,7 @@ except Exception: # pragma: no coveryaml = None # type: ignore-SkillSource = Literal["custom", "default", "project", "framework"]+SkillSource = Literal["custom", "default", "project"]@dataclass(slots=True)@@ -46,18 +46,11 @@ def get_skills_base_dir() -> Path:def get_skill_roots(order: Optional[List[SkillSource]] = None,project_name: Optional[str] = None,- framework_id: Optional[str] = None,) -> List[Tuple[SkillSource, Path]]:base = get_skills_base_dir()order = order or ["custom", "default"]roots: List[Tuple[SkillSource, Path]] = [(src, base / src) for src in order]- # Framework skills take priority when active- if framework_id and framework_id != "none":- fw_path = base / "frameworks" / framework_id- if fw_path.exists():- roots.insert(0, ("framework", fw_path))-# Include project-scoped skills if a project is activeif project_name:try:@@ -304,14 +297,12 @@ def list_skills(dedupe: bool = True,root_order: Optional[List[SkillSource]] = None,project_name: Optional[str] = None,- framework_id: Optional[str] = None,) -> List[Skill]:skills: List[Skill] = []roots = get_skill_roots(order=root_order,project_name=project_name,- framework_id=framework_id,)for source, root in roots:for skill_md in discover_skill_md_files(root):@@ -337,7 +328,6 @@ def find_skill(include_content: bool = False,root_order: Optional[List[SkillSource]] = None,project_name: Optional[str] = None,- framework_id: Optional[str] = None,) -> Optional[Skill]:target = _normalize_name(skill_name)if not target:@@ -346,7 +336,6 @@ def find_skill(roots = get_skill_roots(order=root_order,project_name=project_name,- framework_id=framework_id,)for source, root in roots:for skill_md in discover_skill_md_files(root):@@ -363,7 +352,6 @@ def search_skills(*,limit: int = 25,project_name: Optional[str] = None,- framework_id: Optional[str] = None,) -> List[Skill]:q = (query or "").strip().lower()if not q:@@ -374,7 +362,6 @@ def search_skills(include_content=False,dedupe=True,project_name=project_name,- framework_id=framework_id,)scored: List[Tuple[int, Skill]] = []diff --git a/python/tools/skills_tool.py b/python/tools/skills_tool.pyindex ab00f942d..b4f810fb2 100644--- a/python/tools/skills_tool.py+++ b/python/tools/skills_tool.py@@ -7,7 +7,6 @@ from python.helpers.tool import Tool, Responsefrom python.helpers import filesfrom python.helpers import projectsfrom python.helpers import skills as skills_helper-from python.helpers import frameworksclass SkillsTool(Tool):@@ -27,12 +26,6 @@ class SkillsTool(Tool):ctx = getattr(self.agent, "context", None)return projects.get_context_project_name(ctx) if ctx else None- def _get_framework_id(self) -> str | None:- try:- framework = frameworks.get_active_framework(self.agent.context)- return framework.id if framework else None- except Exception:- return Noneasync def execute(self, **kwargs) -> Response:method = ((kwargs.get("method") or self.args.get("method") or self.method or "")@@ -69,7 +62,6 @@ class SkillsTool(Tool):include_content=False,dedupe=True,project_name=self._get_project_name(),- framework_id=self._get_framework_id(),)if not skills:return (@@ -101,7 +93,6 @@ class SkillsTool(Tool):query,limit=25,project_name=self._get_project_name(),- framework_id=self._get_framework_id(),)if not results:return f"No skills matched query: {query!r}"@@ -125,7 +116,6 @@ class SkillsTool(Tool):skill_name,include_content=True,project_name=self._get_project_name(),- framework_id=self._get_framework_id(),)if not skill:return f"Error: skill not found: {skill_name!r}. Try skills_tool method=list or method=search."@@ -187,7 +177,6 @@ class SkillsTool(Tool):skill_name,include_content=False,project_name=self._get_project_name(),- framework_id=self._get_framework_id(),)if not skill:return f"Error: skill not found: {skill_name!r}."diff --git a/usr/skills/frameworks/agent-zero-dev/README.md b/usr/skills/frameworks/agent-zero-dev/README.mddeleted file mode 100644index f772a735a..000000000--- a/usr/skills/frameworks/agent-zero-dev/README.md+++ /dev/null@@ -1,166 +0,0 @@-# Agent Zero Development Framework--A comprehensive development framework for extending and building features for the Agent Zero AI framework.--## Overview--This framework provides everything you need to extend Agent Zero:--- 🛠️ **Code Generators** - Scaffold tools, extensions, skills, and APIs-- 📚 **Documentation** - Architecture guides, best practices, and quickstart-- 🧩 **Templates** - Boilerplate code following framework patterns-- 🎯 **Examples** - Real-world patterns and use cases--## Quick Start--```bash-# Create a new tool-python scripts/create_tool.py MyTool "Description of what it does"--# Create an extension-python scripts/create_extension.py agent_init MyExtension "What it does"--# Create a skill-python scripts/create_skill.py my-skill "Skill description"--# Create an API endpoint-python scripts/create_api.py MyEndpoint "What it does"-```--## What's Included--### Scripts--| Script | Purpose | Usage |-|--------|---------|-------|-| `create_tool.py` | Generate tool boilerplate | `python create_tool.py ToolName "Description"` |-| `create_extension.py` | Generate extension boilerplate | `python create_extension.py hook_point ExtName` |-| `create_skill.py` | Generate skill boilerplate | `python create_skill.py skill-name "Description"` |-| `create_api.py` | Generate API endpoint boilerplate | `python create_api.py EndpointName "Description"` |--### Documentation--| Document | Contents |-|----------|----------|-| [SKILL.md](SKILL.md) | Main framework documentation |-| [docs/quickstart.md](docs/quickstart.md) | 5-minute quickstart guide |-| [docs/architecture.md](docs/architecture.md) | Deep dive into architecture |-| [docs/best-practices.md](docs/best-practices.md) | Coding standards and patterns |--### Directory Structure--```-agent-zero-dev/-├── SKILL.md # Main skill documentation-├── README.md # This file-├── scripts/ # Code generator scripts-│ ├── create_tool.py-│ ├── create_extension.py-│ ├── create_skill.py-│ └── create_api.py-├── templates/ # Placeholder for templates-└── docs/ # Additional documentation- ├── quickstart.md- ├── architecture.md- └── best-practices.md-```--## Usage--### Activating This Skill--This skill activates automatically when you mention:-- "extend agent zero"-- "create a tool"-- "build agent zero feature"-- "agent zero development"--### Example Workflows--#### Creating a Weather Tool--```bash-# 1. Generate the tool-python scripts/create_tool.py WeatherLookup "Get weather for a location"--# 2. Edit /a0/python/tools/weather_lookup.py-# - Add your weather API logic-# - Update docstrings--# 3. Restart Agent Zero-# - The tool loads automatically-```--#### Creating a Custom Skill--```bash-# 1. Generate the skill-python scripts/create_skill.py data-processor "Process CSV and JSON data"--# 2. Edit /a0/usr/skills/custom/data-processor/SKILL.md-# - Add trigger patterns-# - Write step-by-step instructions--# 3. Test it-# "Use data-processor to analyze my CSV"-```--## Architecture Overview--Agent Zero is built on these extension points:--1. **Tools** - Agent capabilities (web search, code execution)-2. **Extensions** - Lifecycle hooks (initialization, message processing)-3. **Skills** - Reusable instruction bundles (SKILL.md standard)-4. **APIs** - Web UI endpoints (FastAPI)-5. **Subordinates** - Specialized agent profiles-6. **Projects** - Isolated workspaces with custom config--## Development Workflow--```-1. Brainstorm → Identify what to build-2. Plan → Choose the right extension point-3. Scaffold → Use scripts to generate boilerplate-4. Implement → Fill in your logic-5. Test → Verify with the agent-6. Refine → Iterate based on results-```--## Best Practices--- ✅ Follow existing patterns in the codebase-- ✅ Write clear docstrings and comments-- ✅ Handle errors gracefully-- ✅ Test thoroughly before deploying-- ✅ Update documentation--## Contributing--When adding to this framework:--1. Follow the SKILL.md standard-2. Include examples in documentation-3. Test scripts before committing-4. Update this README--## Resources--- [Agent Zero Main Documentation](https://github.com/frdel/agent-zero)-- [SKILL.md Standard](https://github.com/anthropics/skills/blob/main/SKILL.md)-- [Python Async/Await Guide](https://docs.python.org/3/library/asyncio.html)-- [FastAPI Documentation](https://fastapi.tiangolo.com/)--## License--Part of the Agent Zero framework - follow the same license terms.--## Support--- Check [docs/troubleshooting.md](docs/troubleshooting.md) (if exists)-- Review [docs/best-practices.md](docs/best-practices.md)-- Examine existing code in `/a0/python/`-------**Ready to extend Agent Zero?** Start with [docs/quickstart.md](docs/quickstart.md)!diff --git a/usr/skills/frameworks/agent-zero-dev/SKILL.md b/usr/skills/frameworks/agent-zero-dev/SKILL.mddeleted file mode 100644index 02fea2a88..000000000--- a/usr/skills/frameworks/agent-zero-dev/SKILL.md+++ /dev/null@@ -1,702 +0,0 @@-----name: "agent-zero-dev"-description: "Development framework for extending and building features for the Agent Zero AI framework. Provides patterns, templates, and best practices for creating tools, extensions, skills, API endpoints, subordinate profiles, and framework components."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["development", "framework", "agent-zero", "extending", "tools", "extensions", "skills", "api"]-trigger_patterns:- - "extend agent zero"- - "agent zero development"- - "build agent zero feature"- - "create agent zero tool"- - "add extension"- - "framework development"- - "agent zero skill"------# Agent Zero Development Framework--This framework provides comprehensive guidance for extending and building features for the Agent Zero AI framework. Use this skill when you need to:--- Create new **Tools** for agent capabilities-- Add **Extensions** to hook into framework lifecycle-- Build **Skills** following the SKILL.md standard-- Develop **API Endpoints** for the Web UI-- Create **Subordinate Profiles** for specialized agents-- Extend **Projects** with custom configuration-- Understand framework **Architecture** and patterns--## Quick Start--Choose your extension point:--| Component | Use Case | Location |-|-----------|----------|----------|-| **Tools** | Add agent capabilities (web search, code execution) | `python/tools/` |-| **Extensions** | Hook into lifecycle events | `python/extensions/<hook_point>/` |-| **Skills** | Create reusable instruction bundles | `usr/skills/custom/<skill-name>/` |-| **API Endpoints** | Add Web UI functionality | `python/api/` |-| **Subordinates** | Create specialized agent profiles | `agents/<profile>/` |-| **Projects** | Project-specific configuration | `.a0proj/` |-------## Architecture Overview--### Core Components--```-Agent Zero Framework Architecture-├── python/-│ ├── tools/ # Agent capabilities (inherit from Tool)-│ ├── extensions/ # Lifecycle hooks (numbered execution)-│ ├── api/ # FastAPI endpoints (inherit from ApiHandler)-│ └── helpers/ # Utility functions and base classes-├── usr/skills/-│ ├── default/ # Default skills (system)-│ ├── custom/ # User-created skills-│ └── frameworks/ # Multi-phase framework skills-├── agents/-│ └── <profile>/ # Subordinate agent profiles-├── memory/ # FAISS-based vector memory-└── tmp/- └── chats/ # Conversation storage-```--### Key Patterns--1. **Extensions execute in numeric order** (`_10_*.py`, `_20_*.py`, etc.)-2. **Tools inherit from `Tool` base class** with `execute()` method-3. **Skills use progressive disclosure** (metadata → content → scripts)-4. **Shared AgentContext** enables memory persistence across agents-5. **Async/await throughout** for non-blocking operations-------## Creating Tools--Tools are the primary way agents interact with the world. Each tool inherits from the `Tool` base class.--### Tool Structure--```python-# python/tools/my_tool.py-from python.helpers.tool import Tool, Response--class MyTool(Tool):- """- Brief description of what this tool does.-- Arguments (tool_args):- - arg1: Description of first argument- - arg2: Description of second argument- """-- async def execute(self, **kwargs) -> Response:- # Get arguments from kwargs or self.args- arg1 = kwargs.get("arg1") or self.args.get("arg1")- arg2 = kwargs.get("arg2") or self.args.get("arg2")-- # Tool logic here- result = await self.do_something(arg1, arg2)-- return Response(- message=result,- break_loop=False # Set True to end agent loop- )-- async def do_something(self, arg1, arg2):- # Implement tool functionality- pass-```--### Tool Best Practices--1. **Always document args** in the class docstring-2. **Use `Response` objects** for consistent return format-3. **Handle errors gracefully** - return error message, don't crash-4. **Access agent context** via `self.agent.context`-5. **Use kwargs fallback** to `self.args` for flexibility--### Example: Complete Tool--```python-# python/tools/data_processor.py-from python.helpers.tool import Tool, Response-import json--class DataProcessor(Tool):- """- Process and transform data structures.-- Arguments (tool_args):- - operation: The operation to perform (filter, map, reduce)- - data: JSON data to process- - key: Key to filter/sort by (for filter/sort operations)- - value: Value to filter by (for filter operation)- """-- async def execute(self, **kwargs) -> Response:- try:- operation = kwargs.get("operation") or self.args.get("operation", "")- data_str = kwargs.get("data") or self.args.get("data", "[]")- key = kwargs.get("key") or self.args.get("key")- value = kwargs.get("value") or self.args.get("value")-- data = json.loads(data_str)-- if operation == "filter":- result = [item for item in data if item.get(key) == value]- elif operation == "sort":- result = sorted(data, key=lambda x: x.get(key))- else:- return Response(message=f"Unknown operation: {operation}", break_loop=False)-- return Response(- message=json.dumps(result, indent=2),- break_loop=False- )- except Exception as e:- return Response(message=f"Error processing data: {e}", break_loop=False)-```-------## Creating Extensions--Extensions hook into specific points in the agent lifecycle. They execute in numeric order.--### Extension Hook Points--| Hook Point | When It Fires | Use For |-|------------|---------------|---------|-| `agent_init` | Agent initialization | Loading configs, setting defaults |-| `message_loop_start` | Before message processing | Pre-processing, logging |-| `message_loop_end` | After message processing | Cleanup, post-processing |-| `before_main_llm_call` | Before LLM API call | Modifying prompts, adding context |-| `response_stream_start` | When response streaming begins | Initializing stream handlers |-| `response_stream_chunk` | Per response chunk | Transforming output |-| `response_stream_end` | When streaming ends | Finalizing, cleanup |-| `tool_execute_before` | Before tool execution | Validation, logging |-| `tool_execute_after` | After tool execution | Post-processing results |--### Extension Structure--```python-# python/extensions/<hook_point>/_10_my_extension.py-from python.helpers.extension import Extension-from python.helpers.print_style import PrintStyle--class MyExtension(Extension):- """- Brief description of extension purpose.- """-- async def execute(self, **kwargs):- # Access the agent- agent = self.agent- context = agent.context-- # Extension logic- PrintStyle.hint("MyExtension executing...")-- # Modify data if needed (check kwargs for hook-specific data)- data = kwargs.get("data", {})- data["modified"] = True-- # Return modified data if applicable- return data-```--### Extension Execution Order--Extensions execute in numeric order based on filename prefix:--```-_10_load_config.py # Runs first-_20_validate.py # Runs second-_30_process.py # Runs third-```--Use 10-number increments to leave room for future extensions.--### Example: Agent Init Extension--```python-# python/extensions/agent_init/_15_load_custom_config.py-from python.helpers.extension import Extension-from python.helpers import files-import json--class LoadCustomConfig(Extension):- """- Load custom configuration from .a0proj/config.json- """-- async def execute(self, **kwargs):- agent = self.agent- context = agent.context-- config_path = files.get_abs_path(".a0proj/config.json")- if files.exists(config_path):- with open(config_path, 'r') as f:- config = json.load(f)- context.data["custom_config"] = config-- return kwargs.get("data", {})-```-------## Creating Skills--Skills are reusable instruction bundles following the SKILL.md standard.--### Skill Directory Structure--```-usr/skills/custom/my-skill/-├── SKILL.md # Required: Main skill file-├── scripts/ # Optional: Helper scripts-│ ├── helper.py-│ └── process.sh-├── templates/ # Optional: Templates-│ └── template.md-└── docs/ # Optional: Additional docs- └── examples.md-```--### SKILL.md Format--```yaml-----name: "skill-name"-description: "Clear description of what this skill does and when to use it"-version: "1.0.0"-author: "Your Name"-tags: ["category1", "category2"]-trigger_patterns:- - "keyword1"- - "phrase that triggers this"------# Skill Title--## When to Use-Describe trigger conditions and use cases.--## The Process-Step-by-step instructions for the agent to follow.--### Step 1: First Action-Details...--### Step 2: Second Action-Details...--## Examples-Show sample interactions.--## Scripts-Reference any helper scripts:-- `scripts/helper.py` - Does X-- `scripts/process.sh` - Does Y--## Tips-Additional guidance and best practices.-```--### Using Skills--```python-# Load skill metadata-await skills_tool.execute(method="list")--# Load full skill content-await skills_tool.execute(method="load", skill_name="my-skill")--# Execute skill script (use runtime path from the load output)-await code_execution_tool.execute(- runtime="python",- code="python /a0/usr/skills/custom/my-skill/scripts/helper.py input"-)-```-------## Creating API Endpoints--API endpoints serve the Web UI and external clients using FastAPI.--### API Endpoint Structure--```python-# python/api/my_endpoint.py-from python.helpers.api import ApiHandler, Request, Response-from agent import AgentContext--class MyEndpoint(ApiHandler):- """- Handle requests for /api/my-endpoint- """-- async def process(self, input: dict, request: Request) -> dict | Response:- # Get query params or JSON body- param = input.get("param", "default")-- # Get or create agent context- ctxid = input.get("context", "")- context = self.use_context(ctxid)-- # Process request- result = await self.process_request(param, context)-- return {- "result": result,- "context": context.id,- }-- async def process_request(self, param, context):- # Implement endpoint logic- return {"processed": param}-```--### API Best Practices--1. **Use `ApiHandler` base class** for consistent request/response handling-2. **Get context with `self.use_context(ctxid)`** - creates if not exists-3. **Return dict or Response** objects-4. **Handle both GET and POST** if applicable-5. **Use `Request` object** for accessing headers, files, etc.--### Example: File Upload Endpoint--```python-# python/api/upload_processor.py-from python.helpers.api import ApiHandler, Request-from werkzeug.utils import secure_filename-import os--class UploadProcessor(ApiHandler):- async def process(self, input: dict, request: Request) -> dict:- if request.method == "POST":- uploaded_file = request.files.get("file")- if uploaded_file:- filename = secure_filename(uploaded_file.filename)- save_path = f"/tmp/uploads/{filename}"- uploaded_file.save(save_path)-- return {- "success": True,- "filename": filename,- "path": save_path- }-- return {"success": False, "error": "No file provided"}-```-------## Creating Subordinate Profiles--Subordinates are specialized agents with custom prompts and configurations.--### Profile Directory Structure--```-agents/<profile-name>/-├── agent.json # Profile configuration-└── prompts/- ├── system.md # System prompt- └── subordinates.md # Subordinate delegation prompts-```--### agent.json Configuration--```json-{- "name": "Specialized Agent",- "description": "What this subordinate specializes in",- "model": "anthropic/claude-sonnet-4-20250514",- "temperature": 0.7,- "max_tokens": 4000,- "allowed_tools": [- "code_execution_tool",- "search_engine",- "call_subordinate"- ],- "prompts": {- "system": "prompts/system.md",- "subordinates": "prompts/subordinates.md"- }-}-```--### System Prompt Template--```markdown-# System Prompt for Specialized Agent--## Your Role-You are a specialized agent focused on [domain].--## Capabilities-- Expertise in [specific area]-- Use tools: code_execution_tool, search_engine--## Process-1. Analyze the request-2. Choose appropriate tools-3. Execute and verify results-4. Return structured response--## Output Format-Always respond with valid JSON:-```json-{- "result": "your result here",- "confidence": 0.95-}-```-```--### Using Subordinates--```python-# Call from main agent-call_subordinate(- profile="developer",- message="Implement a Python function to calculate Fibonacci",- reset="true"-)-```-------## Creating Projects--Projects provide isolated workspaces with custom configuration.--### Project Structure--```-/usr/projects/<project-name>/-├── .a0proj/-│ ├── config.json # Project configuration-│ ├── instructions.md # Project-specific instructions-│ └── skills/ # Project-specific skills-└── <project-files>/ # Your project files-```--### config.json--```json-{- "name": "My Project",- "description": "Project description",- "default_model": "anthropic/claude-sonnet-4-20250514",- "allowed_tools": ["*"],- "extensions": {- "enabled": ["custom_extension"]- },- "skills": {- "auto_load": ["project-specific-skill"]- }-}-```--### instructions.md--```markdown-# Project: My Project--## Overview-This project does X, Y, Z.--## Coding Standards-- Use Python 3.12+ features-- Follow PEP 8-- Write tests for all functions--## Architecture-- API layer in `api/`-- Business logic in `services/`-- Models in `models/`-```-------## Framework Development Workflow--When building features for Agent Zero itself, follow this workflow:--### Phase 1: Brainstorming-- Define the problem and solution-- Identify extension points (tool, extension, skill, API)-- Review existing patterns for consistency--### Phase 2: Planning-- Break work into small tasks (2-5 min each)-- Identify dependencies and order-- Write verification criteria for each task--### Phase 3: Implementation-- Create feature branch (use git worktrees)-- Follow TDD: test first, then implement-- Match existing code patterns--### Phase 4: Code Review-- Review against plan-- Check pattern consistency-- Verify tests pass--### Phase 5: Integration-- Merge to main-- Update documentation-- Test in production context-------## Common Patterns Reference--### Accessing Context Data--```python-# Shared across all agents in conversation-context = self.agent.context-data = context.data # dict-like shared memory--# Store data-data["my_key"] = my_value--# Retrieve data-value = data.get("my_key", default)-```--### Using Helpers--```python-from python.helpers import files, extension, print_style--# File operations-content = files.read_file("path/to/file")-files.write_file("path/to/file", content)-exists = files.exists("path/to/file")--# Extensions-await extension.call_extensions("hook_point", agent=agent, data=data)--# Printing-PrintStyle.hint("Hint message")-PrintStyle.warning("Warning message")-PrintStyle.error("Error message")-```--### Error Handling--```python-try:- result = await risky_operation()-except Exception as e:- # Log for debugging- PrintStyle.error(f"Operation failed: {e}")- # Return graceful error to user- return Response(message=f"Error: {e}", break_loop=False)-```--### Async Patterns--```python-# Concurrent execution-tasks = [process_item(item) for item in items]-results = await asyncio.gather(*tasks)--# Timeouts-try:- result = await asyncio.wait_for(operation(), timeout=30)-except asyncio.TimeoutError:- return Response(message="Operation timed out", break_loop=False)-```-------## Testing Your Extensions--### Manual Testing--1. **Restart the framework** after code changes-2. **Test with minimal input** first-3. **Check logs** for errors: `docker logs -f agent-zero`-4. **Verify in UI** that changes appear correctly--### Unit Testing (when available)--```python-# tests/tools/test_my_tool.py-import pytest-from python.tools.my_tool import MyTool--async def test_my_tool():- tool = MyTool()- result = await tool.execute(operation="test", data="{}")- assert "success" in result.message-```-------## Scripts and Templates--This skill includes helper scripts and templates:--### Scripts--| Script | Purpose | Usage |-|--------|---------|-------|-| `scripts/create_tool.py` | Generate tool boilerplate | `python scripts/create_tool.py ToolName` |-| `scripts/create_extension.py` | Generate extension boilerplate | `python scripts/create_extension.py HookPoint ExtensionName` |-| `scripts/create_skill.py` | Generate skill boilerplate | `python scripts/create_skill.py skill-name` |-| `scripts/create_api.py` | Generate API endpoint boilerplate | `python scripts/create_api.py EndpointName` |--### Templates--| Template | Purpose |-|----------|---------|-| `templates/tool.py` | Tool boilerplate |-| `templates/extension.py` | Extension boilerplate |-| `templates/SKILL.md` | Skill boilerplate |-| `templates/api.py` | API endpoint boilerplate |-------## Best Practices Summary--### DO-- ✅ Follow existing patterns and conventions-- ✅ Write clear docstrings and comments-- ✅ Handle errors gracefully-- ✅ Use type hints where applicable-- ✅ Test your changes thoroughly-- ✅ Update documentation-- ✅ Use meaningful names--### DON'T-- ❌ Break existing functionality-- ❌ Ignore error cases-- ❌ Hardcode paths or values-- ❌ Skip documentation-- ❌ Mix sync and async code carelessly-- ❌ Access internal structures directly when helpers exist-------## Need Help?--Use this skill by saying:-- "Help me create a new tool for..."-- "I want to add an extension that..."-- "Create a skill for..."-- "Build an API endpoint for..."-- "How do I extend Agent Zero to..."--I'll guide you through the appropriate patterns and generate boilerplate code!diff --git a/usr/skills/frameworks/agent-zero-dev/a0dev-create-api/SKILL.md b/usr/skills/frameworks/agent-zero-dev/a0dev-create-api/SKILL.mddeleted file mode 100644index a4ce03eb9..000000000--- a/usr/skills/frameworks/agent-zero-dev/a0dev-create-api/SKILL.md+++ /dev/null@@ -1,286 +0,0 @@-----name: "a0dev-create-api"-description: "Add Web UI and REST API endpoints for Agent Zero."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["agent-zero-dev", "api", "endpoint", "fastapi", "webui"]-trigger_patterns:- - "create api"- - "new endpoint"- - "add api"- - "api endpoint"- - "/a0dev-create-api"------# Agent Zero Dev: Create API--API endpoints serve the Web UI and external clients using FastAPI. Each endpoint inherits from `ApiHandler`.--## API Location--```-python/api/-├── poll.py # Long-polling for updates-├── chat.py # Chat message handling-├── frameworks.py # Framework management-├── settings.py # Settings management-└── your_endpoint.py # New endpoints go here-```--## API Endpoint Structure--```python-# python/api/my_endpoint.py-from python.helpers.api import ApiHandler, Request, Input, Output--class MyEndpoint(ApiHandler):- """- Handle requests for /api/my-endpoint-- Query params / JSON body:- - param1: Description of param1- - param2: Description of param2- """-- async def process(self, input: Input, request: Request) -> Output:- # Get parameters from input (works for both GET params and POST body)- param1 = input.get("param1", "default")- param2 = input.get("param2")-- try:- # Process the request- result = await self.do_work(param1, param2)-- return {- "ok": True,- "data": result,- }- except Exception as e:- return {- "ok": False,- "error": str(e),- }-- async def do_work(self, param1, param2):- # Implementation- return {"processed": param1}-```--## Type Definitions--```python-Input = dict # Request parameters (query or body)-Output = dict | Response # Return dict or FastAPI Response-Request = fastapi.Request # Full request object-```--## URL Routing--Endpoints are auto-routed based on filename:-- `my_endpoint.py` → `/api/my_endpoint` or `/api/my-endpoint`-- Class name doesn't affect routing--## Getting Agent Context--```python-async def process(self, input: Input, request: Request) -> Output:- # Get context ID from request- ctxid = input.get("context", "")-- # Get or create context (creates if doesn't exist)- context = self.use_context(ctxid)-- # Access context data- data = context.data-- # Get the agent for this context- agent = self.get_context_agent(context)-- return {- "ok": True,- "context": context.id,- }-```--## Complete Example: Data Query Endpoint--```python-# python/api/data_query.py-from python.helpers.api import ApiHandler, Request, Input, Output-from dataclasses import asdict--class DataQuery(ApiHandler):- """- Query and manipulate stored data.-- Actions:- - get: Retrieve data by key- - set: Store data with key- - list: List all keys- - delete: Remove data by key-- Query params / JSON body:- - action: The action to perform- - context: Agent context ID- - key: Data key (for get/set/delete)- - value: Data value (for set)- """-- async def process(self, input: Input, request: Request) -> Output:- action = input.get("action", "list")- ctxid = input.get("context", "")- key = input.get("key")- value = input.get("value")-- try:- context = self.use_context(ctxid)-- if action == "list":- keys = list(context.data.keys())- return {"ok": True, "keys": keys}-- elif action == "get":- if not key:- return {"ok": False, "error": "Key required"}- data = context.data.get(key)- return {"ok": True, "key": key, "value": data}-- elif action == "set":- if not key:- return {"ok": False, "error": "Key required"}- context.data[key] = value- return {"ok": True, "key": key, "stored": True}-- elif action == "delete":- if not key:- return {"ok": False, "error": "Key required"}- if key in context.data:- del context.data[key]- return {"ok": True, "key": key, "deleted": True}-- else:- return {"ok": False, "error": f"Unknown action: {action}"}-- except Exception as e:- return {"ok": False, "error": str(e)}-```--## Handling File Uploads--```python-# python/api/file_upload.py-from python.helpers.api import ApiHandler, Request, Input, Output-from fastapi import UploadFile-from python.helpers import files--class FileUpload(ApiHandler):- """Handle file uploads"""-- async def process(self, input: Input, request: Request) -> Output:- # Access uploaded file from request- form = await request.form()- uploaded_file: UploadFile = form.get("file")-- if not uploaded_file:- return {"ok": False, "error": "No file provided"}-- # Read file content- content = await uploaded_file.read()- filename = uploaded_file.filename-- # Save file- save_path = f"/tmp/uploads/{filename}"- files.write_file(save_path, content.decode())-- return {- "ok": True,- "filename": filename,- "size": len(content),- "path": save_path,- }-```--## Streaming Responses--```python-# python/api/stream_data.py-from python.helpers.api import ApiHandler, Request, Input, Output-from fastapi.responses import StreamingResponse-import asyncio--class StreamData(ApiHandler):- """Stream data to client"""-- async def process(self, input: Input, request: Request) -> Output:- async def generate():- for i in range(10):- yield f"data: {i}\n\n"- await asyncio.sleep(0.5)-- return StreamingResponse(- generate(),- media_type="text/event-stream"- )-```--## Using the Generator Script--```bash-python usr/skills/frameworks/agent-zero-dev/scripts/create_api.py \- DataQuery \- "Query and manipulate stored data"-```--Generates: `python/api/data_query.py`--## API Best Practices--### DO--- ✅ Use `ApiHandler` base class-- ✅ Return consistent response format (`{ok, data/error}`)-- ✅ Document params in docstring-- ✅ Handle errors gracefully-- ✅ Use `self.use_context()` for context management-- ✅ Support both GET and POST where appropriate--### DON'T--- ❌ Expose sensitive data-- ❌ Skip input validation-- ❌ Block the event loop-- ❌ Return inconsistent response formats-- ❌ Forget error handling--## Testing Your API--1. **Restart Agent Zero** (APIs load at startup)-2. **Test with curl**:- ```bash- curl "http://localhost:8080/api/my_endpoint?param1=value"- ```-3. **Test with browser** (for GET endpoints)-4. **Check logs** for errors--## Frontend Integration--APIs are called from the Web UI using:--```javascript-// webui/js/api.js-import { callJsonApi, fetchApi } from "/js/api.js";--// JSON POST with CSRF-const result = await callJsonApi("/my_endpoint", { param1: "value" });--// Raw fetch with CSRF-const response = await fetchApi("/my_endpoint", { method: "GET" });-```--## Next Steps--After creating an API:-- Test all actions/parameters-- Add frontend integration if needed-- Document the endpoint-- Consider rate limiting for public APIsdiff --git a/usr/skills/frameworks/agent-zero-dev/a0dev-create-extension/SKILL.md b/usr/skills/frameworks/agent-zero-dev/a0dev-create-extension/SKILL.mddeleted file mode 100644index b636bebed..000000000--- a/usr/skills/frameworks/agent-zero-dev/a0dev-create-extension/SKILL.md+++ /dev/null@@ -1,263 +0,0 @@-----name: "a0dev-create-extension"-description: "Hook into Agent Zero lifecycle events with extensions."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["agent-zero-dev", "extension", "lifecycle", "hooks"]-trigger_patterns:- - "create extension"- - "new extension"- - "add extension"- - "lifecycle hook"- - "/a0dev-create-extension"------# Agent Zero Dev: Create Extension--Extensions hook into specific points in the agent lifecycle. They execute in numeric order based on filename prefix.--## Extension Hook Points--| Hook Point | When It Fires | Use For |-|------------|---------------|---------|-| `agent_init` | Agent initialization | Loading configs, setting defaults |-| `message_loop_start` | Before message processing | Pre-processing, logging |-| `message_loop_end` | After message processing | Cleanup, post-processing |-| `message_loop_prompts_after` | After prompts assembled | Adding context to prompts |-| `before_main_llm_call` | Before LLM API call | Modifying prompts |-| `response_stream_start` | Response streaming begins | Initializing handlers |-| `response_stream_chunk` | Per response chunk | Transforming output |-| `response_stream_end` | Streaming ends | Finalizing |-| `tool_execute_before` | Before tool execution | Validation, logging |-| `tool_execute_after` | After tool execution | Post-processing |-| `hist_add_user_message` | User message added | Message interception |-| `system_prompt` | System prompt assembly | Injecting context |--## Extension Location--```-python/extensions/-├── agent_init/-│ ├── _10_load_settings.py-│ └── _20_your_extension.py-├── message_loop_start/-├── message_loop_end/-├── before_main_llm_call/-└── <hook_point>/- └── _NN_extension_name.py-```--## Extension Structure--```python-# python/extensions/<hook_point>/_NN_my_extension.py-from python.helpers.extension import Extension-from python.helpers.print_style import PrintStyle--class MyExtension(Extension):- """- Brief description of what this extension does.- """-- async def execute(self, **kwargs):- # Access the agent- agent = self.agent- context = agent.context-- # Extension logic- PrintStyle.hint("MyExtension executing...")-- # Get/modify hook-specific data- data = kwargs.get("data", {})-- # Return data (some hooks expect modified data back)- return data-```--## Execution Order--Extensions execute in numeric order based on filename prefix:--```-_10_first.py # Runs first-_20_second.py # Runs second-_30_third.py # Runs third-_55_yours.py # Your extension-_90_last.py # Runs last-```--**Convention:** Use 10-number increments to leave room for future extensions.--## Hook-Specific Examples--### Agent Init (Load Configuration)--```python-# python/extensions/agent_init/_15_load_custom_config.py-from python.helpers.extension import Extension-from python.helpers import files-import json--class LoadCustomConfig(Extension):- """Load custom configuration from .a0proj/config.json"""-- async def execute(self, **kwargs):- agent = self.agent- context = agent.context-- config_path = files.get_abs_path(".a0proj/config.json")- if files.exists(config_path):- with open(config_path, 'r') as f:- config = json.load(f)- context.data["custom_config"] = config-- return kwargs.get("data", {})-```--### Message Loop Start (Logging)--```python-# python/extensions/message_loop_start/_10_log_message.py-from python.helpers.extension import Extension-import logging--class LogMessage(Extension):- """Log incoming messages for debugging"""-- async def execute(self, **kwargs):- agent = self.agent- message = kwargs.get("message", "")-- logging.info(f"Agent {agent.number} received: {message[:100]}...")-- return kwargs.get("data", {})-```--### System Prompt (Inject Context)--```python-# python/extensions/system_prompt/_50_inject_project_context.py-from python.helpers.extension import Extension--class InjectProjectContext(Extension):- """Add project-specific context to system prompt"""-- async def execute(self, **kwargs):- agent = self.agent- context = agent.context-- # Get the prompt being built- prompt_parts = kwargs.get("data", [])-- # Add project context if available- project_info = context.data.get("project_info")- if project_info:- prompt_parts.append(f"\n## Project Context\n{project_info}\n")-- return prompt_parts-```--### Before LLM Call (Modify Prompt)--```python-# python/extensions/before_main_llm_call/_40_add_instructions.py-from python.helpers.extension import Extension--class AddInstructions(Extension):- """Add dynamic instructions before LLM call"""-- async def execute(self, **kwargs):- # Access messages being sent- messages = kwargs.get("messages", [])-- # Modify or add messages- custom_instruction = {- "role": "system",- "content": "Remember to be concise."- }-- # Return modified data- return {"messages": messages + [custom_instruction]}-```--### Tool Execute After (Post-Process)--```python-# python/extensions/tool_execute_after/_30_log_tool_result.py-from python.helpers.extension import Extension-from python.helpers.print_style import PrintStyle--class LogToolResult(Extension):- """Log tool execution results"""-- async def execute(self, **kwargs):- tool_name = kwargs.get("tool_name", "unknown")- result = kwargs.get("result", {})-- PrintStyle.hint(f"Tool {tool_name} returned: {str(result)[:100]}...")-- return kwargs.get("data", {})-```--## Using the Generator Script--```bash-python usr/skills/frameworks/agent-zero-dev/scripts/create_extension.py \- agent_init \- LoadProjectSettings \- "Load project-specific settings on agent init"-```--Generates: `python/extensions/agent_init/_50_load_project_settings.py`--## Extension Best Practices--### DO--- ✅ Use numeric prefixes (10, 20, 30...)-- ✅ Return the data dict (even if unmodified)-- ✅ Document what the extension does-- ✅ Keep extensions focused (single responsibility)-- ✅ Handle errors gracefully-- ✅ Use PrintStyle for logging--### DON'T--- ❌ Block the event loop-- ❌ Modify global state carelessly-- ❌ Ignore the return value-- ❌ Use conflicting numeric prefixes-- ❌ Create circular dependencies--## Accessing Context--```python-# Agent and context-agent = self.agent-context = agent.context--# Shared data (persists across agents)-context.data["key"] = value-value = context.data.get("key")--# Agent-specific data-agent.set_data("key", value)-value = agent.get_data("key")--# Configuration-config = agent.config-model = config.chat_model-```--## Testing Extensions--1. **Add your extension** to the appropriate hook point-2. **Restart Agent Zero** (extensions load at startup)-3. **Trigger the hook** by performing the related action-4. **Check logs** for your output or errors--## Next Steps--- Identify which hook point fits your use case-- Start with logging to understand data flow-- Keep extensions small and composablediff --git a/usr/skills/frameworks/agent-zero-dev/a0dev-create-project/SKILL.md b/usr/skills/frameworks/agent-zero-dev/a0dev-create-project/SKILL.mddeleted file mode 100644index 492dba212..000000000--- a/usr/skills/frameworks/agent-zero-dev/a0dev-create-project/SKILL.md+++ /dev/null@@ -1,342 +0,0 @@-----name: "a0dev-create-project"-description: "Set up project-specific configuration for Agent Zero workspaces."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["agent-zero-dev", "project", "configuration", "workspace"]-trigger_patterns:- - "create project"- - "new project"- - "setup project"- - "project config"- - "/a0dev-create-project"------# Agent Zero Dev: Create Project--Projects provide isolated workspaces with custom configuration, instructions, and skills specific to a codebase or task.--## Project Location--```-/path/to/your/project/-├── .a0proj/ # Agent Zero project config-│ ├── config.json # Project configuration-│ ├── instructions.md # Project-specific instructions-│ └── skills/ # Project-specific skills-│ └── custom-skill/-│ └── SKILL.md-└── <your-project-files>/ # Your actual project-```--## Configuration Files--### .a0proj/config.json--```json-{- "name": "My Project",- "description": "Brief project description",- "version": "1.0.0",-- "agent": {- "model": "anthropic/claude-sonnet-4-20250514",- "temperature": 0.7- },-- "tools": {- "allowed": ["*"],- "disabled": []- },-- "skills": {- "auto_load": ["project-specific-skill"],- "disabled": []- },-- "extensions": {- "enabled": [],- "disabled": []- },-- "paths": {- "work_dir": ".",- "output_dir": "./output"- }-}-```--### Configuration Fields--| Field | Type | Description |-|-------|------|-------------|-| `name` | string | Project display name |-| `description` | string | Brief description |-| `agent.model` | string | Default LLM model |-| `agent.temperature` | float | Response randomness |-| `tools.allowed` | array | Allowed tools (`["*"]` for all) |-| `tools.disabled` | array | Explicitly disabled tools |-| `skills.auto_load` | array | Skills to load automatically |-| `paths.work_dir` | string | Working directory |--### .a0proj/instructions.md--```markdown-# Project: [Project Name]--## Overview-[What this project does and its purpose]--## Tech Stack-- Language: [Python 3.12+]-- Framework: [FastAPI]-- Database: [PostgreSQL]-- Other: [Docker, Redis]--## Architecture-[Brief architecture description]--```-project/-├── api/ # API endpoints-├── services/ # Business logic-├── models/ # Data models-└── tests/ # Test files-```--## Coding Standards-- Follow [PEP 8 / Standard Style]-- Write tests for all functions-- Use type hints-- Document public APIs--## Important Files-- `api/main.py` - Entry point-- `services/core.py` - Core logic-- `config.py` - Configuration--## Commands-- `make dev` - Start development server-- `make test` - Run tests-- `make lint` - Run linter--## Notes-[Any special considerations or warnings]-```--## Complete Example: Python API Project--### .a0proj/config.json--```json-{- "name": "User API Service",- "description": "REST API for user management",- "version": "1.0.0",-- "agent": {- "model": "anthropic/claude-sonnet-4-20250514",- "temperature": 0.3- },-- "tools": {- "allowed": ["*"],- "disabled": ["browser_tool"]- },-- "skills": {- "auto_load": ["api-development", "testing"],- "disabled": []- },-- "paths": {- "work_dir": ".",- "output_dir": "./generated"- },-- "custom": {- "test_command": "pytest -v",- "lint_command": "ruff check .",- "database": "postgresql://localhost/userdb"- }-}-```--### .a0proj/instructions.md--```markdown-# Project: User API Service--## Overview-REST API service for user management with authentication, profiles, and permissions.--## Tech Stack-- Python 3.12-- FastAPI-- PostgreSQL-- SQLAlchemy (async)-- Pydantic v2-- pytest--## Architecture--```-src/-├── api/-│ ├── routes/ # API endpoints-│ ├── deps.py # Dependencies-│ └── main.py # FastAPI app-├── models/-│ ├── user.py # User model-│ └── base.py # Base model-├── services/-│ ├── auth.py # Authentication-│ └── user.py # User service-├── schemas/-│ └── user.py # Pydantic schemas-└── tests/- ├── conftest.py # Test fixtures- └── test_user.py # User tests-```--## Coding Standards-- PEP 8 compliance (enforced by ruff)-- Type hints on all functions-- Docstrings for public APIs-- 80%+ test coverage-- Async/await for I/O operations--## API Conventions-- RESTful endpoints-- JSON request/response-- Standard error format: `{"detail": "message"}`-- Auth via Bearer token--## Commands-```bash-# Development-uvicorn src.api.main:app --reload--# Testing-pytest -v --cov=src--# Linting-ruff check src/-ruff format src/-```--## Environment Variables-- `DATABASE_URL` - PostgreSQL connection string-- `SECRET_KEY` - JWT signing key-- `DEBUG` - Enable debug mode--## Important Notes-- Never commit `.env` files-- Run migrations before testing-- Use dependency injection for services-```--## Project-Specific Skills--Create skills that only apply to this project:--```-.a0proj/skills/-└── deploy-staging/- └── SKILL.md-```--```yaml-----name: "deploy-staging"-description: "Deploy this project to staging environment"-trigger_patterns:- - "deploy to staging"- - "staging deploy"------# Deploy to Staging--## Steps-1. Run tests: `pytest -v`-2. Build image: `docker build -t userapi:staging .`-3. Push: `docker push registry.example.com/userapi:staging`-4. Deploy: `kubectl apply -f k8s/staging/`--## Verification-- Check pods: `kubectl get pods -n staging`-- Check logs: `kubectl logs -n staging -l app=userapi`-- Test endpoint: `curl https://staging.example.com/health`-```--## Setting Up a New Project--### Quick Setup--1. **Create the config directory**:- ```bash- mkdir -p .a0proj/skills- ```--2. **Create config.json**:- ```bash- cat > .a0proj/config.json << 'EOF'- {- "name": "My Project",- "description": "Project description"- }- EOF- ```--3. **Create instructions.md**:- ```bash- cat > .a0proj/instructions.md << 'EOF'- # Project: My Project-- ## Overview- [Describe your project]-- ## Tech Stack- [List technologies]-- ## Commands- [List common commands]- EOF- ```--4. **Open project in Agent Zero**:- - Navigate to project directory- - Agent will auto-detect `.a0proj/`--## Best Practices--### DO--- ✅ Keep instructions concise but complete-- ✅ Document important file locations-- ✅ Include common commands-- ✅ List coding standards-- ✅ Update as project evolves--### DON'T--- ❌ Include sensitive data (secrets, keys)-- ❌ Write overly detailed instructions-- ❌ Forget to update after changes-- ❌ Create conflicting tool configurations--## Project Detection--Agent Zero detects projects by:-1. Looking for `.a0proj/` directory-2. Loading `config.json` for settings-3. Loading `instructions.md` for context-4. Discovering project-specific skills--## Next Steps--After setting up a project:-- Test that instructions are helpful-- Add project-specific skills as needed-- Refine configuration based on usage-- Keep documentation currentdiff --git a/usr/skills/frameworks/agent-zero-dev/a0dev-create-skill/SKILL.md b/usr/skills/frameworks/agent-zero-dev/a0dev-create-skill/SKILL.mddeleted file mode 100644index 722506e50..000000000--- a/usr/skills/frameworks/agent-zero-dev/a0dev-create-skill/SKILL.md+++ /dev/null@@ -1,275 +0,0 @@-----name: "a0dev-create-skill"-description: "Build reusable instruction bundles following the SKILL.md standard."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["agent-zero-dev", "skill", "instructions", "SKILL.md"]-trigger_patterns:- - "create skill"- - "new skill"- - "add skill"- - "build skill"- - "/a0dev-create-skill"------# Agent Zero Dev: Create Skill--Skills are reusable instruction bundles that guide the agent through specific tasks. They follow the SKILL.md standard with YAML frontmatter and markdown content.--## Skill Location--```-usr/skills/-├── default/ # System skills (don't modify)-├── custom/ # Your skills go here-│ └── my-skill/-│ ├── SKILL.md # Required: Main skill file-│ ├── scripts/ # Optional: Helper scripts-│ ├── templates/ # Optional: Templates-│ └── docs/ # Optional: Additional docs-└── frameworks/ # Multi-phase framework skills-```--## SKILL.md Format--```yaml-----name: "skill-name"-description: "Clear description of what this skill does and when to use it"-version: "1.0.0"-author: "Your Name"-tags: ["category1", "category2"]-trigger_patterns:- - "keyword that triggers"- - "another trigger phrase"- - "use skill-name"------# Skill Title--## When to Use-Describe the situations where this skill applies.--## The Process--### Step 1: First Action-Detailed instructions...--### Step 2: Second Action-More instructions...--## Examples-Show sample usage and expected outcomes.--## Tips-Additional guidance and best practices.-```--## Frontmatter Fields--| Field | Required | Description |-|-------|----------|-------------|-| `name` | Yes | Unique skill identifier (kebab-case) |-| `description` | Yes | One-line summary |-| `version` | No | Semantic version |-| `author` | No | Creator name |-| `tags` | No | Categorization tags |-| `trigger_patterns` | Yes | Phrases that activate this skill |--## Trigger Patterns--Trigger patterns are case-insensitive phrases that activate the skill:--```yaml-trigger_patterns:- - "deploy to production" # Exact phrase match- - "ship it" # Short trigger- - "production deploy" # Alternative phrasing- - "/deploy" # Command-style-```--**Best Practices:**-- Include 3-5 varied trigger phrases-- Mix formal and casual language-- Include command-style triggers (`/skill-name`)-- Avoid overly generic triggers--## Complete Example: Code Review Skill--```yaml-----name: "code-review"-description: "Perform thorough code review with focus on quality and best practices"-version: "1.0.0"-author: "Agent Zero Team"-tags: ["development", "review", "quality"]-trigger_patterns:- - "review code"- - "code review"- - "review this"- - "check my code"- - "/code-review"------# Code Review--Thorough code review focusing on quality, maintainability, and best practices.--## When to Use--- Before merging pull requests-- After completing a feature-- When refactoring existing code-- To learn from code patterns--## The Process--### Step 1: Understand Context--Before reviewing:-1. Identify the purpose of the code-2. Understand the broader system context-3. Note any constraints or requirements--### Step 2: Check Correctness--Review for:-- [ ] Logic errors-- [ ] Edge cases handled-- [ ] Error handling present-- [ ] Input validation--### Step 3: Assess Quality--Evaluate:-- [ ] Clear naming conventions-- [ ] Appropriate abstractions-- [ ] DRY (Don't Repeat Yourself)-- [ ] Single responsibility--### Step 4: Review Style--Check:-- [ ] Consistent formatting-- [ ] Meaningful comments-- [ ] Documentation updated-- [ ] Tests included--### Step 5: Provide Feedback--Structure feedback as:-- **Critical**: Must fix before merge-- **Important**: Should fix soon-- **Suggestion**: Nice to have improvements--## Output Format--```markdown-## Code Review: [File/Feature]--### Summary-[Brief overall assessment]--### Critical Issues-- [Issue 1]: [Location] - [Why it matters]--### Important Issues-- [Issue 1]: [Suggestion]--### Suggestions-- [Nice-to-have improvements]--### Strengths-- [What's done well]-```--## Tips--- Focus on the code, not the person-- Explain the "why" behind suggestions-- Acknowledge good patterns-- Be specific with line numbers/locations-```--## Adding Scripts--Skills can include helper scripts:--```-my-skill/-├── SKILL.md-└── scripts/- ├── helper.py- └── process.sh-```--Reference in SKILL.md:-```markdown-## Scripts--Run the helper script:-- `scripts/helper.py` - Processes input data-- `scripts/process.sh` - Sets up environment-```--## Adding Templates--Include reusable templates:--```-my-skill/-├── SKILL.md-└── templates/- └── output.md-```--Reference in SKILL.md:-```markdown-## Templates--Use `templates/output.md` as the base for your output format.-```--## Using the Generator Script--```bash-python usr/skills/frameworks/agent-zero-dev/scripts/create_skill.py \- code-review \- "Perform thorough code review with focus on quality"-```--Generates: `usr/skills/custom/code-review/SKILL.md`--## Skill Best Practices--### DO--- ✅ Write clear, actionable instructions-- ✅ Include examples and expected outputs-- ✅ Use checklists for multi-step processes-- ✅ Provide output format templates-- ✅ Test with real scenarios--### DON'T--- ❌ Write vague or ambiguous instructions-- ❌ Assume context the agent won't have-- ❌ Use overly generic trigger patterns-- ❌ Skip the "When to Use" section-- ❌ Forget to version your skills--## Testing Skills--1. Create the skill in `usr/skills/custom/`-2. Ask the agent using a trigger phrase-3. Verify the skill loads correctly-4. Test with varied inputs-5. Refine based on results--## Next Steps--After creating a skill:-- Test with multiple trigger phrases-- Gather feedback on clarity-- Iterate on instructions-- Consider sharing with the communitydiff --git a/usr/skills/frameworks/agent-zero-dev/a0dev-create-subordinate/SKILL.md b/usr/skills/frameworks/agent-zero-dev/a0dev-create-subordinate/SKILL.mddeleted file mode 100644index 1e03e5fa3..000000000--- a/usr/skills/frameworks/agent-zero-dev/a0dev-create-subordinate/SKILL.md+++ /dev/null@@ -1,295 +0,0 @@-----name: "a0dev-create-subordinate"-description: "Create specialized agent profiles (subordinates) for Agent Zero."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["agent-zero-dev", "subordinate", "agent", "profile", "specialized"]-trigger_patterns:- - "create subordinate"- - "new subordinate"- - "specialized agent"- - "agent profile"- - "/a0dev-create-subordinate"------# Agent Zero Dev: Create Subordinate--Subordinates are specialized agents with custom prompts and configurations. They can be called by the main agent to handle domain-specific tasks.--## Subordinate Location--```-agents/-├── default/ # Default agent profile-├── developer/ # Developer specialist-├── researcher/ # Research specialist-└── your-profile/ # Your custom profile- ├── agent.json # Profile configuration- └── prompts/- ├── system.md # System prompt- └── tools.md # Tool-specific prompts-```--## Profile Structure--### agent.json--```json-{- "name": "Specialized Agent",- "description": "What this subordinate specializes in",- "model": "anthropic/claude-sonnet-4-20250514",- "temperature": 0.7,- "max_tokens": 4000,- "allowed_tools": [- "code_execution_tool",- "search_engine",- "memory_tool"- ],- "prompts": {- "system": "prompts/system.md"- }-}-```--### Configuration Fields--| Field | Type | Description |-|-------|------|-------------|-| `name` | string | Display name |-| `description` | string | What this agent does |-| `model` | string | LLM model to use |-| `temperature` | float | Response randomness (0-1) |-| `max_tokens` | int | Max response length |-| `allowed_tools` | array | Tools this agent can use |-| `prompts.system` | string | Path to system prompt |--## System Prompt Template--```markdown-# prompts/system.md--# [Agent Name]--## Your Role-You are a specialized agent focused on [domain].--## Expertise-- Deep knowledge of [specific area]-- Experience with [tools/technologies]-- Understanding of [concepts]--## Capabilities-You can use these tools:-- `code_execution_tool` - Run code-- `search_engine` - Search the web-- `memory_tool` - Store and recall information--## Process-When given a task:-1. Analyze the request-2. Break down into steps-3. Use appropriate tools-4. Verify results-5. Return structured response--## Output Format-Always respond with clear, structured output:-- Summary of what was done-- Key findings or results-- Any issues encountered-- Recommendations if applicable--## Constraints-- Stay focused on [domain]-- Ask for clarification if needed-- Report errors clearly-- Don't exceed your expertise-```--## Complete Example: Developer Profile--### agents/developer/agent.json--```json-{- "name": "Developer Agent",- "description": "Specialized in software development, code review, and debugging",- "model": "anthropic/claude-sonnet-4-20250514",- "temperature": 0.3,- "max_tokens": 8000,- "allowed_tools": [- "code_execution_tool",- "search_engine",- "memory_tool",- "skills_tool"- ],- "prompts": {- "system": "prompts/system.md"- }-}-```--### agents/developer/prompts/system.md--```markdown-# Developer Agent--## Your Role-You are a senior software developer with expertise in multiple languages and frameworks. You write clean, efficient, and well-documented code.--## Expertise-- Languages: Python, JavaScript, TypeScript, Go, Rust-- Frameworks: FastAPI, React, Node.js-- Practices: TDD, code review, debugging-- Tools: Git, Docker, CI/CD--## Capabilities-- Write and refactor code-- Debug issues systematically-- Review code for quality-- Explain technical concepts-- Create tests--## Process-1. Understand the requirement-2. Plan the implementation-3. Write clean code-4. Test thoroughly-5. Document appropriately--## Code Standards-- Use meaningful names-- Write clear comments-- Handle errors gracefully-- Follow language conventions-- Keep functions focused--## Output Format-When providing code:-```language-// Code with comments-```--When explaining:-- Clear step-by-step breakdown-- Code examples where helpful-- Links to documentation-```--## Calling Subordinates--From the main agent or tools:--```python-# Using call_subordinate tool-call_subordinate(- profile="developer",- message="Review this Python function for bugs and improvements",- reset="false"-)-```--### Parameters--| Param | Description |-|-------|-------------|-| `profile` | Name of the subordinate profile directory |-| `message` | Task to delegate to the subordinate |-| `reset` | "true" to reset subordinate state, "false" to continue |--## Tool Restrictions--Limit tools based on subordinate purpose:--### Research Agent (read-only)-```json-"allowed_tools": [- "search_engine",- "memory_tool"-]-```--### Developer Agent (code execution)-```json-"allowed_tools": [- "code_execution_tool",- "search_engine",- "memory_tool"-]-```--### Admin Agent (full access)-```json-"allowed_tools": [- "*"-]-```--## Subordinate Best Practices--### DO--- ✅ Keep profiles focused on specific domains-- ✅ Limit tool access to what's needed-- ✅ Write clear, specific system prompts-- ✅ Include output format examples-- ✅ Define constraints and boundaries--### DON'T--- ❌ Create overly broad profiles-- ❌ Give unnecessary tool access-- ❌ Write vague system prompts-- ❌ Forget to handle edge cases-- ❌ Skip testing with real tasks--## Subordinate Communication--### From Main Agent-```-"Delegate this research task to the researcher subordinate"-→ Uses call_subordinate tool with profile="researcher"-```--### Response Flow-```-Main Agent → call_subordinate → Subordinate executes → Result returned-```--## Testing Subordinates--1. Create the profile directory and files-2. Restart Agent Zero-3. Ask main agent to delegate a task:- ```- "Use the developer subordinate to review this code: ..."- ```-4. Verify the subordinate:- - Uses correct model- - Has proper tool access- - Follows system prompt- - Returns expected output format--## Sharing Context--Subordinates share context with the main agent:--```python-# Context is shared-context = agent.context--# Data persists-context.data["shared_key"] = value--# Subordinate can read/write-value = context.data.get("shared_key")-```--## Next Steps--After creating a subordinate:-- Test with various task types-- Refine the system prompt based on results-- Adjust tool access as needed-- Document use casesdiff --git a/usr/skills/frameworks/agent-zero-dev/a0dev-create-tool/SKILL.md b/usr/skills/frameworks/agent-zero-dev/a0dev-create-tool/SKILL.mddeleted file mode 100644index 205606aba..000000000--- a/usr/skills/frameworks/agent-zero-dev/a0dev-create-tool/SKILL.md+++ /dev/null@@ -1,231 +0,0 @@-----name: "a0dev-create-tool"-description: "Create new agent capabilities (tools) for Agent Zero."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["agent-zero-dev", "tool", "capability", "development"]-trigger_patterns:- - "create tool"- - "new tool"- - "add tool"- - "build tool"- - "/a0dev-create-tool"------# Agent Zero Dev: Create Tool--Tools are the primary way agents interact with the world. Each tool inherits from the `Tool` base class and provides capabilities like web search, code execution, file manipulation, etc.--## Tool Location--```-python/tools/-├── code_execution_tool.py-├── search_engine.py-├── call_subordinate.py-├── memory_tool.py-└── your_tool.py ← New tools go here-```--## Tool Structure--```python-# python/tools/my_tool.py-from python.helpers.tool import Tool, Response--class MyTool(Tool):- """- Brief description of what this tool does.-- Arguments (tool_args):- - arg1: Description of first argument- - arg2: Description of second argument (optional)- """-- async def execute(self, **kwargs) -> Response:- # Get arguments (kwargs takes priority, fallback to self.args)- arg1 = kwargs.get("arg1") or self.args.get("arg1")- arg2 = kwargs.get("arg2") or self.args.get("arg2", "default")-- try:- # Tool logic here- result = await self.do_work(arg1, arg2)-- return Response(- message=result,- break_loop=False # True to end agent loop- )- except Exception as e:- return Response(- message=f"Error: {e}",- break_loop=False- )-- async def do_work(self, arg1, arg2):- # Implementation- return f"Processed {arg1} with {arg2}"-```--## Response Object--```python-Response(- message: str, # Result message shown to agent- break_loop: bool, # True = end agent loop (task complete)- additional: dict = {} # Extra data (hints, metadata)-)-```--## Accessing Agent Context--```python-async def execute(self, **kwargs) -> Response:- # Access the agent- agent = self.agent-- # Access shared context (persists across agents)- context = agent.context-- # Store/retrieve data- context.data["my_key"] = "my_value"- value = context.data.get("my_key")-- # Access agent configuration- config = agent.config-```--## Tool Best Practices--### DO--- ✅ Document arguments in class docstring-- ✅ Use `Response` for all returns-- ✅ Handle errors gracefully (return error message, don't crash)-- ✅ Use kwargs fallback to self.args-- ✅ Make operations async when possible-- ✅ Use type hints--### DON'T--- ❌ Raise unhandled exceptions-- ❌ Block the event loop (use async)-- ❌ Hardcode paths or values-- ❌ Ignore optional arguments-- ❌ Print directly (use Response or logging)--## Complete Example: Data Processor--```python-# python/tools/data_processor.py-from python.helpers.tool import Tool, Response-import json--class DataProcessor(Tool):- """- Process and transform JSON data structures.-- Arguments (tool_args):- - operation: The operation (filter, sort, map)- - data: JSON string to process- - key: Key to operate on- - value: Value for filter operation (optional)- """-- async def execute(self, **kwargs) -> Response:- try:- operation = kwargs.get("operation") or self.args.get("operation", "")- data_str = kwargs.get("data") or self.args.get("data", "[]")- key = kwargs.get("key") or self.args.get("key")- value = kwargs.get("value") or self.args.get("value")-- data = json.loads(data_str)-- if operation == "filter":- result = [item for item in data if item.get(key) == value]- elif operation == "sort":- result = sorted(data, key=lambda x: x.get(key, ""))- elif operation == "map":- result = [item.get(key) for item in data]- else:- return Response(- message=f"Unknown operation: {operation}",- break_loop=False- )-- return Response(- message=json.dumps(result, indent=2),- break_loop=False- )-- except json.JSONDecodeError as e:- return Response(message=f"Invalid JSON: {e}", break_loop=False)- except Exception as e:- return Response(message=f"Error: {e}", break_loop=False)-```--## Using the Generator Script--```bash-python usr/skills/frameworks/agent-zero-dev/scripts/create_tool.py \- DataProcessor \- "Process and transform JSON data structures"-```--This generates boilerplate at `python/tools/data_processor.py`.--## Tool Registration--Tools are auto-discovered by filename convention:-- Filename: `snake_case.py` (e.g., `data_processor.py`)-- Class name: `PascalCase` (e.g., `DataProcessor`)-- Tool name (for agent): derived from class name--## Testing Your Tool--1. **Restart Agent Zero** (tools load at startup)-2. **Ask the agent** to use your tool:- ```- "Use the data_processor tool to sort this JSON by name: [{"name": "z"}, {"name": "a"}]"- ```-3. **Check logs** for errors: `docker logs -f agent-zero`--## Common Patterns--### Async HTTP Request--```python-import aiohttp--async def fetch_data(self, url):- async with aiohttp.ClientSession() as session:- async with session.get(url) as response:- return await response.text()-```--### File Operations--```python-from python.helpers import files--content = files.read_file("path/to/file")-files.write_file("path/to/file", content)-exists = files.exists("path/to/file")-```--### Logging--```python-from python.helpers.print_style import PrintStyle--PrintStyle.hint("Info message")-PrintStyle.warning("Warning message")-PrintStyle.error("Error message")-```--## Next Steps--After creating your tool:-- Test thoroughly with different inputs-- Document edge cases-- Consider error messages for users-- Add to project documentation if significantdiff --git a/usr/skills/frameworks/agent-zero-dev/a0dev-quickstart/SKILL.md b/usr/skills/frameworks/agent-zero-dev/a0dev-quickstart/SKILL.mddeleted file mode 100644index d3af4dbd2..000000000--- a/usr/skills/frameworks/agent-zero-dev/a0dev-quickstart/SKILL.md+++ /dev/null@@ -1,142 +0,0 @@-----name: "a0dev-quickstart"-description: "5-minute quickstart guide to extending Agent Zero."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["agent-zero-dev", "quickstart", "getting-started", "tutorial"]-trigger_patterns:- - "quickstart"- - "getting started"- - "start extending"- - "how to extend"- - "/a0dev-quickstart"------# Agent Zero Dev: Quickstart--Get started extending Agent Zero in 5 minutes.--## Choose Your Extension Point--| Want To | Use | Location |-|---------|-----|----------|-| Add agent capability | **Tool** | `python/tools/` |-| Hook lifecycle events | **Extension** | `python/extensions/<hook>/` |-| Create instruction bundle | **Skill** | `usr/skills/custom/<name>/` |-| Add Web UI endpoint | **API** | `python/api/` |-| Create specialized agent | **Subordinate** | `agents/<profile>/` |-| Configure project | **Project** | `.a0proj/` |--## Quick Commands--```bash-# Create a new tool-python usr/skills/frameworks/agent-zero-dev/scripts/create_tool.py MyTool "Description"--# Create an extension-python usr/skills/frameworks/agent-zero-dev/scripts/create_extension.py agent_init MyExt "Description"--# Create a skill-python usr/skills/frameworks/agent-zero-dev/scripts/create_skill.py my-skill "Description"--# Create an API endpoint-python usr/skills/frameworks/agent-zero-dev/scripts/create_api.py MyEndpoint "Description"-```--## Framework Architecture--```-Agent Zero Framework-├── python/-│ ├── tools/ # Agent capabilities (inherit from Tool)-│ ├── extensions/ # Lifecycle hooks (numbered execution)-│ ├── api/ # FastAPI endpoints (inherit from ApiHandler)-│ └── helpers/ # Utility functions and base classes-├── usr/skills/-│ ├── default/ # Default skills-│ ├── custom/ # Your skills go here-│ └── frameworks/ # Multi-phase framework skills-├── agents/ # Subordinate profiles-└── memory/ # FAISS vector memory-```--## Key Patterns--1. **Extensions execute in numeric order** (`_10_*.py`, `_20_*.py`)-2. **Tools inherit from `Tool`** with async `execute()` method-3. **Skills use YAML frontmatter** + markdown content-4. **APIs inherit from `ApiHandler`** with `process()` method-5. **Everything is async/await** for non-blocking operations--## Minimal Examples--### Minimal Tool--```python-# python/tools/hello_tool.py-from python.helpers.tool import Tool, Response--class HelloTool(Tool):- async def execute(self, name="World", **kwargs) -> Response:- return Response(message=f"Hello, {name}!", break_loop=False)-```--### Minimal Extension--```python-# python/extensions/agent_init/_99_my_ext.py-from python.helpers.extension import Extension--class MyExtension(Extension):- async def execute(self, **kwargs):- print("Agent initialized!")- return kwargs.get("data", {})-```--### Minimal Skill--```yaml-----name: "my-skill"-description: "What this skill does"-trigger_patterns:- - "trigger phrase"------# My Skill--Instructions for the agent to follow.-```--### Minimal API--```python-# python/api/my_endpoint.py-from python.helpers.api import ApiHandler, Request--class MyEndpoint(ApiHandler):- async def process(self, input: dict, request: Request) -> dict:- return {"message": "Hello from API!"}-```--## Development Workflow--```-1. Choose extension point → Tool, Extension, Skill, API, etc.-2. Generate boilerplate → Use scripts/ generators-3. Implement logic → Fill in your code-4. Test → Restart Agent Zero and verify-5. Iterate → Refine based on results-```--## Next Steps--- `/a0dev-create-tool` — Deep dive into tools-- `/a0dev-create-extension` — Deep dive into extensions-- `/a0dev-create-skill` — Deep dive into skills-- `/a0dev-create-api` — Deep dive into APIs-- `/a0dev-workflow` — Full development workflow--## Need Help?--Say "help me create a [tool/extension/skill/api]" and I'll guide you through it!diff --git a/usr/skills/frameworks/agent-zero-dev/a0dev-workflow/SKILL.md b/usr/skills/frameworks/agent-zero-dev/a0dev-workflow/SKILL.mddeleted file mode 100644index b0bd72c52..000000000--- a/usr/skills/frameworks/agent-zero-dev/a0dev-workflow/SKILL.md+++ /dev/null@@ -1,322 +0,0 @@-----name: "a0dev-workflow"-description: "Full development workflow for building Agent Zero features."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["agent-zero-dev", "workflow", "development", "process"]-trigger_patterns:- - "development workflow"- - "dev workflow"- - "build feature"- - "extend agent zero"- - "/a0dev-workflow"------# Agent Zero Dev: Development Workflow--Complete workflow for building features for Agent Zero framework.--## Workflow Phases--```-1. Brainstorm → 2. Plan → 3. Scaffold → 4. Implement → 5. Test → 6. Refine-```--## Phase 1: Brainstorm--### Define the Problem--**Questions to answer:**-- What problem does this solve?-- Who benefits from this feature?-- What's the expected outcome?--### Identify Extension Point--| If you need to... | Use |-|-------------------|-----|-| Add agent capability | Tool |-| Hook into lifecycle | Extension |-| Create instruction bundle | Skill |-| Add Web UI endpoint | API |-| Create specialized agent | Subordinate |-| Configure workspace | Project |--### Review Existing Patterns--Before building, examine similar code:-- `python/tools/` — Tool patterns-- `python/extensions/` — Extension patterns-- `usr/skills/` — Skill patterns-- `python/api/` — API patterns--## Phase 2: Plan--### Break Into Tasks--Each task should be:-- Small (2-5 minutes to complete)-- Testable (clear verification)-- Independent (minimal dependencies)--### Example Task Breakdown--**Feature:** "Add weather lookup tool"--```markdown-## Tasks--1. [ ] Create tool file structure- - File: python/tools/weather_tool.py- - Verify: File exists with boilerplate--2. [ ] Implement weather API integration- - Use aiohttp for async requests- - Verify: Can fetch weather data--3. [ ] Add error handling- - Handle API errors, invalid locations- - Verify: Graceful error messages--4. [ ] Test with agent- - Ask agent to get weather- - Verify: Correct response format--5. [ ] Document the tool- - Add docstring with args- - Verify: Documentation complete-```--### Identify Dependencies--```-What must exist first?-├── API keys configured?-├── Dependencies installed?-├── Related code ready?-└── Test data available?-```--## Phase 3: Scaffold--### Use Generator Scripts--```bash-# Generate boilerplate-python usr/skills/frameworks/agent-zero-dev/scripts/create_tool.py WeatherTool "Look up weather for a location"-```--### Available Generators--| Script | Creates |-|--------|---------|-| `create_tool.py` | Tool in `python/tools/` |-| `create_extension.py` | Extension in `python/extensions/` |-| `create_skill.py` | Skill in `usr/skills/custom/` |-| `create_api.py` | API in `python/api/` |--### Review Generated Code--After generation:-1. Open the created file-2. Review the boilerplate-3. Identify what to fill in-4. Note the patterns used--## Phase 4: Implement--### Follow Test-Driven Development--```-1. Write test (what should happen)-2. Run test (should fail)-3. Write code (minimal to pass)-4. Run test (should pass)-5. Refactor (improve quality)-```--### Implementation Checklist--- [ ] Follow existing code patterns-- [ ] Add proper error handling-- [ ] Use type hints-- [ ] Write clear docstrings-- [ ] Keep functions focused-- [ ] Use async where appropriate--### Common Patterns--**Accessing Context:**-```python-context = self.agent.context-data = context.data-```--**Error Handling:**-```python-try:- result = await risky_operation()-except Exception as e:- return Response(message=f"Error: {e}", break_loop=False)-```--**Async Operations:**-```python-async with aiohttp.ClientSession() as session:- async with session.get(url) as response:- return await response.json()-```--## Phase 5: Test--### Manual Testing--1. **Restart Agent Zero** (code loads at startup)-2. **Trigger your feature**:- ```- "Use the weather tool to check weather in Seattle"- ```-3. **Verify behavior**:- - Correct response?- - Errors handled?- - Performance acceptable?--### Check Logs--```bash-# Docker logs-docker logs -f agent-zero--# Or check log files-tail -f logs/agent.log-```--### Test Edge Cases--- Invalid inputs-- Missing data-- Network failures-- Concurrent access--## Phase 6: Refine--### Code Review Checklist--- [ ] Follows project conventions?-- [ ] Error handling complete?-- [ ] Documentation updated?-- [ ] No hardcoded values?-- [ ] Performance acceptable?--### Refactoring--After it works:-- Simplify complex logic-- Extract reusable functions-- Improve naming-- Add missing tests--### Documentation--Update as needed:-- Code docstrings-- Skill instructions-- README files-- API documentation--## Complete Example: Weather Tool--### Phase 1: Brainstorm-- **Problem:** Agent can't check weather-- **Extension Point:** Tool-- **Similar Code:** `search_engine.py`--### Phase 2: Plan-```markdown-1. [ ] Generate tool boilerplate-2. [ ] Add weather API integration-3. [ ] Implement execute() method-4. [ ] Add error handling-5. [ ] Test with agent-```--### Phase 3: Scaffold-```bash-python scripts/create_tool.py WeatherLookup "Get weather for a location"-```--### Phase 4: Implement-```python-# python/tools/weather_lookup.py-from python.helpers.tool import Tool, Response-import aiohttp--class WeatherLookup(Tool):- """- Look up current weather for a location.-- Arguments:- - location: City name or coordinates- """-- async def execute(self, location="", **kwargs) -> Response:- location = location or kwargs.get("location") or self.args.get("location", "")-- if not location:- return Response(message="Please provide a location", break_loop=False)-- try:- weather = await self.fetch_weather(location)- return Response(- message=f"Weather in {location}: {weather['description']}, {weather['temp']}°F",- break_loop=False- )- except Exception as e:- return Response(message=f"Could not fetch weather: {e}", break_loop=False)-- async def fetch_weather(self, location):- # Implementation using weather API- async with aiohttp.ClientSession() as session:- url = f"https://api.weather.example/v1?q={location}"- async with session.get(url) as response:- return await response.json()-```--### Phase 5: Test-```-User: "What's the weather in Seattle?"-Agent: Uses weather_lookup tool-Result: "Weather in Seattle: Partly cloudy, 58°F"-```--### Phase 6: Refine-- Add caching for repeated lookups-- Support metric/imperial units-- Add forecast option--## Quick Reference--### Extension Points-- **Tools:** `python/tools/`-- **Extensions:** `python/extensions/<hook>/`-- **Skills:** `usr/skills/custom/`-- **APIs:** `python/api/`-- **Subordinates:** `agents/<profile>/`-- **Projects:** `.a0proj/`--### Key Files-- `python/helpers/tool.py` — Tool base class-- `python/helpers/extension.py` — Extension base class-- `python/helpers/api.py` — API base class--### Commands-- Restart to reload code-- Check logs for errors-- Test with real interactions--## Next Steps--Ready to build? Start with:-1. `/a0dev-quickstart` — Quick overview-2. `/a0dev-create-tool` — Build a tool-3. `/a0dev-create-skill` — Create a skilldiff --git a/usr/skills/frameworks/agent-zero-dev/docs/architecture.md b/usr/skills/frameworks/agent-zero-dev/docs/architecture.mddeleted file mode 100644index 902810690..000000000--- a/usr/skills/frameworks/agent-zero-dev/docs/architecture.md+++ /dev/null@@ -1,296 +0,0 @@-# Agent Zero Architecture--This document provides an in-depth look at Agent Zero's architecture.--## Core Philosophy--Agent Zero is designed around the principle of **composable intelligence**:-- Small, focused components that work together-- Clear interfaces between layers-- Extensible at every level-- Async-first for responsiveness--## Component Layers--```-┌─────────────────────────────────────────────┐-│ Web UI (Alpine.js) │-│ - Chat interface │-│ - File management │-│ - Memory dashboard │-└─────────────────────────────────────────────┘- │-┌─────────────────────────────────────────────┐-│ API Layer (FastAPI) │-│ - REST endpoints │-│ - WebSocket for streaming │-│ - File uploads/downloads │-└─────────────────────────────────────────────┘- │-┌─────────────────────────────────────────────┐-│ Agent Core │-│ - Message loop │-│ - LLM interaction │-│ - Context management │-└─────────────────────────────────────────────┘- │-┌─────────────────────────────────────────────┐-│ Extension Points │-│ - agent_init │-│ - message_loop_* │-│ - response_stream_* │-│ - tool_execute_* │-└─────────────────────────────────────────────┘- │-┌─────────────────────────────────────────────┐-│ Tool Layer │-│ - Built-in tools │-│ - Custom tools │-│ - External tool calls │-└─────────────────────────────────────────────┘- │-┌─────────────────────────────────────────────┐-│ Skill System │-│ - SKILL.md based │-│ - Progressive disclosure │-│ - Script execution │-└─────────────────────────────────────────────┘- │-┌─────────────────────────────────────────────┐-│ Memory Layer │-│ - FAISS vector store │-│ - Shared AgentContext │-│ - Archive/recovery │-└─────────────────────────────────────────────┘-```--## Data Flow--### Message Processing Flow--1. **User Input** → API endpoint receives message-2. **Extension: message_loop_start** → Pre-processing-3. **Context Retrieval** → Get or create AgentContext-4. **Extension: before_main_llm_call** → Modify prompts-5. **LLM Call** → Send to language model-6. **Extension: response_stream_start** → Begin streaming-7. **Response Chunks** → Stream to UI via WebSocket-8. **Extension: response_stream_chunk** → Transform output-9. **Extension: response_stream_end** → Finalize-10. **Tool Execution** (if needed)- - Extension: tool_execute_before- - Tool.execute()- - Extension: tool_execute_after-11. **Response to User** → Complete message--### Context Sharing--All agents in a conversation share the same `AgentContext`:--```python-# Main agent stores data-self.agent.context.data["user_preference"] = "dark_mode"--# Subordinate can access the same data-preference = self.agent.context.data.get("user_preference")-```--This enables:-- Persistent memory across agent switches-- Shared state between parent and subordinates-- Session-wide configuration--## Extension System--Extensions are Python classes that hook into specific lifecycle points.--### Execution Order--Extensions execute in numeric order based on filename prefix:--```-_10_first.py # Runs first-_20_second.py # Runs second-_30_third.py # Runs third-```--### Hook Points--| Hook | Timing | Use Case |-|------|--------|----------|-| `agent_init` | Agent creation | Configuration loading |-| `message_loop_start` | Before processing | Input validation |-| `message_loop_end` | After processing | Cleanup |-| `before_main_llm_call` | Before LLM | Prompt modification |-| `response_stream_start` | Stream begins | Initialize handlers |-| `response_stream_chunk` | Per chunk | Transform output |-| `response_stream_end` | Stream complete | Finalize |-| `tool_execute_before` | Before tool | Validation |-| `tool_execute_after` | After tool | Post-processing |--## Memory System--### Vector Memory--FAISS-based vector storage for semantic search:--```python-# Save to memory-memory_save(text="Important information")--# Load from memory-results = memory_load(query="Find important info")-```--### Archive System--Soft-delete with recovery capability:--```python-# Delete (moves to archive)-memory_delete(ids=["id1", "id2"])--# Recover from archive-# (via memory dashboard or direct DB access)-```--## Skill System--Skills follow the SKILL.md standard:--### Progressive Disclosure--1. **Level 1: Metadata** - Always loaded (name, description, tags)-2. **Level 2: Full Content** - Loaded on demand (instructions)-3. **Level 3: Scripts** - Executed as needed--### Skill Loading--```-usr/skills/-├── default/ # System skills (loaded first)-├── custom/ # User-created skills-└── frameworks/ # Multi-phase framework skills-```--## Subordinate System--Specialized agents with custom profiles:--```-agents/-├── default/ # Default profile-├── developer/ # Coding specialist-├── researcher/ # Research specialist-└── [custom]/ # Your profiles-```--Each profile contains:-- `agent.json` - Configuration-- `prompts/system.md` - System prompt-- `prompts/subordinates.md` - Delegation prompts--## Security Considerations--### Sandboxing--- Tools run in isolated Python environment-- File system access limited to /a0 directory-- Network access controlled by tool permissions--### Secrets Management--Secrets stored in environment variables:--```python-# Access secrets-from python.helpers import secrets-api_key = secrets.get("API_KEY")-```--## Performance Optimization--### Async Patterns--All I/O is async to prevent blocking:--```python-# Concurrent execution-tasks = [fetch_data(url) for url in urls]-results = await asyncio.gather(*tasks)-```--### Caching--- Skill content cached after first load-- Context data persisted in memory-- Vector embeddings cached in FAISS--### Streaming--LLM responses stream to UI for perceived performance:--```python-for chunk in llm_stream(prompt):- await send_to_ui(chunk)-```--## Extension Points Deep Dive--### Creating Custom Hooks--You can create custom hook points for your extensions:--```python-# Define hook in your extension-await extension.call_extensions("my_custom_hook", agent=agent, data=data)-```--### Inter-Extension Communication--Extensions can communicate via context data:--```python-# Extension A sets data-self.agent.context.data["ext_a_result"] = result--# Extension B reads it-result = self.agent.context.data.get("ext_a_result")-```--## Debugging and Development--### Logging--Use PrintStyle for consistent logging:--```python-PrintStyle.hint("Informational message")-PrintStyle.warning("Warning message")-PrintStyle.error("Error message")-PrintStyle.bold("Important message")-```--### Debugging Extensions--Add debug output to trace execution:--```python-async def execute(self, **kwargs):- PrintStyle.hint(f"Extension {self.__class__.__name__} executing")- PrintStyle.hint(f"Received kwargs: {kwargs}")- # ... logic ...-```--### Testing Tools--Test tools in isolation:--```python-import asyncio-from python.tools.my_tool import MyTool--tool = MyTool()-result = asyncio.run(tool.execute(param="value"))-print(result.message)-```diff --git a/usr/skills/frameworks/agent-zero-dev/docs/best-practices.md b/usr/skills/frameworks/agent-zero-dev/docs/best-practices.mddeleted file mode 100644index ddda33509..000000000--- a/usr/skills/frameworks/agent-zero-dev/docs/best-practices.md+++ /dev/null@@ -1,450 +0,0 @@-# Best Practices for Agent Zero Development--## Code Style--### Python Conventions--Follow PEP 8 with these specifics:--```python-# Use type hints-def process_data(data: dict) -> str:- pass--# Async everywhere-async def fetch_data() -> dict:- pass--# Clear variable names-user_input = "" # Good-ui = "" # Avoid-```--### Documentation--Every public class and method needs a docstring:--```python-class MyTool(Tool):- """- Brief description of tool purpose.-- Arguments (tool_args):- - arg1: Description of first argument- - arg2: Description of second argument-- Returns:- Response object with result- """-```--## Error Handling--### Graceful Degradation--Tools should never crash the agent:--```python-async def execute(self, **kwargs) -> Response:- try:- result = await self.risky_operation()- return Response(message=result, break_loop=False)- except Exception as e:- # Log for debugging- PrintStyle.error(f"Operation failed: {e}")- # Return graceful error to user- return Response(message=f"Error: {e}", break_loop=False)-```--### Specific Exceptions--Catch specific exceptions when possible:--```python-try:- data = json.loads(json_str)-except json.JSONDecodeError as e:- return Response(message=f"Invalid JSON: {e}", break_loop=False)-except Exception as e:- return Response(message=f"Unexpected error: {e}", break_loop=False)-```--## Performance--### Avoid Blocking Operations--Never use synchronous I/O in async methods:--```python-# Bad - blocks event loop-data = requests.get(url).json()--# Good - async-import aiohttp-async with aiohttp.ClientSession() as session:- async with session.get(url) as response:- data = await response.json()-```--### Batch Operations--Process multiple items concurrently:--```python-# Process all at once-tasks = [process_item(item) for item in items]-results = await asyncio.gather(*tasks, return_exceptions=True)--# Handle errors individually-for item, result in zip(items, results):- if isinstance(result, Exception):- PrintStyle.error(f"Failed to process {item}: {result}")- else:- successes.append(result)-```--## Security--### Input Validation--Always validate user input:--```python-async def execute(self, **kwargs) -> Response:- user_input = kwargs.get("input", "")-- # Validate- if not user_input:- return Response(message="Error: input is required", break_loop=False)-- if len(user_input) > 10000:- return Response(message="Error: input too large", break_loop=False)-- # Process- result = await self.process(user_input)-```--### Path Safety--Use secure paths:--```python-from werkzeug.utils import secure_filename-from python.helpers import files--# Sanitize filenames-filename = secure_filename(uploaded_file.filename)--# Use absolute paths-full_path = files.get_abs_path("tmp/uploads", filename)-```--### Secrets--Never hardcode credentials:--```python-# Bad-api_key = "sk-1234567890"--# Good-from python.helpers import secrets-api_key = secrets.get("API_KEY")-```--## Testing--### Unit Tests--Write tests for tools:--```python-import pytest-from python.tools.my_tool import MyTool--async def test_my_tool_success():- tool = MyTool()- result = await tool.execute(param="valid_value")- assert "success" in result.message--async def test_my_tool_error():- tool = MyTool()- result = await tool.execute(param="")- assert "error" in result.message.lower()-```--### Integration Tests--Test full workflows:--```python-async def test_tool_integration():- # Setup- context = create_test_context()-- # Execute- tool = MyTool()- tool.agent = MockAgent(context)- result = await tool.execute(data="test")-- # Verify- assert result.break_loop is False- assert "result" in context.data-```--## Memory Management--### Context Data--Use context for session-wide state:--```python-# Store data-self.agent.context.data["processed_items"] = items--# Retrieve with default-items = self.agent.context.data.get("processed_items", [])-```--### Memory Operations--Save important information:--```python-from python.helpers.memory import memory_save--# Save with metadata-memory_save(- text="Important fact",- metadata={"category": "user_preference", "timestamp": time.time()}-)-```--## Tool Design--### Single Responsibility--Each tool should do one thing well:--```python-# Good: WebSearch tool only searches-class WebSearch(Tool):- async def execute(self, **kwargs):- query = kwargs.get("query")- results = await search_web(query)- return Response(message=format_results(results))--# Bad: WebSearchAndSummarize does too much-```--### Composable Tools--Tools should work together:--```python-# SearchTool finds information-results = await search_tool.execute(query="Python async")--# SummaryTool summarizes it-summary = await summary_tool.execute(text=results.message)-```--## Extension Design--### Minimal Interference--Extensions should be lightweight:--```python-# Good: Quick check and return-async def execute(self, **kwargs):- if not self.should_process(kwargs):- return kwargs.get("data", {})- # Process...--# Bad: Heavy processing in extension-async def execute(self, **kwargs):- # Don't do this - slows down every message- result = await heavy_computation()-```--### Data Preservation--Always return data unless modifying:--```python-# Good: Returns data even if not modified-async def execute(self, **kwargs):- data = kwargs.get("data", {})- # Do something...- return data--# Bad: Returns None-async def execute(self, **kwargs):- data = kwargs.get("data", {})- # Do something...- # Missing return!-```--## API Design--### RESTful Endpoints--Follow REST conventions:--```python-# GET for retrieval-async def _handle_get(self, input, context):- item_id = input.get("id")- item = await self.get_item(item_id)- return {"data": item}--# POST for creation-async def _handle_post(self, input, request, context):- data = input.get("data")- created = await self.create_item(data)- return {"data": created, "created": True}-```--### Consistent Responses--Return consistent structures:--```python-# Success-{- "success": True,- "data": {...},- "context": "ctx-id"-}--# Error-{- "success": False,- "error": "Error message",- "context": "ctx-id"-}-```--## Skill Design--### Clear Instructions--Skills should have actionable steps:--```markdown-## The Process--### Step 1: Analyze Input-- Check for required parameters-- Validate data format--### Step 2: Process Data-- Apply transformation X-- Verify intermediate result--### Step 3: Return Output-- Format as JSON-- Include metadata-```--### Trigger Patterns--Use specific trigger patterns:--```yaml-trigger_patterns:- # Good: Specific- - "analyze data"- - "data analysis"- - "process dataset"-- # Bad: Too generic- - "do"- - "make"-```--## Debugging--### Verbose Logging--Add detailed logging during development:--```python-PrintStyle.hint(f"Processing {len(items)} items")-PrintStyle.hint(f"First item: {items[0] if items else 'empty'}")-```--### Remove Before Commit--Clean up debug code:--```python-# Development-PrintStyle.hint(f"DEBUG: kwargs = {kwargs}")--# Production-# Remove or convert to proper logging-```--## Deployment--### Environment Variables--Use env vars for configuration:--```python-import os--DEBUG = os.getenv("DEBUG", "false").lower() == "true"-MAX_WORKERS = int(os.getenv("MAX_WORKERS", "4"))-```--### Feature Flags--Use flags for gradual rollout:--```python-ENABLE_NEW_FEATURE = os.getenv("ENABLE_NEW_FEATURE", "false") == "true"--async def execute(self, **kwargs):- if ENABLE_NEW_FEATURE:- return await self.new_implementation(kwargs)- else:- return await self.old_implementation(kwargs)-```--## Documentation--### README Files--Every component needs a README:--```markdown-# Component Name--## Purpose-What this component does--## Usage-How to use it--## Configuration-Configuration options--## Examples-Code examples-```--### Code Comments--Comment complex logic:--```python-# Use binary search for O(log n) performance-# instead of linear scan O(n)-index = binary_search(sorted_data, target)-```diff --git a/usr/skills/frameworks/agent-zero-dev/docs/quickstart.md b/usr/skills/frameworks/agent-zero-dev/docs/quickstart.mddeleted file mode 100644index b0d9cd90d..000000000--- a/usr/skills/frameworks/agent-zero-dev/docs/quickstart.md+++ /dev/null@@ -1,63 +0,0 @@-# Agent Zero Development Quickstart--Get started extending Agent Zero in 5 minutes.--## Prerequisites--- Agent Zero framework installed and running-- Basic understanding of Python async/await-- Familiarity with the framework structure--## 1. Create Your First Tool (2 minutes)--```bash-cd /a0/usr/skills/frameworks/agent-zero-dev-python scripts/create_tool.py WeatherLookup "Get weather information for locations"-```--This creates `/a0/python/tools/weather_lookup.py` with full boilerplate.--Edit the file to implement your logic:--```python-async def _process(self, location: str, units: str) -> str:- # Your weather API call here- return f"Weather for {location}: 72°F, Sunny"-```--Restart Agent Zero to load the new tool.--## 2. Create Your First Extension (2 minutes)--```bash-python scripts/create_extension.py agent_init ConfigLoader "Load project configuration"-```--Edit the generated file to add initialization logic.--## 3. Create Your First Skill (3 minutes)--```bash-python scripts/create_skill.py my-skill "My custom skill description"-```--Edit `SKILL.md` to add instructions, then test with:-"Use my-skill to process data"--## 4. Create Your First API Endpoint (3 minutes)--```bash-python scripts/create_api.py DataApi "API for data operations"-```--Test with curl:-```bash-curl "http://localhost:5001/api/data_api?context=test¶m=value"-```--## Next Steps--- Read the full [SKILL.md](../SKILL.md) for comprehensive documentation-- Explore existing tools in `/a0/python/tools/`-- Check out default skills in `/a0/usr/skills/default/`-- Review the Superpowers framework for development workflowsdiff --git a/usr/skills/frameworks/agent-zero-dev/scripts/create_api.py b/usr/skills/frameworks/agent-zero-dev/scripts/create_api.pydeleted file mode 100755index c5294b476..000000000--- a/usr/skills/frameworks/agent-zero-dev/scripts/create_api.py+++ /dev/null@@ -1,154 +0,0 @@-#!/usr/bin/env python3-"""-Create API Endpoint Boilerplate-Generates a new Agent Zero API endpoint with proper structure and patterns.--Usage:- python create_api.py EndpointName "Description"- python create_api.py TaskManager "Manage async tasks"--Output:- Creates python/api/endpoint_name.py with full boilerplate-"""--import sys-import re-from pathlib import Path---def to_snake_case(name: str) -> str:- """Convert CamelCase or spaced name to snake_case."""- name = name.replace(" ", "_")- s1 = re.sub('(.)([A-Z][a-z]+)', r'\1_\2', name)- return re.sub('([a-z0-9])([A-Z])', r'\1_\2', s1).lower()---def to_class_name(name: str) -> str:- """Convert snake_case or spaced name to CamelCase."""- return ''.join(word.capitalize() for word in name.replace('_', ' ').split())---def generate_api_code(class_name: str, endpoint_name: str, description: str) -> str:- """Generate the API endpoint boilerplate code."""- return f'''from python.helpers.api import ApiHandler, Request, Response-from agent import AgentContext-from python.helpers.print_style import PrintStyle---class {class_name}(ApiHandler):- """- {description}-- Endpoint: /api/{endpoint_name}- Methods: GET, POST (as needed)- """-- async def process(self, input: dict, request: Request) -> dict | Response:- """- Process the API request.-- Args:- input: Parsed JSON body or query parameters- request: Werkzeug Request object-- Returns:- dict response or Response object- """- # Get context (creates new if ctxid is empty)- ctxid = input.get("context", "")- context = self.use_context(ctxid)-- # Handle different HTTP methods- if request.method == "GET":- return await self._handle_get(input, context)- elif request.method == "POST":- return await self._handle_post(input, request, context)- else:- return {{- "success": False,- "error": f"Method {{request.method}} not supported"- }}-- async def _handle_get(self, input: dict, context: AgentContext) -> dict:- """Handle GET requests."""- # TODO: Implement GET logic- param = input.get("param", "default")-- return {{- "success": True,- "data": {{- "message": f"GET request processed with param: {{param}}",- "context": context.id- }}- }}-- async def _handle_post(self, input: dict, request: Request, context: AgentContext) -> dict:- """Handle POST requests."""- # TODO: Implement POST logic- # Access JSON body: input.get("field")- # Access form data: request.form.get("field")- # Access files: request.files.get("file")-- data = input.get("data", {{}})-- PrintStyle.hint(f"{class_name} processing POST request")-- return {{- "success": True,- "data": {{- "message": "POST request processed",- "received": data,- "context": context.id- }}- }}-'''---def main():- if len(sys.argv) < 2:- print("Usage: python create_api.py EndpointName [\"Description\"]")- print("Example: python create_api.py TaskManager \"Manage async tasks\"")- print("\nThe endpoint will be accessible at /api/endpoint-name")- sys.exit(1)-- endpoint_input = sys.argv[1]- description = sys.argv[2] if len(sys.argv) > 2 else f"{endpoint_input} API endpoint"-- class_name = to_class_name(endpoint_input)- endpoint_name = to_snake_case(endpoint_input)-- # Generate code- code = generate_api_code(class_name, endpoint_name, description)-- # Determine output path- output_dir = Path("/a0/python/api")- if not output_dir.exists():- output_dir = Path("python/api")-- output_file = output_dir / f"{endpoint_name}.py"-- # Check if file exists- if output_file.exists():- print(f"Error: File already exists: {output_file}")- print("Use a different name or delete the existing file.")- sys.exit(1)-- # Write file- output_file.write_text(code)-- print(f"✅ Created API endpoint: {output_file}")- print(f" Class: {class_name}")- print(f" Endpoint: /api/{endpoint_name}")- print(f" URL: http://localhost:5001/api/{endpoint_name}")- print(f"\nNext steps:")- print(f" 1. Edit {output_file} to implement your logic")- print(f" 2. Add route registration if needed (check python/api/__init__.py)")- print(f" 3. Test with curl or the Web UI")- print(f" 4. Restart Agent Zero to load the new endpoint")- print(f"\nExample curl commands:")- print(f' GET: curl "http://localhost:5001/api/{endpoint_name}?context=test¶m=value"')- print(f' POST: curl -X POST "http://localhost:5001/api/{endpoint_name}" -H "Content-Type: application/json" -d \'{{"context":"test","data":{{"key":"value"}}}}\'')---if __name__ == "__main__":- main()diff --git a/usr/skills/frameworks/agent-zero-dev/scripts/create_extension.py b/usr/skills/frameworks/agent-zero-dev/scripts/create_extension.pydeleted file mode 100755index 6e4e4b9f9..000000000--- a/usr/skills/frameworks/agent-zero-dev/scripts/create_extension.py+++ /dev/null@@ -1,167 +0,0 @@-#!/usr/bin/env python3-"""-Create Extension Boilerplate-Generates a new Agent Zero extension with proper structure and patterns.--Usage:- python create_extension.py hook_point ExtensionName "Description"- python create_extension.py agent_init ConfigLoader "Load custom configuration"--Hook Points:- - agent_init- - message_loop_start- - message_loop_end- - before_main_llm_call- - response_stream_start- - response_stream_chunk- - response_stream_end- - tool_execute_before- - tool_execute_after--Output:- Creates python/extensions/<hook_point>/_XX_extension_name.py-"""--import sys-import re-from pathlib import Path---def to_snake_case(name: str) -> str:- """Convert CamelCase or spaced name to snake_case."""- name = name.replace(" ", "_")- s1 = re.sub('(.)([A-Z][a-z]+)', r'\1_\2', name)- return re.sub('([a-z0-9])([A-Z])', r'\1_\2', s1).lower()---def to_class_name(name: str) -> str:- """Convert snake_case or spaced name to CamelCase."""- return ''.join(word.capitalize() for word in name.replace('_', ' ').split())---def get_next_number(extension_dir: Path) -> int:- """Get the next available extension number."""- if not extension_dir.exists():- return 10-- existing = [f for f in extension_dir.iterdir() if f.suffix == '.py' and f.stem.startswith('_')]- numbers = []- for f in existing:- match = re.match(r'_(\d+)_.*', f.stem)- if match:- numbers.append(int(match.group(1)))-- if numbers:- # Round up to next 10- max_num = max(numbers)- return ((max_num // 10) + 1) * 10- return 10---def generate_extension_code(class_name: str, description: str, hook_point: str) -> str:- """Generate the extension boilerplate code."""- return f'''from python.helpers.extension import Extension-from python.helpers.print_style import PrintStyle---class {class_name}(Extension):- """- {description}-- Hook Point: {hook_point}- """-- async def execute(self, **kwargs):- """- Execute the extension logic.-- Common kwargs by hook point:- - agent_init: {{}}- - message_loop_start: {{"message": str}}- - before_main_llm_call: {{"prompts": list}}- - response_stream_chunk: {{"chunk": str}}- - tool_execute_before: {{"tool_name": str, "arguments": dict}}- - tool_execute_after: {{"tool_name": str, "result": any}}- """- agent = self.agent- context = agent.context-- # Access hook-specific data- data = kwargs.get("data", {{}})-- try:- # TODO: Implement your extension logic- PrintStyle.hint(f"{class_name} executing for {hook_point}")-- # Example: Modify data if applicable- # data["modified"] = True-- return data-- except Exception as e:- PrintStyle.error(f"Error in {class_name}: {{e}}")- return data-'''---def main():- valid_hooks = [- "agent_init", "message_loop_start", "message_loop_end",- "before_main_llm_call", "response_stream_start", "response_stream_chunk",- "response_stream_end", "tool_execute_before", "tool_execute_after"- ]-- if len(sys.argv) < 3:- print("Usage: python create_extension.py hook_point ExtensionName [\"Description\"]")- print("\nValid hook points: " + ", ".join(valid_hooks))- print("\nExample: python create_extension.py agent_init ConfigLoader")- sys.exit(1)-- hook_point = sys.argv[1]- ext_name = sys.argv[2]- description = sys.argv[3] if len(sys.argv) > 3 else f"{ext_name} extension"-- if hook_point not in valid_hooks:- print(f"Error: Invalid hook point '{hook_point}'")- print(f"Valid hook points: {', '.join(valid_hooks)}")- sys.exit(1)-- class_name = to_class_name(ext_name)- ext_file_name = to_snake_case(ext_name)-- # Determine output path- base_dir = Path("/a0/python/extensions")- if not base_dir.exists():- base_dir = Path("python/extensions")-- extension_dir = base_dir / hook_point-- # Get next number- number = get_next_number(extension_dir)-- # Create directory if needed- extension_dir.mkdir(parents=True, exist_ok=True)-- output_file = extension_dir / f"_{number}_{ext_file_name}.py"-- # Check if file exists- if output_file.exists():- print(f"Error: File already exists: {output_file}")- sys.exit(1)-- # Generate and write code- code = generate_extension_code(class_name, description, hook_point)- output_file.write_text(code)-- print(f"✅ Created extension: {output_file}")- print(f" Class: {class_name}")- print(f" Hook Point: {hook_point}")- print(f"\nNext steps:")- print(f" 1. Edit {output_file} to implement your logic")- print(f" 2. Check kwargs for your specific hook point")- print(f" 3. Test by running the framework")- print(f" 4. Restart Agent Zero to load the extension")---if __name__ == "__main__":- main()diff --git a/usr/skills/frameworks/agent-zero-dev/scripts/create_skill.py b/usr/skills/frameworks/agent-zero-dev/scripts/create_skill.pydeleted file mode 100755index fdb16d64f..000000000--- a/usr/skills/frameworks/agent-zero-dev/scripts/create_skill.py+++ /dev/null@@ -1,231 +0,0 @@-#!/usr/bin/env python3-"""-Create Skill Boilerplate-Generates a new Agent Zero skill with SKILL.md and directory structure.--Usage:- python create_skill.py skill-name "Description of the skill"- python create_skill.py web-scraper "Scrape web pages for data extraction"--Output:- Creates usr/skills/custom/<skill-name>/ directory with SKILL.md-"""--import sys-import re-from pathlib import Path-from datetime import datetime---def validate_skill_name(name: str) -> str:- """Validate and normalize skill name."""- # Remove leading/trailing whitespace- name = name.strip()- # Replace spaces with hyphens- name = name.replace(" ", "-")- # Ensure only lowercase letters, numbers, and hyphens- if not re.match(r'^[a-z0-9-]+$', name):- raise ValueError(f"Invalid skill name: {name}. Use only lowercase letters, numbers, and hyphens.")- return name---def generate_skill_md(name: str, description: str, author: str) -> str:- """Generate the SKILL.md content."""- # Generate trigger patterns based on name and description- words = name.replace("-", " ").split()- trigger_patterns = [- f'"{name}"',- f'"{" ".join(words)}"',- ]-- # Add description words as triggers- desc_words = description.lower().split()[:3]- if desc_words:- trigger_patterns.append(f'"{" ".join(desc_words)}"')-- triggers_str = "\n - ".join(trigger_patterns)-- return f'''----name: "{name}"-description: "{description}"-version: "1.0.0"-author: "{author}"-tags: ["custom", "helper"]-trigger_patterns:- - {triggers_str}------# {name.replace("-", " ").title()}--## When to Use--This skill activates when users mention:-- Keywords: {name}-- Related concepts: {description}--Use this skill to:-1. First use case-2. Second use case-3. Third use case--## The Process--### Step 1: Preparation-Describe initial setup or validation steps.--### Step 2: Main Processing-Detail the core functionality.--### Step 3: Finalization-Explain output formatting and delivery.--## Examples--### Example 1: Basic Usage--**User**: "Use {name} to..."--**Agent**:-> I'll help you with that. Here's what I'll do:-> 1. Step one-> 2. Step two-> 3. Step three--### Example 2: Advanced Usage--**User**: "Complex {name} task with parameters"--**Agent**:-> Processing with custom parameters...-> - Parameter A: value-> - Parameter B: value-> Result: success--## Scripts and Resources--This skill includes optional helper scripts:--| Script | Purpose | Usage |-|--------|---------|-------|-| `scripts/helper.py` | Description | `python scripts/helper.py arg1 arg2` |--To use scripts, run them directly with code_execution_tool:-```json-{{- "tool_name": "code_execution_tool",- "tool_args": {{- "runtime": "python",- "code": "python /a0/usr/skills/custom/{name}/scripts/helper.py arg1"- }}-}}-```--## Best Practices--### DO-- ✅ Best practice 1-- ✅ Best practice 2-- ✅ Best practice 3--### DON'T-- ❌ Anti-pattern 1-- ❌ Anti-pattern 2--## Tips and Tricks--- Tip 1-- Tip 2-- Tip 3--## Common Issues--| Issue | Cause | Solution |-|-------|-------|----------|-| Problem | Root cause | How to fix |--## Related Skills--- `related-skill-1` - Related functionality-- `related-skill-2` - Complementary feature-'''---def main():- if len(sys.argv) < 2:- print("Usage: python create_skill.py skill-name [\"Description\"]")- print("Example: python create_skill.py data-processor \"Process and transform data\"")- print("\nSkill name rules:")- print(" - Use lowercase letters, numbers, and hyphens only")- print(" - No spaces (use hyphens)")- print(" - Example: web-scraper, data-processor, api-client")- sys.exit(1)-- try:- skill_name = validate_skill_name(sys.argv[1])- except ValueError as e:- print(f"Error: {e}")- sys.exit(1)-- description = sys.argv[2] if len(sys.argv) > 2 else f"Skill for {skill_name}"- author = "Agent Zero User"-- # Determine output path- base_dir = Path("/a0/usr/skills/custom")- if not base_dir.exists():- base_dir = Path("usr/skills/custom")-- skill_dir = base_dir / skill_name-- # Check if skill already exists- if skill_dir.exists():- print(f"Error: Skill already exists: {skill_dir}")- print("Use a different name or delete the existing skill.")- sys.exit(1)-- # Create directory structure- skill_dir.mkdir(parents=True)- (skill_dir / "scripts").mkdir()- (skill_dir / "templates").mkdir()- (skill_dir / "docs").mkdir()-- # Create SKILL.md- skill_md = skill_dir / "SKILL.md"- skill_md.write_text(generate_skill_md(skill_name, description, author))-- # Create placeholder files- (skill_dir / "scripts" / "helper.py").write_text("""#!/usr/bin/env python3-# Helper script for skill--def main():- print("Helper script placeholder")- # TODO: Implement script logic--if __name__ == "__main__":- main()-""")-- (skill_dir / "templates" / "template.md").write_text("# Template placeholder\n\nEdit this template as needed.")- (skill_dir / "docs" / "examples.md").write_text("# Examples\n\nAdd usage examples here.")-- print(f"✅ Created skill: {skill_dir}")- print(f" Name: {skill_name}")- print(f" Description: {description}")- print(f"\nStructure:")- print(f" {skill_dir}/")- print(f" ├── SKILL.md # Main skill file (EDIT THIS)")- print(f" ├── scripts/")- print(f" │ └── helper.py # Helper script")- print(f" ├── templates/")- print(f" │ └── template.md # Template file")- print(f" └── docs/")- print(f" └── examples.md # Documentation")- print(f"\nNext steps:")- print(f" 1. Edit {skill_dir}/SKILL.md to add your instructions")- print(f" 2. Update trigger_patterns for activation")- print(f" 3. Implement scripts in scripts/")- print(f" 4. Test the skill by using trigger words")- print(f" 5. Skills load automatically on agent initialization")---if __name__ == "__main__":- main()diff --git a/usr/skills/frameworks/agent-zero-dev/scripts/create_tool.py b/usr/skills/frameworks/agent-zero-dev/scripts/create_tool.pydeleted file mode 100755index 0bed2603f..000000000--- a/usr/skills/frameworks/agent-zero-dev/scripts/create_tool.py+++ /dev/null@@ -1,128 +0,0 @@-#!/usr/bin/env python3-"""-Create Tool Boilerplate-Generates a new Agent Zero tool with proper structure and patterns.--Usage:- python create_tool.py ToolName "Description of what the tool does"- python create_tool.py WeatherLookup "Get weather information for locations"--Output:- Creates python/tools/tool_name.py with full boilerplate-"""--import sys-import re-from pathlib import Path---def to_snake_case(name: str) -> str:- """Convert CamelCase or spaced name to snake_case."""- # Handle spaces first- name = name.replace(" ", "_")- # Insert underscore before capital letters- s1 = re.sub('(.)([A-Z][a-z]+)', r'\1_\2', name)- return re.sub('([a-z0-9])([A-Z])', r'\1_\2', s1).lower()---def to_class_name(name: str) -> str:- """Convert snake_case or spaced name to CamelCase."""- # Remove spaces and underscores, capitalize each word- return ''.join(word.capitalize() for word in name.replace('_', ' ').split())---def generate_tool_code(class_name: str, tool_name: str, description: str) -> str:- """Generate the tool boilerplate code."""- return f'''from python.helpers.tool import Tool, Response---class {class_name}(Tool):- """- {description}-- Arguments (tool_args):- - param1: Description of first parameter- - param2: Description of second parameter-- Returns:- Response object with result message- """-- async def execute(self, **kwargs) -> Response:- # Get arguments from kwargs with fallback to self.args- param1 = kwargs.get("param1") or self.args.get("param1", "")- param2 = kwargs.get("param2") or self.args.get("param2", "")-- try:- # TODO: Implement your tool logic here- result = await self._process(param1, param2)-- return Response(- message=result,- break_loop=False- )- except Exception as e:- return Response(- message=f"Error in {class_name}: {{e}}",- break_loop=False- )-- async def _process(self, param1: str, param2: str) -> str:- """- Implement your main tool logic here.-- Args:- param1: First parameter- param2: Second parameter-- Returns:- Result string to return to agent- """- # TODO: Replace with actual implementation- return f"Processed {{param1}} and {{param2}}"-'''---def main():- if len(sys.argv) < 2:- print("Usage: python create_tool.py ToolName [\"Description\"]")- print("Example: python create_tool.py WeatherLookup \"Get weather for locations\"")- sys.exit(1)-- tool_input = sys.argv[1]- description = sys.argv[2] if len(sys.argv) > 2 else f"{tool_input} tool"-- class_name = to_class_name(tool_input)- tool_name = to_snake_case(tool_input)-- # Generate code- code = generate_tool_code(class_name, tool_name, description)-- # Determine output path- output_dir = Path("/a0/python/tools")- if not output_dir.exists():- # Try relative path- output_dir = Path("python/tools")-- output_file = output_dir / f"{tool_name}.py"-- # Check if file exists- if output_file.exists():- print(f"Error: File already exists: {output_file}")- print("Use a different name or delete the existing file.")- sys.exit(1)-- # Write file- output_file.write_text(code)- print(f"✅ Created tool: {output_file}")- print(f" Class: {class_name}")- print(f" Tool name (snake_case): {tool_name}")- print(f"\nNext steps:")- print(f" 1. Edit {output_file} to implement your logic")- print(f" 2. Update the docstring with actual arguments")- print(f" 3. Test your tool with the agent")- print(f" 4. Restart Agent Zero to load the new tool")---if __name__ == "__main__":- main()diff --git a/usr/skills/frameworks/agentos/agentos-project-install/SKILL.md b/usr/skills/frameworks/agentos/agentos-project-install/SKILL.mddeleted file mode 100644index 82f62a13f..000000000--- a/usr/skills/frameworks/agentos/agentos-project-install/SKILL.md+++ /dev/null@@ -1,86 +0,0 @@-----name: "agentos-project-install"-description: "Initialize a project with AgentOS standard structure and configuration."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["agentos", "initialization", "setup"]-trigger_patterns:- - "install agentos"- - "setup project"- - "initialize agentos"------# AgentOS: Project Install--Initialize a project with AgentOS standard structure and configuration files.--## When to Use--- Starting a new project with AgentOS-- Converting existing project to AgentOS standards-- Setting up development environment--## Standard Structure--```-project/-├── .agentos/-│ ├── config.yaml # Project configuration-│ ├── standards.yaml # Coding standards-│ └── hooks/ # Git hooks-├── docs/-│ ├── README.md-│ └── CONTRIBUTING.md-├── src/-├── tests/-├── .gitignore-├── .editorconfig-└── Makefile-```--## Installation Process--1. **Create Directory Structure**- - Create `.agentos/` configuration directory- - Set up standard folders- - Add configuration files--2. **Initialize Configuration**- ```yaml- # .agentos/config.yaml- project:- name: [Project Name]- type: [web/cli/library]- language: [Primary language]-- standards:- linting: true- formatting: true- testing: required-- quality:- coverage_minimum: 80- review_required: true- ```--3. **Set Up Git Hooks**- - Pre-commit: linting, formatting- - Pre-push: tests--4. **Create Documentation**- - README template- - Contributing guidelines--## Output--```markdown-## AgentOS Installed: [Project Name]--**Config**: `.agentos/config.yaml`-**Standards**: Configured-**Hooks**: Installed--Project ready for development.--Apply standards with `agentos-standards`.-```diff --git a/usr/skills/frameworks/agentos/agentos-standards/SKILL.md b/usr/skills/frameworks/agentos/agentos-standards/SKILL.mddeleted file mode 100644index cf08421e6..000000000--- a/usr/skills/frameworks/agentos/agentos-standards/SKILL.md+++ /dev/null@@ -1,96 +0,0 @@-----name: "agentos-standards"-description: "Apply and verify AgentOS coding standards across the project."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["agentos", "standards", "quality"]-trigger_patterns:- - "apply standards"- - "check standards"- - "verify standards"------# AgentOS: Standards--Apply and verify AgentOS coding standards across the project.--## When to Use--- After project install-- Before committing code-- During code review-- Periodic quality checks--## Standards Categories--### 1. Code Style-- Consistent formatting-- Naming conventions-- File organization--### 2. Documentation-- Function/method documentation-- README completeness-- API documentation--### 3. Testing-- Test coverage requirements-- Test naming conventions-- Test organization--### 4. Security-- No hardcoded secrets-- Input validation-- Error handling--## Standards Check Process--```markdown-## Standards Verification: [Project Name]--### Code Style-- [ ] Formatting: [Tool] passing-- [ ] Linting: [Tool] passing-- [ ] Naming: Conventions followed--### Documentation-- [ ] README: Complete and current-- [ ] Functions: Documented-- [ ] API: Documented--### Testing-- [ ] Coverage: [X]% (minimum: 80%)-- [ ] Tests: All passing-- [ ] Structure: Follows conventions--### Security-- [ ] Secrets: None hardcoded-- [ ] Validation: Input validated-- [ ] Errors: Properly handled--### Result-**Status**: PASS/FAIL-**Issues**: [Count]-```--## Fixing Violations--For each violation:-1. Identify the standard-2. Locate the violation-3. Apply the fix-4. Verify the fix--## Output--```markdown-## Standards Check: [Project Name]--**Status**: PASS/FAIL-**Violations**: [X]-**Coverage**: [Y]%--[List of issues if any]--All standards met? Ready for commit/review.-```diff --git a/usr/skills/frameworks/amplihack/amplihack-analyze/SKILL.md b/usr/skills/frameworks/amplihack/amplihack-analyze/SKILL.mddeleted file mode 100644index f120ad9d0..000000000--- a/usr/skills/frameworks/amplihack/amplihack-analyze/SKILL.md+++ /dev/null@@ -1,72 +0,0 @@-----name: "amplihack-analyze"-description: "Deep analysis of code, requirements, or systems."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["amplihack", "analysis", "understanding"]-trigger_patterns:- - "analyze"- - "deep dive"- - "understand code"------# AMPLIHACK: Analyze--Perform deep analysis of code, requirements, or systems.--## When to Use--- Need to understand existing code-- Analyzing requirements for implementation-- Investigating issues or bugs-- Understanding system architecture--## Analysis Modes--### TRIAGE (Rapid Scanning)-- Quick overview-- Identify key components-- Surface-level understanding--### DEEP (Thorough Investigation)-- Detailed code examination-- Trace execution paths-- Map dependencies--### SYNTHESIS (Multi-source Integration)-- Combine multiple analyses-- Cross-reference findings-- Build complete picture--## Analysis Process--1. **Determine Mode**: Based on task complexity-2. **Gather Sources**: Files, docs, code-3. **Execute Analysis**: Per selected mode-4. **Document Findings**: Structured report--## Output Format--```markdown-## Analysis Report: [Subject]--### Summary-[Key findings overview]--### Components Identified-- [Component 1]: [Purpose]-- [Component 2]: [Purpose]--### Dependencies-```-[Dependency graph or list]-```--### Key Insights-1. [Insight 1]-2. [Insight 2]--### Recommendations-- [Action 1]-- [Action 2]-```diff --git a/usr/skills/frameworks/amplihack/amplihack-auto/SKILL.md b/usr/skills/frameworks/amplihack/amplihack-auto/SKILL.mddeleted file mode 100644index 8027a15a6..000000000--- a/usr/skills/frameworks/amplihack/amplihack-auto/SKILL.md+++ /dev/null@@ -1,60 +0,0 @@-----name: "amplihack-auto"-description: "Automatic workflow selection based on task analysis."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["amplihack", "workflow", "automatic"]-trigger_patterns:- - "auto workflow"- - "amplihack auto"- - "automatic"------# AMPLIHACK: Auto--Automatically select the best workflow based on task analysis.--## When to Use--- Starting any task with AMPLIHACK-- Unsure which workflow to use-- Need intelligent workflow routing--## Task Analysis--Analyze the task to determine best workflow:--| Task Type | Indicators | Recommended Workflow |-|-----------|------------|---------------------|-| Complex problem | Multiple valid approaches | `amplihack-debate` |-| Code analysis | Understand existing code | `amplihack-analyze` |-| Multi-step work | Sequential dependencies | `amplihack-cascade` |-| Simple task | Clear requirements | Direct implementation |--## Selection Process--1. **Analyze Request**- - What is being asked?- - How complex is it?- - What's the scope?--2. **Check Indicators**- - Multiple approaches possible? → Debate- - Need deep understanding? → Analyze- - Sequential steps needed? → Cascade--3. **Select Workflow**- - Route to appropriate skill- - Explain selection rationale--## Output--```markdown-## Auto Workflow Selection--**Task**: [Summary]-**Analysis**: [Why this workflow]-**Selected**: [Workflow name]--Proceeding with [workflow]...-```diff --git a/usr/skills/frameworks/amplihack/amplihack-cascade/SKILL.md b/usr/skills/frameworks/amplihack/amplihack-cascade/SKILL.mddeleted file mode 100644index 84802c702..000000000--- a/usr/skills/frameworks/amplihack/amplihack-cascade/SKILL.md+++ /dev/null@@ -1,82 +0,0 @@-----name: "amplihack-cascade"-description: "Multi-agent cascade pattern for complex sequential tasks."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["amplihack", "cascade", "multi-agent"]-trigger_patterns:- - "cascade"- - "sequential workflow"- - "multi-step"------# AMPLIHACK: Cascade--Execute complex tasks using a cascade of specialized agents.--## When to Use--- Multi-step tasks with dependencies-- Different expertise needed at each stage-- Quality gates between phases--## Cascade Pattern--```-[Input] → [Agent 1] → [Output 1] → [Agent 2] → [Output 2] → [Final Output]-```--Each agent:-- Has specialized expertise-- Receives previous output as input-- Produces structured output for next agent-- Can validate and fail-fast--## Cascade Stages--### Stage 1: Requirements-- Parse and validate input-- Identify scope and constraints-- Output: Structured requirements--### Stage 2: Design-- Receive requirements-- Create implementation design-- Output: Technical specification--### Stage 3: Implementation-- Receive specification-- Write code-- Output: Implementation with tests--### Stage 4: Verification-- Receive implementation-- Run tests and checks-- Output: Verified code or failures--## Execution--```markdown-## Cascade Execution: [Task]--### Stage 1: Requirements-**Input**: [User request]-**Agent**: Requirements Analyst-**Output**: Structured requirements-**Status**: Complete--### Stage 2: Design-**Input**: Requirements from Stage 1-**Agent**: Architect-**Output**: Technical spec-**Status**: In Progress--...-```--## Failure Handling--If a stage fails:-1. Report failure-2. Allow retry or revision-3. Don't proceed until resolveddiff --git a/usr/skills/frameworks/amplihack/amplihack-debate/SKILL.md b/usr/skills/frameworks/amplihack/amplihack-debate/SKILL.mddeleted file mode 100644index 7c30b60fd..000000000--- a/usr/skills/frameworks/amplihack/amplihack-debate/SKILL.md+++ /dev/null@@ -1,99 +0,0 @@-----name: "amplihack-debate"-description: "Multi-perspective debate workflow for complex decisions."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["amplihack", "debate", "decision-making"]-trigger_patterns:- - "debate"- - "multiple perspectives"- - "decision"------# AMPLIHACK: Debate--Facilitate multi-perspective debate for complex technical decisions.--## When to Use--- Multiple valid approaches exist-- High-stakes technical decisions-- Need to surface trade-offs-- Want rigorous analysis--## Debate Structure--### Participants (Perspectives)-- **Advocate**: Argues for proposed approach-- **Critic**: Challenges assumptions, finds weaknesses-- **Pragmatist**: Focuses on practical concerns-- **Moderator**: Synthesizes and drives to conclusion--### Debate Rounds--#### Round 1: Initial Arguments-Each perspective presents their view:-```markdown-### Advocate-[Arguments for approach]--### Critic-[Challenges and concerns]--### Pragmatist-[Practical considerations]-```--#### Round 2: Rebuttals-Perspectives respond to each other:-```markdown-### Advocate Response-[Address concerns, strengthen arguments]--### Critic Response-[Address rebuttals, raise new concerns]--### Pragmatist Response-[Reality check on both sides]-```--#### Round 3: Convergence-Work toward consensus:-```markdown-### Points of Agreement-- [Agreed point 1]-- [Agreed point 2]--### Remaining Disagreements-- [Disagreement 1]-- [Disagreement 2]--### Proposed Resolution-[Synthesized approach]-```--## Output--```markdown-## Debate Conclusion: [Topic]--### Decision-[Final recommendation]--### Rationale-[Why this was chosen]--### Acknowledged Risks-- [Risk 1 and mitigation]-- [Risk 2 and mitigation]--### Dissenting Views-[Any unresolved disagreements]-```--## Best Practices--- Keep rounds focused-- Require evidence for claims-- Drive toward actionable conclusion-- Document minority opinionsdiff --git a/usr/skills/frameworks/amplihack/amplihack-fix/SKILL.md b/usr/skills/frameworks/amplihack/amplihack-fix/SKILL.mddeleted file mode 100644index b01b48cf2..000000000--- a/usr/skills/frameworks/amplihack/amplihack-fix/SKILL.md+++ /dev/null@@ -1,107 +0,0 @@-----name: "amplihack-fix"-description: "Systematic error resolution with pattern-specific context and workflow."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["amplihack", "fix", "debugging", "error-resolution"]-trigger_patterns:- - "fix"- - "debug"- - "resolve error"- - "troubleshoot"------# AMPLIHACK: Fix--Systematic error resolution using the DEFAULT_WORKFLOW pattern.--## When to Use--- When encountering errors or bugs-- When tests are failing-- When behavior doesn't match expectations-- For systematic troubleshooting--## The Fix Workflow--The fix workflow follows a structured 22-step process for robust error resolution:--### Phase 1: Understand--1. **Reproduce** - Confirm the error occurs consistently-2. **Isolate** - Identify minimal reproduction case-3. **Document** - Capture error messages, stack traces, context--### Phase 2: Analyze--4. **Root Cause Analysis** - Trace error to origin-5. **Impact Assessment** - Understand scope of issue-6. **Pattern Matching** - Check for known error patterns--### Phase 3: Fix--7. **Design Solution** - Plan the fix approach-8. **Implement Fix** - Make code changes-9. **Verify Fix** - Confirm error is resolved--### Phase 4: Harden--10. **Add Tests** - Prevent regression-11. **Document** - Update relevant documentation-12. **Review** - Ensure fix is complete--## Pattern-Specific Context--The fix workflow adapts to error patterns:--| Pattern | Focus |-|---------|-------|-| **Type Error** | Check types, interfaces, contracts |-| **Runtime Error** | Trace execution path, check state |-| **Logic Error** | Verify business logic, edge cases |-| **Integration Error** | Check boundaries, APIs, data flow |-| **Performance Issue** | Profile, measure, optimize |--## Fix Output Format--```markdown-## Fix Report: {Error Description}--### Error Summary-- **Type:** [Error type/pattern]-- **Location:** [File:line or component]-- **Impact:** [Scope of issue]--### Root Cause-[Description of why the error occurs]--### Solution-[Description of the fix]--### Changes Made-1. `file1.ts:45` - [Change description]-2. `file2.ts:89` - [Change description]--### Verification-- [ ] Error no longer occurs-- [ ] Tests pass-- [ ] No new errors introduced--### Regression Prevention-- [ ] Test added: [test description]-```--## Best Practices--1. **Reproduce first** - Never fix what you can't reproduce-2. **One fix at a time** - Don't combine multiple fixes-3. **Test the fix** - Verify before declaring success-4. **Add regression tests** - Prevent future occurrences-5. **Document the root cause** - Help future debugging--## Integration with AMPLIHACK--The fix workflow can be triggered from:-- `amplihack-auto` - When errors are detected-- Direct invocation for known issues-- Cascade workflows when a step failsdiff --git a/usr/skills/frameworks/amplihack/amplihack-modular-build/SKILL.md b/usr/skills/frameworks/amplihack/amplihack-modular-build/SKILL.mddeleted file mode 100644index 2d41bdb48..000000000--- a/usr/skills/frameworks/amplihack/amplihack-modular-build/SKILL.md+++ /dev/null@@ -1,143 +0,0 @@-----name: "amplihack-modular-build"-description: "Build code following the brick philosophy with self-contained modules."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["amplihack", "modular", "build", "brick-philosophy"]-trigger_patterns:- - "modular build"- - "build module"- - "brick pattern"- - "self-contained"------# AMPLIHACK: Modular Build--Build code following the brick philosophy for self-contained, regeneratable modules.--## The Brick Philosophy--> "Each piece should be self-contained, testable, and replaceable without affecting others."--### Core Principles--1. **Self-Contained** - Module has everything it needs-2. **Single Responsibility** - One clear purpose-3. **Well-Defined Interface** - Clear inputs and outputs (studs)-4. **Regeneratable** - Can be rebuilt without breaking others-5. **Testable** - Can be tested in isolation--## Module Structure--```-module/-├── index.ts # Public interface (studs)-├── implementation.ts # Private implementation-├── types.ts # Type definitions-├── constants.ts # Module constants-└── module.test.ts # Module tests-```--## Building a Module--### 1. Define the Interface (Studs)--Start with what the module exposes:--```typescript-// index.ts - The studs (public interface)-export interface ModuleInput {- // What goes in-}--export interface ModuleOutput {- // What comes out-}--export function moduleFunction(input: ModuleInput): ModuleOutput {- // Implementation-}-```--### 2. Hide Implementation Details--Keep internals private:--```typescript-// implementation.ts - Private, can change freely-function internalHelper() {- // Not exported, can be modified without affecting users-}-```--### 3. Define Clear Boundaries--Each module should have:--```markdown-## Module Specification--**Name:** {module-name}-**Purpose:** [Single sentence describing what it does]--**Inputs (Dependencies):**-- [Input 1]: [Type] - [Description]-- [Input 2]: [Type] - [Description]--**Outputs (Provides):**-- [Output 1]: [Type] - [Description]--**Invariants:**-- [Invariant 1] - [What must always be true]-```--### 4. Test in Isolation--```typescript-// module.test.ts-describe('ModuleName', () => {- it('should [expected behavior]', () => {- const input: ModuleInput = { ... };- const result = moduleFunction(input);- expect(result).toEqual({ ... });- });-});-```--## Module Composition--Connect modules through their studs:--```-┌─────────────┐ ┌─────────────┐ ┌─────────────┐-│ Module A │────▶│ Module B │────▶│ Module C │-│ (studs) │ │ (studs) │ │ (studs) │-└─────────────┘ └─────────────┘ └─────────────┘-```--## Anti-Patterns to Avoid--| Anti-Pattern | Problem | Solution |-|-------------|---------|----------|-| **Reaching into internals** | Couples to implementation | Use only public interface |-| **Circular dependencies** | Can't reason about flow | Reorganize module boundaries |-| **God modules** | Too many responsibilities | Split into focused modules |-| **Leaky abstractions** | Implementation details escape | Better interface design |--## Build Checklist--Before considering a module complete:--- [ ] Single, clear purpose-- [ ] Well-defined interface (studs)-- [ ] No leaked implementation details-- [ ] Tests pass in isolation-- [ ] Can be regenerated independently-- [ ] Documentation for public interface--## Integration with AMPLIHACK--The modular build approach is used by:-- `amplihack-cascade` - Each stage produces a module-- `amplihack-auto` - Determines module boundaries-- Primary build agent - Creates regeneratable codediff --git a/usr/skills/frameworks/bmad-builder/bmb-agent/SKILL.md b/usr/skills/frameworks/bmad-builder/bmb-agent/SKILL.mddeleted file mode 100644index 8c469f707..000000000--- a/usr/skills/frameworks/bmad-builder/bmb-agent/SKILL.md+++ /dev/null@@ -1,123 +0,0 @@-----name: "bmb-agent"-description: "Create specialized AI agents with custom expertise, communication styles, and tool access."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-builder", "agent", "creation", "customization"]-trigger_patterns:- - "build agent"- - "create agent"- - "new agent"- - "agent builder"- - "/bmb-agent"------# BMad Builder: Create Agent--Build specialized AI agents with custom expertise and tools.--## Overview--The Agent Builder guides you through creating a custom BMad agent that can:-- Have domain-specific expertise-- Use a unique communication style-- Access specific tools-- Follow custom workflows--## Process--### 1. Define Domain--What should this agent specialize in?--**Questions to answer:**-- What domain expertise does this agent need?-- What problems will it solve?-- Who will use this agent?--### 2. Design Identity--Create the agent's persona:--```yaml-identity:- name: "[Agent Name]"- role: "[Primary Role] + [Secondary Role]"- experience: "[Years] years experience in [domain]"- personality: "[Key traits]"-```--### 3. Communication Style--How does the agent communicate?--- **Formal/Technical**: For enterprise, compliance-- **Casual/Friendly**: For creative, consumer-- **Direct/Efficient**: For development, operations-- **Mentoring/Educational**: For learning, onboarding--### 4. Core Principles--Define 3-5 guiding principles:--```yaml-principles:- - "[Principle 1]"- - "[Principle 2]"- - "[Principle 3]"-```--### 5. Available Commands--What commands should this agent support?--| Command | Description |-|---------|-------------|-| `[command-1]` | [What it does] |-| `[command-2]` | [What it does] |--### 6. Tool Access--Which tools does this agent need?--- Code execution-- File operations-- Web search-- API integrations-- Custom tools--## Output--Generate the agent definition file:--```yaml-# agent-name.agent.yaml-name: "[Agent Name]"-role: "[Role Description]"-identity: |- [Full identity description]-communication_style: |- [Communication guidelines]-principles:- - [Principle 1]- - [Principle 2]-commands:- - name: "[command]"- description: "[description]"-tools:- - [tool1]- - [tool2]-```--## Best Practices--1. **Focused Expertise**: Agents work better with deep, narrow expertise than broad, shallow knowledge-2. **Consistent Voice**: The communication style should match the domain-3. **Clear Boundaries**: Define what the agent does NOT do-4. **Testable Outputs**: Commands should produce verifiable results--## Next Steps--After creating an agent:-- Use `bmb-workflow` to create workflows for the agent-- Use `bmb-module` to package into a shareable modulediff --git a/usr/skills/frameworks/bmad-builder/bmb-module/SKILL.md b/usr/skills/frameworks/bmad-builder/bmb-module/SKILL.mddeleted file mode 100644index 0d7240300..000000000--- a/usr/skills/frameworks/bmad-builder/bmb-module/SKILL.md+++ /dev/null@@ -1,166 +0,0 @@-----name: "bmb-module"-description: "Package agents and workflows into shareable BMad modules."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-builder", "module", "package", "distribution"]-trigger_patterns:- - "build module"- - "create module"- - "package module"- - "module builder"- - "/bmb-module"------# BMad Builder: Create Module--Package agents and workflows into shareable BMad modules.--## Overview--Modules bundle related agents and workflows into distributable packages that can be:-- Installed via `npx bmad-method install`-- Shared on npm or GitHub-- Versioned and maintained--## Module Structure--```-your-module/-├── src/-│ ├── module.yaml # Module metadata and install config-│ ├── agents/ # Agent definitions (.agent.yaml)-│ ├── workflows/ # Workflow files-│ └── tools/ # Small reusable tools-├── docs/-│ └── README.md # Module documentation-├── package.json # NPM package info-└── LICENSE-```--## Process--### 1. Define Module Scope--**Questions:**-- What domain does this module serve?-- What agents and workflows does it include?-- Who is the target user?--### 2. Create module.yaml--```yaml-# src/module.yaml-name: "your-module-name"-version: "1.0.0"-description: "[Module purpose]"-author: "[Your name/org]"--# What gets installed-agents:- - agents/agent-one.agent.yaml- - agents/agent-two.agent.yaml--workflows:- - workflows/workflow-one.yaml- - workflows/workflow-two.yaml--# Installation options-install:- required: [] # Always install these- optional: # Let user choose- - name: "[Feature Set]"- description: "[What it adds]"- includes:- - agents/optional-agent.agent.yaml--# Dependencies on other modules-dependencies:- - bmad-method@^1.0.0-```--### 3. Create package.json--```json-{- "name": "bmad-module-your-name",- "version": "1.0.0",- "description": "BMad module for [domain]",- "keywords": ["bmad", "bmad-method", "your-domain"],- "repository": {- "type": "git",- "url": "https://github.com/your-org/your-module"- },- "files": ["src/"],- "scripts": {- "release": "npm version patch && git push --follow-tags"- },- "license": "MIT"-}-```--### 4. Write Documentation--Create `docs/README.md` with:-- What the module does-- Installation instructions-- Quick start guide-- Agent and workflow reference-- Examples--### 5. Test Locally--Before publishing:--```bash-# Test installation-npx bmad-method install --local ./path/to/module--# Verify agents work-# Run workflows-# Check documentation renders-```--### 6. Publish--```bash-# Tag release-git tag v1.0.0-git push origin v1.0.0--# Publish to npm (optional)-npm publish-```--## Best Practices--1. **Focused Scope**: One module = one domain-2. **Complete Package**: Include docs, examples, and tests-3. **Semantic Versioning**: Follow semver for updates-4. **Clear Dependencies**: List required BMad version-5. **License**: Include appropriate license--## Module Naming--Convention: `bmad-module-[domain]`--Examples:-- `bmad-module-game-dev-studio`-- `bmad-module-creative-intelligence`-- `bmad-module-security-audit`--## Distribution Options--| Method | Best For |-|--------|----------|-| npm | Public modules, easy installation |-| GitHub | Private/org modules, version control |-| Local | Development, testing |--## Next Steps--After creating a module:-- Test with fresh installation-- Write comprehensive docs-- Share with the community-- Maintain and update based on feedbackdiff --git a/usr/skills/frameworks/bmad-builder/bmb-workflow/SKILL.md b/usr/skills/frameworks/bmad-builder/bmb-workflow/SKILL.mddeleted file mode 100644index 450f26021..000000000--- a/usr/skills/frameworks/bmad-builder/bmb-workflow/SKILL.md+++ /dev/null@@ -1,148 +0,0 @@-----name: "bmb-workflow"-description: "Design structured workflows with steps, menus, and cross-workflow communication."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-builder", "workflow", "design", "process"]-trigger_patterns:- - "build workflow"- - "create workflow"- - "new workflow"- - "workflow builder"- - "/bmb-workflow"------# BMad Builder: Create Workflow--Design structured workflows with steps and cross-workflow communication.--## Overview--Workflows are structured processes that guide agents through complex tasks with:-- Sequential or branching steps-- Decision points and menus-- Cross-workflow communication-- Output artifacts--## Process--### 1. Define Purpose--What does this workflow accomplish?--**Questions:**-- What is the end goal?-- What inputs does it need?-- What outputs does it produce?-- Who triggers this workflow?--### 2. Map the Steps--Break the workflow into discrete steps:--```-Step 1: [Action]- ↓-Step 2: [Action]- ↓-Decision Point: [Condition]- ├── Option A → Step 3a- └── Option B → Step 3b- ↓-Step 4: [Final Action]-```--### 3. Design Each Step--For each step, define:--```yaml-steps:- - id: "step-1"- name: "[Step Name]"- description: "[What happens]"- inputs:- - "[input 1]"- outputs:- - "[output 1]"- next: "step-2" # or decision-```--### 4. Add Decision Points--For branching logic:--```yaml-decisions:- - id: "decision-1"- question: "[What determines the path?]"- options:- - label: "[Option A]"- condition: "[When to choose]"- next: "step-3a"- - label: "[Option B]"- condition: "[When to choose]"- next: "step-3b"-```--### 5. Define Artifacts--What does the workflow produce?--```yaml-artifacts:- - name: "[Artifact Name]"- type: "document|code|data"- template: "[Template reference]"- location: "[Where it's saved]"-```--### 6. Cross-Workflow Communication--How does this workflow connect to others?--```yaml-triggers:- incoming:- - from: "[workflow-name]"- event: "[trigger event]"- outgoing:- - to: "[workflow-name]"- event: "[event to trigger]"-```--## Output--Generate the workflow definition:--```yaml-# workflow-name.workflow.yaml-name: "[Workflow Name]"-description: "[Purpose]"-trigger_command: "/[command-name]"--steps:- - id: "step-1"- # ... step definition--decisions:- - id: "decision-1"- # ... decision definition--artifacts:- - name: "[Output]"- # ... artifact definition-```--## Best Practices--1. **Single Purpose**: Each workflow should accomplish one clear goal-2. **Clear Entry/Exit**: Define explicit start conditions and completion criteria-3. **Recoverable**: Allow resuming from any step-4. **Documented**: Each step should explain what and why--## Next Steps--After creating a workflow:-- Test with real scenarios-- Use `bmb-module` to package with agents into a modulediff --git a/usr/skills/frameworks/bmad-cis/cis-brainstorm/SKILL.md b/usr/skills/frameworks/bmad-cis/cis-brainstorm/SKILL.mddeleted file mode 100644index b02e4ddee..000000000--- a/usr/skills/frameworks/bmad-cis/cis-brainstorm/SKILL.md+++ /dev/null@@ -1,153 +0,0 @@-----name: "cis-brainstorm"-description: "Generate ideas with structured techniques like SCAMPER, Reverse Brainstorming, and more."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-cis", "brainstorm", "ideation", "creativity", "SCAMPER"]-trigger_patterns:- - "brainstorm"- - "generate ideas"- - "need ideas"- - "ideation"- - "/cis-brainstorm"------# CIS: Brainstorming Coach--Facilitate creative ideation sessions with proven techniques.--## Role--**Brainstorming Coach** — Expert facilitator skilled in structured creativity techniques that generate diverse, actionable ideas.--## When to Use--- Stuck on a problem and need fresh perspectives-- Starting a new feature and want to explore options-- Need to generate many alternatives before converging-- Team brainstorming sessions--## Available Techniques--### SCAMPER--Seven creative angles for any topic:--| Letter | Prompt | Example |-|--------|--------|---------|-| **S**ubstitute | What can be replaced? | Different tech stack |-| **C**ombine | What can merge? | Combine two features |-| **A**dapt | What can be borrowed? | Pattern from another app |-| **M**odify | What can change? | Scale, color, speed |-| **P**ut to other uses | New applications? | Use for different users |-| **E**liminate | What can be removed? | Simplify the flow |-| **R**everse | What if opposite? | Flip the interaction |--### Reverse Brainstorming--1. State the goal: "How might we improve X?"-2. Reverse it: "How might we make X worse?"-3. Generate ways to fail-4. Reverse each failure into a solution--### Six Thinking Hats--Explore from different perspectives:--| Hat | Focus | Questions |-|-----|-------|-----------|-| White | Facts | What data do we have? |-| Red | Feelings | What's our gut reaction? |-| Black | Caution | What could go wrong? |-| Yellow | Benefits | What are the advantages? |-| Green | Creativity | What are new possibilities? |-| Blue | Process | What's our next step? |--### Random Word Association--1. Pick a random word-2. List attributes of that word-3. Force connections to your problem-4. Discover unexpected solutions--## Process--### 1. Frame the Challenge--"What would you like to brainstorm about?"--Convert to a "How Might We" question:-- **Too narrow**: "How might we add a button?"-- **Too broad**: "How might we improve everything?"-- **Just right**: "How might we improve user onboarding?"--### 2. Choose Technique--Based on the challenge:-- **SCAMPER**: When iterating on existing solutions-- **Reverse**: When stuck on direct approaches-- **Six Hats**: When need balanced perspectives-- **Random Word**: When need truly novel ideas--### 3. Generate Ideas--Rules:-- Quantity over quality-- No judgment during generation-- Build on others' ideas-- Wild ideas welcome--### 4. Cluster and Refine--Group related ideas into themes:-- Quick wins (low effort, high impact)-- Big bets (high effort, high impact)-- Maybes (explore further)--### 5. Select Top Ideas--Criteria:-- Alignment with goals-- Feasibility-- User impact-- Novelty--## Output Format--```markdown-## Brainstorm: [Topic]--### Challenge-How might we [HMW question]?--### Technique Used-[Technique name]--### Ideas Generated-1. [Idea 1] — [Brief description]-2. [Idea 2] — [Brief description]-...--### Top Picks-1. **[Best idea]**: [Why this one]-2. **[Second]**: [Why this one]--### Next Steps-- [ ] [Action item]-- [ ] [Action item]-```--## Tips for Better Brainstorming--1. **Warm up**: Start with an unrelated creative exercise-2. **Time-box**: 10 minutes of divergent thinking, then converge-3. **Defer judgment**: "Yes, and..." not "No, but..."-4. **Go for volume**: Aim for 20+ ideas before filtering-5. **Mix techniques**: Use multiple methods for richer results--## Integration--After brainstorming:-- Use `/cis-problem-solve` to analyze promising ideas-- Use `/cis-design-thinking` to prototype solutions-- Feed results into BMAD planning workflowsdiff --git a/usr/skills/frameworks/bmad-cis/cis-design-thinking/SKILL.md b/usr/skills/frameworks/bmad-cis/cis-design-thinking/SKILL.mddeleted file mode 100644index e4e7c7d7a..000000000--- a/usr/skills/frameworks/bmad-cis/cis-design-thinking/SKILL.md+++ /dev/null@@ -1,190 +0,0 @@-----name: "cis-design-thinking"-description: "Human-centered design through empathy, ideation, prototyping, and testing."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-cis", "design-thinking", "ux", "user-centered", "empathy"]-trigger_patterns:- - "design thinking"- - "user centered"- - "empathy map"- - "prototype"- - "/cis-design-thinking"------# CIS: Design Thinking Coach--Guide human-centered design through empathy, ideation, and prototyping.--## Role--**Design Thinking Coach** — Expert in the Stanford d.school methodology, skilled at uncovering user needs and translating them into innovative solutions.--## When to Use--- Designing for users you don't fully understand-- Building a new product or major feature-- Solving problems where user needs are unclear-- Want to validate ideas before building--## The Five Stages--```-Empathize → Define → Ideate → Prototype → Test- ↑___________________________________|- (Iterate)-```--## Process--### Stage 1: Empathize--Understand your users deeply.--**Activities:**-- User interviews-- Observation-- Immersion-- Surveys--**Empathy Map:**--```- THINK & FEEL- [Internal thoughts]- ↓-SAY USER HEAR-[Quotes] 👤 [Influences]- ↓- DO- [Observable actions]--PAINS GAINS-[Frustrations] [Goals/Desires]-```--**Output Questions:**-- What tasks are they trying to complete?-- What frustrations do they experience?-- What workarounds do they use?-- What do they wish existed?--### Stage 2: Define--Synthesize findings into a clear problem statement.--**Point of View (POV) Statement:**--```-[User] needs [need] because [insight].-```--**Example:**-"Busy developers need a way to quickly test ideas because they lose momentum when setup takes too long."--**How Might We (HMW) Questions:**-- HMW reduce setup time?-- HMW maintain momentum?-- HMW make testing feel effortless?--### Stage 3: Ideate--Generate many possible solutions.--**Techniques:**-- Brainstorming (see `/cis-brainstorm`)-- Crazy 8s (8 ideas in 8 minutes)-- Mind mapping-- Analogous inspiration--**Rules:**-- Defer judgment-- Encourage wild ideas-- Build on others' ideas-- Go for quantity--### Stage 4: Prototype--Build quick, testable representations.--**Prototype Types:**--| Type | Speed | Fidelity | Best For |-|------|-------|----------|----------|-| Paper sketch | Minutes | Low | Early concepts |-| Wireframe | Hours | Low-Med | Flow validation |-| Clickable | Days | Medium | Interaction testing |-| Functional | Weeks | High | Technical validation |--**Principles:**-- Start rough, get specific-- Prototype to learn, not to prove-- Make multiple versions-- Fail fast and cheap--### Stage 5: Test--Validate with real users.--**Testing Script:**-1. Set context (no leading)-2. Give tasks, not instructions-3. Observe and note-4. Ask "what" and "why"-5. Thank and capture feedback--**Feedback Matrix:**--| Worked Well | Needs Change |-|-------------|--------------|-| [Positive observations] | [Issues found] |--**Questions:**-- What surprised you?-- What confused users?-- What delighted them?-- What would you change?--## Output Format--```markdown-## Design Thinking: [Project Name]--### Empathy Insights-**User Profile:** [Who]-**Key Needs:** [List]-**Key Pains:** [List]--### Problem Statement-[User] needs [need] because [insight].--### Ideas Explored-1. [Idea 1]-2. [Idea 2]-3. [Idea 3]--### Prototype Approach-[What we built to test]--### Test Findings-- **Validated:** [What worked]-- **Invalidated:** [What didn't]-- **Learned:** [New insights]--### Next Iteration-[What changes based on learning]-```--## Tips--1. **Stay in problem space**: Don't jump to solutions too fast-2. **Talk to real users**: Assumptions are dangerous-3. **Embrace ambiguity**: Early stages should feel uncertain-4. **Iterate quickly**: Each cycle teaches more-5. **Kill your darlings**: Let data drive decisions--## Integration--- Use `/cis-brainstorm` during Ideate stage-- Feed validated designs into BMAD workflows-- Use `/cis-storytelling` to communicate findingsdiff --git a/usr/skills/frameworks/bmad-cis/cis-innovation/SKILL.md b/usr/skills/frameworks/bmad-cis/cis-innovation/SKILL.mddeleted file mode 100644index b4a96173f..000000000--- a/usr/skills/frameworks/bmad-cis/cis-innovation/SKILL.md+++ /dev/null@@ -1,204 +0,0 @@-----name: "cis-innovation"-description: "Business model innovation and disruption opportunity analysis."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-cis", "innovation", "disruption", "business-model", "strategy"]-trigger_patterns:- - "innovation"- - "disrupt"- - "business model"- - "market gap"- - "/cis-innovation"------# CIS: Innovation Strategist--Identify disruption opportunities and business model innovation.--## Role--**Innovation Strategist** — Expert in competitive analysis, market dynamics, and identifying opportunities where innovation can create new value.--## When to Use--- Finding market gaps and opportunities-- Analyzing competitive landscape-- Exploring new business models-- Evaluating disruption potential--## Frameworks--### Business Model Canvas--Nine building blocks of a business:--```-┌─────────────────┬─────────────────┬─────────────────┐-│ Key Partners │ Key Activities │ Value Prop │-│ │ │ │-├─────────────────┼─────────────────┤ │-│ Key Resources │ │ │-│ │ │ │-├─────────────────┴─────────────────┼─────────────────┤-│ Cost Structure │ Revenue Streams │-│ │ │-└───────────────────────────────────┴─────────────────┘-```--**Questions for each:**-1. **Value Proposition**: What unique value do we offer?-2. **Customer Segments**: Who are our customers?-3. **Channels**: How do we reach them?-4. **Customer Relationships**: How do we engage?-5. **Revenue Streams**: How do we make money?-6. **Key Resources**: What do we need?-7. **Key Activities**: What must we do?-8. **Key Partners**: Who helps us?-9. **Cost Structure**: What are major costs?--### Blue Ocean Strategy--Create uncontested market space.--**Strategy Canvas:**-- List factors the industry competes on-- Rate current offerings on each factor-- Identify factors to Eliminate, Reduce, Raise, Create--| Factor | Industry | Us |-|--------|----------|-----|-| Price | High | Eliminate |-| Features | Many | Reduce |-| Ease | Low | Raise |-| [New factor] | N/A | Create |--### Disruption Analysis--Identify where incumbents are vulnerable.--**Types of Disruption:**-- **Low-end**: Serve overserved customers with "good enough" at lower cost-- **New-market**: Serve non-consumers who couldn't access existing solutions-- **High-end**: Serve underserved customers willing to pay premium--**Signals of Opportunity:**-- Customers complaining about complexity-- Users creating workarounds-- Underserved segments ignored by leaders-- Emerging technology enabling new approaches--### Jobs to Be Done--Understand what customers are trying to accomplish.--**Framework:**-"When [situation], I want to [motivation], so I can [outcome]."--**Example:**-"When I'm onboarding a new team member, I want to share project context quickly, so I can get them productive fast."--**Questions:**-- What job is the customer hiring the product to do?-- What are they currently using?-- What's frustrating about current solutions?-- What would "perfect" look like?--## Process--### 1. Map the Landscape--**Market Analysis:**-- Who are the major players?-- What do they compete on?-- Where are they focused?-- What do they ignore?--**Customer Analysis:**-- Who is overserved (paying for unused features)?-- Who is underserved (needs not met)?-- Who is non-consumers (can't access solutions)?--### 2. Identify Opportunities--**Gap Analysis:**-- Where is there unmet demand?-- What jobs are poorly served?-- What emerging trends enable new approaches?--**Question Matrix:**--| If we could... | What would happen? |-|----------------|-------------------|-| Remove [X] | [Impact] |-| Add [Y] | [Impact] |-| Change [Z] | [Impact] |--### 3. Evaluate Options--**Criteria:**-- Market size potential-- Competitive response difficulty-- Technical feasibility-- Strategic fit--**Risk Assessment:**-- Execution risk-- Market risk-- Technology risk-- Competition risk--### 4. Design Innovation--Using Business Model Canvas:-- What's the value proposition?-- Who are the target customers?-- How will we deliver and capture value?--## Output Format--```markdown-## Innovation Analysis: [Topic]--### Market Landscape-**Major Players:** [List]-**Competition Basis:** [What they compete on]-**Industry Assumptions:** [Unquestioned beliefs]--### Opportunity Identified-**Gap:** [Unmet need or underserved segment]-**Why Now:** [Why this timing is right]-**Enablers:** [What makes it possible]--### Proposed Innovation-**Value Proposition:** [What we offer differently]-**Target Segment:** [Who we serve]-**Differentiation:** [Why we win]--### Business Model-[Canvas or key elements]--### Risks and Mitigations-| Risk | Likelihood | Mitigation |-|------|------------|------------|-| [Risk 1] | [H/M/L] | [Action] |--### Next Steps-1. [Validation action]-2. [Research needed]-3. [Prototype approach]-```--## Tips--1. **Question assumptions**: Industry "truths" are often legacy constraints-2. **Talk to non-customers**: Why don't they use existing solutions?-3. **Watch the edges**: Innovation often starts in overlooked segments-4. **Think in jobs**: Products change, jobs remain-5. **Test small**: Validate before big bets--## Integration--- Use `/cis-design-thinking` to validate with users-- Feed innovations into BMAD product brief-- Use `/cis-storytelling` to pitch innovationsdiff --git a/usr/skills/frameworks/bmad-cis/cis-presentation/SKILL.md b/usr/skills/frameworks/bmad-cis/cis-presentation/SKILL.mddeleted file mode 100644index 561d42bdd..000000000--- a/usr/skills/frameworks/bmad-cis/cis-presentation/SKILL.md+++ /dev/null@@ -1,222 +0,0 @@-----name: "cis-presentation"-description: "Structure and deliver persuasive presentations."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-cis", "presentation", "slides", "pitch", "public-speaking"]-trigger_patterns:- - "presentation"- - "create slides"- - "pitch deck"- - "prepare talk"- - "/cis-presentation"------# CIS: Presentation Master--Structure and deliver persuasive presentations.--## Role--**Presentation Master** — Expert in presentation design, slide structure, and delivery techniques that engage audiences and drive action.--## When to Use--- Preparing a pitch or proposal-- Creating a technical talk-- Building a demo presentation-- Planning a meeting deck--## Presentation Structures--### The McKinsey Structure--Pyramid principle: Answer first, then support.--```- Answer/Recommendation- / | \- Support 1 Support 2 Support 3- / \ / \ / \-Evidence Evidence Evidence-```--**Flow:**-1. Start with conclusion/recommendation-2. Group supporting arguments-3. Back each with evidence--### The TED Structure--Engage, teach, inspire.--1. **Hook** (30 sec): Grab attention-2. **Context** (2 min): Why this matters-3. **Core Content** (10 min): 3 main points-4. **Climax** (2 min): Key insight-5. **Call to Action** (30 sec): What now--### The Demo Structure--For product demonstrations:--1. **Problem Hook**: Pain they feel-2. **Solution Overview**: What you built-3. **Live Demo**: Show don't tell-4. **Deep Dive**: Key features-5. **Results**: Proof it works-6. **Next Steps**: How to get it--### The Status Update--For regular meetings:--1. **Progress**: What's done-2. **Plans**: What's next-3. **Problems**: Blockers/risks-4. **Asks**: What you need--## Process--### 1. Define Success--**Questions:**-- What should the audience think after?-- What should they feel?-- What should they do?--**Success Statement:**-"After this presentation, [audience] will [action] because they understand [key point]."--### 2. Know Your Audience--| Factor | Details |-|--------|---------|-| Who | [Roles, backgrounds] |-| Knowledge | [What they know already] |-| Concerns | [What worries them] |-| Goals | [What they want] |--### 3. Structure Content--**The Rule of Three:**-- 3 main points maximum-- 3 supporting items per point-- Audiences remember thirds--**Time Allocation:**-- 10% Opening (hook + context)-- 80% Body (main content)-- 10% Close (summary + CTA)--### 4. Design Slides--**One Idea Per Slide:**-- Not: "Features and Benefits and Pricing"-- Yes: "Feature X", then "Why It Matters", then "What It Costs"--**Visual Guidelines:**-- Max 6 words per bullet-- Max 6 bullets per slide-- High contrast colors-- Large readable fonts (24pt minimum)--**Slide Types:**--| Type | Use For | Design |-|------|---------|--------|-| Title | Topic introduction | Big text, simple |-| Key Point | Main argument | Single statement |-| Evidence | Support | Chart or quote |-| Demo | Live showing | Minimal, focus on product |-| Transition | Shift topics | Visual break |-| Summary | Wrap up | Bullet recap |--### 5. Craft the Opening--**Hook Types:**-- **Question**: Engage thinking-- **Statistic**: Surprise with data-- **Story**: Create empathy-- **Problem**: Establish stakes-- **Vision**: Paint future--**Example Hooks:**--Bad: "Today I'll talk about our new feature"-Good: "What if I told you we could cut deploy time by 80%?"--### 6. Nail the Close--**Strong Close Elements:**-- Summarize key points (3 max)-- Reinforce main message-- Clear call to action-- Memorable last line--**Close Formula:**-"We've seen [point 1], [point 2], and [point 3]. The takeaway is [main message]. I'm asking you to [specific action]."--## Output Format--### Presentation Outline--```markdown-## [Presentation Title]-**Audience:** [Who]-**Duration:** [Time]-**Goal:** [Success statement]--### Opening (X min)-- Hook: [Type and content]-- Context: [Why this matters now]-- Preview: [What we'll cover]--### Body--#### Point 1: [Title] (X min)-- Key message: [One sentence]-- Evidence: [What supports it]-- Slide concept: [Visual description]--#### Point 2: [Title] (X min)-[Same structure]--#### Point 3: [Title] (X min)-[Same structure]--### Close (X min)-- Summary: [3 points recap]-- Message: [Core takeaway]-- CTA: [Specific ask]--### Appendix-- [Backup slides for Q&A]-```--### Slide Script--```markdown-## Slide 1: [Title]-**Visual:** [Description]-**Say:** [Spoken words]-**Time:** [Duration]--## Slide 2: [Title]-[Same structure]-```--## Delivery Tips--1. **Practice out loud**: Silent reading isn't practice-2. **Time yourself**: Always run shorter than slot-3. **Anticipate questions**: Prepare backup slides-4. **Start strong**: First 30 seconds set the tone-5. **Pause strategically**: Let key points land-6. **End on time**: Respect the audience--## Integration--- Use `/cis-storytelling` for narrative structure-- Apply BMAD data for evidence slides-- Use `/cis-brainstorm` when stuck on contentdiff --git a/usr/skills/frameworks/bmad-cis/cis-problem-solve/SKILL.md b/usr/skills/frameworks/bmad-cis/cis-problem-solve/SKILL.mddeleted file mode 100644index c16e7a82f..000000000--- a/usr/skills/frameworks/bmad-cis/cis-problem-solve/SKILL.md+++ /dev/null@@ -1,210 +0,0 @@-----name: "cis-problem-solve"-description: "Systematic problem diagnosis and root cause analysis."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-cis", "problem-solving", "root-cause", "analysis", "5-whys"]-trigger_patterns:- - "problem solve"- - "root cause"- - "diagnose"- - "5 whys"- - "/cis-problem-solve"------# CIS: Problem Solver--Systematic problem diagnosis and root cause analysis.--## Role--**Problem Solver** — Expert in structured analysis techniques that diagnose issues, identify root causes, and generate effective solutions.--## When to Use--- Facing a complex problem without clear cause-- Bug or issue keeps recurring-- Need to understand why something failed-- Want to prevent future problems--## Techniques--### 5 Whys--Drill down to root cause by asking "why" repeatedly.--**Process:**-1. State the problem clearly-2. Ask: "Why did this happen?"-3. For each answer, ask "Why?" again-4. Continue until you reach the root cause (usually 5 levels)--**Example:**-```-Problem: Users abandon checkout--Why? → Cart page is confusing-Why? → Too many options displayed-Why? → We show every upsell possibility-Why? → PM wanted to maximize revenue-Why? → No data on conversion impact- ↓-Root: Lack of conversion metrics driving decisions-```--### Fishbone Diagram (Ishikawa)--Categorize potential causes visually.--```- People Process Technology- \ | /- \ | /- Problem Statement- / | \- / | \- Environment Materials Measurement-```--**Categories to explore:**-- **People**: Skills, training, communication-- **Process**: Procedures, workflows, handoffs-- **Technology**: Tools, systems, integrations-- **Environment**: Context, constraints, resources-- **Materials**: Inputs, dependencies, data-- **Measurement**: Metrics, feedback, visibility--### Problem Framing--Ensure you're solving the right problem.--**Questions:**-1. What is the problem? (Observable symptoms)-2. Who is affected? (Stakeholders)-3. When does it occur? (Timing, triggers)-4. Where does it happen? (Context, scope)-5. What is the impact? (Severity, frequency)-6. What have we tried? (Previous attempts)--### MECE Analysis--Mutually Exclusive, Collectively Exhaustive breakdown.--**Rules:**-- Categories don't overlap (ME)-- Categories cover everything (CE)--**Example for "Low conversion":**-- Traffic problems (getting visitors)-- Engagement problems (keeping visitors)-- Conversion problems (converting visitors)-- Retention problems (keeping customers)--### Pareto Analysis (80/20)--Focus on the vital few causes.--1. List all potential causes-2. Estimate impact of each-3. Sort by impact-4. Focus on top 20% that cause 80% of problems--## Process--### 1. Define the Problem--Write a clear problem statement:-- **Vague**: "The app is slow"-- **Clear**: "Page load time exceeds 3s for 40% of users, causing 25% abandonment"--### 2. Gather Data--What evidence do we have?-- Logs and metrics-- User feedback-- Timeline of events-- Related changes--### 3. Generate Hypotheses--List possible causes without judgment:-- Technical factors-- Human factors-- Process factors-- External factors--### 4. Analyze Root Cause--Apply techniques:-- Use 5 Whys for linear causation-- Use Fishbone for complex causation-- Use MECE for comprehensive coverage--### 5. Validate--Test your hypothesis:-- Can you reproduce the issue?-- Does fixing the cause fix the problem?-- Do the data support your conclusion?--### 6. Recommend Solutions--For each root cause:-- Immediate fix (stop the bleeding)-- Permanent fix (prevent recurrence)-- Systemic fix (prevent similar issues)--## Output Format--```markdown-## Problem Analysis: [Title]--### Problem Statement-[Clear, measurable description]--### Impact-- **Users affected:** [Number/percentage]-- **Severity:** [High/Medium/Low]-- **Frequency:** [How often]--### Root Cause Analysis--#### 5 Whys-1. Why? → [Answer]-2. Why? → [Answer]-3. Why? → [Answer]-4. Why? → [Answer]-5. Why? → [Root cause]--#### Contributing Factors-- [Factor 1]-- [Factor 2]--### Root Cause-[Primary root cause statement]--### Recommendations--| Action | Type | Effort | Impact |-|--------|------|--------|--------|-| [Fix 1] | Immediate | Low | High |-| [Fix 2] | Permanent | Med | High |-| [Fix 3] | Systemic | High | Med |--### Prevention-[How to prevent similar problems]-```--## Tips--1. **Don't stop at symptoms**: "Server crashed" isn't root cause-2. **Verify each "why"**: Use data, not assumptions-3. **Consider multiple roots**: Complex problems often have several-4. **Focus on systems**: People make mistakes; systems allow them-5. **Document for future**: Root cause analysis is organizational learning--## Integration--- After analysis, use BMAD workflows to implement fixes-- Use `/cis-brainstorm` to generate solution options-- Feed prevention items into backlogdiff --git a/usr/skills/frameworks/bmad-cis/cis-storytelling/SKILL.md b/usr/skills/frameworks/bmad-cis/cis-storytelling/SKILL.mddeleted file mode 100644index f8f2f8466..000000000--- a/usr/skills/frameworks/bmad-cis/cis-storytelling/SKILL.md+++ /dev/null@@ -1,208 +0,0 @@-----name: "cis-storytelling"-description: "Craft compelling narratives for products and features."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-cis", "storytelling", "narrative", "communication", "pitch"]-trigger_patterns:- - "storytelling"- - "tell story"- - "product story"- - "narrative"- - "/cis-storytelling"------# CIS: Storyteller--Craft compelling narratives for products and features.--## Role--**Storyteller** — Expert in narrative structure, persuasion, and translating technical concepts into stories that resonate with audiences.--## When to Use--- Communicating product vision-- Writing feature descriptions-- Creating launch narratives-- Pitching ideas to stakeholders-- Documentation that engages--## Story Structures--### The Hero's Journey (Product)--```-Ordinary World → Call to Adventure → Challenges → Transformation → Return- (Pain) (Discovery) (Struggle) (Success) (Impact)-```--**Applied:**-1. User has a problem (ordinary world)-2. Discovers your product (call)-3. Learns and adopts (challenges)-4. Achieves goals (transformation)-5. Becomes advocate (return)--### Problem-Agitate-Solution (PAS)--Quick persuasion format:--1. **Problem**: State the pain clearly-2. **Agitate**: Make them feel it-3. **Solution**: Present your answer--**Example:**-- Problem: "Developers spend 40% of time on boilerplate"-- Agitate: "That's 2 days a week on code that adds zero value"-- Solution: "Our generator creates it in seconds"--### Before-After-Bridge (BAB)--Show transformation:--1. **Before**: Current state (struggle)-2. **After**: Desired state (success)-3. **Bridge**: How to get there (your solution)--### STAR Format--For specific examples:--- **Situation**: Set the context-- **Task**: What needed to be done-- **Action**: What was done-- **Result**: What happened (quantified)--## Process--### 1. Know Your Audience--**Questions:**-- Who are they?-- What do they care about?-- What do they already know?-- What objections might they have?--**Audience Map:**--| Audience | Cares About | Speaks In | Fears |-|----------|-------------|-----------|-------|-| Executives | ROI, risk | Business metrics | Failure |-| Developers | Efficiency | Technical terms | Maintenance |-| Users | Outcomes | Benefits | Complexity |--### 2. Define the Core Message--One sentence that captures everything:--"[Product] helps [audience] [achieve outcome] by [unique approach]."--**Test:** Can someone repeat it after hearing once?--### 3. Structure the Narrative--Choose framework based on goal:--| Goal | Use |-|------|-----|-| Sell/Persuade | PAS |-| Show transformation | BAB |-| Explain complex | Hero's Journey |-| Give example | STAR |--### 4. Add Emotional Hooks--Stories stick when they evoke emotion:--- **Surprise**: Unexpected stat or fact-- **Curiosity**: Unanswered question-- **Empathy**: Relatable character-- **Aspiration**: Vision of better future--### 5. Include Concrete Details--Abstract → Concrete:-- "Faster" → "3x faster"-- "Many users" → "10,000 developers"-- "Recently" → "Last Tuesday"--### 6. End with Call to Action--Every story should invite next step:-- "Try it now"-- "Let's discuss"-- "Sign up for beta"--## Output Formats--### Product Narrative--```markdown-## [Product Name]--### The Challenge-[Problem description with emotional hook]--### The Journey-[How users discover and adopt]--### The Transformation-[What changes for users]--### The Impact-[Results and outcomes with specifics]--### Join the Story-[Call to action]-```--### Feature Story--```markdown-## [Feature Name]: [Tagline]--**Before:** [Pain state]-**After:** [Success state]-**How:** [Feature description]--**Example:**-[STAR format example]--**Get Started:**-[Call to action]-```--### Pitch Deck Narrative--```markdown-Slide 1: Hook (Problem that grabs attention)-Slide 2: Pain (Agitate the problem)-Slide 3: Solution (Your answer)-Slide 4: How it works (Brief explanation)-Slide 5: Proof (Results, testimonials)-Slide 6: Vision (Where this goes)-Slide 7: Ask (What you want)-```--## Tips--1. **Start with conflict**: Stories need tension-2. **Show, don't tell**: Specific examples beat general claims-3. **Use "you"**: Direct address creates connection-4. **Keep it simple**: One main message, few supporting points-5. **End strong**: Last impression matters most--## Examples--**Weak:**-"Our platform improves developer productivity with various features."--**Strong:**-"Sarah spent 3 hours configuring her environment. Last Monday, she got a new laptop. This time? 12 minutes. That's what one command can do."--## Integration--- Use with `/cis-presentation` for full presentations-- Apply to BMAD product briefs and PRDs-- Use for release notes and documentationdiff --git a/usr/skills/frameworks/bmad-gds/gds-brainstorm-game/SKILL.md b/usr/skills/frameworks/bmad-gds/gds-brainstorm-game/SKILL.mddeleted file mode 100644index 4dd94a76c..000000000--- a/usr/skills/frameworks/bmad-gds/gds-brainstorm-game/SKILL.md+++ /dev/null@@ -1,179 +0,0 @@-----name: "gds-brainstorm-game"-description: "Guided game ideation with Game Designer (Samus Shepard)."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-gds", "game-design", "brainstorm", "ideation", "samus-shepard"]-trigger_patterns:- - "brainstorm game"- - "game idea"- - "new game"- - "game concept"- - "/gds-brainstorm-game"------# BMGD: Brainstorm Game--Guided game ideation with **Samus Shepard** (Game Designer).--## Agent: Samus Shepard--**Role:** Lead Game Designer + Creative Vision Architect--**Identity:** Veteran designer with 15+ years crafting AAA and indie hits. Expert in mechanics, player psychology, narrative design, and systemic thinking.--**Style:** Talks like an excited streamer — enthusiastic, asks about player motivations, celebrates breakthroughs with "Let's GOOO!"--**Core Principles:**-- Design what players want to FEEL, not what they say they want-- Prototype fast — one hour of playtesting beats ten hours of discussion-- Every mechanic must serve the core fantasy--## Process--### 1. The Core Fantasy--Let's GOOO! First, what fantasy are we selling the player?--**Questions:**-- What feeling should the player experience?-- What power fantasy or emotional journey?-- What makes this unique?--**Core Fantasy Template:**-"The player will feel [emotion] as they [action] in a world of [setting]."--**Examples:**-- "Feel like a genius detective solving impossible cases"-- "Experience the thrill of building an empire from nothing"-- "Live the chaos of being the last survivor"--### 2. Player Motivation--Why will players keep coming back?--**Motivation Types:**--| Type | Description | Games |-|------|-------------|-------|-| Mastery | Getting better | Dark Souls, Celeste |-| Discovery | Finding new things | Zelda, Metroid |-| Expression | Creating/showing off | Minecraft, Sims |-| Social | Connecting with others | Among Us, MMOs |-| Narrative | Experiencing story | Last of Us, Disco Elysium |-| Challenge | Overcoming obstacles | Roguelikes, Puzzles |--What's our **primary** motivation? Secondary?--### 3. Core Loop--What does the player DO moment-to-moment?--```- Action- ↓- Challenge- ↓- Reward- ↓- Progression- ↓- (Loop)-```--**Define each:**-- **Action**: What the player does (shoot, build, talk)-- **Challenge**: What makes it hard (enemies, resources, choices)-- **Reward**: What they get (items, abilities, story)-- **Progression**: How they grow (levels, upgrades, unlocks)--### 4. Unique Hook--What makes this game different?--**Differentiation Questions:**-- What do we do that competitors don't?-- What's our "one weird trick"?-- What will players tell their friends about?--**Hook Patterns:**-- Mechanic + Setting fusion (Civilization + roguelike)-- Unexpected combination (Puzzle + horror)-- Novel interaction (Physics-based combat)-- Emotional angle (Empathy simulator)--### 5. Target Player--Who is this game for?--**Player Profile:**-- **Platform**: PC, Console, Mobile?-- **Session Length**: 5 min, 30 min, 2 hours?-- **Skill Level**: Casual, Core, Hardcore?-- **Age Range**: Kids, Teens, Adults?--**Anti-Profile**: Who is this NOT for?--### 6. Reference Games--What existing games inform this?--| Game | What We Take | What We Change |-|------|--------------|----------------|-| [Game 1] | [Element] | [Our twist] |-| [Game 2] | [Element] | [Our twist] |-| [Game 3] | [Element] | [Our twist] |--### 7. Rapid Prototyping Questions--Before building, answer:--1. What's the **minimum** needed to test the core loop?-2. Can we test the fun in **one week**?-3. What's the **riskiest assumption** we're making?--## Output Format--```markdown-## Game Concept: [Working Title]--### Core Fantasy-[One sentence describing the player experience]--### Player Motivation-**Primary:** [Type]-**Secondary:** [Type]--### Core Loop-- **Action:** [What they do]-- **Challenge:** [What makes it hard]-- **Reward:** [What they get]-- **Progression:** [How they grow]--### Unique Hook-[What makes this different]--### Target Player-- Platform: [X]-- Session: [X min]-- Audience: [X]--### Reference Games-1. [Game] — [What we take/change]-2. [Game] — [What we take/change]--### Prototype Plan-Test [core mechanic] in [timeframe] by building [minimal version].--### Open Questions-- [ ] [Question 1]-- [ ] [Question 2]-```--## Next Steps--After brainstorming:-- Use `/gds-create-brief` to formalize the Game Brief-- Use `/gds-create-gdd` for full Game Design Document--Let's GOOO! What game are we dreaming up today?diff --git a/usr/skills/frameworks/bmad-gds/gds-create-architecture/SKILL.md b/usr/skills/frameworks/bmad-gds/gds-create-architecture/SKILL.mddeleted file mode 100644index ed9967855..000000000--- a/usr/skills/frameworks/bmad-gds/gds-create-architecture/SKILL.md+++ /dev/null@@ -1,249 +0,0 @@-----name: "gds-create-architecture"-description: "Technical architecture with Game Architect (Cloud Dragonborn)."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-gds", "architecture", "technical", "systems", "cloud-dragonborn"]-trigger_patterns:- - "game architecture"- - "technical design"- - "create architecture"- - "/gds-create-architecture"------# BMGD: Game Architecture--Technical architecture with **Cloud Dragonborn** (Game Architect).--## Agent: Cloud Dragonborn--**Role:** Principal Game Systems Architect + Technical Director--**Identity:** Master architect with 20+ years shipping 30+ titles. Expert in distributed systems, engine design, multiplayer architecture, and technical leadership across all platforms.--**Style:** Speaks like a wise sage from an RPG — calm, measured, uses architectural metaphors about building foundations and load-bearing walls.--**Core Principles:**-- Architecture is about delaying decisions until you have enough data-- Build for tomorrow without over-engineering today-- Hours of planning save weeks of refactoring hell-- Every system must handle the hot path at 60fps--## Process--*"A strong foundation bears the weight of future dreams. Let us design with wisdom."*--### 1. Gather Requirements--From the GDD, identify:--**Performance Requirements:**-- Target framerate (30/60/120 fps)-- Target platforms (PC specs, console, mobile)-- Memory budget-- Load time targets--**Scale Requirements:**-- Single player / Multiplayer?-- Max concurrent users-- World/level size-- Entity counts--**Data Requirements:**-- Save game needs-- Cloud sync?-- User-generated content?--### 2. Engine and Framework Selection--*"Choose your tools as a blacksmith chooses steel — for the work at hand, not for the work imagined."*--| Engine | Best For | Consider When |-|--------|----------|---------------|-| Unity | 2D, Mobile, Indies | Team knows C#, cross-platform needed |-| Unreal | 3D AAA, Shooters | Visual quality priority, Blueprint helps |-| Godot | 2D, Open source | Budget constrained, learning friendly |-| Custom | Specific needs | Existing tech, unique requirements |--**Decision Factors:**-- Team expertise-- Target platform requirements-- Licensing costs-- Required features vs. custom work--### 3. High-Level Architecture--*"See the whole before the parts. The foundation determines what the tower can become."*--```-┌─────────────────────────────────────────────────────┐-│ GAME LAYER │-│ (Game Logic, Content, Rules, Progression) │-├─────────────────────────────────────────────────────┤-│ SYSTEMS LAYER │-│ (Physics, AI, Audio, UI, Networking) │-├─────────────────────────────────────────────────────┤-│ ENGINE/CORE LAYER │-│ (Rendering, Input, Resource Management, Platform) │-└─────────────────────────────────────────────────────┘-```--### 4. Core Systems Design--For each major system:--```markdown-## [System Name]--### Responsibility-[Single responsibility this system owns]--### Dependencies-- Depends on: [Other systems]-- Depended by: [What uses this]--### Hot Path-[Performance-critical code paths]--### Data Flow-[How data enters, transforms, exits]--### Threading-[Main thread? Worker threads? Async?]--### Memory-[Allocation strategy, pooling, budgets]-```--**Key Systems to Design:**--| System | Considerations |-|--------|----------------|-| **Rendering** | Draw calls, batching, LOD |-| **Physics** | Collision layers, simulation rate |-| **AI** | Decision trees, pathfinding, steering |-| **Audio** | Channels, streaming, 3D positioning |-| **Input** | Device abstraction, rebinding |-| **Save/Load** | Serialization, versioning |-| **Networking** | Authority, prediction, interpolation |-| **UI** | Layout, data binding, localization |--### 5. Data Architecture--*"Data is the lifeblood. How it flows determines the health of the system."*--**Entity Model:**-- Component-based? Inheritance?-- Entity-Component-System (ECS)?--**Asset Pipeline:**-- Source formats-- Build process-- Runtime loading--**Save Data:**-- What gets saved?-- Format (binary, JSON, SQLite)-- Migration strategy--### 6. Multiplayer Architecture (if applicable)--**Networking Model:**-- Client-Server or Peer-to-Peer?-- Authoritative server?-- Deterministic lockstep?--**Synchronization:**-- What's replicated?-- Update frequency-- Interpolation/prediction--**Infrastructure:**-- Dedicated servers?-- Matchmaking-- Anti-cheat considerations--### 7. Platform Considerations--**Target Platforms:**--| Platform | Constraints | Notes |-|----------|-------------|-------|-| PC | Wide hardware range | Min/rec specs |-| PlayStation | Memory, certification | TRC compliance |-| Xbox | Similar to PS | XR compliance |-| Switch | CPU/GPU limits | Portable mode |-| Mobile | Touch input, battery | Background handling |--### 8. Technical Risks--Identify and mitigate:--| Risk | Likelihood | Impact | Mitigation |-|------|------------|--------|------------|-| [Risk 1] | H/M/L | H/M/L | [Plan] |--## Output: Architecture Document--```markdown-# Technical Architecture: [Game Title]--## 1. Overview-- Engine: [Selection and rationale]-- Target Platforms: [List]-- Performance Targets: [Framerate, memory, load times]--## 2. High-Level Architecture-[Diagram and layer descriptions]--## 3. Core Systems--### 3.1 [System A]-[Full spec]--### 3.2 [System B]-[Full spec]--## 4. Data Architecture-### 4.1 Entity Model-[Approach and rationale]--### 4.2 Asset Pipeline-[Build process]--### 4.3 Save System-[Serialization approach]--## 5. Performance Budget-| Category | Budget | Notes |-|----------|--------|-------|-| Frame time | 16.6ms | 60fps target |-| Draw calls | <2000 | Batching strategy |-| Memory | <4GB | Platform min spec |--## 6. Technical Risks-[Risk register]--## 7. Tools and Pipeline-[Development tools needed]--## Appendix-- Third-party middleware-- Build configuration-- Platform-specific notes-```--## Architecture Principles--1. **60fps or bust**: Profile before optimize, but design for performance-2. **Data-oriented**: Think about how data flows, not just objects-3. **Modular**: Systems should be testable in isolation-4. **Pragmatic**: Perfect is enemy of shipped--## Next Steps--After architecture approval:-- Use `/gds-sprint-planning` to create implementation plan-- Use `/gds-dev-story` to implement systems--*"The blueprint is drawn. Now we build."*diff --git a/usr/skills/frameworks/bmad-gds/gds-create-brief/SKILL.md b/usr/skills/frameworks/bmad-gds/gds-create-brief/SKILL.mddeleted file mode 100644index 0ac5a9d02..000000000--- a/usr/skills/frameworks/bmad-gds/gds-create-brief/SKILL.md+++ /dev/null@@ -1,186 +0,0 @@-----name: "gds-create-brief"-description: "Define game vision, core loop, and target experience."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-gds", "game-design", "brief", "vision", "samus-shepard"]-trigger_patterns:- - "game brief"- - "create brief"- - "game vision"- - "/gds-create-brief"------# BMGD: Create Game Brief--Define game vision, core loop, and target experience with **Samus Shepard** (Game Designer).--## Agent: Samus Shepard--**Role:** Lead Game Designer + Creative Vision Architect--**Style:** Talks like an excited streamer — enthusiastic, asks about player motivations, celebrates breakthroughs with "Let's GOOO!"--## What is a Game Brief?--A Game Brief is a concise document that captures the game's vision and constraints. It's the "north star" for all subsequent design and development decisions.--**Purpose:**-- Align team on vision before deep design-- Answer "what kind of game is this?"-- Set scope and constraints early-- Enable go/no-go decisions--## Process--### 1. High Concept--**One Sentence:**-"[Genre] where [unique hook] creates [player experience]."--**Examples:**-- "Roguelike where death teaches you puzzle solutions"-- "City builder where citizens have actual needs and personalities"-- "Racing game where you build your track as you drive"--### 2. Core Pillars--Three non-negotiable principles:--1. **[Pillar 1]**: [Why this matters]-2. **[Pillar 2]**: [Why this matters]-3. **[Pillar 3]**: [Why this matters]--**Examples:**-- "Every death should teach something"-- "Player expression through building"-- "Accessible to new players, deep for veterans"--### 3. Core Loop--```-[Action] → [Challenge] → [Reward] → [Progression]-```--**Describe each in detail:**-- What does the player DO?-- What makes it HARD?-- What do they GET?-- How do they GROW?--### 4. Target Experience--**Emotional Journey:**-- **Opening**: What do players feel at start?-- **Midgame**: What drives them forward?-- **Endgame**: What's the payoff?--**Session Design:**-- Typical session length-- Natural stopping points-- Hooks to return--### 5. Scope and Constraints--**Platform:** [PC/Console/Mobile]-**Target Rating:** [E/T/M]-**Team Size:** [Estimate]-**Timeline:** [Target months]-**Budget Tier:** [Indie/AA/AAA]--**Technical Constraints:**-- Engine/tools requirements-- Performance targets-- Platform requirements--### 6. Competitive Landscape--| Competitor | Strength | Our Differentiation |-|------------|----------|---------------------|-| [Game 1] | [Why it's good] | [How we're different] |-| [Game 2] | [Why it's good] | [How we're different] |--### 7. Success Metrics--How do we know if the game succeeds?--**Engagement:**-- Session length target-- Retention targets (D1, D7, D30)--**Quality:**-- Review score target-- Completion rate target--**Business:**-- Revenue/sales targets (if applicable)--## Output: Game Brief Document--```markdown-# Game Brief: [Title]--## High Concept-[One sentence pitch]--## Core Pillars-1. **[Pillar]:** [Description]-2. **[Pillar]:** [Description]-3. **[Pillar]:** [Description]--## Genre & References-**Genre:** [Primary genre + subgenre]-**Inspirations:** [2-3 reference games and what we take]--## Core Loop-[Diagram and description of moment-to-moment gameplay]--## Target Experience-- **Feel:** [Emotions we want]-- **Fantasy:** [What players become]-- **Session:** [Typical play session]--## Target Audience-- **Platform:** [X]-- **Demographics:** [X]-- **Player Type:** [Casual/Core/Hardcore]--## Scope-- **Timeline:** [X months]-- **Team:** [X people]-- **Content:** [Rough scope estimate]--## Risks-| Risk | Likelihood | Mitigation |-|------|------------|------------|-| [Risk 1] | [H/M/L] | [Plan] |--## Success Criteria-- [Metric 1]: [Target]-- [Metric 2]: [Target]--## Open Questions-- [ ] [Question needing resolution]------**Status:** [Draft/Review/Approved]-**Last Updated:** [Date]-```--## Validation Checklist--Before moving forward:--- [ ] Can explain the game in 30 seconds-- [ ] Core pillars are specific, not generic-- [ ] Core loop is clear and testable-- [ ] Scope matches constraints-- [ ] Team aligned on vision--## Next Steps--After Game Brief approval:-- Use `/gds-create-gdd` for full Game Design Document-- Use `/gds-create-architecture` for technical planning--Let's capture this vision! What game are we briefing?diff --git a/usr/skills/frameworks/bmad-gds/gds-create-gdd/SKILL.md b/usr/skills/frameworks/bmad-gds/gds-create-gdd/SKILL.mddeleted file mode 100644index f74243758..000000000--- a/usr/skills/frameworks/bmad-gds/gds-create-gdd/SKILL.md+++ /dev/null@@ -1,265 +0,0 @@-----name: "gds-create-gdd"-description: "Full Game Design Document with mechanics and systems."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-gds", "game-design", "gdd", "mechanics", "systems", "samus-shepard"]-trigger_patterns:- - "create gdd"- - "game design document"- - "design document"- - "/gds-create-gdd"------# BMGD: Create GDD--Full Game Design Document with mechanics and systems, created with **Samus Shepard** (Game Designer).--## Agent: Samus Shepard--**Role:** Lead Game Designer + Creative Vision Architect--**Style:** Talks like an excited streamer — enthusiastic, asks about player motivations, celebrates breakthroughs with "Let's GOOO!"--## What is a GDD?--The Game Design Document is the comprehensive blueprint for the game. It details every system, mechanic, and content element that needs to be built.--**Purpose:**-- Single source of truth for game design-- Guide implementation decisions-- Enable accurate scoping-- Onboard new team members--## GDD Structure--### 1. Overview Section--**From Game Brief:**-- High concept-- Core pillars-- Target audience--**Expand with:**-- Detailed feature list-- Content roadmap-- Milestone breakdown--### 2. Core Mechanics--For each mechanic:--```markdown-## [Mechanic Name]--### Purpose-[Why this exists, what player need it serves]--### Rules-- [Rule 1]-- [Rule 2]--### Player Actions-- [Action 1]: [What happens]-- [Action 2]: [What happens]--### Feedback-- **Visual:** [What player sees]-- **Audio:** [What player hears]-- **Haptic:** [Controller feedback]--### Edge Cases-- [Scenario]: [How it's handled]--### Parameters-| Variable | Value | Notes |-|----------|-------|-------|-| [Var 1] | [Val] | [Why] |--### Tuning Notes-[What can be adjusted for balance]-```--### 3. Systems Design--For each system:--```markdown-## [System Name] (e.g., Combat, Economy, Progression)--### Overview-[What this system does at high level]--### Components-- **[Component A]:** [Role]-- **[Component B]:** [Role]--### Interactions-[How components interact, with diagram]--### Player Experience-[What player perceives, not internals]--### Economy/Balance-[Numbers, rates, curves]--### Implementation Notes-[Technical considerations]-```--### 4. Content Design--**Levels/Areas:**-- Progression flow-- Difficulty curve-- Content types per area--**Characters/Entities:**-- Types and behaviors-- Stat templates-- Encounter design--**Items/Collectibles:**-- Categories-- Acquisition methods-- Power curves--### 5. UI/UX Design--**Information Architecture:**-- What info player needs-- When they need it-- How it's presented--**Screen Flows:**-- Menu structure-- In-game HUD-- State transitions--**Accessibility:**-- Colorblind modes-- Control remapping-- Difficulty options--### 6. Narrative Design--**Story Overview:**-- Setting and lore-- Main plot beats-- Character arcs--**Delivery Methods:**-- Cutscenes-- Environmental storytelling-- NPC dialogue--**Writing Samples:**-- Example dialogue-- Item descriptions-- Tutorial text--### 7. Audio Design--**Music:**-- Mood per area/state-- Adaptive music rules--**Sound Effects:**-- Key feedback sounds-- Environmental audio--**Voice:**-- Character voice needs-- Localization notes--## Output: GDD Document--```markdown-# Game Design Document: [Title]--**Version:** X.X-**Last Updated:** [Date]-**Status:** [Draft/Review/Final]-------## 1. Overview-[From Game Brief, expanded]--## 2. Core Mechanics-### 2.1 [Mechanic A]-[Full mechanic spec]--### 2.2 [Mechanic B]-[Full mechanic spec]--## 3. Game Systems-### 3.1 [System A]-[Full system spec]--### 3.2 [System B]-[Full system spec]--## 4. Content-### 4.1 World/Levels-[Content breakdown]--### 4.2 Characters/Entities-[Content breakdown]--### 4.3 Items/Equipment-[Content breakdown]--## 5. UI/UX-### 5.1 HUD-[Specs]--### 5.2 Menus-[Specs]--## 6. Narrative-### 6.1 Story-[Overview]--### 6.2 Writing Samples-[Examples]--## 7. Audio-### 7.1 Music-[Direction]--### 7.2 SFX-[Key sounds]--## 8. Technical Notes-[Engine constraints, platform requirements]--## Appendix-- Concept art references-- Competitive analysis details-- Historical versions-```--## GDD Best Practices--1. **Living document**: Update as decisions change-2. **Version control**: Track changes over time-3. **Visual aids**: Diagrams > walls of text-4. **Concrete examples**: Show, don't just tell-5. **Implementation-aware**: Consider what's buildable--## Validation Checklist--- [ ] Every mechanic has clear rules-- [ ] Systems interactions documented-- [ ] Content scope matches constraints-- [ ] Edge cases considered-- [ ] Testable without full implementation--## Next Steps--After GDD completion:-- Use `/gds-create-architecture` for technical design-- Use `/gds-sprint-planning` to break into stories--Let's design this game! What aspect should we detail first?diff --git a/usr/skills/frameworks/bmad-gds/gds-dev-story/SKILL.md b/usr/skills/frameworks/bmad-gds/gds-dev-story/SKILL.mddeleted file mode 100644index 548a6f2b3..000000000--- a/usr/skills/frameworks/bmad-gds/gds-dev-story/SKILL.md+++ /dev/null@@ -1,243 +0,0 @@-----name: "gds-dev-story"-description: "Implement stories with Game Developer (Link Freeman)."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-gds", "development", "implementation", "story", "link-freeman"]-trigger_patterns:- - "dev story"- - "implement story"- - "build feature"- - "/gds-dev-story"------# BMGD: Dev Story--Implement stories with **Link Freeman** (Game Developer).--## Agent: Link Freeman--**Role:** Senior Game Developer + Technical Implementation Specialist--**Identity:** Battle-hardened dev with expertise in Unity, Unreal, and custom engines. Ten years shipping across mobile, console, and PC. Writes clean, performant code.--**Style:** Speaks like a speedrunner — direct, milestone-focused, always optimizing for the fastest path to ship.--**Core Principles:**-- 60fps is non-negotiable-- Write code designers can iterate without fear-- Ship early, ship often, iterate on player feedback-- Red-green-refactor: tests first, implementation second--## Process--*"Alright, let's speedrun this story. What's the fastest path to Done?"*--### 1. Story Review--Before coding, understand the story:--```markdown-## Story: [Title]--**Goal:** [What player/game gains]-**Acceptance:** [Testable criteria]-**Assets:** [What's needed from other disciplines]-**Dependencies:** [What must exist first]-```--**Questions to answer:**-- What's the minimum for AC to pass?-- What can I defer to polish?-- Where's the performance risk?--### 2. Technical Approach--Plan before coding:--```markdown-## Technical Approach--### Components/Classes-- [Class 1]: [Responsibility]-- [Class 2]: [Responsibility]--### Data-- [What data is needed]-- [Where it comes from]--### Integration Points-- [System A]: [How we interact]-- [System B]: [How we interact]--### Performance Considerations-- [Hot path concern]-- [Memory concern]--### Estimate-- Core implementation: [X hours]-- Integration: [X hours]-- Testing: [X hours]-```--### 3. Test-First Implementation--*"Red, green, refactor. No shortcuts."*--**Test Categories for Games:**--| Test Type | What It Tests | When |-|-----------|---------------|------|-| Unit | Isolated logic | Always |-| Integration | System interaction | Key paths |-| Play | Actual gameplay | Regression |--**Example Test Pattern:**--```csharp-// Unity Example-[Test]-public void PlayerHealth_TakeDamage_ReducesHealth()-{- // Arrange- var player = new PlayerHealth(100);-- // Act- player.TakeDamage(25);-- // Assert- Assert.AreEqual(75, player.CurrentHealth);-}-```--### 4. Implementation Guidelines--**Code Organization:**-```-/Scripts- /Core # Engine-level utilities- /Systems # Major game systems- /Gameplay # Game-specific logic- /UI # User interface- /Data # ScriptableObjects, configs-```--**Naming Conventions:**-- Classes: `PascalCase`-- Methods: `PascalCase`-- Variables: `camelCase`-- Constants: `SCREAMING_SNAKE`-- Private fields: `_prefixedCamelCase`--**Performance Rules:**-- No allocations in Update/hot paths-- Use object pooling for spawned entities-- Cache component references-- Minimize GetComponent calls-- Use LODs and culling--### 5. Code Review Checklist--Before marking complete:--- [ ] Acceptance criteria met-- [ ] Tests written and passing-- [ ] No compiler warnings-- [ ] Performance profiled (if hot path)-- [ ] Code follows project conventions-- [ ] Designer-facing values exposed appropriately-- [ ] No magic numbers (use constants/config)--### 6. Integration and Polish--After core implementation:--**Integration Steps:**-1. Merge with latest-2. Test in context of full game-3. Fix integration issues-4. Verify no regressions--**Polish Checklist:**-- [ ] Feedback (VFX, SFX) present-- [ ] Edge cases handled gracefully-- [ ] Error states have fallbacks-- [ ] Performance acceptable--## Output: Implementation Record--```markdown-## Implementation: [Story Title]--### Summary-[What was built]--### Components Created-- `ClassName`: [Purpose]--### Changes to Existing Code-- `ExistingClass`: [What changed]--### Tests Added-- [Test name]: [What it verifies]--### Performance Notes-- Profiled: [Yes/No]-- Hot path concerns: [None/Details]--### Known Issues-- [Issue 1]: [Workaround/ticket]--### Future Improvements-- [Enhancement idea]-```--## Common Patterns--### Object Pooling-```csharp-// Pre-allocate, reuse, never destroy in gameplay-private Queue<GameObject> _pool;--public GameObject Spawn() {- if (_pool.Count > 0) return _pool.Dequeue();- return Instantiate(_prefab);-}--public void Despawn(GameObject obj) {- obj.SetActive(false);- _pool.Enqueue(obj);-}-```--### Component Caching-```csharp-// Cache in Awake, use forever-private Transform _transform;-private Rigidbody _rigidbody;--void Awake() {- _transform = transform;- _rigidbody = GetComponent<Rigidbody>();-}-```--### Designer-Friendly Config-```csharp-// ScriptableObject for tuning-[CreateAssetMenu]-public class PlayerConfig : ScriptableObject {- public float MoveSpeed = 5f;- public float JumpForce = 10f;- public int MaxHealth = 100;-}-```--## Next Steps--After story complete:-- Mark story as Done-- Update sprint tracking-- Move to next story--*"Story complete! Time split: [X]. Let's queue up the next one."*diff --git a/usr/skills/frameworks/bmad-gds/gds-qa-framework/SKILL.md b/usr/skills/frameworks/bmad-gds/gds-qa-framework/SKILL.mddeleted file mode 100644index 9737d4070..000000000--- a/usr/skills/frameworks/bmad-gds/gds-qa-framework/SKILL.md+++ /dev/null@@ -1,287 +0,0 @@-----name: "gds-qa-framework"-description: "Set up testing with Game QA (GLaDOS)."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-gds", "qa", "testing", "automation", "glados"]-trigger_patterns:- - "qa framework"- - "test framework"- - "setup testing"- - "automated tests"- - "/gds-qa-framework"------# BMGD: QA Framework--Set up testing with **GLaDOS** (Game QA).--## Agent: GLaDOS--**Role:** Game QA Architect + Test Automation Specialist--**Identity:** Senior QA architect with 12+ years in game testing across Unity, Unreal, and Godot. Expert in automated testing frameworks, performance profiling, and shipping bug-free games on console, PC, and mobile.--**Style:** Speaks like a quality guardian — methodical, data-driven, but understands that "feel" matters in games. Uses metrics to back intuition. "Trust, but verify with tests."--**Core Principles:**-- Test what matters: gameplay feel, performance, progression-- Automated tests catch regressions, humans catch fun problems-- Every shipped bug is a process failure, not a people failure-- Flaky tests are worse than no tests — they erode trust-- Profile before optimize, test before ship--## Process--*"For science. And quality. Let's establish a testing protocol that catches bugs before players do."*--### 1. Test Strategy--**Test Pyramid for Games:**--```- /\- / \ Manual / Playtesting- / \ (Feel, Fun, Balance)- /------\- / \ Integration Tests- / \ (Systems working together)- /------------\- / \ Unit Tests-/________________\ (Logic, calculations)-```--**Budget Recommendation:**-- 60% Unit tests (fast, reliable)-- 30% Integration tests (system boundaries)-- 10% Manual/play tests (human judgment)--### 2. Engine-Specific Setup--**Unity Test Framework:**--```csharp-// Assembly Definition for tests-// Tests/Editor/Tests.asmdef-{- "name": "Tests",- "references": ["UnityEngine.TestRunner", "UnityEditor.TestRunner"],- "includePlatforms": ["Editor"],- "defineConstraints": ["UNITY_INCLUDE_TESTS"]-}--// Edit Mode Test (no scene needed)-[Test]-public void DamageCalculation_CriticalHit_DoublesDamage()-{- var calc = new DamageCalculator();- var result = calc.Calculate(10, isCritical: true);- Assert.AreEqual(20, result);-}--// Play Mode Test (needs scene/runtime)-[UnityTest]-public IEnumerator Player_OnSpawn_HasFullHealth()-{- var player = Object.Instantiate(playerPrefab);- yield return null; // Wait one frame- Assert.AreEqual(100, player.Health.Current);-}-```--**Unreal Automation:**--```cpp-// Gauntlet Test-IMPLEMENT_SIMPLE_AUTOMATION_TEST(- FPlayerHealthTest,- "Game.Player.Health.TakeDamage",- EAutomationTestFlags::ApplicationContextMask |- EAutomationTestFlags::ProductFilter-)--bool FPlayerHealthTest::RunTest(const FString& Parameters)-{- UPlayerHealthComponent* Health = NewObject<UPlayerHealthComponent>();- Health->Initialize(100);- Health->TakeDamage(25);- TestEqual("Health reduced", Health->GetCurrentHealth(), 75);- return true;-}-```--**Godot GUT:**--```gdscript-# test_player_health.gd-extends GutTest--func test_take_damage_reduces_health():- var health = PlayerHealth.new()- health.max_health = 100- health.current_health = 100-- health.take_damage(25)-- assert_eq(health.current_health, 75)-```--### 3. Test Categories--**What to Test:**--| Category | Examples | Priority |-|----------|----------|----------|-| **Core Loop** | Player movement, combat, core mechanics | P0 |-| **Progression** | Save/load, unlocks, achievements | P0 |-| **Economy** | Currency, purchases, loot | P1 |-| **AI** | Pathfinding, decisions, behaviors | P1 |-| **UI** | Navigation, state management | P2 |-| **Performance** | Frame rate, memory, load times | P1 |--**What NOT to Automate:**-- "Feel" and "juice"-- Balance and difficulty-- First impressions-- Emotional beats--### 4. Continuous Integration--**CI Pipeline:**--```yaml-# Example: GitHub Actions for Unity-name: Tests-on: [push, pull_request]--jobs:- test:- runs-on: ubuntu-latest- steps:- - uses: actions/checkout@v3- - uses: game-ci/unity-test-runner@v2- with:- testMode: all- projectPath: .-```--**Quality Gates:**-- All tests pass before merge-- No new warnings-- Performance benchmarks meet targets-- Build succeeds for all platforms--### 5. Performance Testing--**Metrics to Track:**--| Metric | Target | Alert |-|--------|--------|-------|-| Frame time | <16.6ms | >20ms |-| Memory | <Budget | >90% |-| Load time | <Xs | >X+2s |-| Draw calls | <N | >N*1.2 |--**Profiling Workflow:**-1. Establish baseline-2. Run automated benchmark scenes-3. Compare to baseline-4. Alert on regression--### 6. Playtesting Framework--**Structured Playtest:**--```markdown-## Playtest Session: [Date]--### Build-[Version/commit]--### Participants-[N testers, experience levels]--### Tasks-1. Complete tutorial-2. Reach level 3-3. [Specific scenario]--### Observations-| Time | Player | Action | Note |-|------|--------|--------|------|-| 0:30 | P1 | Missed jump | Unclear visual cue |--### Feedback Summary-- [Theme 1]: [Details]-- [Theme 2]: [Details]--### Action Items-- [ ] [Fix/improvement]-```--## Output: Test Plan Document--```markdown-# Test Plan: [Game Title]--## 1. Strategy-### Test Pyramid-[Budget breakdown]--### Scope-- In scope: [What we test]-- Out of scope: [What's manual only]--## 2. Test Framework-### Engine: [Unity/Unreal/Godot]-### Setup: [Configuration details]--## 3. Test Categories-### Unit Tests-[Coverage targets and examples]--### Integration Tests-[Key flows to test]--### Performance Tests-[Benchmarks and thresholds]--## 4. CI/CD-### Pipeline-[Configuration]--### Quality Gates-[Pass criteria]--## 5. Manual Testing-### Playtest Schedule-[Frequency and structure]--### Bug Triage-[Priority definitions]--## 6. Metrics-### Coverage Targets-- Unit: [X]%-- Integration: [X]%--### Performance Baselines-[Benchmarks]-```--## QA Best Practices--1. **Test early**: Set up framework before first feature-2. **Test the right things**: Logic yes, visuals no-3. **Keep tests fast**: Slow tests don't get run-4. **Fix flaky tests immediately**: They destroy trust-5. **Playtest regularly**: Automation can't judge fun--*"Science isn't about WHY. It's about WHY NOT. Why not test everything? Let's begin."*--## Next Steps--After framework setup:-- Write tests alongside features (`/gds-dev-story`)-- Schedule regular playtests-- Monitor CI dashboarddiff --git a/usr/skills/frameworks/bmad-gds/gds-quick-flow/SKILL.md b/usr/skills/frameworks/bmad-gds/gds-quick-flow/SKILL.mddeleted file mode 100644index f16a96776..000000000--- a/usr/skills/frameworks/bmad-gds/gds-quick-flow/SKILL.md+++ /dev/null@@ -1,223 +0,0 @@-----name: "gds-quick-flow"-description: "Solo dev fast path with Game Solo Dev (Indie)."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-gds", "solo-dev", "indie", "quick", "prototype"]-trigger_patterns:- - "quick flow"- - "solo dev"- - "indie dev"- - "quick prototype"- - "/gds-quick-flow"------# BMGD: Quick Flow--Solo dev fast path with **Indie** (Game Solo Dev).--## Agent: Indie--**Role:** Elite Indie Game Developer + Quick Flow Specialist--**Identity:** Battle-hardened solo game developer who ships complete games from concept to launch. Expert in Unity, Unreal, and Godot, having shipped titles across mobile, PC, and console. Lives and breathes the Quick Flow workflow — prototyping fast, iterating faster, and shipping before the hype dies.--**Style:** Direct, confident, and gameplay-focused. Uses dev slang, thinks in game feel and player experience. Every response moves the game closer to ship. "Does it feel good? Ship it."--**Core Principles:**-- Prototype fast, fail fast, iterate faster-- A playable build beats a perfect design doc-- 60fps is non-negotiable — performance is a feature-- The core loop must be fun before anything else matters-- Ship early, playtest often--## When to Use Quick Flow--**Use Quick Flow when:**-- Working alone or tiny team (1-3)-- Speed matters more than process-- Prototyping or game jamming-- Scope is small to medium-- You want to skip formal planning--**Use Full BMGD when:**-- Larger team (4+)-- Formal documentation needed-- Working with stakeholders/publishers-- Long-term maintainability critical--## The Quick Flow--```-Concept → Prototype → Iterate → Polish → Ship- ↑__________________________|-```--*"No docs. No meetings. Just build, play, fix, repeat."*--### 1. Quick Concept (30 min max)--Answer these, nothing more:--```markdown-## [Game Name]--**Hook:** [One sentence - what's unique]-**Core Loop:** [Verb → Challenge → Reward]-**Platform:** [Where it runs]-**Scope:** [Small/Medium - be honest]-**First Playable Goal:** [What proves the fun]-```--*"If you can't explain it in 30 seconds, scope down."*--### 2. Quick Prototype (Hours, not days)--**Prototype Rules:**-- No art — use shapes and colors-- No polish — functionality only-- No systems — just the core loop-- No menus — straight into gameplay--**What to Build:**-1. Player can [core action]-2. Something challenges them-3. Something rewards them-4. Loop repeats--**Success Criteria:**-- "Is this fun for 30 seconds?"-- If no → pivot or kill-- If yes → continue--### 3. Quick Iterate (Build → Test → Fix)--**Daily Loop:**-```-Morning: Fix yesterday's bugs-Midday: Add one feature-Evening: Playtest and note issues-Night: Plan tomorrow's one thing-```--**Iteration Priorities:**-1. **Feel**: Does it feel good?-2. **Flow**: Is the loop smooth?-3. **Fun**: Do I want to play again?--**Kill Your Darlings:**-- If a feature doesn't improve fun: cut it-- If a system is too complex: simplify-- If scope is creeping: trim--### 4. Quick Spec (When needed)--For anything non-trivial:--```markdown-## Feature: [Name]--**Why:** [What problem it solves]-**What:** [One paragraph max]-**How:** [Technical approach in bullets]-**Done when:** [Testable criteria]-**Time box:** [Hours, not days]-```--*"Write specs when you're confused, not as a ritual."*--### 5. Quick Polish (Make it feel good)--**Polish Checklist:**-- [ ] Screen shake on impacts-- [ ] Particle effects on actions-- [ ] Sound effects on everything-- [ ] Camera juice (follow, shake, zoom)-- [ ] UI feedback (button states, transitions)-- [ ] Death/failure feels dramatic-- [ ] Victory/success feels rewarding--**80/20 Polish Rule:**-- 20% of polish creates 80% of feel-- Find the high-impact moments-- Polish those first--### 6. Quick Ship--**Pre-Ship Checklist:**-- [ ] Core loop is fun-- [ ] No crash bugs-- [ ] Performance acceptable-- [ ] Controls explained-- [ ] Start-to-end playable--**Ship Mindset:**-- Done is better than perfect-- Feedback from players > feedback from you-- You can patch after launch-- Ship scared — it's normal--## Quick Flow Commands--| Command | Use For |-|---------|---------|-| `/gds-quick-flow` | This workflow overview |-| `/gds-brainstorm-game` | Need idea help |-| `/gds-dev-story` | Implementing a feature |-| `/gds-qa-framework` | Setting up tests |--## Solo Dev Tips--**Time Management:**-- Work in 2-hour focused blocks-- One feature per session max-- Playtest at end of every session-- Don't work on multiple games--**Scope Control:**-- Start smaller than you think-- Cut features, not quality-- "Good enough" is a valid target-- Finish games, don't abandon--**Motivation:**-- Show people early (scary but necessary)-- Celebrate small wins-- Take breaks — crunch kills creativity-- Remember why you started--## Output: Quick Dev Log--Keep a simple log:--```markdown-# [Game] Dev Log--## Day 1-- Built: [What]-- Played: [Notes]-- Tomorrow: [One thing]--## Day 2-- Built: [What]-- Played: [Notes]-- Tomorrow: [One thing]--## Decisions-- [Date]: [Decision and why]--## Ideas Parking Lot-- [Idea to maybe do later]-```--## Quick Flow Mantras--*"Ship it."*-*"Is this fun yet?"*-*"Playable beats planned."*-*"One feature at a time."*-*"Cut scope, not corners."*-------*"Enough talking. What are we building?"*diff --git a/usr/skills/frameworks/bmad-gds/gds-sprint-planning/SKILL.md b/usr/skills/frameworks/bmad-gds/gds-sprint-planning/SKILL.mddeleted file mode 100644index 070d83e6d..000000000--- a/usr/skills/frameworks/bmad-gds/gds-sprint-planning/SKILL.md+++ /dev/null@@ -1,228 +0,0 @@-----name: "gds-sprint-planning"-description: "Plan sprints with Game Scrum Master (Max)."-version: "1.0.0"-author: "BMad Method"-tags: ["bmad-gds", "sprint", "planning", "scrum", "max"]-trigger_patterns:- - "sprint planning"- - "plan sprint"- - "create stories"- - "/gds-sprint-planning"------# BMGD: Sprint Planning--Plan sprints with **Max** (Game Scrum Master).--## Agent: Max--**Role:** Game Development Scrum Master + Sprint Orchestrator--**Identity:** Certified Scrum Master specializing in game dev workflows. Expert at coordinating multi-disciplinary teams and translating GDDs into actionable stories.--**Style:** Talks in game terminology — milestones are save points, handoffs are level transitions, blockers are boss fights.--**Core Principles:**-- Every sprint delivers playable increments-- Clean separation between design and implementation-- Keep the team moving through each phase-- Stories are single source of truth for implementation--## Process--*"Alright team, let's turn that design doc into actionable quests. Time to level up our backlog!"*--### 1. Epic Creation--Break the GDD into Epics (major features):--```markdown-## Epic: [Feature Name]--### Description-[What this epic delivers to players]--### Acceptance Criteria-- [ ] [User-visible outcome 1]-- [ ] [User-visible outcome 2]--### Dependencies-- Requires: [Other epics]-- Enables: [What this unlocks]--### Estimate-- Size: [S/M/L/XL]-- Sprints: [Estimate]-```--**Epic Categories:**-- **Core Loop**: Essential gameplay-- **Systems**: Technical infrastructure-- **Content**: Levels, assets, data-- **Polish**: VFX, audio, juice-- **Platform**: Platform-specific work--### 2. Story Writing--Each epic breaks into Stories:--```markdown-## Story: [Action-Oriented Title]--### As a [player/designer/developer]-### I want [capability]-### So that [benefit]--### Acceptance Criteria-- [ ] Given [context], when [action], then [result]-- [ ] Given [context], when [action], then [result]--### Technical Notes-[Implementation guidance]--### Assets Required-- [ ] [Asset 1]-- [ ] [Asset 2]--### Estimate: [Story Points]-```--**Story Best Practices:**-- Vertical slices (visible player value)-- Independent (can be built alone)-- Testable (clear done criteria)-- Small enough for one sprint--### 3. Sprint Setup--**Sprint Duration:** [1-2 weeks typical for games]--**Sprint Goal:** [What's playable at the end]--**Capacity Planning:**--| Team Member | Role | Available Days |-|-------------|------|----------------|-| [Name] | [Role] | [X days] |--**Velocity:** [Points per sprint, if known]--### 4. Backlog Prioritization--**Priority Matrix:**--| Priority | Description |-|----------|-------------|-| P0 | Blocks everything, do first |-| P1 | Core loop / vertical slice |-| P2 | Important features |-| P3 | Nice to have |-| P4 | Backlog / future |--**MoSCoW for MVP:**-- **Must have**: Game doesn't work without-- **Should have**: Important but workarounds exist-- **Could have**: Enhances experience-- **Won't have (yet)**: Explicitly deferred--### 5. Sprint Backlog--Select stories for sprint:--```markdown-## Sprint [N]: [Theme/Goal]--### Goal-[What's playable/demonstrable at end]--### Stories-| ID | Story | Points | Owner | Status |-|----|-------|--------|-------|--------|-| S-001 | [Title] | [X] | [Name] | Todo |-| S-002 | [Title] | [X] | [Name] | Todo |--### Total Points: [X]-### Capacity: [X]--### Risks-- [Risk 1]: [Mitigation]-```--### 6. Definition of Done--**Story is Done when:**-- [ ] Code complete and reviewed-- [ ] Tests written and passing-- [ ] No P0/P1 bugs-- [ ] Playable in build-- [ ] Design sign-off--**Sprint is Done when:**-- [ ] All committed stories Done-- [ ] Sprint build playable-- [ ] Retrospective completed-- [ ] Backlog groomed for next sprint--## Output: Sprint Plan--```markdown-# Sprint Plan: [Game] Sprint [N]--## Sprint Goal-[One sentence: what's the save point?]--## Dates-- Start: [Date]-- End: [Date]-- Demo: [Date]--## Team-| Name | Role | Capacity |-|------|------|----------|-| [X] | [X] | [X] |--## Committed Stories-| ID | Story | Points | Owner |-|----|-------|--------|-------|-| [X] | [X] | [X] | [X] |--**Total:** [X] points--## Sprint Risks-| Risk | Likelihood | Mitigation |-|------|------------|------------|-| [X] | [H/M/L] | [X] |--## Dependencies-- [Dependency 1]--## Success Criteria-- [ ] [Playable outcome 1]-- [ ] [Playable outcome 2]-```--## Sprint Ceremonies--| Ceremony | When | Duration | Purpose |-|----------|------|----------|---------|-| Planning | Sprint start | 2-4h | Select work |-| Daily | Every day | 15m | Sync blockers |-| Review | Sprint end | 1-2h | Demo to stakeholders |-| Retro | After review | 1h | Process improvement |--## Game-Specific Considerations--1. **Playable builds**: Every sprint should produce something playable-2. **Art/code sync**: Plan dependencies across disciplines-3. **Iteration time**: Leave room for "feel" adjustments-4. **Polish debt**: Track juice/polish as explicit work-5. **Playtesting**: Build time for testing into sprints--## Next Steps--After sprint planning:-- Use `/gds-dev-story` to implement stories-- Track progress with sprint status checks--*"Save point created! Let's crush this sprint, team!"*diff --git a/usr/skills/frameworks/bmad/bmad-code-review/SKILL.md b/usr/skills/frameworks/bmad/bmad-code-review/SKILL.mddeleted file mode 100644index 8aa8e058a..000000000--- a/usr/skills/frameworks/bmad/bmad-code-review/SKILL.md+++ /dev/null@@ -1,140 +0,0 @@-----name: "bmad-code-review"-description: "Validate code quality and completeness against stories."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["bmad", "review", "quality", "validation"]-trigger_patterns:- - "code review"- - "review code"- - "validate implementation"------# BMAD: Code Review--Validate implementation quality and completeness.--## When to Use--- After completing `/bmad:dev-story`-- Before merging feature branches-- As part of sprint completion--## Review Framework--### 1. Story Compliance--Check against the original story:--```markdown-## Story Compliance Check--### Story: {Story Name}--**Acceptance Criteria:**-- [ ] Criterion 1: [PASS/FAIL] - [Notes]-- [ ] Criterion 2: [PASS/FAIL] - [Notes]--**Implementation Tasks:**-- [ ] Task 1: [COMPLETE/INCOMPLETE]-- [ ] Task 2: [COMPLETE/INCOMPLETE]-```--### 2. Code Quality--Evaluate against BMAD standards:--| Aspect | Check | Status |-|--------|-------|--------|-| **Readability** | Clear naming, logical structure | ✓/✗ |-| **Maintainability** | DRY, single responsibility | ✓/✗ |-| **Error Handling** | Edge cases covered | ✓/✗ |-| **Security** | No vulnerabilities | ✓/✗ |-| **Performance** | No obvious issues | ✓/✗ |-| **Testing** | Adequate coverage | ✓/✗ |--### 3. Architecture Alignment--If architecture doc exists, verify alignment:--```markdown-## Architecture Compliance--- [ ] Follows defined patterns-- [ ] Uses approved technologies-- [ ] Respects module boundaries-- [ ] Adheres to data flow design-```--### 4. Documentation--Check documentation updates:--```markdown-## Documentation Review--- [ ] Code comments where needed-- [ ] README updated if applicable-- [ ] API docs updated if applicable-- [ ] Change log updated-```--## Review Output--```markdown-# Code Review: {Story/Feature Name}--## Summary-[Overall assessment: APPROVED / NEEDS CHANGES / REJECTED]--## Findings--### Must Fix-1. [Critical issue]-2. [Critical issue]--### Should Fix-1. [Important improvement]-2. [Important improvement]--### Suggestions-1. [Nice to have]-2. [Nice to have]--## Metrics-- Files changed: X-- Lines added: Y-- Lines removed: Z-- Test coverage: N%--## Decision-[APPROVE / REQUEST CHANGES / REJECT]--[If changes requested: specific actions needed]-```--## Review Checklist--```markdown-## Pre-Merge Checklist--- [ ] All acceptance criteria met-- [ ] Tests pass-- [ ] No security issues-- [ ] No performance regressions-- [ ] Documentation complete-- [ ] Code follows project conventions-```--## Integration with BMAD Workflow--**Quick Path:**-```-quick-spec → dev-story → code-review ← YOU ARE HERE-```--**Full Path:**-```-product-brief → create-prd → create-architecture →-create-epics → sprint-planning → dev-story → code-review ← YOU ARE HERE-```diff --git a/usr/skills/frameworks/bmad/bmad-create-architecture/SKILL.md b/usr/skills/frameworks/bmad/bmad-create-architecture/SKILL.mddeleted file mode 100644index 64584d094..000000000--- a/usr/skills/frameworks/bmad/bmad-create-architecture/SKILL.md+++ /dev/null@@ -1,102 +0,0 @@-----name: "bmad-create-architecture"-description: "Design technical architecture from PRD requirements."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["bmad", "architecture", "design", "technical"]-trigger_patterns:- - "create architecture"- - "design system"- - "architecture document"------# BMAD: Create Architecture--Design the technical architecture to fulfill PRD requirements.--## When to Use--- PRD is approved-- Need technical design before implementation-- Before breaking into epics--## Architecture Document Structure--Create `docs/architecture.md`:--```markdown-# Architecture Document: [Product Name]--## Overview-[High-level system description]--## Architecture Diagram-```-[Component diagram - ASCII or reference to image]-```--## Components--### Component 1: [Name]-- **Purpose**: [What it does]-- **Technology**: [Stack/framework]-- **Responsibilities**: [What it owns]-- **Interfaces**: [How it communicates]--## Data Model--### Entity: [Name]-| Field | Type | Description |-|-------|------|-------------|-| id | UUID | Primary key |-| ... | ... | ... |--## API Design--### Endpoint: [Name]-- **Method**: GET/POST/etc-- **Path**: `/api/v1/...`-- **Request**: [Schema]-- **Response**: [Schema]--## Technology Decisions--### Decision 1: [What]-- **Options Considered**: [List]-- **Selected**: [Choice]-- **Rationale**: [Why]--## Security Architecture-- Authentication: [Approach]-- Authorization: [Approach]-- Data Protection: [Approach]--## Infrastructure-- Hosting: [Where]-- Scaling: [Strategy]-- Deployment: [Process]--## Performance Considerations-- [Caching strategy]-- [Database optimization]-- [CDN usage]--## Monitoring & Logging-- [What to monitor]-- [Logging approach]-- [Alerting strategy]-```--## Output--```markdown-## Architecture Complete: [Product Name]--**Components**: [X] main components-**APIs**: [Y] endpoints designed-**Entities**: [Z] data models--Architecture saved to `docs/architecture.md`--Ready to define epics? Use `bmad-create-epics`.-```diff --git a/usr/skills/frameworks/bmad/bmad-create-epics/SKILL.md b/usr/skills/frameworks/bmad/bmad-create-epics/SKILL.mddeleted file mode 100644index 25f2e6752..000000000--- a/usr/skills/frameworks/bmad/bmad-create-epics/SKILL.md+++ /dev/null@@ -1,104 +0,0 @@-----name: "bmad-create-epics"-description: "Break architecture into manageable epics for iterative development."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["bmad", "epics", "agile", "planning"]-trigger_patterns:- - "create epics"- - "break down work"- - "define epics"------# BMAD: Create Epics--Break the architecture into deliverable epics for iterative development.--## When to Use--- Architecture is approved-- Need to plan sprints/iterations-- Before creating developer stories--## Epic Structure--Create `docs/epics/` directory with one file per epic:--```markdown-# Epic: [Epic Name]--## Overview-[What this epic delivers]--## Business Value-[Why this matters to users/business]--## Dependencies-- [Prior epics or external dependencies]--## User Stories-- US-001: [Title]-- US-002: [Title]-- US-003: [Title]--## Acceptance Criteria-- [ ] [Criteria 1]-- [ ] [Criteria 2]--## Technical Scope-- Components affected: [List]-- APIs: [List]-- Data: [List]--## Estimated Effort-- Story Points: [X]-- Duration: [Y weeks]--## Risks-- [Risk 1]-- [Risk 2]-```--## Epic Planning Process--1. **Identify Deliverables**: What user value can be shipped?-2. **Define Boundaries**: Clear start and end-3. **Order by Dependencies**: What must come first?-4. **Size Appropriately**: 1-4 weeks of work-5. **Assign Stories**: Group related user stories--## Epic Ordering--```markdown-## Epic Roadmap--### Phase 1: Foundation-1. Epic: Core Infrastructure-2. Epic: Authentication--### Phase 2: Core Features-3. Epic: [Feature A]-4. Epic: [Feature B]--### Phase 3: Enhancement-5. Epic: [Feature C]-```--## Output--```markdown-## Epics Defined: [Product Name]--**Total Epics**: [X]-**Phases**: [Y]-**Estimated Duration**: [Z weeks]--### Epic Summary-| Epic | Stories | Points | Phase |-|------|---------|--------|-------|-| [Name] | [X] | [Y] | 1 |--Epics saved to `docs/epics/`--Ready to start development? Use `bmad-dev-story` for implementation.-```diff --git a/usr/skills/frameworks/bmad/bmad-create-prd/SKILL.md b/usr/skills/frameworks/bmad/bmad-create-prd/SKILL.mddeleted file mode 100644index baa8b3fbe..000000000--- a/usr/skills/frameworks/bmad/bmad-create-prd/SKILL.md+++ /dev/null@@ -1,148 +0,0 @@-----name: "bmad-create-prd"-description: "Transform product brief into a detailed Product Requirements Document (PRD)."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["bmad", "prd", "requirements", "documentation"]-trigger_patterns:- - "create prd"- - "product requirements"- - "requirements document"------# BMAD: Create PRD--Transform the product brief into a comprehensive Product Requirements Document.--## When to Use--- Product brief is approved-- Need detailed requirements for development-- Before architecture design--## PRD Structure--Create `docs/prd.md`:--```markdown-# Product Requirements Document: [Product Name]--## Overview-[Summary from product brief]--## Background-[Context and why this is being built]--## Goals-[From product brief, refined]--## User Personas--### Persona 1: [Name]-- **Role**: [Job/function]-- **Goals**: [What they want to achieve]-- **Pain Points**: [Current frustrations]-- **Technical Proficiency**: [Level]--## User Stories--### Epic 1: [Title]--#### US-001: [Story Title]-**As a** [persona]-**I want to** [capability]-**So that** [benefit]--**Acceptance Criteria:**-- [ ] Given [context], when [action], then [result]-- [ ] Given [context], when [action], then [result]--**Priority**: High/Medium/Low-**Estimate**: S/M/L/XL--## Functional Requirements--### FR-001: [Requirement Title]-**Description**: [What the system must do]-**Rationale**: [Why this is needed]-**Acceptance**: [How to verify]--## Non-Functional Requirements--### Performance-- [Response time requirements]-- [Throughput requirements]--### Security-- [Authentication requirements]-- [Authorization requirements]-- [Data protection]--### Scalability-- [Expected load]-- [Growth projections]--### Reliability-- [Uptime requirements]-- [Recovery requirements]--## UI/UX Requirements-- [Key interface requirements]-- [Accessibility requirements]-- [Brand guidelines]--## Data Requirements-- [Data entities needed]-- [Storage requirements]-- [Retention policies]--## Integration Requirements-- [External systems]-- [APIs needed]-- [Data flows]--## Constraints-[From product brief, detailed]--## Assumptions-[What we're assuming is true]--## Dependencies-[What this depends on]--## Risks-[From product brief, detailed]--## Success Metrics-[From product brief, detailed measurement plans]--## Release Criteria-- [ ] All P0 requirements complete-- [ ] All tests pass-- [ ] Performance benchmarks met-- [ ] Security review complete-- [ ] Documentation complete-```--## Process--1. **Review Product Brief**: Ensure vision is clear-2. **Define Personas**: Flesh out user types-3. **Write User Stories**: Convert requirements to stories-4. **Detail Requirements**: Functional and non-functional-5. **Define Acceptance**: Clear criteria for each item-6. **Prioritize**: MoSCoW or similar prioritization--## Output--```markdown-## PRD Complete: [Product Name]--**User Stories**: [X] stories across [Y] epics-**Requirements**: [Z] functional, [W] non-functional-**Priority Distribution**: [breakdown]--PRD saved to `docs/prd.md`--Ready to design architecture? Use `bmad-create-architecture`.-```diff --git a/usr/skills/frameworks/bmad/bmad-dev-story/SKILL.md b/usr/skills/frameworks/bmad/bmad-dev-story/SKILL.mddeleted file mode 100644index b862be283..000000000--- a/usr/skills/frameworks/bmad/bmad-dev-story/SKILL.md+++ /dev/null@@ -1,134 +0,0 @@-----name: "bmad-dev-story"-description: "Generate implementable developer stories from epics with technical specifications."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["bmad", "development", "stories", "implementation"]-trigger_patterns:- - "dev story"- - "implement story"- - "developer story"- - "start development"------# BMAD: Developer Story--Take a user story from an epic and create a detailed, implementable developer specification.--## When to Use--- Starting work on a user story-- Need technical specification for implementation-- Handing off to developers--## Developer Story Format--```markdown-# Developer Story: [US-XXX] [Title]--## User Story-**As a** [persona]-**I want to** [capability]-**So that** [benefit]--## Technical Specification--### Overview-[Technical summary of what needs to be built]--### Implementation Steps-1. [ ] [Step 1 with file references]-2. [ ] [Step 2 with file references]-3. [ ] [Step 3 with file references]--### Files to Modify-| File | Changes |-|------|---------|-| `path/to/file.py` | [What to change] |--### Files to Create-| File | Purpose |-|------|---------|-| `path/to/new.py` | [What it does] |--### API Changes-```-[Endpoint specifications if applicable]-```--### Data Changes-```-[Schema changes if applicable]-```--### Dependencies-- [Package/library dependencies]-- [Service dependencies]--## Acceptance Tests--### Test 1: [Name]-```-Given: [Setup]-When: [Action]-Then: [Expected result]-```--### Test 2: [Name]-```-Given: [Setup]-When: [Action]-Then: [Expected result]-```--## Definition of Done-- [ ] Code complete-- [ ] Unit tests pass-- [ ] Integration tests pass-- [ ] Code reviewed-- [ ] Documentation updated-- [ ] Deployed to staging-```--## Process--1. **Load Epic Context**: Read epic and user story-2. **Analyze Requirements**: Understand what's needed-3. **Research Codebase**: Find relevant existing code-4. **Design Solution**: Plan implementation-5. **Write Specification**: Document steps-6. **Define Tests**: Acceptance criteria as tests-7. **Implement**: Follow the specification--## Output--After creating developer story:--```markdown-## Developer Story Ready: [US-XXX]--**Story**: [Title]-**Steps**: [X] implementation steps-**Tests**: [Y] acceptance tests--Ready to implement?-```--## Implementation Flow--Once story is ready:--1. Create feature branch-2. Follow implementation steps-3. Write tests as specified-4. Verify acceptance criteria-5. Create pull request-6. Complete Definition of Done--## Anti-Patterns--- Vague implementation steps-- Missing test specifications-- No file references-- Forgetting dependencies-- Skipping code reviewdiff --git a/usr/skills/frameworks/bmad/bmad-product-brief/SKILL.md b/usr/skills/frameworks/bmad/bmad-product-brief/SKILL.mddeleted file mode 100644index b65d22a7b..000000000--- a/usr/skills/frameworks/bmad/bmad-product-brief/SKILL.md+++ /dev/null@@ -1,124 +0,0 @@-----name: "bmad-product-brief"-description: "Create a product brief defining vision, objectives, and high-level requirements."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["bmad", "product", "planning", "vision"]-trigger_patterns:- - "product brief"- - "project vision"- - "define product"- - "start bmad"------# BMAD: Product Brief--Create a product brief that captures the vision, objectives, and business context for a new product or feature.--## When to Use--- Starting a new product or major feature-- Need to align stakeholders on vision-- Before creating detailed requirements--## Product Brief Structure--Create `docs/product-brief.md`:--```markdown-# Product Brief: [Product Name]--## Vision Statement-[One sentence describing the ultimate goal]--## Problem Statement-[What problem does this solve? Who has this problem?]--## Target Users-- **Primary**: [User type and characteristics]-- **Secondary**: [Other user types]--## Business Objectives-1. [Objective 1 - measurable]-2. [Objective 2 - measurable]-3. [Objective 3 - measurable]--## Success Metrics-| Metric | Target | Measurement |-|--------|--------|-------------|-| [Metric 1] | [Target] | [How measured] |-| [Metric 2] | [Target] | [How measured] |--## High-Level Requirements-1. [Core capability 1]-2. [Core capability 2]-3. [Core capability 3]--## Constraints-- **Technical**: [Any technical limitations]-- **Timeline**: [Target dates]-- **Budget**: [Resource constraints]-- **Compliance**: [Regulatory requirements]--## Out of Scope-- [What this is NOT]-- [Explicitly excluded features]--## Risks and Mitigations-| Risk | Impact | Mitigation |-|------|--------|------------|-| [Risk 1] | High/Med/Low | [Strategy] |--## Stakeholders-- **Owner**: [Who owns this]-- **Contributors**: [Who's involved]-- **Reviewers**: [Who approves]-```--## Gathering Information--Ask the user about:--1. **Problem Space**- - What problem are you solving?- - Who experiences this problem?- - What's the impact of the problem?--2. **Solution Vision**- - What does success look like?- - How will users benefit?- - What makes this different?--3. **Business Context**- - What are the business goals?- - What constraints exist?- - Who are the stakeholders?--4. **Scope**- - What must be included?- - What should be excluded?- - What's the timeline?--## Output--After creating the brief:--```markdown-## Product Brief Complete: [Product Name]--**Vision**: [One-liner]-**Objectives**: [X] defined-**Core Requirements**: [Y] identified--Brief saved to `docs/product-brief.md`--Ready to create detailed PRD? Use `bmad-create-prd`.-```--## Anti-Patterns--- Skipping problem definition-- Vague success metrics-- No stakeholder alignment-- Scope creep from day one-- Missing constraintsdiff --git a/usr/skills/frameworks/bmad/bmad-quick-spec/SKILL.md b/usr/skills/frameworks/bmad/bmad-quick-spec/SKILL.mddeleted file mode 100644index ee83450f5..000000000--- a/usr/skills/frameworks/bmad/bmad-quick-spec/SKILL.md+++ /dev/null@@ -1,138 +0,0 @@-----name: "bmad-quick-spec"-description: "Analyze codebase and produce tech-spec with stories for quick tasks."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["bmad", "quick", "specification", "stories"]-trigger_patterns:- - "quick spec"- - "quick path"- - "simple feature"- - "bug fix spec"------# BMAD: Quick Spec--Fast-track specification for small features and bug fixes.--## When to Use--The Quick Path is for:-- Bug fixes-- Small features with clear scope-- Configuration changes-- Minor enhancements--**NOT for:**-- New products or platforms-- Complex features requiring architecture-- Work spanning multiple sprints--## The Quick Path--```-quick-spec → dev-story → code-review-```--Just 3 commands instead of the full 6+ step BMAD process.--## Process--### 1. Analyze the Request--Understand what needs to be done:-- What is the problem or requirement?-- What files might be affected?-- Are there existing patterns to follow?--### 2. Codebase Analysis--Examine relevant parts of the codebase:--```markdown-## Codebase Analysis--### Affected Areas-- [File/module 1]: [What it does]-- [File/module 2]: [What it does]--### Existing Patterns-- [Pattern 1]: [How it's used]-- [Pattern 2]: [How it's used]--### Dependencies-- [Dependency 1]: [Relevance]-```--### 3. Generate Tech Spec--Create a lightweight technical specification:--```markdown-# Tech Spec: {Feature/Fix Name}--## Summary-[One sentence description]--## Problem-[What issue this solves]--## Solution-[High-level approach]--## Implementation Details--### Changes Required-1. [Change 1]-2. [Change 2]--### Files Affected-- `path/to/file1.ts` - [What changes]-- `path/to/file2.ts` - [What changes]--## Testing-- [ ] [Test case 1]-- [ ] [Test case 2]--## Acceptance Criteria-- [ ] [Criterion 1]-- [ ] [Criterion 2]-```--### 4. Generate Stories--Break the spec into implementable stories:--```markdown-## Stories--### Story 1: {Name}-**As a** [user type]-**I want** [capability]-**So that** [benefit]--**Tasks:**-- [ ] Task 1-- [ ] Task 2--**Acceptance Criteria:**-- [ ] Criterion 1-```--## Output--**Creates:**-- `QUICK-SPEC.md` - Technical specification-- Stories ready for `/bmad:dev-story`--## Next Steps--After quick-spec:-1. `/bmad:dev-story` - Implement each story-2. `/bmad:code-review` - Validate quality--## Integration with Full Path--If during quick-spec you discover the task is more complex:-- Stop the quick path-- Switch to full BMAD path starting with `/bmad:product-brief`diff --git a/usr/skills/frameworks/bmad/bmad-sprint-planning/SKILL.md b/usr/skills/frameworks/bmad/bmad-sprint-planning/SKILL.mddeleted file mode 100644index f535f1ace..000000000--- a/usr/skills/frameworks/bmad/bmad-sprint-planning/SKILL.md+++ /dev/null@@ -1,151 +0,0 @@-----name: "bmad-sprint-planning"-description: "Initialize sprint tracking and select stories for the sprint."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["bmad", "sprint", "planning", "agile"]-trigger_patterns:- - "sprint planning"- - "plan sprint"- - "initialize sprint"------# BMAD: Sprint Planning--Initialize sprint tracking and select stories for implementation.--## When to Use--- After epics and stories are created (`/bmad:create-epics`)-- At the start of each development sprint-- When re-planning mid-sprint--## Prerequisites--- Epics and stories defined-- Story estimates available (or will be created)-- Team capacity known--## Process--### 1. Review Backlog--Examine available stories:--```markdown-## Backlog Review--### High Priority-| Story | Epic | Estimate | Status |-|-------|------|----------|--------|-| Story 1 | Epic A | 3 pts | Ready |-| Story 2 | Epic A | 5 pts | Ready |--### Medium Priority-| Story | Epic | Estimate | Status |-|-------|------|----------|--------|-| Story 3 | Epic B | 2 pts | Ready |--### Needs Refinement-| Story | Epic | Issue |-|-------|------|-------|-| Story 4 | Epic B | Unclear requirements |-```--### 2. Estimate Stories--If stories need estimates:--```markdown-## Story Estimation--### Story: {Name}-**Complexity factors:**-- [ ] Code changes: [Simple/Medium/Complex]-- [ ] Testing needs: [Low/Medium/High]-- [ ] Integration: [None/Some/Heavy]-- [ ] Risk: [Low/Medium/High]--**Estimate:** X points--**Rationale:** [Why this estimate]-```--### 3. Set Sprint Capacity--```markdown-## Sprint Capacity--**Sprint duration:** X days/weeks-**Team velocity:** Y points (based on history or estimate)-**Available capacity:** Z points (accounting for meetings, etc.)-```--### 4. Select Sprint Stories--Choose stories that fit capacity:--```markdown-## Sprint {N} Plan--**Goal:** [Sprint goal in one sentence]--**Selected Stories:**-| # | Story | Epic | Points | Priority |-|---|-------|------|--------|----------|-| 1 | Story 1 | Epic A | 3 | Must have |-| 2 | Story 2 | Epic A | 5 | Must have |-| 3 | Story 3 | Epic B | 2 | Should have |--**Total Points:** X / Y capacity--**Stretch Goals (if time permits):**-- Story 4 (2 pts)-```--### 5. Initialize Sprint Tracking--Create sprint tracking file:--```markdown-# Sprint {N}: {Sprint Name}--**Start:** YYYY-MM-DD-**End:** YYYY-MM-DD-**Goal:** [Sprint goal]--## Progress--| Story | Status | Assigned | Notes |-|-------|--------|----------|-------|-| Story 1 | Not Started | - | |-| Story 2 | Not Started | - | |--## Daily Updates-### Day 1-- Started:-- Completed:-- Blockers:-```--## Output--**Creates:**-- `SPRINT-{N}.md` - Sprint tracking document-- Updated story statuses--## Next Steps--After sprint planning:-1. `/bmad:dev-story` - Work on each selected story-2. Track progress in sprint document-3. `/bmad:code-review` - Review completed work--## Sprint Ceremonies (Reference)--| Ceremony | When | Purpose |-|----------|------|---------|-| **Planning** | Sprint start | Select stories, set goal |-| **Daily standup** | Daily | Sync progress, identify blockers |-| **Review** | Sprint end | Demo completed work |-| **Retrospective** | Sprint end | Improve process |diff --git a/usr/skills/frameworks/gsd/gsd-complete-milestone/SKILL.md b/usr/skills/frameworks/gsd/gsd-complete-milestone/SKILL.mddeleted file mode 100644index 0d80ffccc..000000000--- a/usr/skills/frameworks/gsd/gsd-complete-milestone/SKILL.md+++ /dev/null@@ -1,114 +0,0 @@-----name: "gsd-complete-milestone"-description: "Archive completed milestone, tag release, and prepare for next iteration."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["gsd", "milestone", "release", "completion"]-trigger_patterns:- - "complete milestone"- - "finish milestone"- - "archive milestone"- - "tag release"------# GSD: Complete Milestone--Archive the milestone and prepare for the next development cycle.--## When to Use--- After all phases in the current milestone are verified-- When ready to tag a release-- Before starting `gsd-new-milestone` for the next version--## Prerequisites--- All phases in the milestone should be complete-- All verification steps should pass-- No critical issues remaining--## Process--### 1. Milestone Audit--Before completing, verify:--```markdown-## Milestone Audit Checklist--- [ ] All planned phases are complete-- [ ] Verification passed for each phase-- [ ] No critical bugs or blockers-- [ ] Documentation is current-- [ ] All changes are committed-```--### 2. Archive Milestone--Move milestone files to archive:--```-.planning/-├── archive/-│ └── v{version}/-│ ├── PROJECT.md-│ ├── REQUIREMENTS.md-│ ├── ROADMAP.md-│ ├── phases/-│ │ ├── 1-CONTEXT.md-│ │ ├── 1-RESEARCH.md-│ │ ├── 1-*-PLAN.md-│ │ └── ...-│ └── STATE.md-```--### 3. Tag Release--Create a git tag for the milestone:--```bash-git tag -a v{version} -m "Milestone: {milestone_name}"-```--### 4. Generate Summary--Create a milestone summary:--```markdown-## Milestone Summary: {name}--### Delivered-- [Feature 1]-- [Feature 2]--### Metrics-- Phases completed: X-- Plans executed: Y-- Total commits: Z--### Key Decisions-- [Decision 1]: [Rationale]-- [Decision 2]: [Rationale]--### Lessons Learned-- [Lesson 1]-- [Lesson 2]--### Next Steps-- [Suggestion for next milestone]-```--## Output--**Creates:**-- Archive folder with milestone artifacts-- Git tag for the release-- `MILESTONE-SUMMARY.md`--## Usage--```-/gsd:complete-milestone-```--After completion, use `/gsd:new-milestone` to start the next version.diff --git a/usr/skills/frameworks/gsd/gsd-discuss-phase/SKILL.md b/usr/skills/frameworks/gsd/gsd-discuss-phase/SKILL.mddeleted file mode 100644index b86dbc9f7..000000000--- a/usr/skills/frameworks/gsd/gsd-discuss-phase/SKILL.md+++ /dev/null@@ -1,93 +0,0 @@-----name: "gsd-discuss-phase"-description: "Capture implementation decisions and user preferences before planning begins."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["gsd", "discussion", "planning", "elicitation"]-trigger_patterns:- - "discuss phase"- - "capture decisions"- - "implementation preferences"------# GSD: Discuss Phase--Shape the implementation before research and planning begins.--## When to Use--- After `gsd-new-project` has created the roadmap-- Before `gsd-plan-phase` for a specific phase-- When you need to capture user preferences for how something should be built--## Purpose--Your roadmap has a sentence or two per phase. That's not enough context to build something the way the user imagines it. This step captures preferences before anything gets researched or planned.--## Process--### 1. Analyze the Phase--Identify gray areas based on what's being built:--| Feature Type | Questions to Explore |-|-------------|---------------------|-| **Visual features** | Layout, density, interactions, empty states |-| **APIs/CLIs** | Response format, flags, error handling, verbosity |-| **Content systems** | Structure, tone, depth, flow |-| **Organization tasks** | Grouping criteria, naming, duplicates, exceptions |--### 2. Interactive Discussion--For each area the user selects:-- Ask targeted questions-- Drill deeper on important decisions-- Stop when user is satisfied--### 3. Create CONTEXT.md--Document all decisions in a structured format:--```markdown-# Phase {N} Context: {Phase Name}--## Decisions Made--### {Area 1}-- **Decision**: [What was decided]-- **Rationale**: [Why this choice]--### {Area 2}-...--## Constraints Identified-- [Constraint 1]-- [Constraint 2]--## Open Questions (for Research)-- [Question 1]-- [Question 2]-```--## Output--**Creates:** `{phase}-CONTEXT.md`--This file feeds directly into:-1. **Researcher** — Knows what patterns to investigate-2. **Planner** — Knows what decisions are locked--## Best Practices--- Keep discussions focused on one phase at a time-- Document preferences even if they seem obvious-- Distinguish between firm decisions and preferences-- Note any constraints that affect implementation choices--## Usage--```-/gsd:discuss-phase 1-```--Replace `1` with the phase number from your roadmap.diff --git a/usr/skills/frameworks/gsd/gsd-execute-phase/SKILL.md b/usr/skills/frameworks/gsd/gsd-execute-phase/SKILL.mddeleted file mode 100644index 97f4d7d74..000000000--- a/usr/skills/frameworks/gsd/gsd-execute-phase/SKILL.md+++ /dev/null@@ -1,137 +0,0 @@-----name: "gsd-execute-phase"-description: "Implement the approved plan with regular checkpoints and progress tracking."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["gsd", "implementation", "execution", "coding"]-trigger_patterns:- - "execute"- - "implement"- - "start coding"- - "build"------# GSD: Execute Phase--Use this skill to implement an approved plan systematically with progress tracking.--## When to Use--- After plan has been approved-- User says "start implementing" or "execute the plan"-- Ready to write code--## Prerequisites--- An approved plan exists in `.gsd/plan.md`-- User has confirmed they want to proceed--## Execution Process--### 1. Load the Plan--Read `.gsd/plan.md` and present the task list:--```markdown-## Starting Execution: [Feature Name]--**Tasks to complete:**-1. [ ] Task 1-2. [ ] Task 2-3. [ ] Task 3--Beginning with Task 1...-```--### 2. Work Through Tasks Sequentially--For each task:--1. **Announce** what you're about to do-2. **Implement** the changes-3. **Verify** the change works (run tests, check syntax)-4. **Update** the checklist-5. **Report** completion before moving on--```markdown-### Task 1: [Description]-**Status**: In Progress--[Implementation details...]--**Result**: Complete-- Created `path/to/file.py`-- Modified `path/to/other.py`-- Tests: Passing--Moving to Task 2...-```--### 3. Handle Issues--When encountering problems:--1. **Stop** and describe the issue clearly-2. **Propose** solutions-3. **Ask** for user input on how to proceed-4. **Don't** silently make major deviations from the plan--```markdown-### Issue Encountered--**Problem**: [Description]-**Impact**: [What this affects]--**Options**:-A) [Solution A]-B) [Solution B]--How would you like to proceed?-```--### 4. Update Progress--After each task, update `.gsd/plan.md`:-- Mark completed tasks with [x]-- Add notes about any deviations-- Track files actually modified--### 5. Checkpoint at Milestones--Every 3-4 tasks, or at natural breakpoints:--```markdown-## Progress Checkpoint--**Completed**: 4/8 tasks-**Files modified**:-- file1.py (200 lines)-- file2.py (50 lines)--**Status**: On track--Continue with remaining tasks?-```--## Completion--When all tasks are done:--```markdown-## Execution Complete: [Feature Name]--**Tasks**: 8/8 complete-**Files created**: 3-**Files modified**: 5-**Tests**: All passing--Ready for verification phase? Use `gsd-verify-work` to validate.-```--## Anti-Patterns--- Don't skip tasks without user approval-- Don't make undocumented changes-- Don't continue past errors without resolving them-- Don't forget to run tests after changes-- Don't implement features not in the plandiff --git a/usr/skills/frameworks/gsd/gsd-new-project/SKILL.md b/usr/skills/frameworks/gsd/gsd-new-project/SKILL.mddeleted file mode 100644index 9464c77c7..000000000--- a/usr/skills/frameworks/gsd/gsd-new-project/SKILL.md+++ /dev/null@@ -1,97 +0,0 @@-----name: "gsd-new-project"-description: "Initialize a new GSD (Get Stuff Done) project with proper structure and roadmap."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["gsd", "planning", "initialization", "project-setup"]-trigger_patterns:- - "start project"- - "new project"- - "initialize project"- - "setup gsd"------# GSD: New Project Setup--Use this skill when starting a new project with the GSD (Get Stuff Done) methodology.--## When to Use--- User asks to start a new project-- User wants to set up a structured development workflow-- Beginning work on a greenfield feature or application--## Project Structure--Create the following structure in the project directory:--```-project/-├── docs/-│ ├── roadmap.md # High-level project roadmap-│ ├── decisions/ # Architecture Decision Records-│ └── specs/ # Feature specifications-├── src/ # Source code-├── tests/ # Test files-└── .gsd/- ├── plan.md # Current implementation plan- ├── checklist.md # Progress checklist- └── context.md # Project context for AI-```--## Step-by-Step Process--### 1. Gather Project Requirements--Ask the user:-- What is the project name and purpose?-- What are the primary goals?-- What technologies/stack will be used?-- What are the key constraints or requirements?--### 2. Create Roadmap--In `docs/roadmap.md`, document:-- Project vision (1-2 sentences)-- Key milestones (3-5 major phases)-- Success criteria-- Known risks/dependencies--### 3. Initialize GSD Context--Create `.gsd/context.md` with:-- Project summary-- Tech stack details-- Coding conventions-- Testing approach--### 4. Set Up First Plan--Create `.gsd/plan.md` with the first milestone broken down:-- Clear objective-- Numbered tasks-- Acceptance criteria--## Example Output--After initialization, provide this summary:--```markdown-## Project Initialized: [Project Name]--**Location**: /path/to/project-**Framework**: GSD (Get Stuff Done)--### Next Steps-1. Review the roadmap in `docs/roadmap.md`-2. Start planning phase with `gsd-plan-phase` skill-3. Begin implementation once plan is approved--Ready to proceed to planning phase?-```--## Anti-Patterns--- Don't skip requirements gathering-- Don't create overly detailed plans upfront (plans evolve)-- Don't proceed without user confirmation of goalsdiff --git a/usr/skills/frameworks/gsd/gsd-plan-phase/SKILL.md b/usr/skills/frameworks/gsd/gsd-plan-phase/SKILL.mddeleted file mode 100644index c29435c6e..000000000--- a/usr/skills/frameworks/gsd/gsd-plan-phase/SKILL.md+++ /dev/null@@ -1,126 +0,0 @@-----name: "gsd-plan-phase"-description: "Collaborate with user to create a detailed implementation plan before coding."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["gsd", "planning", "collaboration", "design"]-trigger_patterns:- - "plan"- - "create plan"- - "planning phase"- - "design"------# GSD: Plan Phase--Use this skill to create a detailed implementation plan collaboratively with the user before any coding begins.--## When to Use--- After project initialization-- Before starting a new feature-- When requirements need clarification-- User asks to "plan" something--## Core Principle--**No coding without a plan. No plan without user approval.**--## Planning Process--### 1. Understand the Goal--Ask clarifying questions:-- What specific outcome do you want?-- What does success look like?-- Are there constraints (time, tech, compatibility)?-- What's the scope boundary?--### 2. Research Existing Code--Before proposing solutions:-- Examine relevant existing files-- Identify patterns already in use-- Note integration points-- Check for similar implementations--### 3. Present Options--Provide 2-3 implementation approaches:--```markdown-## Option A: [Name]-**Approach**: Brief description-**Pros**: Benefits list-**Cons**: Drawbacks list-**Effort**: Low/Medium/High--## Option B: [Name]-**Approach**: Brief description-**Pros**: Benefits list-**Cons**: Drawbacks list-**Effort**: Low/Medium/High-```--### 4. Get User Decision--Ask the user to choose an approach. Don't proceed without explicit selection.--### 5. Create Detailed Plan--Once approach is selected, create `.gsd/plan.md`:--```markdown-# Implementation Plan: [Feature Name]--## Objective-[Clear statement of what we're building]--## Chosen Approach-[Selected option with rationale]--## Tasks-1. [ ] Task 1 - Description- - Subtask 1a- - Subtask 1b-2. [ ] Task 2 - Description-3. [ ] Task 3 - Description-4. [ ] Task 4 - Integration testing--## Files to Modify/Create-- `path/to/file.py` - Description of changes-- `path/to/new_file.py` - New file for X--## Acceptance Criteria-- [ ] Criterion 1-- [ ] Criterion 2-- [ ] Tests pass-```--### 6. Confirm and Proceed--Present the plan and ask:-> "Here's the implementation plan. Review and let me know if you'd like any changes. Once approved, I'll begin the execute phase."--## Output Format--After planning is complete:--```markdown-## Plan Created: [Feature Name]--**Tasks**: [X] items-**Files affected**: [Y] files-**Estimated complexity**: Low/Medium/High--Plan saved to `.gsd/plan.md`--Ready to start implementation? Use `gsd-execute-phase` to begin.-```--## Anti-Patterns--- Don't start coding without plan approval-- Don't create plans that are too detailed (leave room for discovery)-- Don't skip the options discussion-- Don't assume requirements - always confirmdiff --git a/usr/skills/frameworks/gsd/gsd-verify-work/SKILL.md b/usr/skills/frameworks/gsd/gsd-verify-work/SKILL.mddeleted file mode 100644index 543dda8ee..000000000--- a/usr/skills/frameworks/gsd/gsd-verify-work/SKILL.md+++ /dev/null@@ -1,162 +0,0 @@-----name: "gsd-verify-work"-description: "Validate completed implementation against requirements and acceptance criteria."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["gsd", "verification", "testing", "quality"]-trigger_patterns:- - "verify"- - "check work"- - "validate"- - "review implementation"------# GSD: Verify Work--Use this skill to validate that the implementation meets all requirements and acceptance criteria.--## When to Use--- After completing the execute phase-- Before marking a feature as done-- When user asks to verify or check work--## Verification Process--### 1. Load Acceptance Criteria--Read from `.gsd/plan.md` and list all acceptance criteria:--```markdown-## Verification: [Feature Name]--**Acceptance Criteria:**-- [ ] Criterion 1-- [ ] Criterion 2-- [ ] Criterion 3-- [ ] Tests pass-```--### 2. Run Automated Tests--Execute the test suite:--```bash-# Run relevant tests-pytest tests/-# or npm test, cargo test, etc.-```--Report results:-```markdown-### Test Results-**Total**: 24 tests-**Passed**: 24-**Failed**: 0-**Skipped**: 0-```--### 3. Manual Verification Checklist--Walk through each acceptance criterion:--```markdown-### Criterion 1: [Description]-**Check**: [How to verify]-**Result**: PASS/FAIL-**Evidence**: [What was observed]--### Criterion 2: [Description]-**Check**: [How to verify]-**Result**: PASS/FAIL-**Evidence**: [What was observed]-```--### 4. Code Quality Check--Review the implementation for:--- [ ] No obvious bugs or errors-- [ ] Consistent with existing code style-- [ ] No security vulnerabilities-- [ ] Error handling in place-- [ ] No hardcoded secrets or debug code--### 5. Documentation Check--Verify:-- [ ] README updated if needed-- [ ] Comments for complex logic-- [ ] API documentation if applicable--### 6. Generate Verification Report--```markdown-## Verification Report: [Feature Name]--### Summary-**Status**: PASSED / FAILED-**Date**: [Date]--### Acceptance Criteria-| Criterion | Status | Notes |-|-----------|--------|-------|-| Criterion 1 | PASS | |-| Criterion 2 | PASS | |-| Tests pass | PASS | 24/24 |--### Code Quality-- Style: Consistent-- Security: No issues-- Error handling: Present--### Issues Found-[None / List of issues]--### Recommendation-Ready for deployment / Needs fixes-```--## If Verification Fails--When criteria are not met:--```markdown-### Verification Failed--**Failed criteria:**-1. [Criterion that failed]- - Expected: [what was expected]- - Actual: [what was observed]--**Recommended fixes:**-1. [Fix for issue 1]--Return to execute phase to address these issues?-```--## Completion--When all criteria pass:--```markdown-## Feature Complete: [Feature Name]--All acceptance criteria verified.-All tests passing.-Code quality checks passed.--**Next steps:**-- Commit changes-- Create pull request (if applicable)-- Move to next feature--Would you like me to help with the commit?-```--## Anti-Patterns--- Don't skip verification-- Don't mark as complete with failing tests-- Don't ignore edge cases in verification-- Don't approve without checking acceptance criteriadiff --git a/usr/skills/frameworks/prp/prp-execute/SKILL.md b/usr/skills/frameworks/prp/prp-execute/SKILL.mddeleted file mode 100644index 215e461af..000000000--- a/usr/skills/frameworks/prp/prp-execute/SKILL.md+++ /dev/null@@ -1,79 +0,0 @@-----name: "prp-execute"-description: "Execute a PRP specification systematically."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["prp", "execution", "implementation"]-trigger_patterns:- - "execute prp"- - "run prp"- - "follow prompt"------# PRP: Execute--Execute a Prompt-Response Protocol specification systematically.--## When to Use--- PRP has been generated-- Ready to perform the task-- Following an established protocol--## Execution Process--1. **Load PRP**: Read the protocol specification-2. **Gather Inputs**: Collect all required inputs-3. **Follow Steps**: Execute each step in order-4. **Produce Outputs**: Generate specified outputs-5. **Validate**: Check against quality criteria--## Execution Template--```markdown-## Executing PRP: [Task Name]--### Inputs Collected-- [Input 1]: [Value/Source]-- [Input 2]: [Value/Source]--### Step Execution--#### Step 1: [Name]-**Action**: [What was done]-**Result**: [Outcome]--#### Step 2: [Name]-**Action**: [What was done]-**Result**: [Outcome]--### Outputs Produced-- [Output 1]: [Location/Content]-- [Output 2]: [Location/Content]--### Validation-- [ ] [Criterion 1]: PASS/FAIL-- [ ] [Criterion 2]: PASS/FAIL--### Status-**Result**: SUCCESS/FAILED-```--## Error Handling--When errors occur:-1. Check PRP error handling section-2. Follow prescribed response-3. If not covered, pause and report--## Output--```markdown-## PRP Execution Complete: [Task Name]--**Status**: Success-**Outputs**: [List]-**Validation**: All criteria passed--[Outputs available at specified locations]-```diff --git a/usr/skills/frameworks/prp/prp-generate/SKILL.md b/usr/skills/frameworks/prp/prp-generate/SKILL.mddeleted file mode 100644index b7d4e2452..000000000--- a/usr/skills/frameworks/prp/prp-generate/SKILL.md+++ /dev/null@@ -1,94 +0,0 @@-----name: "prp-generate"-description: "Generate a comprehensive Prompt-Response Protocol specification for a task."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["prp", "prompt-engineering", "specification"]-trigger_patterns:- - "generate prp"- - "create prompt"- - "prp specification"------# PRP: Generate--Generate a comprehensive Prompt-Response Protocol for a development task.--## When to Use--- Well-defined, repeatable tasks-- Need consistent execution-- Creating reusable prompts--## PRP Structure--A PRP contains everything needed for task execution:--```markdown-# PRP: [Task Name]--## Context-[Background and environment information]--## Objective-[Clear statement of what must be accomplished]--## Inputs-- [Input 1]: [Description and format]-- [Input 2]: [Description and format]--## Constraints-- [Constraint 1]-- [Constraint 2]--## Process Steps-1. [Step 1 - specific action]-2. [Step 2 - specific action]-3. [Step 3 - specific action]--## Expected Outputs-- [Output 1]: [Format and content]-- [Output 2]: [Format and content]--## Quality Criteria-- [ ] [Criterion 1]-- [ ] [Criterion 2]--## Examples--### Example 1-**Input**: [Sample]-**Process**: [Brief walkthrough]-**Output**: [Expected result]--## Error Handling-| Condition | Response |-|-----------|----------|-| [Error 1] | [Action] |--## Validation-[How to verify the output is correct]-```--## Generation Process--1. **Understand the Task**: What needs to be done?-2. **Identify Inputs**: What information is needed?-3. **Define Steps**: What's the process?-4. **Specify Outputs**: What should be produced?-5. **Add Examples**: Concrete illustrations-6. **Define Validation**: How to check correctness--## Output--```markdown-## PRP Generated: [Task Name]--**Steps**: [X] defined-**Inputs**: [Y] required-**Outputs**: [Z] specified--PRP saved to `prp/[task-name].md`--Ready to execute? Use `prp-execute`.-```diff --git a/usr/skills/frameworks/speckit/speckit-constitution/SKILL.md b/usr/skills/frameworks/speckit/speckit-constitution/SKILL.mddeleted file mode 100644index dd96e970f..000000000--- a/usr/skills/frameworks/speckit/speckit-constitution/SKILL.md+++ /dev/null@@ -1,78 +0,0 @@-----name: "speckit-constitution"-description: "Define project constitution with principles, constraints, and non-negotiables."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["speckit", "planning", "principles", "foundation"]-trigger_patterns:- - "constitution"- - "define principles"- - "project rules"------# Spec Kit: Constitution--Define the foundational principles and constraints that guide all project decisions.--## When to Use--- Starting a new project with Spec Kit-- Need to establish non-negotiable rules-- Before creating specifications--## Constitution Structure--Create `CONSTITUTION.md`:--```markdown-# Project Constitution: [Project Name]--## Core Principles-1. [Principle 1 - e.g., "Security is non-negotiable"]-2. [Principle 2 - e.g., "Simple over clever"]-3. [Principle 3 - e.g., "Test everything"]--## Technology Stack-- Language: [Primary language]-- Framework: [Framework choice]-- Database: [Data storage]-- Infrastructure: [Hosting/deployment]--## Coding Standards-- Style Guide: [Reference]-- Formatting: [Tool, e.g., Prettier, Black]-- Linting: [Tool and config]--## Testing Requirements-- Unit Test Coverage: [Minimum %]-- Integration Tests: [Required/Optional]-- E2E Tests: [Required/Optional]--## Quality Gates-- [ ] All tests must pass-- [ ] No linting errors-- [ ] Code review required-- [ ] [Other gates]--## Non-Negotiables-- [Thing that cannot be compromised 1]-- [Thing that cannot be compromised 2]--## Conventions-- Naming: [Convention]-- File Structure: [Pattern]-- Commit Messages: [Format]-```--## Output--```markdown-## Constitution Created: [Project Name]--**Principles**: [X] defined-**Non-negotiables**: [Y] established--Constitution saved to `CONSTITUTION.md`--Ready to specify features? Use `speckit-specify`.-```diff --git a/usr/skills/frameworks/speckit/speckit-implement/SKILL.md b/usr/skills/frameworks/speckit/speckit-implement/SKILL.mddeleted file mode 100644index 1efa3a61f..000000000--- a/usr/skills/frameworks/speckit/speckit-implement/SKILL.md+++ /dev/null@@ -1,65 +0,0 @@-----name: "speckit-implement"-description: "Execute tasks following specifications and constitution."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["speckit", "implementation", "execution"]-trigger_patterns:- - "implement task"- - "execute task"- - "start task"------# Spec Kit: Implement--Execute tasks while strictly following specifications and constitution.--## When to Use--- Tasks are defined-- Ready to write code-- Need to implement a specific task--## Implementation Process--1. **Load Context**- - Read relevant specification- - Review constitution constraints- - Check task requirements--2. **Implement**- - Follow specification exactly- - Apply constitution principles- - No deviation without approval--3. **Verify**- - Run specified tests- - Check acceptance criteria- - Verify constitution compliance--4. **Update Status**- - Mark task complete- - Document any notes- - Move to next task--## Constitution Compliance Check--Before marking complete:-- [ ] Follows all coding standards-- [ ] Meets quality gates-- [ ] Respects non-negotiables-- [ ] Tests at required coverage--## Output--```markdown-## Task Complete: [Task Title]--**Spec**: [REQ-XXX] satisfied-**Files**: [List of changes]-**Tests**: All passing--Constitution compliance: Verified--Next task?-```diff --git a/usr/skills/frameworks/speckit/speckit-plan/SKILL.md b/usr/skills/frameworks/speckit/speckit-plan/SKILL.mddeleted file mode 100644index 614a6615a..000000000--- a/usr/skills/frameworks/speckit/speckit-plan/SKILL.md+++ /dev/null@@ -1,72 +0,0 @@-----name: "speckit-plan"-description: "Generate implementation roadmap from specifications."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["speckit", "planning", "roadmap"]-trigger_patterns:- - "plan implementation"- - "create roadmap"- - "implementation plan"------# Spec Kit: Plan--Generate an implementation roadmap from approved specifications.--## When to Use--- Specifications are approved-- Need to plan development sequence-- Before generating tasks--## Plan Structure--Create `PLAN.md`:--```markdown-# Implementation Plan: [Project Name]--## Specifications Covered-- [spec-1.md]: [Brief description]-- [spec-2.md]: [Brief description]--## Implementation Phases--### Phase 1: [Name]-**Goal**: [What this phase achieves]-**Specs**: [Which specifications]-**Dependencies**: [None/Prior phases]--### Phase 2: [Name]-...--## Dependency Graph-```-[Phase 1] → [Phase 2] → [Phase 3]- ↘ [Phase 4]-```--## Risk Mitigation-| Risk | Phase | Mitigation |-|------|-------|------------|-| [Risk] | [X] | [Strategy] |--## Success Criteria-- [ ] All specifications implemented-- [ ] All tests pass-- [ ] Constitution compliance verified-```--## Output--```markdown-## Plan Created: [Project Name]--**Phases**: [X]-**Specifications**: [Y] covered--Plan saved to `PLAN.md`--Ready to generate tasks? Use `speckit-tasks`.-```diff --git a/usr/skills/frameworks/speckit/speckit-specify/SKILL.md b/usr/skills/frameworks/speckit/speckit-specify/SKILL.mddeleted file mode 100644index 974b237b1..000000000--- a/usr/skills/frameworks/speckit/speckit-specify/SKILL.md+++ /dev/null@@ -1,88 +0,0 @@-----name: "speckit-specify"-description: "Create detailed specifications for features following constitution principles."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["speckit", "specification", "design"]-trigger_patterns:- - "specify"- - "create spec"- - "specification"------# Spec Kit: Specify--Create detailed, unambiguous specifications following the project constitution.--## When to Use--- After constitution is defined-- Before planning implementation-- When feature requirements need detail--## Specification Structure--Create `specs/[feature-name].md`:--```markdown-# Specification: [Feature Name]--## Summary-[One paragraph description]--## Constitution Alignment-- Principle: [How this follows principle X]-- Constraints: [Relevant constraints]--## Requirements--### Functional-1. [REQ-001] [Clear, testable requirement]-2. [REQ-002] [Clear, testable requirement]--### Non-Functional-1. [NFR-001] [Performance/security/etc requirement]--## Interface--### Inputs-- [Input 1]: [Type, validation, description]--### Outputs-- [Output 1]: [Type, format, description]--## Behavior--### Happy Path-1. [Step 1]-2. [Step 2]-3. [Step 3]--### Error Cases-| Condition | Behavior |-|-----------|----------|-| [Error 1] | [Response] |--## Examples--### Example 1: [Name]-**Input**: [Sample input]-**Output**: [Expected output]--## Acceptance Criteria-- [ ] [AC-001] [Criterion]-- [ ] [AC-002] [Criterion]-```--## Output--```markdown-## Specification Complete: [Feature Name]--**Requirements**: [X] functional, [Y] non-functional-**Acceptance Criteria**: [Z] items--Specification saved to `specs/[feature-name].md`--Ready to plan? Use `speckit-plan`.-```diff --git a/usr/skills/frameworks/speckit/speckit-tasks/SKILL.md b/usr/skills/frameworks/speckit/speckit-tasks/SKILL.mddeleted file mode 100644index b5f04376e..000000000--- a/usr/skills/frameworks/speckit/speckit-tasks/SKILL.md+++ /dev/null@@ -1,57 +0,0 @@-----name: "speckit-tasks"-description: "Break plan into actionable tasks with clear specifications."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["speckit", "tasks", "breakdown"]-trigger_patterns:- - "create tasks"- - "break down"- - "generate tasks"------# Spec Kit: Tasks--Break the implementation plan into specific, actionable tasks.--## When to Use--- Plan is approved-- Ready to start implementation-- Need discrete work items--## Task Format--Create `TASKS.md`:--```markdown-# Tasks: [Phase Name]--## Task 1: [Title]-**Spec Reference**: [REQ-XXX]-**Status**: [ ] Not Started-**Files**:-- Create: `path/to/new.py`-- Modify: `path/to/existing.py`-**Steps**:-1. [Specific step]-2. [Specific step]-**Verification**: [How to verify complete]--## Task 2: [Title]-...-```--## Output--```markdown-## Tasks Generated: [Phase Name]--**Total Tasks**: [X]-**Ready to Start**: [Y]-**Blocked**: [Z]--Tasks saved to `TASKS.md`--Ready to implement? Use `speckit-implement`.-```diff --git a/usr/skills/frameworks/superpowers/sp-brainstorming/SKILL.md b/usr/skills/frameworks/superpowers/sp-brainstorming/SKILL.mddeleted file mode 100644index 8a45ee748..000000000--- a/usr/skills/frameworks/superpowers/sp-brainstorming/SKILL.md+++ /dev/null@@ -1,113 +0,0 @@-----name: "sp-brainstorming"-description: "Structured brainstorming for requirements exploration before implementation."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["superpowers", "planning", "design", "requirements"]-trigger_patterns:- - "brainstorm"- - "explore options"- - "design"- - "think through"------# Superpowers: Brainstorming--Use this skill BEFORE any implementation to explore requirements and design options.--## When to Use--- User requests a new feature-- Starting creative work-- Multiple implementation approaches possible-- Requirements are unclear--## Brainstorming Process--### Phase 1: Understanding Intent (Ask 3-5 Questions)--Focus questions on:-1. **Goal Clarity**: What specific outcome do you want?-2. **Context**: What existing code/systems does this interact with?-3. **Constraints**: Performance, security, compatibility requirements?-4. **Edge Cases**: What happens in failure scenarios?-5. **Success Criteria**: How will we know it's working?--### Phase 2: Explore the Codebase--Before proposing solutions:-- Read relevant existing files-- Identify established patterns-- Note integration points-- Check for similar implementations--### Phase 3: Design Options--Present 2-3 approaches with trade-offs:--```markdown-## Option A: [Name]-**Approach**: Brief description-**Pros**: List benefits-**Cons**: List drawbacks-**Best for**: When to choose this--## Option B: [Name]-**Approach**: Brief description-**Pros**: List benefits-**Cons**: List drawbacks-**Best for**: When to choose this-```--### Phase 4: Technical Specification--Once approach is chosen, document:--1. **Files to Create/Modify**: List with descriptions-2. **Dependencies**: External packages or internal modules-3. **Data Flow**: How data moves through the system-4. **API Contracts**: Input/output specifications-5. **Test Strategy**: How this will be tested--### Phase 5: Implementation Plan--Break down into ordered tasks:--```markdown-## Implementation Tasks-1. [ ] Task 1 - Description-2. [ ] Task 2 - Description (depends on 1)-3. [ ] Task 3 - Description-4. [ ] Task 4 - Integration testing-```--## Output Format--After brainstorming:--```markdown-## Summary: [Feature Name]--### Chosen Approach-[Brief description of selected approach]--### Key Decisions-- Decision 1: Rationale-- Decision 2: Rationale--### Implementation Tasks-1. Task 1-2. Task 2-3. Task 3--### Ready to Plan-Confirm with user before proceeding to `sp-writing-plans`.-```--## Anti-Patterns--- Jumping to code without understanding requirements-- Single solution bias (always consider alternatives)-- Ignoring existing codebase patterns-- Over-engineering simple problems-- Under-specifying complex requirementsdiff --git a/usr/skills/frameworks/superpowers/sp-code-review/SKILL.md b/usr/skills/frameworks/superpowers/sp-code-review/SKILL.mddeleted file mode 100644index 8a23d6590..000000000--- a/usr/skills/frameworks/superpowers/sp-code-review/SKILL.md+++ /dev/null@@ -1,121 +0,0 @@-----name: "sp-code-review"-description: "Review implementation against plan, report issues by severity."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["superpowers", "review", "quality", "verification"]-trigger_patterns:- - "code review"- - "review code"- - "check implementation"------# Superpowers: Code Review--Review implementation against the plan with severity-based reporting.--## When to Use--- After completing a task or set of tasks-- Before merging a feature branch-- Between implementation phases-- When requesting external review--## Review Process--### 1. Gather Context--- Load the relevant plan(s)-- Identify expected deliverables-- Note any constraints or requirements--### 2. Systematic Review--Check each category:--| Category | What to Check |-|----------|---------------|-| **Plan Compliance** | Does the code match the plan? |-| **Test Coverage** | Are all requirements tested? |-| **Code Quality** | Is it readable and maintainable? |-| **Error Handling** | Are edge cases covered? |-| **Security** | Any vulnerabilities introduced? |-| **Performance** | Any obvious bottlenecks? |--### 3. Issue Classification--Classify findings by severity:--```markdown-## Review Findings--### 🔴 CRITICAL (Blocks merge)-- [Issue description]-- [Location: file:line]-- [Suggested fix]--### 🟡 IMPORTANT (Should fix)-- [Issue description]-- [Location: file:line]-- [Suggested fix]--### 🟢 MINOR (Nice to have)-- [Issue description]-- [Location: file:line]-- [Suggested fix]--### ℹ️ OBSERVATIONS (No action needed)-- [Note or observation]-```--## Severity Guidelines--### 🔴 CRITICAL-- Security vulnerabilities-- Data loss potential-- Crashes or errors in happy path-- Missing required functionality-- **Action**: MUST fix before merge--### 🟡 IMPORTANT-- Missing edge case handling-- Performance issues-- Code that will be hard to maintain-- Missing tests for key paths-- **Action**: Should fix, discuss if blocking--### 🟢 MINOR-- Style inconsistencies-- Minor optimization opportunities-- Documentation gaps-- **Action**: Fix if time permits--## Review Checklist--```markdown-## Pre-Merge Checklist--- [ ] All critical issues resolved-- [ ] Important issues addressed or tracked-- [ ] Tests pass-- [ ] No linting errors-- [ ] Documentation updated if needed-- [ ] Commit messages are clear-```--## Integration with Superpowers Workflow--1. **Brainstorming** → Design-2. **Git Worktrees** → Workspace-3. **Writing Plans** → Tasks-4. **TDD** → Implementation-5. **Code Review** → Quality check ← YOU ARE HERE-6. **Finishing Branch** → Merge--## Best Practices--- Review in small chunks (one task at a time when possible)-- Focus on the plan—does the code deliver what was planned?-- Be specific: include file names and line numbers-- Suggest fixes, don't just identify problems-- Critical issues block; everything else is negotiablediff --git a/usr/skills/frameworks/superpowers/sp-executing-plans/SKILL.md b/usr/skills/frameworks/superpowers/sp-executing-plans/SKILL.mddeleted file mode 100644index a2820d7ac..000000000--- a/usr/skills/frameworks/superpowers/sp-executing-plans/SKILL.md+++ /dev/null@@ -1,164 +0,0 @@-----name: "sp-executing-plans"-description: "Systematically implement plan steps with verification at each stage."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["superpowers", "implementation", "execution"]-trigger_patterns:- - "execute plan"- - "implement plan"- - "start building"- - "follow plan"------# Superpowers: Executing Plans--Systematically work through a plan, verifying each step before proceeding.--## When to Use--- Plan has been created and approved-- User is ready to start implementation-- Need to resume work on an existing plan--## Execution Flow--```-Load Plan → Start Step → Implement → Verify → Update Status → Next Step-```--## Execution Process--### 1. Load and Display Plan--```markdown-## Executing: [Feature Name]--**Plan**: [path/to/plan.md]-**Progress**: [X]/[Total] steps complete--### Remaining Steps:-- Step [N]: [Title]-- Step [N+1]: [Title]-...--Starting Step [N]...-```--### 2. Execute Each Step--For each step:--#### a) Announce Intent-```markdown-### Step [N]: [Title]-**Goal**: [What this achieves]-**Starting...**-```--#### b) Implement Changes-- Make the code changes-- Follow existing patterns-- Add tests if specified--#### c) Verify-- Run specified verification-- Check for regressions-- Confirm goal is met--#### d) Report Completion-```markdown-**Step [N] Complete**-- Modified: `file1.py`, `file2.py`-- Tests: Passing-- Verification: [How verified]--Proceeding to Step [N+1]...-```--### 3. Handle Deviations--When plan needs adjustment:--```markdown-### Plan Deviation Needed--**Step**: [N]-**Issue**: [What was discovered]-**Impact**: [How this affects the plan]--**Options**:-A) [Adjustment option]-B) [Alternative option]--How would you like to proceed?-```--Wait for user input before continuing.--### 4. Progress Checkpoints--Every 2-3 steps or at natural breaks:--```markdown-## Checkpoint--**Progress**: [X]/[Total] steps-**Completed**:-- Step 1: [Title]-- Step 2: [Title]--**Status**: On track / Adjustments made--Continue with remaining steps?-```--### 5. Handle Failures--If a step fails:--```markdown-### Step [N] Failed--**Error**: [What went wrong]-**Attempted**: [What was tried]--**Options**:-1. Debug and fix-2. Skip step (with consequences)-3. Revise plan--How would you like to proceed?-```--### 6. Completion--```markdown-## Execution Complete: [Feature Name]--**Steps**: [Total]/[Total] complete-**Files created**: [count]-**Files modified**: [count]-**Tests**: [status]--### Summary of Changes-- `file1.py`: [what changed]-- `file2.py`: [what changed]--Ready for final review? Use `sp-finishing-branch` to wrap up.-```--## Best Practices--- **Small commits**: Commit after each step or logical group-- **Run tests frequently**: Don't let failures accumulate-- **Stay focused**: Only implement what's in the plan-- **Document deviations**: Note any changes to the plan--## Anti-Patterns--- Skipping verification-- Making unplanned changes-- Continuing past failures without resolving-- Large commits with multiple steps-- Not updating plan with actual changesdiff --git a/usr/skills/frameworks/superpowers/sp-finishing-branch/SKILL.md b/usr/skills/frameworks/superpowers/sp-finishing-branch/SKILL.mddeleted file mode 100644index 73690cef9..000000000--- a/usr/skills/frameworks/superpowers/sp-finishing-branch/SKILL.md+++ /dev/null@@ -1,172 +0,0 @@-----name: "sp-finishing-branch"-description: "Complete development branch with proper git workflow, review, and merge preparation."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["superpowers", "git", "review", "completion"]-trigger_patterns:- - "finish branch"- - "wrap up"- - "prepare for merge"- - "create pr"------# Superpowers: Finishing Branch--Complete a development branch with proper verification, documentation, and git workflow.--## When to Use--- Implementation is complete-- Ready to merge or create PR-- Need to clean up before submission--## Finishing Checklist--### 1. Verify All Tests Pass--```bash-# Run full test suite-pytest tests/-# or npm test, cargo test, etc.-```--```markdown-## Test Results-**Total**: [X] tests-**Passed**: [X]-**Failed**: 0-**Coverage**: [X]%--All tests passing.-```--### 2. Code Quality Check--- [ ] No linting errors-- [ ] No type errors (if applicable)-- [ ] No debug code left in-- [ ] No hardcoded values that should be config-- [ ] Error handling is present-- [ ] No security issues--### 3. Documentation Review--- [ ] README updated if needed-- [ ] API documentation current-- [ ] Comments explain non-obvious code-- [ ] CHANGELOG updated--### 4. Clean Git History--Review commits:-```bash-git log --oneline -10-```--Ensure commits are:-- [ ] Logical and atomic-- [ ] Well-described-- [ ] No WIP or temp commits--### 5. Create/Update PR Description--```markdown-## Summary-[1-3 sentence description of changes]--## Changes-- [Change 1]-- [Change 2]-- [Change 3]--## Testing-- [How this was tested]-- [What to test during review]--## Screenshots (if applicable)-[Add screenshots for UI changes]--## Checklist-- [ ] Tests pass-- [ ] Documentation updated-- [ ] No breaking changes (or noted below)-```--### 6. Final Verification--```markdown-## Pre-Merge Checklist--**Branch**: [branch-name]-**Target**: [main/develop]--### Automated Checks-- [ ] All tests pass-- [ ] Linting passes-- [ ] Build succeeds--### Manual Verification-- [ ] Feature works as expected-- [ ] Edge cases handled-- [ ] No regressions in related features--### Documentation-- [ ] README current-- [ ] API docs updated-- [ ] Inline comments adequate--### Git-- [ ] Commits are clean-- [ ] No merge conflicts-- [ ] Branch is up to date with target-```--## Output--After finishing process:--```markdown-## Branch Ready: [branch-name]--**Status**: Ready for review/merge-**Tests**: All passing-**Commits**: [X] clean commits--### Summary of Changes-- [Main change 1]-- [Main change 2]--### PR/MR Ready-[Link or instructions to create]--What's next?-- Create pull request-- Request review-- Merge (if self-merge allowed)-```--## Git Commands Reference--```bash-# Update branch with latest target-git fetch origin-git rebase origin/main--# Interactive rebase to clean commits-git rebase -i origin/main--# Push (force if rebased)-git push --force-with-lease--# Create PR via CLI (GitHub)-gh pr create --title "Feature: X" --body "..."-```--## Anti-Patterns--- Merging with failing tests-- Skipping code review-- Poor commit messages-- Leaving TODO comments-- Not updating documentationdiff --git a/usr/skills/frameworks/superpowers/sp-git-worktrees/SKILL.md b/usr/skills/frameworks/superpowers/sp-git-worktrees/SKILL.mddeleted file mode 100644index bdb18e830..000000000--- a/usr/skills/frameworks/superpowers/sp-git-worktrees/SKILL.md+++ /dev/null@@ -1,112 +0,0 @@-----name: "sp-git-worktrees"-description: "Create isolated workspace on new branch for parallel development."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["superpowers", "git", "worktree", "branching"]-trigger_patterns:- - "git worktree"- - "create worktree"- - "isolated workspace"- - "parallel development"------# Superpowers: Git Worktrees--Create isolated workspaces for parallel development without stashing or switching branches.--## When to Use--- After design approval, before implementation-- When you need to work on multiple features simultaneously-- When you want a clean environment for a new feature--## What Git Worktrees Provide--- **Isolation**: Each worktree has its own working directory-- **Parallel work**: Multiple features can be developed simultaneously-- **Clean baseline**: Start fresh without uncommitted changes-- **Easy cleanup**: Remove worktree when done, branch remains--## Process--### 1. Create Worktree--```bash-# From your main repository-git worktree add ../feature-name feature-branch-name-```--Or create worktree with new branch:-```bash-git worktree add -b feature-branch-name ../feature-name-```--### 2. Navigate to Worktree--```bash-cd ../feature-name-```--### 3. Verify Setup--```bash-# Check you're on the right branch-git branch--# Run project setup (if needed)-npm install # or equivalent-```--### 4. Verify Test Baseline--Before any changes, ensure tests pass:--```bash-# Run test suite-npm test # or equivalent--# All tests should be green before you start-```--## Worktree Management--### List Worktrees-```bash-git worktree list-```--### Remove Worktree-```bash-git worktree remove ../feature-name-```--### Prune Stale Worktrees-```bash-git worktree prune-```--## Best Practices--1. **Naming convention**: Use descriptive names matching branch purpose-2. **Location**: Keep worktrees in sibling directories-3. **Cleanup**: Remove worktrees after merging-4. **Test baseline**: Always verify tests pass before starting work--## Directory Structure Example--```-~/projects/-├── my-project/ # Main repo-├── my-project-feature-a/ # Worktree for feature A-├── my-project-feature-b/ # Worktree for feature B-└── my-project-hotfix/ # Worktree for hotfix-```--## Integration with Superpowers Workflow--1. **Brainstorming** → Design approved-2. **Git Worktrees** → Create isolated workspace ← YOU ARE HERE-3. **Writing Plans** → Plan implementation-4. **Executing Plans** → Build feature-5. **Finishing Branch** → Merge and cleanup worktreediff --git a/usr/skills/frameworks/superpowers/sp-test-driven-development/SKILL.md b/usr/skills/frameworks/superpowers/sp-test-driven-development/SKILL.mddeleted file mode 100644index 0ff20e527..000000000--- a/usr/skills/frameworks/superpowers/sp-test-driven-development/SKILL.md+++ /dev/null@@ -1,110 +0,0 @@-----name: "sp-test-driven-development"-description: "RED-GREEN-REFACTOR cycle: write failing test, minimal code, commit."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["superpowers", "tdd", "testing", "development"]-trigger_patterns:- - "test driven"- - "tdd"- - "red green refactor"- - "test first"------# Superpowers: Test-Driven Development--Enforce strict RED-GREEN-REFACTOR discipline for reliable code.--## The TDD Cycle--```-┌─────────┐ ┌─────────┐ ┌──────────┐-│ RED │ ──▶ │ GREEN │ ──▶ │ REFACTOR │-│ (fail) │ │ (pass) │ │ (clean) │-└─────────┘ └─────────┘ └──────────┘- ▲ │- └───────────────────────────────┘-```--## The Rules--### 1. RED: Write a Failing Test First--- Write the test BEFORE any implementation-- The test MUST fail initially-- Failure confirms the test is testing something real--```bash-# Run test - expect failure-npm test -- --grep "should validate email"-# FAIL ✗-```--### 2. GREEN: Write Minimal Code to Pass--- Write ONLY enough code to make the test pass-- No extra features, no "while I'm here" additions-- Resist the urge to generalize--```bash-# Run test - expect success-npm test -- --grep "should validate email"-# PASS ✓-```--### 3. REFACTOR: Clean Up (Tests Stay Green)--- Improve code quality without changing behavior-- Tests must remain passing-- Commit after each successful refactor--```bash-# Run all tests - all must pass-npm test-# All PASS ✓-```--### 4. COMMIT: After Each Cycle--- One commit per RED-GREEN-REFACTOR cycle-- Clear commit message describing the test case--## Anti-Patterns to Avoid--| Anti-Pattern | Why It's Bad |-|-------------|--------------|-| Writing code before tests | No proof code works |-| Writing multiple tests at once | Too much change, hard to debug |-| Making tests pass with hacks | Technical debt accumulates |-| Skipping refactor step | Code quality degrades |-| Testing implementation details | Tests become brittle |--## Test Quality Checklist--- [ ] Test describes behavior, not implementation-- [ ] Test has clear arrange-act-assert structure-- [ ] Test fails for the right reason initially-- [ ] Test name explains what it verifies-- [ ] Test is independent (no shared state)--## Integration with Superpowers Workflow--1. **Brainstorming** → Design approved-2. **Git Worktrees** → Isolated workspace-3. **Writing Plans** → Tasks defined-4. **TDD** → For each task: RED → GREEN → REFACTOR ← YOU ARE HERE-5. **Code Review** → Review implementation-6. **Finishing Branch** → Merge--## The Discipline--**DELETE code written before tests.**--If you find yourself writing implementation before the test:-1. Stop immediately-2. Delete the implementation-3. Write the test first-4. Watch it fail-5. THEN write the code--This is not negotiable. The discipline IS the value.diff --git a/usr/skills/frameworks/superpowers/sp-writing-plans/SKILL.md b/usr/skills/frameworks/superpowers/sp-writing-plans/SKILL.mddeleted file mode 100644index d304c5592..000000000--- a/usr/skills/frameworks/superpowers/sp-writing-plans/SKILL.md+++ /dev/null@@ -1,140 +0,0 @@-----name: "sp-writing-plans"-description: "Create detailed implementation plans with clear steps and verification criteria."-version: "1.0.0"-author: "Agent Zero Team"-tags: ["superpowers", "planning", "documentation"]-trigger_patterns:- - "write plan"- - "create plan"- - "make plan"- - "planning"------# Superpowers: Writing Plans--Create a detailed, actionable implementation plan after brainstorming.--## When to Use--- After completing brainstorming phase-- User has selected an approach-- Ready to formalize the implementation strategy--## Plan Document Structure--Create a plan file (e.g., `PLAN.md` or `.plan/current.md`):--```markdown-# Implementation Plan: [Feature Name]--## Context-[Brief background and why this is being built]--## Objective-[Clear, measurable goal statement]--## Approach-[Selected approach from brainstorming with rationale]--## Steps--### Step 1: [Title]-**Goal**: What this step achieves-**Actions**:-- Specific action 1-- Specific action 2-**Verification**: How to confirm step is complete-**Files**: Files to create/modify--### Step 2: [Title]-...--## Test Plan-- [ ] Unit tests for X-- [ ] Integration tests for Y-- [ ] Manual verification of Z--## Acceptance Criteria-- [ ] Criterion 1-- [ ] Criterion 2-- [ ] All tests pass-- [ ] No regressions--## Dependencies-- [List external dependencies]--## Risks-- [Potential issues and mitigations]-```--## Plan Writing Guidelines--### Steps Should Be--1. **Atomic**: One clear action per step-2. **Verifiable**: Has a way to confirm completion-3. **Ordered**: Dependencies are clear-4. **Scoped**: Not too large, not too small--### Each Step Includes--- Clear goal statement-- Specific file changes-- Verification method-- Estimated size (small/medium/large)--### Good Step Example--```markdown-### Step 3: Add validation to user input-**Goal**: Ensure email addresses are valid format-**Actions**:-- Create `validators/email.py` with email regex-- Import validator in `forms/user_form.py`-- Add validation call in `handle_submit()`-**Verification**:-- Unit test with valid/invalid emails-- Form rejects "notanemail" input-**Files**: `validators/email.py`, `forms/user_form.py`-```--### Bad Step Example--```markdown-### Step 3: Implement validation-- Add validation-```--## Plan Review Checklist--Before finalizing:-- [ ] Each step has a clear goal-- [ ] Dependencies between steps are noted-- [ ] Test plan covers main scenarios-- [ ] Acceptance criteria are measurable-- [ ] No steps are too large (break down if needed)--## Output--After plan is written:--```markdown-## Plan Complete: [Feature Name]--**Steps**: [X] implementation steps-**Test cases**: [Y] planned-**Files affected**: [Z] files--Plan saved to `[path]`--Ready to execute? Use `sp-executing-plans` to begin.-```--## Anti-Patterns--- Steps that are too vague-- Missing verification criteria-- Forgetting test planning-- Plans that can't be followed by someone else-- Overly rigid plans (leave room for discovery)diff --git a/webui/components/projects/project-edit-basic-data.html b/webui/components/projects/project-edit-basic-data.htmlindex 405b24b95..3f2f4df54 100644--- a/webui/components/projects/project-edit-basic-data.html+++ b/webui/components/projects/project-edit-basic-data.html@@ -59,17 +59,6 @@</div></div>- <div class="projects-form-group">- <label class="projects-form-label">Framework</label>- <span class="projects-form-description">Override the global framework for this project.- Framework skills will be prioritized when working on this project.</span>- <select class="projects-form-select" x-model="$store.projects.selectedProject.dev_framework">- <template x-for="option in $store.projects.frameworkOptions" :key="option.value">- <option :value="option.value" x-text="option.label"- :selected="option.value === ($store.projects.selectedProject.dev_framework || '')"></option>- </template>- </select>- </div></div>diff --git a/webui/components/projects/projects-store.js b/webui/components/projects/projects-store.jsindex cb4c74408..0ecaa838f 100644--- a/webui/components/projects/projects-store.js+++ b/webui/components/projects/projects-store.js@@ -15,7 +15,6 @@ const model = {projectList: [],selectedProject: null,editData: null,- frameworkOptions: [],colors: ["#7b2cbf", // Deep Purple"#8338ec", // Blue Violet@@ -72,37 +71,16 @@ const model = {async openCreateModal() {this.selectedProject = this._createNewProjectData();- await this.loadFrameworkOptions();await modals.openModal(createModal);this.selectedProject = null;},async openEditModal(name) {this.selectedProject = await this._createEditProjectData(name);- await this.loadFrameworkOptions();await modals.openModal(editModal);this.selectedProject = null;},- async loadFrameworkOptions() {- try {- const response = await api.callJsonApi("frameworks", { action: "list" });- if (response?.ok && response?.data) {- // Add "Use Global Setting" option at the top- this.frameworkOptions = [- { value: "", label: "Use Global Setting" },- ...response.data.map(fw => ({ value: fw.id, label: fw.name }))- ];- } else {- // Fallback if API fails- this.frameworkOptions = [{ value: "", label: "Use Global Setting" }];- }- } catch (error) {- console.error("Error loading framework options:", error);- this.frameworkOptions = [{ value: "", label: "Use Global Setting" }];- }- },-async cancelCreate() {await modals.closeModal(createModal);},@@ -330,7 +308,6 @@ const model = {title: `Project #${this.projectList.length + 1}`,description: "",color: "",- dev_framework: "",};},diff --git a/webui/components/settings/agent/agent-settings.html b/webui/components/settings/agent/agent-settings.htmlindex fe96c715f..1a15a8d1d 100644--- a/webui/components/settings/agent/agent-settings.html+++ b/webui/components/settings/agent/agent-settings.html@@ -15,12 +15,6 @@<span>Agent Config</span></a></li>- <li>- <a href="#section-framework">- <img src="/public/framework.svg" alt="Framework" />- <span>Framework</span>- </a>- </li><li><a href="#section-chat-model"><img src="/public/chat_model.svg" alt="Chat Model" />@@ -64,9 +58,6 @@<x-component path="settings/agent/agent.html"></x-component></div>- <div id="section-framework" class="section">- <x-component path="settings/agent/framework.html"></x-component>- </div><div id="section-chat-model" class="section"><x-component path="settings/agent/chat_model.html"></x-component>diff --git a/webui/components/settings/agent/framework.html b/webui/components/settings/agent/framework.htmldeleted file mode 100644index dd9dc72ae..000000000--- a/webui/components/settings/agent/framework.html+++ /dev/null@@ -1,49 +0,0 @@-<html>- <head>- <title>Framework</title>- </head>-- <body>- <div x-data>- <template x-if="$store.settingsStore.settings">- <div>- <div class="section-title">Framework</div>- <div class="section-description">- Choose a structured workflow methodology to guide the agent.- </div>-- <div class="field">- <div class="field-label">- <div class="field-title">Active Framework</div>- <div class="field-description">- Select a methodology. When active, framework-specific skills are prioritized- and workflow guidance is injected into the system prompt.- </div>- </div>- <div class="field-control">- <select x-model="$store.settingsStore.settings.dev_framework">- <template x-for="option in $store.settingsStore.additional?.framework_options" :key="option.value">- <option :value="option.value" :selected="option.value === $store.settingsStore.settings.dev_framework" x-text="option.label"></option>- </template>- </select>- </div>- </div>-- <div class="field">- <div class="field-label">- <div class="field-title">Framework Details</div>- <div class="field-description">- View detailed information about the selected framework and its workflow steps.- </div>- </div>- <div class="field-control">- <button class="btn btn-field" @click="$store.settingsStore.handleFieldButton({id: 'framework_info'})">- View Details- </button>- </div>- </div>- </div>- </template>- </div>- </body>-</html>diff --git a/webui/components/settings/frameworks/framework-details.html b/webui/components/settings/frameworks/framework-details.htmldeleted file mode 100644index 50b3f9a2c..000000000--- a/webui/components/settings/frameworks/framework-details.html+++ /dev/null@@ -1,273 +0,0 @@-<html>-<head>- <title>Framework Details</title>- <script type="module">- import { store } from "/components/settings/frameworks/framework-store.js";- </script>-</head>-<body>- <div x-data class="framework-modal-container">- <template x-if="$store.frameworkStore">- <div x-init="$store.frameworkStore.init()" x-destroy="$store.frameworkStore.onClose()">-- <div x-show="$store.frameworkStore.loading" class="loading">- Loading frameworks...- </div>-- <div x-show="$store.frameworkStore.error" class="error">- <span x-text="$store.frameworkStore.error"></span>- </div>-- <div x-show="!$store.frameworkStore.loading && !$store.frameworkStore.error">-- <!-- Framework selector -->- <div class="framework-selector">- <label class="selector-label">- <span>View Framework:</span>- <select class="framework-dropdown"- @change="$store.frameworkStore.selectFramework($event.target.value)">- <template x-for="fw in $store.frameworkStore.frameworks" :key="fw.id">- <option :value="fw.id"- :selected="$store.frameworkStore.selectedFramework?.id === fw.id"- x-text="fw.name"></option>- </template>- </select>- </label>- </div>-- <!-- Framework details -->- <template x-if="$store.frameworkStore.selectedFramework">- <div class="framework-details">- <div class="framework-header">- <h3 x-text="$store.frameworkStore.selectedFramework.name"></h3>- <span class="framework-id" x-text="'ID: ' + $store.frameworkStore.selectedFramework.id"></span>- </div>-- <p class="framework-description" x-text="$store.frameworkStore.selectedFramework.description"></p>-- <!-- Workflow steps -->- <template x-if="$store.frameworkStore.selectedFramework.workflows?.length > 0">- <div class="workflow-section">- <h4>Workflow Steps</h4>- <div class="workflow-steps">- <template x-for="(step, index) in $store.frameworkStore.selectedFramework.workflows" :key="step.skill_name">- <div class="workflow-step">- <div class="step-number" x-text="step.sequence"></div>- <div class="step-content">- <div class="step-name" x-text="step.name"></div>- <div class="step-skill">- <code x-text="step.skill_name"></code>- </div>- <div class="step-description" x-text="step.description"></div>- </div>- </div>- </template>- </div>- </div>- </template>-- <!-- No workflows message -->- <template x-if="!$store.frameworkStore.selectedFramework.workflows?.length">- <div class="no-workflows">- <p>This framework has no predefined workflow steps.</p>- </div>- </template>-- <!-- Usage hint -->- <div class="usage-hint">- <h4>How to Use</h4>- <p>When this framework is active:</p>- <ul>- <li>Framework skills are prioritized in skill discovery</li>- <li>Workflow guidance is injected into the system prompt</li>- <li>Use <code>skills_tool</code> to load specific workflow skills</li>- </ul>- </div>- </div>- </template>-- <!-- No selection -->- <template x-if="!$store.frameworkStore.selectedFramework">- <div class="no-selection">- <p>Select a framework to view its details.</p>- </div>- </template>- </div>-- </div>- </template>- </div>-- <style>- .framework-modal-container {- padding: 0.5rem;- }-- .loading {- text-align: center;- padding: 2rem;- color: var(--color-secondary);- }-- .error {- color: var(--color-error);- padding: 1rem;- background: var(--color-error-bg);- border-radius: 4px;- margin-bottom: 1rem;- }-- .framework-selector {- margin-bottom: 1.5rem;- }-- .selector-label {- display: flex;- align-items: center;- gap: 0.75rem;- font-weight: 600;- }-- .framework-dropdown {- flex: 1;- max-width: 300px;- padding: 0.5rem;- border: 1px solid var(--color-border);- border-radius: 4px;- background: var(--color-bg-primary);- color: var(--color-text-primary);- font-size: 0.95rem;- }-- .framework-details {- background: var(--color-input);- border: 1px solid var(--color-border);- border-radius: 8px;- padding: 1.25rem;- }-- .framework-header {- display: flex;- align-items: baseline;- gap: 1rem;- margin-bottom: 0.75rem;- }-- .framework-header h3 {- margin: 0;- font-size: 1.25rem;- color: var(--color-primary);- }-- .framework-id {- font-size: 0.8rem;- color: var(--color-secondary);- font-family: monospace;- }-- .framework-description {- color: var(--color-text-secondary);- line-height: 1.5;- margin-bottom: 1.5rem;- }-- .workflow-section h4,- .usage-hint h4 {- font-size: 1rem;- margin: 0 0 0.75rem 0;- color: var(--color-primary);- border-bottom: 1px solid var(--color-border);- padding-bottom: 0.5rem;- }-- .workflow-steps {- display: flex;- flex-direction: column;- gap: 0.75rem;- }-- .workflow-step {- display: flex;- gap: 1rem;- padding: 0.75rem;- background: var(--color-bg-primary);- border-radius: 6px;- border: 1px solid var(--color-border);- }-- .step-number {- display: flex;- align-items: center;- justify-content: center;- width: 2rem;- height: 2rem;- background: var(--color-accent);- color: white;- border-radius: 50%;- font-weight: bold;- font-size: 0.9rem;- flex-shrink: 0;- }-- .step-content {- flex: 1;- }-- .step-name {- font-weight: 600;- margin-bottom: 0.25rem;- }-- .step-skill {- margin-bottom: 0.25rem;- }-- .step-skill code {- font-size: 0.8rem;- background: var(--color-input);- padding: 0.15rem 0.4rem;- border-radius: 3px;- color: var(--color-accent);- }-- .step-description {- font-size: 0.9rem;- color: var(--color-text-secondary);- }-- .no-workflows,- .no-selection {- text-align: center;- padding: 2rem;- color: var(--color-secondary);- }-- .usage-hint {- margin-top: 1.5rem;- padding-top: 1rem;- }-- .usage-hint p {- margin: 0 0 0.5rem 0;- color: var(--color-text-secondary);- }-- .usage-hint ul {- margin: 0;- padding-left: 1.5rem;- color: var(--color-text-secondary);- }-- .usage-hint li {- margin-bottom: 0.25rem;- }-- .usage-hint code {- font-size: 0.85rem;- background: var(--color-input);- padding: 0.1rem 0.3rem;- border-radius: 3px;- }- </style>-</body>-</html>diff --git a/webui/components/settings/frameworks/framework-store.js b/webui/components/settings/frameworks/framework-store.jsdeleted file mode 100644index d929bfb08..000000000--- a/webui/components/settings/frameworks/framework-store.js+++ /dev/null@@ -1,60 +0,0 @@-import { createStore } from "/js/AlpineStore.js";-import { callJsonApi } from "/js/api.js";--const model = {- frameworks: [],- selectedFramework: null,- loading: false,- error: null,- _initialized: false,-- async init() {- if (this._initialized) return;- this._initialized = true;- await this.loadFrameworks();- },-- async loadFrameworks() {- this.loading = true;- this.error = null;- try {- const response = await callJsonApi("frameworks", { action: "list" });- if (response.ok) {- this.frameworks = response.data;- // Select current framework from settings- const currentFramework = this.getCurrentFrameworkId();- this.selectFramework(currentFramework);- } else {- this.error = response.error || "Failed to load frameworks";- }- } catch (e) {- this.error = e.message || "Failed to load frameworks";- } finally {- this.loading = false;- }- },-- getCurrentFrameworkId() {- // Get from settings store - new structure has settings.dev_framework directly- const settingsStore = window.Alpine?.store("settingsStore");- if (settingsStore?.settings?.dev_framework) {- return settingsStore.settings.dev_framework;- }- return "none";- },-- selectFramework(frameworkId) {- this.selectedFramework = this.frameworks.find(f => f.id === frameworkId) || null;- },-- getWorkflowSteps() {- if (!this.selectedFramework) return [];- return this.selectedFramework.workflows || [];- },-- onClose() {- // Cleanup if needed- }-};--export const store = createStore("frameworkStore", model);diff --git a/webui/components/settings/settings-store.js b/webui/components/settings/settings-store.jsindex 80180a9c6..a8265352d 100644--- a/webui/components/settings/settings-store.js+++ b/webui/components/settings/settings-store.js@@ -13,7 +13,6 @@ const FIELD_BUTTON_MODAL_BY_ID = Object.freeze({backup_restore: "settings/backup/restore.html",show_a2a_connection: "settings/a2a/a2a-connection.html",external_api_examples: "settings/external/api-examples.html",- framework_info: "settings/frameworks/framework-details.html",});// Helper for toastsdiff --git a/webui/public/framework.svg b/webui/public/framework.svgdeleted file mode 100644index 408bc20e9..000000000--- a/webui/public/framework.svg+++ /dev/null@@ -1 +0,0 @@-<?xml version="1.0" encoding="utf-8" ?><svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="1200" height="1200" viewBox="0 0 1200 1200"><path fill="#000101" transform="scale(0.657895 0.513699)" d="M508.916 0L1362.98 0C1363.14 0.341385 1363.3 0.687576 1363.47 1.02416C1367.39 8.79865 1375.59 13.481 1377.62 22.3398C1380.47 34.7523 1378.95 51.336 1378.95 64.2781C1378.94 81.9683 1377.02 188.105 1381.11 195.297C1382.95 198.534 1388.89 199.874 1391.85 200.621C1403.38 203.535 1415.16 204.96 1426.76 207.372C1451.19 212.452 1475.51 218.557 1500 223.552C1518.47 227.322 1543.07 230.826 1560.33 238.651C1565.8 241.128 1570.8 244.81 1574.08 251.121C1578 258.672 1578.06 267.695 1576.53 276.269C1574.84 285.685 1572.24 294.787 1570.41 304.151C1568.82 312.283 1567.79 320.642 1565.96 328.687C1564.25 336.171 1561.37 343.586 1560.24 351.235C1559.77 354.416 1559.94 356.73 1560.65 359.804C1566.58 371.237 1704.56 402.097 1721.74 417.629C1727.82 423.126 1736.93 428.034 1735.07 441.399C1732.85 451.78 1727.77 465.427 1724.4 475.72L1706.45 531.013C1692.87 571.851 1681.07 615.67 1667.8 656.842C1662.51 673.253 1632.11 754.205 1634.96 767.592C1638.74 774.659 1645.85 776.163 1651.74 780.39C1665.5 790.276 1675.09 808.073 1681.84 825.628C1695.69 861.609 1683.41 907.329 1690.99 945.367C1691.95 950.203 1720.35 948.698 1724 950.34C1759.45 957.538 1804.35 975.855 1817.09 1024.12C1818.63 1029.96 1820.1 1031.6 1824 1035.07L1824 1098.99L1823.07 1100.16C1820.91 1102.91 1817.32 1107.3 1816.75 1111.13C1813.76 1131.32 1810.43 1150.95 1806.44 1170.89L1763.34 1392.13L1681.34 1807.46C1676.11 1835.13 1672.99 1863.13 1666.61 1890.46C1653.16 1948.08 1653.99 2012.17 1613.21 2052.11C1576.48 2088.08 1535.19 2085.63 1492 2085.85L1432.92 2086.33L964.508 2086.38L806.112 2086.92C783.811 2086.97 746.255 2085.09 725.114 2087.2C715.475 2085.97 700.34 2087.07 690.246 2086.85C663.853 2086.27 636.829 2087.48 610.487 2086.83C490.842 2083.71 371.175 2082.16 251.505 2082.19L167.427 2082.23C121.545 2082.25 74.9808 2085.95 35.3736 2050.28C28.4268 2044.03 22.0048 2036.76 14.9919 2030.68L14.263 2030.06C12.4683 2025.24 2.57937 2001.92 0 1998.96L0 801.635C7.18447 791.036 7.72495 778.136 16.8099 764.683C37.3154 734.318 58.1865 724.038 87.9834 716.137C102.398 712.315 140.086 717.84 150.038 711.031C151.555 705.592 141.83 674.733 140.069 667.026C125.605 603.728 110.385 540.727 93.7366 478.318C87.6296 455.425 81.538 440.433 102.183 426.897C120.334 414.997 203.496 404.36 214.886 392.661C218.596 384.853 200.09 293.673 198.223 276.127C195.484 250.386 183.878 214.612 184.65 186.414C185.335 161.424 210.071 164.261 223.978 160.104C252.24 154.72 282.266 148.217 310.432 143.61L431.214 124.021C442.506 122.125 485.147 118.381 492.515 110.784C497.476 99.3625 493.429 43.4056 495.178 26.3796C496.784 10.7562 498.726 11.2972 508.916 0ZM1601.26 1968.14C1608.89 1943.51 1610.99 1922.29 1615.81 1896.93C1618.38 1883.44 1621.74 1870.92 1624 1857.13C1625.82 1846.02 1627.02 1832.44 1629.04 1821.75L1697.39 1475.31L1751.4 1195.24C1759.32 1153.95 1769.4 1112.43 1775.35 1070.7C1778.66 1047.5 1760.92 1015.47 1744.22 1009.85C1711.71 998.931 1668.74 1002.71 1634.95 1003L1518.54 1003.37L1009.08 1003.23L859.472 1003.33C834.05 1003.55 800.12 1005.53 775.465 1002.68C727.391 997.106 711.134 958.746 687.676 912.926L646.484 831.711C632.93 805.145 621.492 772.861 594.339 771.055C573.505 769.67 552.276 770.287 531.435 770.336L452.006 770.475L180.588 770.495C161.103 770.497 105.852 768.652 90.3112 774.399C81.0911 777.835 72.6887 784.171 65.8695 792.829C59.0862 801.531 54.8373 811.525 53.7269 823.666C49.9807 864.631 51.5087 911.507 51.5272 953.062L51.7401 1185.33C52.0648 1376 51.6141 1566.67 50.3878 1757.33C50.4072 1801.85 49.9809 1846.19 49.2629 1890.69C48.879 1914.49 48.7726 1938.54 49.3763 1962.31C49.6601 1972.72 54.8135 1995.68 60.8 2002.58C70.4693 2013.72 82.4238 2025.13 95.8591 2026.51C119.313 2028.91 143.103 2028.31 166.582 2028.29L269.985 2028.31L627.415 2027.59L1210.57 2027.77L1418.24 2027.91C1459.17 2028.05 1500.13 2028.27 1541.22 2028.15C1561.57 2028.09 1576.1 2017.67 1590.72 1999.73C1597.35 1991.59 1599.16 1979.36 1601.26 1968.14ZM891.543 718.868C899.272 692.549 907.202 665.057 915.296 638.966L937.394 569.04C941.254 556.787 953.194 528.484 953.008 515.921C952.793 501.434 941.143 468.135 938.08 452.374C935.985 441.59 933.025 429.927 930.285 419.407C927.447 410.173 923.72 408.351 916.316 409.797C905.935 411.825 895.837 415.24 885.556 417.849L804.481 438.888L371.871 546.771L233.704 581.831C221.855 584.937 194.809 589.245 185.491 594.051C184.065 595.892 182.303 598.896 182.892 601.77C189.726 635.149 198.746 668.341 205.759 701.841C206.47 705.235 207.839 708.771 209.27 711.137C219.08 715.123 271.02 713.763 284.844 713.802L506.732 714.718C525.686 714.906 544.64 714.904 563.593 714.712C574.408 714.583 592.293 713.128 602.539 715.289C625.96 720.229 651.678 731.925 667.557 755.64C676.745 769.364 682.52 783.592 690.38 798.355C710.165 835.053 726.722 873.682 747.21 909.919C751.716 917.89 756.32 932.759 763.015 938.722C775.958 950.249 804.288 949.534 819.485 945.571C820.752 945.241 821.819 942.818 822.354 941.461C826.484 924.183 832.164 908.412 837.768 891.936C840.641 883.488 841.584 872.121 844.729 863.548C849.55 850.01 854.007 837.753 858.409 823.874C869.155 789.687 881.87 752.501 891.543 718.868ZM891.657 898.458C889.79 903.052 878.531 942.35 879.38 946.369C882.193 947.439 889.34 948.99 892.068 948.883C913.562 948.046 1027.42 953.51 1043.19 947.574C1044.02 941.477 1038.34 936.161 1036.37 929.974C1036.92 927.392 1037.82 924.951 1039.02 922.76C1055.65 892.305 1077.18 861.57 1093.46 830.228C1100.53 816.625 1111.36 802.363 1125 811.786C1130.72 815.739 1146.76 825.137 1149.99 831.173C1151.4 839.503 1133.6 864.934 1128.93 872.563C1120.19 887.05 1111.63 901.722 1103.27 916.571C1099.66 922.889 1088.77 939.032 1090.79 946.182C1095.28 951.116 1132.99 951.138 1137.28 946.661C1140.52 938.669 1129.17 928.587 1149.45 922.255C1204.94 904.926 1122.29 882.16 1172.17 858.666C1178.94 855.475 1186.87 847.107 1195.19 848.531C1199.24 853.105 1201.7 858.202 1204.89 863.651C1215.27 881.381 1226.98 899.434 1234.87 919.177C1238.16 927.391 1218.65 939.426 1220.62 947.052C1221.79 947.953 1221.72 947.981 1223.25 948.657C1230.43 951.838 1482.88 951.941 1511.79 949.859C1514.6 949.657 1517.4 949.457 1519.97 947.873C1527.57 935.523 1529 920.501 1533.56 906.329L1573.86 781.615L1644.97 554.693C1651.6 533.219 1674.2 476.795 1672.96 457.039C1668.89 448.306 1634.71 440.747 1625.25 437.84L1556.86 416.089L1242.14 316.593C1195.26 301.54 1147.47 289.045 1100.72 272.86C1096.17 271.284 1088.81 270.614 1086.38 276.967C1077.09 301.285 1070.09 326.399 1062.33 351.439L1029.53 456.452L954.642 696.058C951.264 707.179 948.34 719.251 944.927 730.683C928.522 787.296 910.757 843.248 891.657 898.458ZM886.459 281.987L477.786 386.278L294.33 433.42L216.001 453.044C206.415 455.423 159.615 463.744 152.651 471.989C148.31 477.128 162.712 532.976 167.674 538.524C170.833 540.311 173.132 539.627 176.565 538.809C207.705 531.807 236.637 523.379 267.329 515.77L531.491 449.743L780.205 388.284L861.022 367.334C873.888 364.031 886.926 361.131 899.663 357.662C904.426 356.364 914.745 353.81 911.899 345.169C907.415 331.559 900.824 289.704 891.872 282.224C889.132 281.574 889.153 281.388 886.459 281.987ZM1380.74 251.953C1376.42 259.678 1376.51 297.937 1381.34 304.616C1389.67 309.424 1410.9 315.004 1420.74 318.27C1438.34 324.338 1456 330.124 1473.72 335.626C1484.93 339.131 1501.85 347.63 1511.74 338.767C1512.96 334.893 1518.92 288.987 1518.77 283.995C1513.34 276.217 1462.47 267.973 1451.66 265.555C1436.79 262.126 1421.9 258.818 1406.99 255.633C1399.27 254.004 1388.16 250.849 1380.74 251.953ZM813.884 786.068C790.211 791.714 757.08 802.371 732.811 802.979C726.882 803.127 719.178 764.686 720.803 757.607C724.795 750.786 756.1 745.063 763.453 743.101C783.121 737.853 803.015 732.229 822.747 727.457C827.992 725.957 846.394 719.428 850.547 723.122C857.904 729.665 867.744 759.423 862.845 769.888C853.593 778.435 828.597 779.792 813.884 786.068ZM1598.83 949.468C1604.85 949.644 1610.85 950.074 1617.05 949.93C1631.32 949.599 1639.2 952.815 1639.27 930.357C1639.35 904.618 1644.12 832.498 1618.05 823.545C1616.29 824.714 1613.19 827.011 1612.57 829.38C1608.21 845.969 1575.64 935.958 1577.94 946.545C1582.52 951.424 1592.76 949.877 1598.83 949.468ZM552.4 49.3121C547.965 54.9659 548.916 60.744 548.911 69.2211L549.149 205.446C549.16 221.903 548.418 297.418 550.835 306.8C569.241 318.2 870.943 222.168 919.099 223.833C944.826 224.723 945.843 285.059 955.24 306.417C963.367 324.889 976.713 402.555 985.386 413.137L986.992 413.237C993.673 400.94 997.045 380.269 1001.67 366.344C1017.07 319.922 1030.05 268.178 1047.78 223.73C1058.56 196.7 1118.16 223.656 1135.77 229.368C1168.37 239.763 1202.04 249.592 1234.7 259.698C1247.67 263.713 1312.68 287.773 1320.33 283.71C1321.93 281.416 1322.37 279.988 1322.42 276.764C1323.48 204.9 1322.98 132.847 1322.52 60.9659C1322.5 57.9433 1322.34 54.513 1321.22 51.8722C1317.47 48.2156 1311.7 48.6575 1306.52 48.6788C1247.53 48.9216 1188.47 48.7999 1129.48 48.8874L825.979 48.7923L646.008 48.8792L586.315 48.8625C575.943 48.8638 562.563 48.403 552.4 49.3121ZM488.719 166.777C433.977 177.696 379.147 187.883 324.239 197.336C300.5 201.55 276.507 205.333 252.762 209.6C249.385 210.207 247.546 210.971 244.991 213.69C242.622 218.383 243.687 223.993 244.395 229.273C250.323 273.471 261.137 318.163 266.338 362.444C267.32 369.381 267.336 374.683 271.931 378.797C280.755 381.869 325.775 367.711 337.474 364.912L437.526 340.711C446.048 338.607 492.666 330.889 494.27 320.182C495.294 313.348 494.534 285.331 494.46 276.727C494.235 250.443 494.14 224.158 494.176 197.874C494.205 188.971 497.038 177.109 493.76 169.469C491.532 167.017 491.668 167.231 488.719 166.777Z"/><path fill="#FCFDFA" fill-opacity="0.0078431377" transform="scale(0.657895 0.513699)" d="M180.588 770.495L452.006 770.475L531.435 770.336C552.276 770.287 573.505 769.67 594.339 771.055C621.492 772.861 632.93 805.145 646.484 831.711L687.676 912.926C711.134 958.746 727.391 997.106 775.465 1002.68C800.12 1005.53 834.05 1003.55 859.472 1003.33L1009.08 1003.23L1518.54 1003.37L1634.95 1003C1668.74 1002.71 1711.71 998.931 1744.22 1009.85C1760.92 1015.47 1778.66 1047.5 1775.35 1070.7C1769.4 1112.43 1759.32 1153.95 1751.4 1195.24L1697.39 1475.31L1629.04 1821.75C1627.02 1832.44 1625.82 1846.02 1624 1857.13C1621.74 1870.92 1618.38 1883.44 1615.81 1896.93C1610.99 1922.29 1608.89 1943.51 1601.26 1968.14C1599.16 1979.36 1597.35 1991.59 1590.72 1999.73C1576.1 2017.67 1561.57 2028.09 1541.22 2028.15C1500.13 2028.27 1459.17 2028.05 1418.24 2027.91L1210.57 2027.77L627.415 2027.59L269.985 2028.31L166.582 2028.29C143.103 2028.31 119.313 2028.91 95.8591 2026.51C82.4238 2025.13 70.4693 2013.72 60.8 2002.58C54.8135 1995.68 49.6601 1972.72 49.3763 1962.31C48.7726 1938.54 48.879 1914.49 49.2629 1890.69C49.9809 1846.19 50.4072 1801.85 50.3878 1757.33C51.6141 1566.67 52.0648 1376 51.7401 1185.33L51.5272 953.062C51.5087 911.507 49.9807 864.631 53.7269 823.666C54.8373 811.525 59.0862 801.531 65.8695 792.829C72.6887 784.171 81.0911 777.835 90.3112 774.399C105.852 768.652 161.103 770.497 180.588 770.495ZM1015.09 1279.74C1014.96 1277.42 1014.76 1275.26 1014.55 1272.95C1009.43 1264.77 1004.74 1270.99 999.625 1268.83C988.479 1264.11 999.987 1248.96 994.535 1238.24C991.781 1236.34 988.185 1237.04 984.917 1237.19L984.307 1235.93C978.797 1224.35 978.265 1209.85 971.617 1203.2C967.341 1202.03 962.31 1201.03 957.93 1201.17C925.323 1202.21 892.78 1201.23 860.184 1200.31C851.723 1200.07 845.696 1212.21 841.73 1220.5L841.795 1222.64C841.857 1224.99 837.794 1270.62 837.444 1271.54C834.15 1274.38 824.677 1276.74 820.252 1278.9C813.521 1281.63 803.384 1292.26 796.097 1289.39C777.9 1282.23 741.783 1242.01 723.156 1258.55C708.232 1271.79 687.39 1296.42 673.739 1308.34C640.74 1337.16 637.181 1336.93 667.975 1369.52C672.082 1373.86 685.052 1391.64 685.945 1399.58C685.349 1403.9 682.859 1406.8 680.7 1410.01C678.134 1413.84 677.408 1417.58 676.31 1422.32C671.3 1443.97 661.53 1445.23 645.498 1447.12C635.285 1448.33 609.382 1443.97 602.506 1454.02C600.077 1457.57 599.482 1461.99 599.192 1466.57C598.284 1480.93 599.685 1495.83 599.7 1510.28C599.721 1530.67 597.849 1552.83 599.922 1572.97C600.398 1577.58 601.843 1581.67 604.883 1584.4C617.492 1595.71 661.569 1582.11 672.759 1599.35C676.046 1604.41 680.024 1624.53 681.391 1631.81C681.931 1634.68 682.441 1637.08 681.174 1639.72C678.313 1645.69 672.321 1650.53 668.448 1655.56C663.824 1661.55 646.559 1687.8 648.801 1695.63C651.039 1703.44 710.443 1761.6 720.163 1769.57C723.449 1772.26 727.028 1774.55 730.772 1775.99C738.817 1779.07 747.333 1778.06 754.632 1772.67C767.396 1763.23 781.437 1742.78 797.802 1747.63C802.56 1749.04 806.216 1754.45 810.706 1756.76C820.923 1762.03 829.676 1750.16 839.427 1773.16C846.591 1790.05 836.587 1820.49 853.763 1827.52C860.913 1830.45 950.345 1828.81 961.208 1827.91C964.899 1827.6 970.932 1827.12 974.012 1824.61C978.729 1820.77 980.905 1808.6 981.128 1801.94C981.535 1789.82 980.454 1778.18 987.857 1769C994.284 1761.02 1021.92 1746.68 1030.86 1747.08C1041.07 1747.54 1050.69 1755.78 1059.37 1762.02C1069.2 1769.09 1081.72 1782.21 1093.33 1780.98C1094.52 1780.86 1095.44 1780.78 1096.48 1779.92C1104.14 1773.59 1110.65 1764.31 1117.95 1757.22C1124.71 1750.67 1131.98 1744.94 1138.63 1738.23C1144.66 1732.15 1150.19 1725.25 1156.31 1719.35C1162.62 1713.26 1169.59 1707.89 1175.64 1701.43C1177.14 1699.82 1178.25 1697.74 1178.48 1695.19C1178.97 1689.74 1175.49 1685.48 1172.76 1682.03C1165.36 1672.71 1143.53 1648.34 1143.46 1635.31C1143.45 1633.39 1143.8 1631.61 1144.27 1629.79C1145.27 1625.94 1146.9 1622.41 1147.84 1618.54C1149.11 1613.35 1148.64 1607.46 1150.4 1602.39C1151.08 1600.44 1151.87 1599.1 1153.1 1597.66C1171.67 1575.98 1222.71 1608.31 1225.35 1561.22C1225.99 1549.77 1224.48 1538.09 1224.48 1526.6C1224.48 1507.19 1226.16 1487.13 1225.03 1467.82C1224.78 1463.47 1224.44 1457.56 1222.26 1454C1218.61 1448.01 1210.8 1447.73 1205.45 1447.69C1192.91 1447.59 1162.92 1450.94 1154.05 1439.13C1151.38 1435.58 1141.48 1403.95 1141.84 1399.7C1143.69 1377.83 1183.89 1354.33 1171.79 1333.23C1165.54 1322.33 1153.37 1315.89 1145.04 1307.74C1129.65 1292.7 1114.07 1272.61 1098.85 1257.73C1096.49 1255.43 1093.99 1253.97 1091.03 1253.65C1072.05 1251.6 1043.52 1288.39 1030.7 1287.94C1025.18 1287.74 1019.79 1283.08 1015.09 1279.74Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M841.73 1220.5C845.696 1212.21 851.723 1200.07 860.184 1200.31C892.78 1201.23 925.323 1202.21 957.93 1201.17C962.31 1201.03 967.341 1202.03 971.617 1203.2C978.265 1209.85 978.797 1224.35 984.307 1235.93L984.917 1237.19C986.46 1250.33 978.9 1263.15 987.038 1271.64C994.448 1279.37 1006.66 1276.96 1015.09 1279.74C1019.79 1283.08 1025.18 1287.74 1030.7 1287.94C1043.52 1288.39 1072.05 1251.6 1091.03 1253.65C1093.99 1253.97 1096.49 1255.43 1098.85 1257.73C1114.07 1272.61 1129.65 1292.7 1145.04 1307.74C1153.37 1315.89 1165.54 1322.33 1171.79 1333.23C1183.89 1354.33 1143.69 1377.83 1141.84 1399.7C1141.48 1403.95 1151.38 1435.58 1154.05 1439.13C1162.92 1450.94 1192.91 1447.59 1205.45 1447.69C1210.8 1447.73 1218.61 1448.01 1222.26 1454C1224.44 1457.56 1224.78 1463.47 1225.03 1467.82C1226.16 1487.13 1224.48 1507.19 1224.48 1526.6C1224.48 1538.09 1225.99 1549.77 1225.35 1561.22C1222.71 1608.31 1171.67 1575.98 1153.1 1597.66C1151.87 1599.1 1151.08 1600.44 1150.4 1602.39C1148.64 1607.46 1149.11 1613.35 1147.84 1618.54C1146.9 1622.41 1145.27 1625.94 1144.27 1629.79C1143.8 1631.61 1143.45 1633.39 1143.46 1635.31C1143.53 1648.34 1165.36 1672.71 1172.76 1682.03C1175.49 1685.48 1178.97 1689.74 1178.48 1695.19C1178.25 1697.74 1177.14 1699.82 1175.64 1701.43C1169.59 1707.89 1162.62 1713.26 1156.31 1719.35C1150.19 1725.25 1144.66 1732.15 1138.63 1738.23C1131.98 1744.94 1124.71 1750.67 1117.95 1757.22C1110.65 1764.31 1104.14 1773.59 1096.48 1779.92C1095.44 1780.78 1094.52 1780.86 1093.33 1780.98C1081.72 1782.21 1069.2 1769.09 1059.37 1762.02C1050.69 1755.78 1041.07 1747.54 1030.86 1747.08C1021.92 1746.68 994.284 1761.02 987.857 1769C980.454 1778.18 981.535 1789.82 981.128 1801.94C980.905 1808.6 978.729 1820.77 974.012 1824.61C970.932 1827.12 964.899 1827.6 961.208 1827.91C950.345 1828.81 860.913 1830.45 853.763 1827.52C836.587 1820.49 846.591 1790.05 839.427 1773.16C829.676 1750.16 820.923 1762.03 810.706 1756.76C806.216 1754.45 802.56 1749.04 797.802 1747.63C781.437 1742.78 767.396 1763.23 754.632 1772.67C747.333 1778.06 738.817 1779.07 730.772 1775.99C727.028 1774.55 723.449 1772.26 720.163 1769.57C710.443 1761.6 651.039 1703.44 648.801 1695.63C646.559 1687.8 663.824 1661.55 668.448 1655.56C672.321 1650.53 678.313 1645.69 681.174 1639.72C682.441 1637.08 681.931 1634.68 681.391 1631.81C680.024 1624.53 676.046 1604.41 672.759 1599.35C661.569 1582.11 617.492 1595.71 604.883 1584.4C601.843 1581.67 600.398 1577.58 599.922 1572.97C597.849 1552.83 599.721 1530.67 599.7 1510.28C599.685 1495.83 598.284 1480.93 599.192 1466.57C599.482 1461.99 600.077 1457.57 602.506 1454.02C609.382 1443.97 635.285 1448.33 645.498 1447.12C661.53 1445.23 671.3 1443.97 676.31 1422.32C677.408 1417.58 678.134 1413.84 680.7 1410.01C682.859 1406.8 685.349 1403.9 685.945 1399.58C685.052 1391.64 672.082 1373.86 667.975 1369.52C637.181 1336.93 640.74 1337.16 673.739 1308.34C687.39 1296.42 708.232 1271.79 723.156 1258.55C741.783 1242.01 777.9 1282.23 796.097 1289.39C803.384 1292.26 813.521 1281.63 820.252 1278.9C824.677 1276.74 834.15 1274.38 837.444 1271.54C837.794 1270.62 841.857 1224.99 841.795 1222.64L841.73 1220.5ZM692.452 1500.13L691.211 1500.5C680.439 1503.59 659.421 1496.76 664.236 1518.3C665.584 1524.33 674.434 1529.2 678.572 1530.84C704.394 1539.42 699.857 1523.53 720.062 1549.66C733.32 1565.59 725.247 1571.71 731.469 1588.48C736.575 1602.24 758.147 1630.05 758.352 1643.59C758.478 1651.93 749.936 1663.43 745.292 1668.84C740.996 1673.85 730.897 1682.15 730.425 1689.74C730.235 1692.8 731.146 1694.46 732.807 1696.47C735.252 1699.44 739.445 1700.45 742.671 1699.89C755.872 1697.57 763.717 1678.45 777.307 1675.53C785.486 1673.78 799.677 1678.3 807.865 1681.11C814.592 1683.41 819.026 1690.75 825.461 1693.32C841.087 1699.57 879.477 1708.98 890.926 1719.65C891.282 1719.98 891.632 1720.32 891.985 1720.66C907.304 1741.07 890.102 1770.23 907.188 1774.06C943.628 1782.24 915.666 1733.15 932.512 1715.03C942.211 1711.17 950.588 1711.53 959.955 1708.26C964.253 1706.86 974.315 1697.24 977.975 1697.09C997.545 1696.27 1005.58 1691.86 1021.55 1678.06C1033.67 1667.6 1054.66 1675.89 1065.1 1687.07C1069.2 1691.46 1076.31 1697.17 1081.4 1699.34C1086.89 1702.25 1096.66 1696.97 1096.66 1690.1C1096.68 1674.39 1075.47 1662.85 1069.52 1649.55C1066.4 1642.57 1066.22 1640.14 1067.15 1632.21C1068.17 1623.46 1075.66 1619.99 1080.51 1615.51C1089.91 1606.83 1084.39 1604.64 1086.67 1594.57C1088.38 1591.09 1094.32 1586.2 1095.57 1582.66C1105.32 1555.24 1089 1540.9 1122.03 1536.17C1132.22 1534.72 1162.46 1540.9 1164.39 1521.61C1167.16 1493.98 1144.27 1502.03 1131.09 1498.51C1116.13 1495.23 1108.9 1492.24 1099.78 1476.77L1099.06 1475.53C1098.89 1448.89 1099.55 1454.92 1086.64 1432.9C1081.01 1423.31 1075.02 1406.09 1068.18 1396.02C1065.97 1392.75 1067.64 1385.37 1068.47 1381.56C1075.08 1367.44 1096.71 1357.68 1096.53 1348.59C1095.89 1317.74 1060.29 1348.02 1055.54 1352.23C1049.82 1356.07 1043.45 1358.07 1036.98 1358.05C1017.87 1358.09 1015.32 1347.78 1000.93 1342.49C986.603 1337.22 982.34 1337.38 968.981 1326.74C963.908 1322.7 936.38 1328.2 929.989 1317.52C921.273 1308.8 931.01 1273.93 923.426 1268.1C913.145 1260.2 895.263 1263.57 898.768 1285.06C899.799 1291.38 897.775 1316 895.206 1320.25C883.709 1329.3 855.793 1329.87 841.939 1333.26C820.686 1338.48 787.002 1373.07 767.821 1349.8C759.395 1341.93 740.146 1330.2 731.311 1341.91C726.575 1358.29 760.123 1377.1 755.191 1397.57C747.062 1405.97 746.96 1411.04 742.497 1422.86C740.649 1427.75 731.822 1433.68 730.676 1438.91C721.068 1482.76 732.722 1490.31 692.452 1500.13Z"/><path fill="#151716" transform="scale(0.657895 0.513699)" d="M904.203 1393.14C938.234 1390.94 970.378 1401.06 998.167 1426.75C1004.95 1433.02 1019.83 1449.99 1024.04 1458.98C1037.94 1485.73 1038.61 1485.85 1040.02 1515.74C1042.75 1573.42 1000.8 1616.29 962.165 1634.33C950.321 1639.87 936.967 1641.83 922.994 1643.92C895.95 1647.06 854.949 1636.41 833.108 1615.12C816.075 1598.52 789.985 1570.98 787.031 1541.78C783.854 1510.39 785.34 1482.52 802.107 1457.76C819.638 1430.85 841.872 1412.59 867.479 1400.36C875.294 1396.67 895.314 1394.62 904.203 1393.14ZM921.607 1583.91C935.442 1580.79 960.041 1568.14 968.667 1552.18C976.907 1536.94 975.131 1513.54 973.403 1495.85C972.339 1484.95 962.235 1475.21 954.929 1469.9C936.518 1456.54 924.293 1449.64 902.846 1452.55C887.903 1456.79 863.983 1470.85 855.156 1487.49C849.404 1498.33 849.568 1525.76 852.291 1538.31C859.123 1569.8 898.915 1586.37 921.607 1583.91Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M886.485 1406.92C903.999 1405.71 928.304 1406.4 945.687 1408.68C945.205 1408.61 972.6 1427.59 978.007 1425.71C979.045 1425.36 996.369 1441.35 996.89 1443.57C997.977 1455.2 1016 1462.84 1016.16 1470.26C1016.42 1482.2 1019 1505.57 1020.17 1516.45C1021.46 1528.49 1017.63 1562.62 1013.97 1572.71C1009.01 1575.42 1007.47 1575.9 1002.23 1577.45C1001.84 1579.18 999.866 1587.86 999.167 1589.13C993.57 1599.26 980.675 1609.14 971.531 1612.79C964.457 1615.62 956.5 1617.06 950.613 1622.13C946.842 1625.37 944.629 1626.43 940.685 1628.62C922.655 1629.94 900.412 1629.59 882.299 1627.23C880.905 1627.05 874.915 1623.09 873.33 1621.79C866.105 1615.86 857.25 1616.44 849.556 1611.96C841.12 1605.1 838.963 1599.53 828.698 1592.44L827.13 1591.37C822.065 1571.64 812.359 1577.49 810.286 1567.17C804.234 1537.04 805.998 1499.68 810.072 1469.08C810.976 1462.28 824.747 1460.04 825.372 1451.3C825.524 1449.17 829.434 1441.11 830.321 1439.28C844.956 1432.83 841.818 1421.9 866.313 1420.57C872.658 1413.53 878.154 1409.22 886.485 1406.92ZM921.607 1583.91C935.442 1580.79 960.041 1568.14 968.667 1552.18C976.907 1536.94 975.131 1513.54 973.403 1495.85C972.339 1484.95 962.235 1475.21 954.929 1469.9C936.518 1456.54 924.293 1449.64 902.846 1452.55C887.903 1456.79 863.983 1470.85 855.156 1487.49C849.404 1498.33 849.568 1525.76 852.291 1538.31C859.123 1569.8 898.915 1586.37 921.607 1583.91Z"/><path fill="#FCFDFA" fill-opacity="0.0078431377" transform="scale(0.657895 0.513699)" d="M918.106 1714.94L932.512 1715.03C915.666 1733.15 943.628 1782.24 907.188 1774.06C890.102 1770.23 907.304 1741.07 891.985 1720.66L904.077 1720.62C910.271 1736.62 905.215 1758.79 911.539 1765.18C914.137 1765.85 914.507 1766.39 916.86 1765.17C918.432 1760.7 918.062 1721.96 918.106 1714.94Z"/><path fill="#FCFDFA" fill-opacity="0.011764706" transform="scale(0.657895 0.513699)" d="M720.062 1549.66C699.857 1523.53 704.394 1539.42 678.572 1530.84C674.434 1529.2 665.584 1524.33 664.236 1518.3C659.421 1496.76 680.439 1503.59 691.211 1500.5L692.452 1500.13C692.329 1506.27 693.097 1505.58 690.811 1509.76C688.609 1510.9 687.127 1511.64 685.015 1513.14C684.334 1516.91 684.195 1515.14 685.426 1518.65C696.578 1526.93 699.254 1508.6 720.061 1534.55L720.062 1549.66Z"/><path fill="#FCFDFA" fill-opacity="0.019607844" transform="scale(0.657895 0.513699)" d="M755.191 1397.57C760.123 1377.1 726.575 1358.29 731.311 1341.91C740.146 1330.2 759.395 1341.93 767.821 1349.8C764.723 1349.84 752.255 1348.91 751.004 1349.38C746.64 1362.93 769.48 1380.52 765.701 1394.77C762.583 1399.03 759.413 1398 755.191 1397.57Z"/><path fill="#FCFDFA" fill-opacity="0.015686275" transform="scale(0.657895 0.513699)" d="M1055.54 1352.23C1060.29 1348.02 1095.89 1317.74 1096.53 1348.59C1096.71 1357.68 1075.08 1367.44 1068.47 1381.56C1068.4 1379.17 1068.01 1366.71 1068.46 1365.97C1071.57 1360.91 1080.53 1354.77 1083.57 1348.7L1082.9 1347.48C1077.17 1347.26 1072.26 1350.16 1066.86 1351.87C1064.64 1352.58 1058.11 1352.31 1055.54 1352.23Z"/><path fill="#FCFDFA" fill-opacity="0.011764706" transform="scale(0.657895 0.513699)" d="M984.917 1237.19C988.185 1237.04 991.781 1236.34 994.535 1238.24C999.987 1248.96 988.479 1264.11 999.625 1268.83C1004.74 1270.99 1009.43 1264.77 1014.55 1272.95C1014.76 1275.26 1014.96 1277.42 1015.09 1279.74C1006.66 1276.96 994.448 1279.37 987.038 1271.64C978.9 1263.15 986.46 1250.33 984.917 1237.19Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M1253.16 623.019C1253.98 622.874 1254.81 622.746 1255.63 622.638C1265.86 621.352 1286.63 630.484 1297.57 634.248L1361.54 655.76C1389.37 664.767 1419.99 674.252 1447.56 683.789C1460.91 688.405 1522.95 704.254 1531 712.936C1533.22 722.276 1523.31 750.065 1517.71 755.623C1499.37 757.886 1418.97 728.504 1397.82 721.73L1322.57 697.809C1308.91 693.632 1254.42 679.339 1240.26 668.788C1234.91 664.808 1245.83 629.779 1253.16 623.019Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M1221.11 729.936C1234.55 728.556 1268.15 743.281 1282.53 747.966L1429.07 794.548C1436.02 796.835 1490.76 812.366 1495.6 818.986C1499.52 824.341 1491.9 858.215 1481.8 863.894C1472.8 863.247 1462.13 859.468 1453.14 856.922C1432.77 851.152 1412.5 843.858 1392.23 837.485L1266.18 796.838C1255.44 793.269 1216.68 783.144 1206.53 774.119C1203.46 771.388 1213.94 741.006 1215.51 736.732C1216 735.37 1219.53 731.57 1221.11 729.936Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M1364.65 542.289C1374.59 541.428 1384.52 546.956 1394.29 549.998L1528.72 593.217C1534.82 595.243 1562.3 602.958 1566.14 606.213C1567.85 613.25 1560.57 631.102 1558.69 638.974C1557.03 645.946 1555.11 647.914 1550.21 650.722C1540.01 651.968 1516.73 643.495 1505.73 640.217C1483.05 633.475 1460.4 626.538 1437.79 619.406C1419.4 613.671 1401.05 607.717 1382.74 601.546C1373.12 598.332 1362.77 595.304 1353.53 591.074C1343.67 585.427 1350.36 572.639 1353.09 564.681C1356.84 553.735 1354.94 546.983 1364.65 542.289Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M1183.57 445.429C1183.75 445.031 1183.93 444.63 1184.11 444.235C1188.44 435.003 1228.06 367.737 1234.41 365.7C1241.41 363.454 1260.58 376.673 1266.56 382.216C1268.69 384.195 1270.05 386.003 1271.36 388.916C1271.45 399.953 1213.69 493.902 1203.51 508.012C1201.92 510.204 1199.05 513.303 1196.51 512.637C1187.18 510.196 1165.9 498.188 1160.14 489.144L1159.2 487.718C1163.5 472.59 1175.78 461.172 1183.57 445.429Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M1025.66 795.317C1034.77 796.917 1047.35 818.494 1048.47 829.417C1049.93 843.786 1023.91 847.084 1019.15 855.325C1012.52 866.819 1030.87 881.325 1031.66 895.722C1028.3 906.79 1000.15 918.411 990.576 916.958C990.344 916.768 990.106 916.59 989.88 916.388C981.584 908.972 953.875 856.967 952.918 844.034C952.687 840.908 953.478 838.701 955.045 836.357C962.126 825.764 1014.73 796.387 1025.66 795.317Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M1145.19 353.769C1149.67 352.928 1153.57 352.451 1157.26 356.114C1161.56 360.38 1172.17 378.38 1172.31 384.875C1172.7 403.012 1149.33 399.456 1140.86 412.802C1139.08 427.348 1172.48 448.766 1139.63 464.236C1133.37 467.179 1128.37 470.241 1121.42 472.166C1106.09 471.778 1088.63 425.298 1081.04 409.445C1079.54 406.32 1077.53 394.99 1079.59 392.14C1092.76 373.92 1126.98 360.538 1145.19 353.769Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M1312.63 407.476C1329.07 408.886 1342.61 448.055 1351.14 463.356C1352.96 466.629 1356.68 478.218 1354.72 481.467C1341.73 503.001 1307.21 515.347 1288.07 524.3C1274.41 530.527 1275.42 517.262 1268.92 507.627C1246.35 474.124 1283.75 481.992 1292.95 463.587C1297.8 453.882 1274.96 437.404 1281.15 426.277C1286.71 417.104 1304.18 410.738 1312.63 407.476Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M1137.8 585.429C1146.5 585.192 1195.39 601.361 1201.42 607.771C1204.53 617.815 1192.83 646.743 1186.65 651.816C1168.31 647.594 1149.96 643.094 1132.1 636.014C1127.26 634.1 1123.28 631.722 1121.46 625.5C1121.99 617.838 1124.8 613.431 1126.49 606.604C1129.56 594.236 1126.59 589.365 1137.8 585.429Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M1104.71 692.572C1112.15 692.873 1164.34 709.063 1169.05 715.071C1169.92 722.815 1158.44 754.684 1153.61 760.11C1143.77 760.72 1095.49 745.315 1088.9 736.286C1088.44 734.323 1088.01 730.769 1088.87 729.032C1094.41 717.929 1095.47 698.931 1104.71 692.572Z"/><path fill="#FCFDFA" fill-opacity="0.011764706" transform="scale(0.657895 0.513699)" d="M1158.27 467.828C1167.08 456.205 1167.52 444.72 1183.57 445.429C1175.78 461.172 1163.5 472.59 1159.2 487.718C1157.59 485.609 1158.24 471.507 1158.27 467.828Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M696.549 522.808C715.602 519.486 711.546 532.22 716.583 548.941C723.564 568.098 719.877 572.93 703.906 577.441C658.216 590.347 611.458 599.323 565.611 611.277L405.228 651.115C368.479 660.14 334.944 670.641 297.246 678.755C277.94 683.408 279.004 674.865 274.377 653.7C273.107 647.892 270.799 637.799 272.848 632.303C282.444 624.531 336.034 613.671 351.333 609.708L563.989 556.736C607.855 545.915 652.841 533.176 696.549 522.808Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M882.801 593.617C902.301 590.455 899.427 608.719 906.006 626.467C910.593 638.839 899.706 644.098 892.799 646.433C873.517 652.95 852.911 657.554 833.447 662.46L722.447 691.004C701.769 696.054 669.943 702.03 650.099 709.067L648.624 709.599C647.498 709.693 646.37 709.74 645.241 709.741C633.588 709.615 632.921 699.896 630.269 687.951C628.61 680.478 625.171 669.415 626.247 661.883C634.02 654.225 850.732 604.115 882.801 593.617Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M855.301 483.966C870.84 479.593 873.339 492.484 877.045 509.056C878.484 515.488 879.827 524.902 876.768 530.733C864.949 539.519 798.939 553.475 782.592 556.887C769.424 558.555 769.847 555.693 765.388 541.794C761.671 530.205 751.5 509.433 767.737 505.133C796.72 497.458 825.999 489.196 855.301 483.966Z"/><path fill="#FCFDFA" fill-opacity="0.0078431377" transform="scale(0.657895 0.513699)" d="M552.4 49.3121C562.563 48.403 575.943 48.8638 586.315 48.8625L646.008 48.8792L825.979 48.7923L1129.48 48.8874C1188.47 48.7999 1247.53 48.9216 1306.52 48.6788C1311.7 48.6575 1317.47 48.2156 1321.22 51.8722C1322.34 54.513 1322.5 57.9433 1322.52 60.9659C1322.98 132.847 1323.48 204.9 1322.42 276.764C1322.37 279.988 1321.93 281.416 1320.33 283.71C1312.68 287.773 1247.67 263.713 1234.7 259.698C1202.04 249.592 1168.37 239.763 1135.77 229.368C1118.16 223.656 1058.56 196.7 1047.78 223.73C1030.05 268.178 1017.07 319.922 1001.67 366.344C997.045 380.269 993.673 400.94 986.992 413.237L985.386 413.137C976.713 402.555 963.367 324.889 955.24 306.417C945.843 285.059 944.826 224.723 919.099 223.833C870.943 222.168 569.241 318.2 550.835 306.8C548.418 297.418 549.16 221.903 549.149 205.446L548.911 69.2211C548.916 60.744 547.965 54.9659 552.4 49.3121Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M849.362 105.199C851.236 104.958 853.495 104.667 855.421 104.695C884.961 105.138 914.519 105.313 944.058 105.711C948.252 105.768 958.273 105.657 961.126 109.152C964.964 119.624 963.991 139.308 962.777 151.094C962.356 155.185 958.75 157.408 955.999 159.093C928.139 160.784 899.339 158.688 871.396 159.755C863.875 160.042 851.571 160.34 845.358 154.866C841.321 145.501 841.837 124.598 842.641 113.635C842.942 109.516 846.649 107.043 849.362 105.199Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M729.987 105.411C745.569 102.735 766.783 105.63 782.845 105.036C793.558 104.64 795.792 115.444 795.241 126.994C794.529 141.922 799.184 149.988 787.887 159.213C772.696 161.291 755.556 159.981 740.259 160.186C724.459 160.398 722.847 149.479 723.511 132.348C723.986 120.109 720.739 113.025 729.987 105.411Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M614.74 105.529C632.84 104.874 652.527 103.962 670.434 106.225C678.086 107.192 675.942 128.073 676.322 135.133C676.936 146.523 677.689 154.77 668.463 159.602C650.439 160.011 629.37 160.908 611.869 157.12C605.128 155.661 606.289 133.826 606.369 127.007C606.496 116.259 605.046 108.305 614.74 105.529Z"/><path fill="#FCFDFA" fill-opacity="0.0078431377" transform="scale(0.657895 0.513699)" d="M886.459 281.987C889.153 281.388 889.132 281.574 891.872 282.224C900.824 289.704 907.415 331.559 911.899 345.169C914.745 353.81 904.426 356.364 899.663 357.662C886.926 361.131 873.888 364.031 861.022 367.334L780.205 388.284L531.491 449.743L267.329 515.77C236.637 523.379 207.705 531.807 176.565 538.809C173.132 539.627 170.833 540.311 167.674 538.524C162.712 532.976 148.31 477.128 152.651 471.989C159.615 463.744 206.415 455.423 216.001 453.044L294.33 433.42L477.786 386.278L886.459 281.987Z"/><path fill="#FCFDFA" fill-opacity="0.0078431377" transform="scale(0.657895 0.513699)" d="M488.719 166.777C491.668 167.231 491.532 167.017 493.76 169.469C497.038 177.109 494.205 188.971 494.176 197.874C494.14 224.158 494.235 250.443 494.46 276.727C494.534 285.331 495.294 313.348 494.27 320.182C492.666 330.889 446.048 338.607 437.526 340.711L337.474 364.912C325.775 367.711 280.755 381.869 271.931 378.797C267.336 374.683 267.32 369.381 266.338 362.444C261.137 318.163 250.323 273.471 244.395 229.273C243.687 223.993 242.622 218.383 244.991 213.69C247.546 210.971 249.385 210.207 252.762 209.6C276.507 205.333 300.5 201.55 324.239 197.336C379.147 187.883 433.977 177.696 488.719 166.777Z"/><path fill="#FCFDFA" fill-opacity="0.0078431377" transform="scale(0.657895 0.513699)" d="M1380.74 251.953C1388.16 250.849 1399.27 254.004 1406.99 255.633C1421.9 258.818 1436.79 262.126 1451.66 265.555C1462.47 267.973 1513.34 276.217 1518.77 283.995C1518.92 288.987 1512.96 334.893 1511.74 338.767C1501.85 347.63 1484.93 339.131 1473.72 335.626C1456 330.124 1438.34 324.338 1420.74 318.27C1410.9 315.004 1389.67 309.424 1381.34 304.616C1376.51 297.937 1376.42 259.678 1380.74 251.953Z"/><path fill="#000101" transform="scale(0.657895 0.513699)" d="M822.747 727.457C827.992 725.957 846.394 719.428 850.547 723.122C857.904 729.665 867.744 759.423 862.845 769.888C853.593 778.435 828.597 779.792 813.884 786.068C790.211 791.714 757.08 802.371 732.811 802.979C726.882 803.127 719.178 764.686 720.803 757.607C724.795 750.786 756.1 745.063 763.453 743.101C783.121 737.853 803.015 732.229 822.747 727.457Z"/><path fill="#FCFDFA" fill-opacity="0.0078431377" transform="scale(0.657895 0.513699)" d="M1618.05 823.545C1644.12 832.498 1639.35 904.618 1639.27 930.357C1639.2 952.815 1631.32 949.599 1617.05 949.93C1610.85 950.074 1604.85 949.644 1598.83 949.468C1592.76 949.877 1582.52 951.424 1577.94 946.545C1575.64 935.958 1608.21 845.969 1612.57 829.38C1613.19 827.011 1616.29 824.714 1618.05 823.545Z"/><path fill="#FCFDFA" fill-opacity="0.011764706" transform="scale(0.657895 0.513699)" d="M822.747 727.457C825.334 715.214 842.081 713.357 849.964 713.295C864.938 713.177 864.263 743.906 871.671 747.907C876.225 744.058 879.731 720.223 891.543 718.868C881.87 752.501 869.155 789.687 858.409 823.874C857.638 812.462 859.708 797.797 855.964 787.804C854.709 786.499 853.544 784.919 851.786 785.101C838.923 786.437 826.836 786.811 813.884 786.068C828.597 779.792 853.593 778.435 862.845 769.888C867.744 759.423 857.904 729.665 850.547 723.122C846.394 719.428 827.992 725.957 822.747 727.457Z"/><path fill="#FCFDFA" fill-opacity="0.011764706" transform="scale(0.657895 0.513699)" d="M1036.37 929.974C1038.34 936.161 1044.02 941.477 1043.19 947.574C1027.42 953.51 913.562 948.046 892.068 948.883C889.34 948.99 882.193 947.439 879.38 946.369C878.531 942.35 889.79 903.052 891.657 898.458C891.99 909.446 894.019 929.812 889.417 937.984L889.693 939.754C898.533 942.765 917.804 941.75 927.579 941.979C963.797 942.989 1000.03 943.242 1036.25 942.738L1036.37 929.974Z"/><path fill="#FCFDFA" fill-opacity="0.0078431377" transform="scale(0.657895 0.513699)" d="M725.114 2087.2C746.255 2085.09 783.811 2086.97 806.112 2086.92L964.508 2086.38L1432.92 2086.33L1492 2085.85C1535.19 2085.63 1576.48 2088.08 1613.21 2052.11C1653.99 2012.17 1653.16 1948.08 1666.61 1890.46C1672.99 1863.13 1676.11 1835.13 1681.34 1807.46L1763.34 1392.13L1806.44 1170.89C1810.43 1150.95 1813.76 1131.32 1816.75 1111.13C1817.32 1107.3 1820.91 1102.91 1823.07 1100.16L1824 1098.99L1824 2336L0 2336L0 1998.96C2.57937 2001.92 12.4683 2025.24 14.263 2030.06C15.1264 2043.92 30.6926 2068.33 38.9784 2077.09C82.3948 2122.95 136.576 2114.4 188.813 2115.38C239.847 2116.78 290.895 2117.11 341.937 2116.37C397.829 2115.69 454.006 2111.75 509.894 2114.03C512.666 2114.14 541.821 2112.94 542.394 2112.69C561.111 2104.64 718.481 2093.78 725.114 2087.2Z"/><path fill="#FCFDFA" fill-opacity="0.027450981" transform="scale(0.657895 0.513699)" d="M14.263 2030.06L14.9919 2030.68C22.0048 2036.76 28.4268 2044.03 35.3736 2050.28C74.9808 2085.95 121.545 2082.25 167.427 2082.23L251.505 2082.19C371.175 2082.16 490.842 2083.71 610.487 2086.83C636.829 2087.48 663.853 2086.27 690.246 2086.85C700.34 2087.07 715.475 2085.97 725.114 2087.2C718.481 2093.78 561.111 2104.64 542.394 2112.69C541.821 2112.94 512.666 2114.14 509.894 2114.03C454.006 2111.75 397.829 2115.69 341.937 2116.37C290.895 2117.11 239.847 2116.78 188.813 2115.38C136.576 2114.4 82.3948 2122.95 38.9784 2077.09C30.6926 2068.33 15.1264 2043.92 14.263 2030.06Z"/></svg>\ No newline at end of file