nddev-zcode-app

Authors a ZCode slash command as commands/<name>.md in a marketplace. Use when adding or defining a slash (/) command, including nested colon-separated commands. For a SKILL.md use add-skill; for a subagent use add-agent.

Scaffolds a new self-contained ZCode marketplace — a complete ~/.zcode setup — under zcode_tools/marketplaces/. Use when creating a brand-new setup or profile such as nddev-builder or nddev-designer, or bootstrapping a marketplace directory from scratch.

Scaffolds a new self-contained plugin bundle inside a ZCode marketplace and registers it in marketplace.json. Use when adding a plugin to a marketplace, or grouping skills, commands, and agents into one installable bundle.

Adds a model provider to a marketplace's config template. Use when adding or configuring an LLM provider — OpenAI, Anthropic, or a custom OpenAI-compatible endpoint — or wiring provider models, base URL, or API-key placeholders into a ZCode setup.

Authors a ZCode skill (SKILL.md) inside a plugin bundle or at user scope. Use when adding a skill or teaching the agent a reusable workflow. For a slash command use add-command; for a subagent use add-agent.

Runs an isolated install-and-verify loop for a marketplace using temporary HOME and ZCODE_HOME, proving components flatten and load without touching live ~/.zcode. Use to behaviorally test a plugin during development, after static validation.

A guided first run of the nddev-builder toolkit — from zero to a working, validated ZCode plugin or marketplace in ordered steps. Use when new to nddev-builder, onboarding, or unsure which skill to start with.

Orients you in the nddev-builder toolkit and in how ZCode 3.5.2 discovers and loads extensions. Use when asking how nddev-builder is structured, how ZCode loads skills/commands/agents, where components go and why, why an installed skill is not loading, what the installer does (flatten to user scope), or the install/remove/switch lifecycle. Read this first before authoring or debugging a marketplace.

Designs multi-subagent workflows for a ZCode plugin within the 3.5.2 limits — user-scope agents, foreground, parallel-yes/background-no — using Explore for recon and critic panels with on-disk evidence. Use when a plugin needs several agents to cooperate rather than one.

Reviews a whole ZCode marketplace for release readiness across all plugins — identity and version-lockstep presence, cross-plugin basename safety, inert-field and secret scans, English-only, and a clean install plan. Use before shipping a marketplace, after per-artifact review and static validation.

Composes a complete ZCode plugin from a described intent — a metadata-only manifest plus the right mix of skills, commands, agents, hooks, and MCP config — and registers it in the marketplace. Use when starting a plugin from a goal rather than adding one component at a time.

Validates a marketplace's components statically before install, so an authoring mistake fails at author time instead of install time. Use before installing or shipping a marketplace, or when a skill, command, or agent is being rejected or silently dropped.

Registers a tool integration for the agent — a classic MCP server or a lean CLI+skill alternative. Use when adding any external tool, API, or data source the agent should call, or choosing between an MCP server and a CLI tool. For a plain CLI tool use add-tool.

Registers a ZCode lifecycle hook in a marketplace's hooks.json. Use when adding or configuring a SessionStart, UserPromptSubmit, PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure, or Stop hook, or wiring a hook matcher, command, or timeout.

Adds a CLI tool — a non-MCP executable script plus an optional companion skill — to a plugin bundle. Use when adding a linter, formatter, utility script, or any command-line tool the agent should run. For a classic MCP server use add-mcp-server.

Distributes a ZCode marketplace so others can install it — via a GitHub repo, Git URL, local path, or ZIP URL added through the ZCode Marketplace tab — and explains the headless-flatten vs UI-install paths. Use when shipping a marketplace beyond this repo's installer.

Authors a ZCode subagent as agents/<name>.md in a marketplace. Use when adding, defining, or configuring a subagent — a reviewer, researcher, or worker the main agent can delegate to. For a slash command use add-command; for a SKILL.md use add-skill.

Authors and maintains ZCode AGENTS.md instruction files at user or workspace scope. Use when adding default agent instructions, editing AGENTS.md, deciding user-vs-workspace scope, or reasoning about the load and merge order of instruction files in ZCode.

Adds a reference documentation file — a spec, format reference, or design doc — under a plugin's references/ directory. Use when adding background documentation that plugin skills and commands should cite. Reference docs are plain Markdown, not a loadable component type.

Enables or disables a registered plugin in a marketplace's config template. Use when a plugin is registered in marketplace.json but not active, or when toggling a plugin on or off for a setup.

Lists the plugins, skills, commands, agents, hooks, and MCP servers in a marketplace. Read-only — makes no changes. Use when inspecting what a marketplace contains, or checking existing components before adding or removing one.

Removes a component — a plugin, skill, command, agent, reference, or CLI tool — from a marketplace safely, refusing when it is still referenced elsewhere. Use when cleaning up, refactoring, or deleting a component that is no longer needed.