/archer-supreme-dx

Framework SUPREME Production medium usage

/archer-supreme-dx

Overview

The /archer-supreme-dx command is the ARCHER SUPREME Developer Experience system -- a comprehensive development workflow optimization engine that operates at SUPREME authority level to deliver the ultimate development environment for the Prismatic Platform. In a codebase of over 2.8 million lines of code, 100+ umbrella applications, and 37,000+ files, development productivity depends critically on the quality of tooling, environment configuration, workflow automation, and integration with the platform's extensive ecosystem. The /archer-supreme-dx command addresses every dimension of this challenge.

The command manages five interconnected aspects of developer experience. Environment Setup handles shell integration, Git hooks configuration, editor integration, and MCP server initialization. Workflow Optimization configures command shortcuts, alias systems, auto-completion, and quick navigation across the codebase. Productivity Tools integrates session context management, quality gate automation, test runner integration, and documentation generation into seamless workflows. Diagnostics identifies and resolves development environment issues that degrade productivity. Status Monitoring provides a comprehensive health report of the development environment with actionable improvement recommendations.

Unlike utility commands that perform a single function, /archer-supreme-dx operates as a meta-command that orchestrates the entire development experience ecosystem. Executed by the archer-supreme-dx-commander agent, it has SUPREME authority to modify shell configurations, install Git hooks, configure MCP server connections, and optimize the development pipeline end-to-end. The SUPREME authority level ensures that DX optimizations can reach into every corner of the development environment without encountering permission barriers that would leave gaps in the optimization surface.

Usage

/archer-supreme-dx [ACTION] [OPTIONS]

Check Current DX Status and Health

/archer-supreme-dx status

Full Development Environment Setup

/archer-supreme-dx setup

Optimize Existing Workflows

/archer-supreme-dx optimize

Enhance with Additional Productivity Tools

/archer-supreme-dx enhance

Diagnose and Fix DX Issues

/archer-supreme-dx diagnose --verbose

Options and Parameters

ParameterPositionRequiredTypeDefaultDescription
action1NostringstatusAction: setup, optimize, enhance, diagnose, status
--profile--NostringdefaultDX profile: default, minimal, full
--verbose--NobooleanfalseEnable verbose output with detailed diagnostics

Action Descriptions

ActionPurposeDuration
setupFull environment initialization from scratch5-15 minutes
optimizeTune existing configuration for maximum efficiency2-5 minutes
enhanceAdd advanced productivity tools and integrations3-10 minutes
diagnoseIdentify and report DX issues with remediation steps1-3 minutes
statusHealth check and productivity score assessment< 30 seconds

DX Profiles

ProfileDescriptionUse Case
defaultStandard development configuration with all essential toolsMost developers
minimalLightweight setup with core tools onlyCI/CD environments, containers
fullMaximum productivity with all optional enhancementsPower users, SUPREME operators

Authority and Access

PropertyValue
Authority LevelSUPREME
Executing Agentarcher-supreme-dx-commander
StatusProduction
Usage FrequencyMedium
CategoryFramework / Developer Experience
Modelclaude-opus-4-6
ToolsTask, Bash, Grep, Glob, Read, Edit, Write
Shell Integrationzsh, bash
Editor SupportVS Code, Zed, Aide, Neovim
MCP Servers14+ server configurations

Technical Implementation

The DX command implements a comprehensive environment assessment and optimization pipeline. The setup action performs a multi-phase initialization that installs Git hooks, configures shell integrations, establishes MCP server connections, enables quality gate automation, and validates the entire configuration. Each phase reports its status and any issues encountered, ensuring complete transparency about the state of the development environment.

defmodule PrismaticDX.Command do
  @moduledoc """
  ARCHER SUPREME Developer Experience command handler.
  Manages comprehensive development environment optimization
  with multi-phase setup, diagnostics, and health monitoring.
  """

  alias PrismaticDX.{Environment, Workflow, Productivity, Diagnostics}

  @spec execute(String.t(), keyword()) :: {:ok, map()} | {:error, term()}
  def execute(action, opts \\ []) do
    profile = Keyword.get(opts, :profile, :default)
    verbose = Keyword.get(opts, :verbose, false)

    case action do
      "setup" -> setup_environment(profile, verbose)
      "optimize" -> optimize_workflows(profile, verbose)
      "enhance" -> enhance_productivity(profile, verbose)
      "diagnose" -> run_diagnostics(verbose)
      "status" -> check_status(verbose)
    end
  end

  defp setup_environment(profile, verbose) do
    phases = [
      {:shell, &Environment.configure_shell/2},
      {:git_hooks, &Environment.install_git_hooks/2},
      {:mcp_servers, &Environment.setup_mcp_servers/2},
      {:quality_gates, &Environment.enable_quality_gates/2},
      {:editor, &Environment.configure_editor/2},
      {:validation, &Environment.validate_setup/2}
    ]

    results =
      Enum.map(phases, fn {phase, func} ->
        result = func.(profile, verbose)
        {phase, result}
      end)

    {:ok, %{
      phases_completed: Enum.count(results, fn {_, r} -> match?({:ok, _}, r) end),
      total_phases: length(phases),
      details: Map.new(results)
    }}
  end

  defp check_status(verbose) do
    checks = %{
      shell: Environment.check_shell_integration(),
      git_hooks: Environment.check_git_hooks(),
      mcp_servers: Environment.check_mcp_servers(),
      quality_gates: Environment.check_quality_gates(),
      editor: Environment.check_editor_integration()
    }

    score = calculate_productivity_score(checks)

    {:ok, %{
      productivity_score: score,
      checks: checks,
      recommendations: generate_recommendations(checks),
      verbose_details: if(verbose, do: detailed_diagnostics(checks), else: nil)
    }}
  end
