@zeyue0329/xiaoma-cli 1.6.4 → 1.7.0

package/src/utility/models/agent-config-template.md

@@ -1,23 +0,0 @@
-```xml
-<agent-config name="" title="">
-
-    <llm critical="true">
-        <i>ALWAYS respond in {core:communication_language}.</i>
-    </llm>
-
-    <!-- Standard Agent Persona Configuration -->
-
-    <role></role>
-    <identity></identity>
-    <communication_style></communication_style>
-    <principles></principles>
-    <memories>
-        <memory>The users name is {core:user_name}</memory>
-    </memories>
-
-    <!-- User Added custom Agent Configuration Nodes -->
-
-    <!-- Agent-specific configuration nodes -->
-
-</agent-config>
-```

package/src/utility/models/agent-in-team-activation.xml

@@ -1,3 +0,0 @@
-<activation critical="MANDATORY">
-
-</activation>

package/src/utility/models/fragments/activation-rules.xml

@@ -1,7 +0,0 @@
-<rules>
-  <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
-  <!-- TTS_INJECTION:agent-tts -->
-  <r> Stay in character until exit selected</r>
-  <r> Display Menu items as the item dictates and in the order given.</r>
-  <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
-</rules>

package/src/utility/models/fragments/activation-steps.xml

@@ -1,16 +0,0 @@
-<step n="1">Load persona from this current agent file (already in context)</step>
-<step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-    - Load and read {project-root}/{xiaoma_folder}/{{module}}/config.yaml NOW
-    - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-    - VERIFY: If config not loaded, STOP and report error to user
-    - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
-<step n="3">Remember: user's name is {user_name}</step>
-{AGENT_SPECIFIC_STEPS}
-<step n="{MENU_STEP}">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
-    ALL menu items from menu section</step>
-<step n="{HALT_STEP}">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
-    match</step>
-<step n="{INPUT_STEP}">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
-    to clarify | No match → show "Not recognized"</step>
-<step n="{EXECUTE_STEP}">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
-    (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>

package/src/utility/models/fragments/handler-action.xml

@@ -1,4 +0,0 @@
-    <handler type="action">
-      When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
-      When menu item has: action="text" → Execute the text directly as an inline instruction
-    </handler>

package/src/utility/models/fragments/handler-data.xml

@@ -1,5 +0,0 @@
-    <handler type="data">
-      When menu item has: data="path/to/file.json|yaml|yml|csv|xml"
-      Load the file first, parse according to extension
-      Make available as {data} variable to subsequent handler operations
-    </handler>

package/src/utility/models/fragments/handler-exec.xml

@@ -1,6 +0,0 @@
-<handler type="exec">
-  When menu item or handler has: exec="path/to/file.md":
-  1. Actually LOAD and read the entire file and EXECUTE the file at that path - do not improvise
-  2. Read the complete file and follow all instructions within it
-  3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context.
-</handler>

package/src/utility/models/fragments/handler-multi.xml

@@ -1,14 +0,0 @@
-<handler type="multi">
-  When menu item has: type="multi" with nested handlers
-  1. Display the multi item text as a single menu option
-  2. Parse all nested handlers within the multi item
-  3. For each nested handler:
-     - Use the 'match' attribute for fuzzy matching user input (or Exact Match of character code in brackets [])
-     - Execute based on handler attributes (exec, workflow, action)
-  4. When user input matches a handler's 'match' pattern:
-     - For exec="path/to/file.md": follow the `handler type="exec"` instructions
-     - For workflow="path/to/workflow.yaml": follow the `handler type="workflow"` instructions
-     - For action="...": Perform the specified action directly
-  5. Support both exact matches and fuzzy matching based on the match attribute
-  6. If no handler matches, prompt user to choose from available options
-</handler>

package/src/utility/models/fragments/handler-tmpl.xml

@@ -1,5 +0,0 @@
-    <handler type="tmpl">
-      When menu item has: tmpl="path/to/template.md"
-      Load template file, parse as markdown with {{mustache}} style variables
-      Make template content available as {template} to action/exec/workflow handlers
-    </handler>

package/src/utility/models/fragments/handler-validate-workflow.xml

@@ -1,7 +0,0 @@
-<handler type="validate-workflow">
-  When command has: validate-workflow="path/to/workflow.yaml"
-  1. You MUST LOAD the file at: {project-root}/{xiaoma_folder}/core/tasks/validate-workflow.xml
-  2. READ its entire contents and EXECUTE all instructions in that file
-  3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist
-  4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify
-</handler>

package/src/utility/models/fragments/handler-workflow.xml

@@ -1,9 +0,0 @@
-<handler type="workflow">
-  When menu item has: workflow="path/to/workflow.yaml"
-  1. CRITICAL: Always LOAD {project-root}/{xiaoma_folder}/core/tasks/workflow.xml
-  2. Read the complete file - this is the CORE OS for executing XIAOMA workflows
-  3. Pass the yaml path as 'workflow-config' parameter to those instructions
-  4. Execute workflow.xml instructions precisely following all steps
-  5. Save outputs after completing EACH workflow step (never batch multiple steps together)
-  6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
-</handler>

package/src/utility/models/fragments/menu-handlers.xml

@@ -1,6 +0,0 @@
-<menu-handlers>
-  <extract>{DYNAMIC_EXTRACT_LIST}</extract>
-  <handlers>
-{DYNAMIC_HANDLERS}
-  </handlers>
-</menu-handlers>

package/src/utility/models/fragments/web-bundle-activation-steps.xml

@@ -1,32 +0,0 @@
-<step n="1">Load persona from this current agent XML block containing this activation you are reading now</step>
-{AGENT_SPECIFIC_STEPS}
-<step n="{MENU_STEP}">Show greeting + numbered list of ALL commands IN ORDER from current agent's menu section</step>
-<step n="{HALT_STEP}">CRITICAL HALT. AWAIT user input. NEVER continue without it.</step>
-<step n="{INPUT_STEP}">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
-  to clarify | No match → show "Not recognized"</step>
-<step n="{EXECUTE_STEP}">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
-  (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-<bundled-files critical="MANDATORY">
-  <access-method>
-    All dependencies are bundled within this XML file as &lt;file&gt; elements with CDATA content.
-    When you need to access a file path like "{xiaoma_folder}/core/tasks/workflow.xml":
-    1. Find the &lt;file id="{xiaoma_folder}/core/tasks/workflow.xml"&gt; element in this document
-    2. Extract the content from within the CDATA section
-    3. Use that content as if you read it from the filesystem
-  </access-method>
-  <rules>
-    <rule>NEVER attempt to read files from filesystem - all files are bundled in this XML</rule>
-    <rule>File paths starting with "{xiaoma_folder}/" refer to &lt;file id="..."&gt; elements</rule>
-    <rule>When instructions reference a file path, locate the corresponding &lt;file&gt; element by matching the id attribute</rule>
-    <rule>YAML files are bundled with only their web_bundle section content (flattened to root level)</rule>
-  </rules>
-</bundled-files>
-
-<rules>
-  Stay in character until *exit
-  Number all option lists, use letters for sub-options
-  All file content is bundled in &lt;file&gt; elements - locate by id attribute
-  NEVER attempt filesystem operations - everything is in this XML
-  Menu triggers use asterisk (*) - display exactly as shown
-</rules>

package/src/utility/templates/agent.customize.template.yaml

@@ -1,42 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-# After editing: npx xiaoma-cli build <agent-name>
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

package/src/xmc/_module-installer/install-config.yaml

@@ -1,53 +0,0 @@
-# XIAOMA™ Method Core Configuration
-
-code: xmc
-name: "XMC: XiaoMa Method Agile-AI Driven-Development"
-default_selected: true # This module will be selected by default for new installations
-
-header: "XiaoMa Method™: Breakthrough Method of Agile-Ai Driven-Dev"
-subheader: "Agent and Workflow Configuration for this module"
-
-# Variables from Core Config inserted:
-## user_name
-## communication_language
-## output_folder
-## xiaoma_folder
-## install_user_docs
-## kb_install
-
-project_name:
-  prompt: "What is the title of your project you will be working on?"
-  default: "{directory_name}"
-  result: "{value}"
-
-user_skill_level:
-  prompt:
-    - "What is your technical experience level?"
-    - "This affects how agents explain concepts to you (NOT document content)."
-    - "Documents are always concise for LLM efficiency."
-  default: "intermediate"
-  result: "{value}"
-  single-select:
-    - value: "beginner"
-      label: "Beginner - New to development, explain concepts clearly"
-    - value: "intermediate"
-      label: "Intermediate - Familiar with development, balance explanation with efficiency"
-    - value: "expert"
-      label: "Expert - Deep technical knowledge, be direct and technical"
-
-sprint_artifacts:
-  default: "docs/sprint-artifacts"
-  result: "{project-root}/{value}"
-
-tea_use_mcp_enhancements:
-  prompt: "Enable Test Architect Playwright MCP capabilities (healing, exploratory, verification)? You have to setup your MCPs yourself; refer to test-architecture.md for hints."
-  default: false
-  result: "{value}"
-
-tea_use_playwright_utils:
-  prompt:
-    - "Are you using playwright-utils (@seontechnologies/playwright-utils) in your project?"
-    - "This adds fixture-based utilities for auth, API requests, network recording, polling, intercept, recurse, logging, file download handling, and burn-in."
-    - "You must install packages yourself, or use test architect's *framework command."
-  default: false
-  result: "{value}"

package/src/xmc/_module-installer/installer.js

@@ -1,131 +0,0 @@
-const fs = require('fs-extra');
-const path = require('node:path');
-const chalk = require('chalk');
-const platformCodes = require(path.join(__dirname, '../../../../tools/cli/lib/platform-codes'));
-
-/**
- * XMC Module Installer
- * Standard module installer function that executes after IDE installations
- *
- * @param {Object} options - Installation options
- * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-config.yaml
- * @param {Array<string>} options.installedIDEs - Array of IDE codes that were installed
- * @param {Object} options.logger - Logger instance for output
- * @returns {Promise<boolean>} - Success status
- */
-async function install(options) {
-  const { projectRoot, config, installedIDEs, logger } = options;
-
-  try {
-    logger.log(chalk.blue('🚀 Installing XMC Module...'));
-
-    // Check and create tech_docs directory if configured
-    if (config['tech_docs']) {
-      // Strip {project-root}/ prefix if present
-      const techDocsConfig = config['tech_docs'].replace('{project-root}/', '');
-      const techDocsPath = path.join(projectRoot, techDocsConfig);
-
-      if (await fs.pathExists(techDocsPath)) {
-        // Check if template exists, add if missing
-        const templateDest = path.join(techDocsPath, 'technical-decisions-template.md');
-        if (!(await fs.pathExists(templateDest))) {
-          const templateSource = path.join(__dirname, 'assets', 'technical-decisions-template.md');
-          if (await fs.pathExists(templateSource)) {
-            await fs.copy(templateSource, templateDest);
-            logger.log(chalk.green('✓ Added technical decisions template to existing directory'));
-          }
-        }
-      } else {
-        logger.log(chalk.yellow(`Creating technical documentation directory: ${techDocsConfig}`));
-        await fs.ensureDir(techDocsPath);
-
-        // Copy technical decisions template
-        const templateSource = path.join(__dirname, 'assets', 'technical-decisions-template.md');
-        const templateDest = path.join(techDocsPath, 'technical-decisions-template.md');
-
-        if (await fs.pathExists(templateSource)) {
-          await fs.copy(templateSource, templateDest, { overwrite: false });
-          logger.log(chalk.green('✓ Added technical decisions template'));
-        }
-      }
-    }
-
-    // Create output directory if configured
-    if (config['output_folder']) {
-      // Strip {project-root}/ prefix if present
-      const outputConfig = config['output_folder'].replace('{project-root}/', '');
-      const outputPath = path.join(projectRoot, outputConfig);
-      if (!(await fs.pathExists(outputPath))) {
-        logger.log(chalk.yellow(`Creating output directory: ${outputConfig}`));
-        await fs.ensureDir(outputPath);
-      }
-    }
-
-    // Create dev story location if configured
-    if (config['sprint_artifacts']) {
-      // Strip {project-root}/ prefix if present
-      const storyConfig = config['sprint_artifacts'].replace('{project-root}/', '');
-      const storyPath = path.join(projectRoot, storyConfig);
-      if (!(await fs.pathExists(storyPath))) {
-        logger.log(chalk.yellow(`Creating story directory: ${storyConfig}`));
-        await fs.ensureDir(storyPath);
-      }
-    }
-
-    // Handle IDE-specific configurations if needed
-    if (installedIDEs && installedIDEs.length > 0) {
-      logger.log(chalk.cyan(`Configuring XMC for IDEs: ${installedIDEs.join(', ')}`));
-
-      // Add any IDE-specific XMC configurations here
-      for (const ide of installedIDEs) {
-        await configureForIDE(ide, projectRoot, config, logger);
-      }
-    }
-
-    logger.log(chalk.green('✓ XMC Module installation complete'));
-    return true;
-  } catch (error) {
-    logger.error(chalk.red(`Error installing XMC module: ${error.message}`));
-    return false;
-  }
-}
-
-/**
- * Configure XMC module for specific platform/IDE
- * @private
- */
-async function configureForIDE(ide, projectRoot, config, logger) {
-  // Validate platform code
-  if (!platformCodes.isValidPlatform(ide)) {
-    logger.warn(chalk.yellow(`  Warning: Unknown platform code '${ide}'. Skipping XMC configuration.`));
-    return;
-  }
-
-  const platformName = platformCodes.getDisplayName(ide);
-
-  // Try to load platform-specific handler
-  const platformSpecificPath = path.join(__dirname, 'platform-specifics', `${ide}.js`);
-
-  try {
-    if (await fs.pathExists(platformSpecificPath)) {
-      const platformHandler = require(platformSpecificPath);
-
-      if (typeof platformHandler.install === 'function') {
-        await platformHandler.install({
-          projectRoot,
-          config,
-          logger,
-          platformInfo: platformCodes.getPlatform(ide), // Pass platform metadata
-        });
-      }
-    } else {
-      // No platform-specific handler for this IDE
-      logger.log(chalk.dim(`  No XMC-specific configuration for ${platformName}`));
-    }
-  } catch (error) {
-    logger.warn(chalk.yellow(`  Warning: Could not load XMC platform-specific handler for ${platformName}: ${error.message}`));
-  }
-}
-
-module.exports = { install };

package/src/xmc/_module-installer/platform-specifics/claude-code.js

@@ -1,35 +0,0 @@
-const chalk = require('chalk');
-
-/**
- * XMC Platform-specific installer for Claude Code
- *
- * @param {Object} options - Installation options
- * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-config.yaml
- * @param {Object} options.logger - Logger instance for output
- * @param {Object} options.platformInfo - Platform metadata from global config
- * @returns {Promise<boolean>} - Success status
- */
-async function install(options) {
-  const { logger, platformInfo } = options;
-  // projectRoot and config available for future use
-
-  try {
-    const platformName = platformInfo ? platformInfo.name : 'Claude Code';
-    logger.log(chalk.cyan(`  XMC-${platformName} Specifics installed`));
-
-    // Add Claude Code specific XMC configurations here
-    // For example:
-    // - Custom command configurations
-    // - Agent party configurations
-    // - Workflow integrations
-    // - Template mappings
-
-    return true;
-  } catch (error) {
-    logger.error(chalk.red(`Error installing XMC Claude Code specifics: ${error.message}`));
-    return false;
-  }
-}
-
-module.exports = { install };

package/src/xmc/_module-installer/platform-specifics/windsurf.js

@@ -1,32 +0,0 @@
-const chalk = require('chalk');
-
-/**
- * XMC Platform-specific installer for Windsurf
- *
- * @param {Object} options - Installation options
- * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-config.yaml
- * @param {Object} options.logger - Logger instance for output
- * @returns {Promise<boolean>} - Success status
- */
-async function install(options) {
-  const { logger } = options;
-  // projectRoot and config available for future use
-
-  try {
-    logger.log(chalk.cyan('  XMC-Windsurf Specifics installed'));
-
-    // Add Windsurf specific XMC configurations here
-    // For example:
-    // - Custom cascades
-    // - Workflow adaptations
-    // - Template configurations
-
-    return true;
-  } catch (error) {
-    logger.error(chalk.red(`Error installing XMC Windsurf specifics: ${error.message}`));
-    return false;
-  }
-}
-
-module.exports = { install };

package/src/xmc/sub-modules/claude-code/config.yaml

@@ -1,5 +0,0 @@
-# Powered by XIAOMA™ Core
-name: xmccc
-short-title: XMC Claude Code Sub Module
-author: Brian (XiaoMa) Madison
-submodule: true