C3 Platform Reference
Bundle OKF 0.2 · 0 conceitos · GenvidTechnologies/claude-code-plugin-gvt-construct3
Open source Repository Open in the app JSON README (API)
About
# C3 Platform Reference
Background reference on **Construct 3 itself** — the on-disk JSON formats and runtime semantics that construct3-chef reads, mutates, and extracts. This is distinct from the **tooling** reference — construct3-chef's own commands, recipe format, and generators — which lives in the `construct3-chef` server's `docs:///index` resource, versioned with the tool, and is deliberately not duplicated here.
These notes were adapted from a production C3 project; project-specific (game) content has been removed, leaving the platform mechanics that apply to any Construct 3 project. Example object, layer, and function names in code samples are illustrative only.
One doc in this set — `toolchain-config.md` — covers a cross-tool concern (how both bundled MCP servers resolve configuration from the workspace root) that neither tool's own docs own; field-level reference for each tool stays in that tool's own documentation.
| Doc | Covers |
| --- | ------ |
| [construct3-guide.md
Details
- Kind
- OKF bundles
- Topic
- Media, design & games
- 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:03:57
- Updated
- 2026-09-09 12:03:57
- Origin id
GenvidTechnologies/claude-code-plugin-gvt-construct3:plugin/docs/c3/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`.