🕵️‍♂️ @anon1911/anon

The spec-driven Senior Developer agent CLI & MCP server who never sleeps, doesn't drink all your coffee, and actively prevents you from breaking production at 3 AM.

@anon1911/anon (pronounced anon, like that mysterious helper who fixes your bugs when you aren't looking) is a specification-driven developer agent that acts as an automated "Senior Developer" in your workspace.

It automatically detects your tech stack, enforces strict custom guardrails, writes highly-tailored editor instructions (.cursorrules, .clinerules, etc.), runs pre-flight regression audits, and exposes an MCP (Model Context Protocol) server gateway to bridge LLM clients (like Antigravity, Claude Desktop, Cursor) to your tools (Figma, Git, Jira).

🚀 Key Features

• 🕵️‍♂️ Stack Scanner (No-Config Detective): Inspects your codebase to auto-detect languages (TypeScript, Rust, Go, Python), styling (Tailwind, Sass, CSS), databases, package managers, and test runners.
• 🛡️ Spec-Driven Guardrails: Enforces rules defined in .anon/config.json. Will instantly block banned imports (looking at you, axios) or forbidden console logs before they reach staging.
• 🧠 Bespoke Editor Rules Generator: Auto-writes precise instruction rules tailored exactly to your workspace for Cursor (.cursorrules), Cline/Roo Code (.clinerules), GitHub Copilot (.github/copilot-instructions.md), and Antigravity (.antigravity/instructions.md).
• 🌉 MCP Server Proxy Gateway: Exposes local code standard tools to your editor LLMs, and proxies requests to sub-MCP tools (e.g. Figma, Git, Jira) so your agents have super-powers.
• ⚖️ Pre-Flight Regression Audits: Run anon audit to find out if the compile errors on your branch are actually your fault, or if they were already broken on the base branch. Save hours of unnecessary debugging!

📦 Installation

To use anon globally anywhere on your machine:

npm install -g @anon1911/anon

Or, install it as a devDependency in your repository:

npm install --save-dev @anon1911/anon

⚡ Quick Start

1. Initialize anon

Scan your repository and set up configuration files:

# If installed globally:
anon init

# Or via npx:
npx -y @anon1911/anon init

This launches a quick wizard to choose your favorite development platforms:

Choose target AI Platform(s) for development:
  1 : VS Code + GitHub Copilot
  2 : VS Code + Claude (Cline / Roo Code)
  3 : Cursor
  4 : Antigravity
  5 : Claude Desktop (MCP)
  6 : All Platforms
  7 : None (only setup .anon config)

After choosing, it automatically writes:

• 📁 .anon/config.json: Core stack settings and validation patterns.
• 📄 Custom editor rule files (e.g., .cursorrules, .clinerules) so your AI assistant knows exactly what dependencies, design patterns, and naming conventions to respect.

2. Verify Guardrails

Check if any files violate your rules:

anon verify

Or check specific files:

anon verify src/index.ts src/utils/config.ts

3. Generate Project Context Report

Need to catch an external LLM up on your project? Generate a beautiful text-based project tree and stack summary file:

anon context

Creates a comprehensive summary report of your project's architecture, file structure, and stack.

🛠️ CLI Command Reference

| Command | Description | | :--- | :--- | | anon init | Scans the stack and initializes .anon/config.json and rules. | | anon verify [files...] | Checks workspace code against guardrails (fails on banned patterns). | | anon context | Generates a Markdown report & Visual Tree of your codebase structure. | | anon build | Compiles your project using the auto-detected compiler. | | anon test | Runs the test suites matching your auto-detected test runner. | | anon feature <name> | Scaffolds a new git feature branch, checklist, and ticket context. | | anon fix <description> | Diagnoses compilation/build bugs, and outputs a diagnostic manifest. | | anon update <package> | Upgrades a dependency and executes builds/tests to check for regression. | | anon review [base] | Compares your branch with a base branch (main) to review rules compliance. | | anon sync [base] | Pulls/merges changes from a base branch, flagging potential merge conflicts. | | anon audit [base] | Compares build/lint failures on your branch vs base branch to isolate regressions. | | anon pr [base] | Pushes your active branch and drafts a Pull Request. | | anon design <figmaUrl>| Imports assets/SVGs/fonts from Figma and scaffolds matching local components. | | anon mcp start | Starts the Model Context Protocol (MCP) server. |

🔌 MCP Server Gateway Configuration

You can easily register anon as an MCP server in your favorite IDE or client (Claude Desktop, VS Code Cline, VS Code Roo Code, or Cursor) either automatically via the CLI or manually.

⚡ Automatic IDE Registration & De-confliction

If you have other MCP servers configured (e.g., a standalone Figma MCP server), they might conflict with anon's integrated tools. You can prioritize anon and automatically set up the configurations using the CLI:

# Register in all detected IDE configurations
anon mcp register-ide

# Register in a specific IDE (claude, cline, roo, or cursor)
anon mcp register-ide claude

# Prioritize anon and disable conflicting servers (backs them up safely in config)
anon mcp register-ide --clean

🛠️ Manual Configuration

If you prefer to configure the server manually, add the following entry to your Claude Desktop config (claude_desktop_config.json), Cursor config (mcp.json), or VS Code extension settings (cline_mcp_settings.json):

{
  "mcpServers": {
    "anon": {
      "command": "npx",
      "args": ["-y", "@anon1911/anon", "mcp", "start"]
    }
  }
}

[!TIP] To route other servers (like Figma or Github) safely through anon to avoid duplication, define them under the mcpGateways field in your local .anon/config.json instead of placing them directly in your IDE settings.

Exposed MCP Tools

Once configured, your AI assistant will gain access to these tools:

• get_project_context: Retrieve project configuration, stack details, and rules.
• verify_code_standards: Run guardrail checks & pattern validation on target files.
• run_agent_command: Safely run compilation, tests, or linters and return error reports.
• setup_anon_config: Automate scanning and configuring .anon/config.json.
• create_feature_branch: Generate feature branches and checklist manifests.
• diagnose_and_scaffold_fix: Compile and create diagnostic manifests for bugs.
• upgrade_package_dependency: Update dependencies and verify compatibility.
• sync_and_resolve_conflicts: Safely merge base branch updates.
• audit_bug_regressions: Differentiate between new regressions and pre-existing main branch issues.
• push_and_create_pull_request: Automate branch pushes and pull request setups.
• scaffold_figma_design: Retrieve Figma assets/styles and scaffold layouts.
• scaffold_ui_component: Scaffold semantic and structured UI component templates.
• audit_wcag_accessibility: Scan component code for accessibility issues and auto-patch them.
• generate_frontend_tests: Generate unit tests for React components using Vitest/Jest.
• optimize_component_performance: Detect and refactor rendering bottlenecks.

⚙️ Configuration File (.anon/config.json)

Customize anon's behavior inside .anon/config.json. Below is an example structure:

{
  "name": "my-awesome-app",
  "techStack": {
    "language": "typescript",
    "framework": "nextjs",
    "styling": "tailwindcss",
    "database": "postgresql"
  },
  "guardrails": {
    "bannedImports": [
      {
        "pattern": "^axios$",
        "message": "Use standard native fetch utility instead of axios to reduce bundle size."
      }
    ],
    "patterns": [
      {
        "regex": "console\\.log",
        "message": "Console logs are forbidden in production. Use our logging service instead."
      }
    ],
    "requiresTests": true
  },
  "mcpGateways": {
    "figma": {
      "command": "npx",
      "args": ["-y", "@figma/mcp-server"]
    }
  }
}

🛡️ License

MIT. Go forth and write beautiful, regression-free code! 🚀