end

The status action computes a productivity score (0-100) based on the health of each DX component. The scoring system evaluates shell integration, Git hook installation, MCP server connectivity, quality gate configuration, and editor integration. Each component contributes to the overall score proportionally to its impact on development productivity. The diagnose action provides deep analysis of each component, identifying specific issues and generating targeted remediation steps.

Status Output Structure

The status report provides a structured overview of development environment health:

ARCHER SUPREME DX STATUS
========================

Environment:
  Shell: zsh (integrated)
  Git hooks: Installed (pre-commit, commit-msg, pre-push)
  MCP servers: 14 active
  Quality gates: Enabled (all passing)
  Editor: Configured (VS Code + Zed)

Workflows:
  Auto-commit: Ready
  Auto-test: Ready
  Auto-doc: Ready
  Session management: Active

Productivity Score: 95/100
  - Session management: Excellent
  - Command efficiency: High
  - Integration level: Full
  - Quality automation: Complete

Recommendations:
  - Enable auto-evolution for continuous improvement
  - Configure custom aliases for frequent operations

Workflow Integration

The /archer-supreme-dx command is typically the first command invoked when onboarding to the Prismatic Platform or when setting up a new development environment. The setup action provides a guided initialization that transforms a bare environment into a fully configured, optimized development workspace in minutes rather than hours.

For existing environments, the optimize action periodically tunes configurations based on updated platform requirements. As new MCP servers are added, new quality gates are introduced, or new Git hook phases are implemented, running /archer-supreme-dx optimize ensures the local environment stays aligned with the platform's evolving requirements.

The diagnose action is the first recourse when development environment issues arise. Rather than manually checking individual configuration files and tool installations, the diagnostic engine systematically evaluates every DX component and produces a prioritized list of issues with specific remediation steps. This eliminates the common pattern of developers spending hours debugging environment issues that a structured diagnostic could identify in seconds.

Integration Points

ComponentRelationship
Prismatic AgentsExecuted by archer-supreme-dx-commander agent
AIAD RegistryCommand specification and discovery
Quality GatesConfigures and validates quality gate automation
TelemetryCommand execution metrics and DX health tracking
Git HooksInstalls and manages pre-commit, commit-msg, pre-push hooks
MCP ServersConfigures 14+ MCP server connections
Shell Integrationzsh/bash alias, completion, and navigation configuration
Editor IntegrationVS Code, Zed, Aide, Neovim plugin and settings
Session ContextSession context management automation
/agentsAgent discovery integration for development workflows
/aiad-dashboardDashboard integration for monitoring DX metrics

Doctrine Compliance

All DX operations are governed by the NO MERCY, NO DOUBTS doctrine:

  • NO MERCY: Development environments must be fully configured. No partial setups, no skipped phases, no optional quality gates left disabled. The setup action runs all phases to completion and reports failures explicitly. Missing Git hooks, disconnected MCP servers, and disabled quality gates are treated as violations, not acceptable defaults. Every developer environment must meet the same standard.
  • NO DOUBTS: The diagnose action performs thorough investigation before recommending remediation. Issues are verified against actual environment state, not assumed from configuration files. The productivity score is computed from real measurements, not self-reported metrics. Recommendations are specific and actionable, with exact commands to execute for remediation.

The DX system enforces the platform's Session Discipline Protocol by ensuring that Git hooks are installed and active, preventing the use of forbidden flags like --no-verify, and configuring automatic session context persistence.

Best Practices

  1. Run setup on new environments immediately: Execute /archer-supreme-dx setup --profile full as the first action on any new development environment. This prevents hours of incremental configuration and ensures consistency across development environments.

  2. Check status at session start: Run /archer-supreme-dx status at the beginning of each development session. Environment drift (updated tools, changed configurations, expired credentials) can silently degrade productivity. Regular status checks catch drift early.

  3. Use diagnose before manual fixes: When encountering development environment issues, always run /archer-supreme-dx diagnose --verbose before attempting manual remediation. The diagnostic engine often identifies the root cause faster than manual investigation and suggests the correct fix.

  4. Keep the full profile for active development: The full profile includes advanced productivity tools that significantly accelerate common operations. Reserve the minimal profile for CI/CD and container environments where resource constraints justify reduced tooling.

  5. Re-optimize after platform updates: When the platform introduces new MCP servers, quality gates, or Git hook phases, run /archer-supreme-dx optimize to incorporate the new components into the development environment. This keeps the local environment synchronized with platform evolution.

  • /archer-supreme - Supreme authority activation for platform-wide operations
  • /seadf - Self-Evolving Autonomous Development Framework control and monitoring
  • /connect - MCP server connection management across 14+ servers
  • /quality-gates - Enforce quality gate checkpoints with zero-warning compilation validation
  • /commit - Smart commit with quality gates and conventional format
  • /analyze - System architecture analysis with dependency mapping
  • /aiad-dashboard - AIAD dashboard for intelligence and domain monitoring

Connect & Contribute

Created by Tomáš Korcak (korczis) | Open Source under GHL