Back to the catalog

GenvidTechnologies/claude-code-plugin-gvt-construct3 · wiki

Bundle OKF 0.2 · 16 conceitos · GenvidTechnologies/claude-code-plugin-gvt-construct3

Open source Repository Open in the app JSON README (API)

About

<!-- `okf_version` is the ONLY frontmatter key permitted here (§8/§12) — this
file is the bundle-root index for the dev-workspace wiki. A
`wiki/<subdir>/index.md` carries NO frontmatter at all. -->

# Wiki Index

The dev-workspace wiki for `claude-code-plugin-gvt-construct3` — how maintaining
*this plugin* works. Every page under `wiki/` is listed here, one line each,
grouped under section headings. `/gvt-dev:maintain-wiki` keeps the list current:
a new page is registered here when it's created, and `lint` flags any page listed
in **no** index. Each entry's description is the linked page's frontmatter
`description`, so the index and the page can't drift.

See [`wiki-schema.md`](wiki-schema.md) for the page format and
maintenance rules.

> **Scope.** This bundle covers the **dev workspace**. The shipped C3 platform
> reference is a *separate* OKF bundle at `plugin/docs/c3/`, maintained by hand
> against `construct3-sample` rather than by `ingest` — see the schema doc's
> two-bundles not

Details

Kind
OKF bundles
Topic
Productivity
Publisher
genvidtechnologies
Origin
okf_github
Category
dados
Version
0.2
Last push
2026-09-03T18:59:12Z
Repository state
ativo
Language
JavaScript
License
MIT-0
Added
2026-09-09 12:02:17
Updated
2026-09-09 12:02:17
Origin id
GenvidTechnologies/claude-code-plugin-gvt-construct3:wiki/index.md

README

# claude-code-plugin-gvt-construct3

The **`gvt-construct3` plugin** for Claude Code — Construct 3 platform knowledge, C3 agents, and a convention audit for any repository with a Construct 3 project on disk.

It bundles the **construct3-chef** and **c3-domain-manager** MCP servers, ships the `c3-explorer` and `c3-implementer` agents, and owns the canonical **C3 platform reference** (`plugin/docs/c3/`). It is **independent of the `gvt-dev` plugin** — installable on its own.

It is distributed through the [`claude-code-marketplace`](https://github.com/genvid-holdings/claude-code-marketplace) catalog (marketplace name `genvid-plugins`).

## Install

```text
/plugin marketplace add https://github.com/genvid-holdings/claude-code-marketplace.git
/plugin install gvt-construct3@genvid-plugins
```

The plugin declares `construct3-chef` and `c3-domain-manager` in its `plugin.json` (`mcpServers`), so they start when the plugin is enabled. They may appear as **"Pending approval"** — approve them once.

Then verify the repo satisfies the contract:

```text
/gvt-construct3:audit-c3-conventions
```

The audit checks for a **C3-project marker** and that both MCP servers are reachable at their minimum versions.

## What the plugin provides

**Agents** (dispatched via `subagent_type: "gvt-construct3:<name>"`):

| Agent | Model | Purpose |
|-------|-------|---------|
| `c3-explorer` | haiku | Read-only C3 recon — DSL, layouts, domain index, search |
| `c3-implementer` | opus | C3 mutations via recipes, layout/sprite scaffolding, project sync |

**Skill** (invoked as `/gvt-construct3:<name>`):

| Skill | Purpose |
|-------|---------|
| `audit-c3-conventions` | Read-only validator — C3-project marker + MCP server reachability/versions |
| `author-navigation-patterns` | Authors/validates a chef `navigation.targetPatterns` convention for wrapper-routed navigation |
| `build-reference` | Builds chef's `c3-reference` cache (built-in ACEs + concept docs) so `search-docs` resolves built-ins |
| `create-c3-op` | Authors + dry-run-validates a construct3-chef user-defined op wrapper (params + `{{PARAM}}` placement) |

**Bundled docs** (`plugin/docs/c3/`): the canonical **C3 platform reference** — event-sheet architecture, layouts, scripting, TS integration, and `construct3-guide.md`. The agents link these via `${CLAUDE_PLUGIN_ROOT}/docs/c3/*`.

**Bundled MCP servers** (`plugin.json` `mcpServers`): `construct3-chef` (recipes, DSL, scaffolding; its own docs at the `construct3-chef` server's `docs:///index` resource) and `c3-domain-manager` (domain index, overrides).

## The convention contract

`gvt-construct3` requires a consuming repo to be a Construct 3 project with the two MCP servers available. The full contract — including the optional, project-owned context the agents read from your `CLAUDE.md` — is documented in [`plugin/CONVENTIONS.md`](plugin/CONVENTIONS.md).

## Knowledge boundaries

- **C3 platform reference** (how Construct 3 behaves) → this plugin (`plugin/docs/c3/`).
- **Tooling reference** (recipe format, generators, CLI, recipe gotchas) → the `construct3-chef` server's `docs:///index` resource, versioned with the tool.
- **Project-specific facts** (named layouts, file paths, commit format, project gotchas) → the consuming repo.

## Contributing

The shipped plugin lives in the **`plugin/`** subfolder; the repo root is the dev workspace (a `gvt-dev` consumer). See [`CLAUDE.md`](CLAUDE.md) for the full layout.

- Skills are directories with `SKILL.md`; agents are flat `.md` files in `plugin/agents/`.
- Top-level frontmatter is fixed (`name`, `description`, plus Anthropic-supported fields); custom expectations go under `metadata.expects`.
- Validate with `cd plugin && claude plugin validate .`.
- Test the audit with `cd plugin && node --test skills/audit-c3-conventions/scripts/test/*.test.mjs`.

More