Coder Nexus

Agent and skill bundles for software delivery in VS Code / Antigravity.

This extension copies Coder Nexus agent profiles, skills, and rules into the workspace you choose. A host agent uses them to turn a real request into approved requirements, design, implementation, review, and verification. The extension also includes an architecture dashboard. Roles run when the host invokes them; installing the extension does not start an autonomous agent team.

How the pieces fit

Feature work uses three actual user approvals: requirements → design → implementation plan. Delivery then implements bounded phases, reviews the code revision, records evidence, and performs independent acceptance verification. Work items live under .superpowers/work-items/<slug>/vN/; smaller work types have their own sequences.

All stacks share one set of role agents and process skills; each pack adds its own rules and <stack>-<slot> skills, and .agents/stack.json records which pack owns which paths. The Frontend–Backend API handshake is a documented contract workflow; in separate workspaces agents exchange contract artifacts, in a monorepo each side edits only the paths its pack owns.

Related MCP server: devops-mcp-server

Architecture profiles

The three profiles describe where a Flutter project's reusable foundations come from. They are alternatives, not maturity levels or separate agent teams.

All three guides ship in the same Flutter bundle. There is currently no separate installer or --profile option for external projects. Profile selection is recorded in the approved design. Company package details live in the separate packages' guidance/GUIDE.md files; they are not included in this extension.

Validators accept the selected profile and reserve company-specific checks for iMESPro. External Client conventions still require source inspection, analysis and runtime evidence. A complete external delivery replay is not yet verified.

Current support

• Flutter: the primary maintained delivery workflow, with the deepest guidance for iMESPro packages.

• Backend: a preview pack on the shared roles (clean architecture, API contracts, unit tests, review and verification skills); equivalent delivery acceptance has not been demonstrated.

• Frappe UI: a preview pack (clean architecture and the Frappe UI catalog). Steps without Frappe guidance install as placeholders that make agents stop with BLOCKED instead of borrowing Flutter rules.

• General Web: not a pack yet.

The FE source manifest lists 19 public skills across framework/shared folders and 8 MCP tools. Installation selects shared skills plus the chosen framework; it does not install all 19 into every workspace.

Quickstart

No repository clone is needed. You install the extension, then let it install the CLI.

1. Install the extension

In VS Code / Antigravity open Extensions (Cmd+Shift+X / Ctrl+Shift+X), search Coder Nexus (IMP-AIFactory.coder-nexus, published on Open VSX) and click Install. A .vsix from GitHub Releases also works (Install from VSIX...).

2. Install the coder-nexus CLI (one click)

The CLI is the MCP server runtime (coder-nexus serve) plus the Huly and Flutter setup commands. The extension does not bundle it.

Click Coder Nexus in the status bar → Install / Update CLI (or run Coder Nexus: Install / Update CLI). The terminal installs uv if missing, then the CLI pinned to the extension version. Manual equivalent:

curl -LsSf https://astral.sh/uv/install.sh | sh        # Windows: powershell -c "irm https://astral.sh/uv/install.ps1 | iex"
uv tool install --force git+https://github.com/pzakhim/coder-nexus.git@vX.Y.Z   # X.Y.Z = extension version
coder-nexus --help

After updating the extension, run Install / Update CLI again so the CLI matches. Run Coder Nexus: Doctor to check the CLI.

3. Sync agents into your project

Open the project. When the extension recognizes Flutter, Frappe or Backend folders (also in subfolders of a monorepo) it offers Sync Now; otherwise run Coder Nexus: Sync Stacks to Workspace (Auto-Detect) and tick the stacks the workspace contains. This writes:

• .agents/plugins/coder-nexus/: the shared skills plus the <stack>-* skills of each selected pack,

• .agents/agents/: the six roles, each followed by the rules of every selected pack,

• .agents/stack.json: the selected packs and the paths each one owns (edit the paths if detection guessed wrong).

Add … Pack to Workspace commands add one pack to the ones already installed. Re-syncing replaces only these generated files and removes the pre-2.8 coder-nexus-fe / coder-nexus-be folders. Sync again after the CLI is installed so mcp_config.json points at the absolute CLI path (IDEs launched from the Dock/Finder may not see ~/.local/bin). Sync Plugin to Antigravity Global Config is an explicit, separate command (Flutter).

4. Connect Huly (optional, no agent needed)

From the project folder:

coder-nexus setup huly           # prompts for email/password (add --url for self-hosted Huly), writes ./.env
coder-nexus setup huly --check   # authentication status; exit 0 only when logged in
coder-nexus my-tasks     # lists your open tasks: proves the connection works
coder-nexus task-detail AUTH-101

Make sure .env is in your project's .gitignore. setup huly stores the password and session token in plain text there.

To exercise the MCP tools without an agent: npx @modelcontextprotocol/inspector coder-nexus serve.

5. Flutter setup

coder-nexus doctor                                              # read-only: Huly status + Flutter gate
coder-nexus setup flutter --check                               # read-only gate
coder-nexus setup flutter --profile external-standard           # any Flutter project
coder-nexus setup flutter --profile imespro                     # company projects

imespro clones app-core, app-util and app-ui-kit next to the project from the company Git group set in CODER_NEXUS_CORE_GIT (for example export CODER_NEXUS_CORE_GIT=ssh://git@git.example.com/group); it needs company Git access. Without --profile, setup asks; with --yes it defaults to imespro. Use the extension (step 3) to install plugins: coder-nexus install-plugin only works from a source checkout.

Verification and boundaries

The Hub suite (uv run --offline python -m pytest -q) covers validators, Huly adapter, setup, profile regression and CLI/extension installation. These are Hub and packaging checks. A real approved feature replay through host invocation, implementation, review, runtime visuals, and acceptance testing remains NOT_RUN.

Huly operations are read-only. Credentials belong in the Client's untracked .env. Agents cannot self-approve gates, invent package APIs, or turn BLOCKED, NOT_RUN, or UNVERIFIED into PASS. Lexical validators do not replace Client analysis and runtime tests.

More documentation (not included in the VSIX):

• Installation and CLI setup

• Flutter profiles and iMESPro packages

• Release notes: GitHub Releases

Maintained by IMP-AIFactory.