--- title: Extension builder slug: extension-builder description: Build a Cedros extension in GitHub with the assistant, or generate a paste-ready prompt for your AI code editor. productSlug: cedros productLabel: Cedros sectionKey: build sectionLabel: Build --- # Extension builder The Extension builder helps you create optional site features you can install, reuse, and share across Cedros sites. Use the assistant to build and package an extension in a connected GitHub repository, or create a prompt for your own AI code editor. ## Before you start - You need the **data:ops:write** permission. Without it, the page is read-only. - Assistant builds need a configured intelligence provider under **Providers**. - Assistant builds need the default GitHub credential in **Vault** to be complete. - Connect at least one allowed GitHub repository. The editor-prompt path does not require a provider, Vault credential, or repository. ## What's on this page The page has two authoring paths and a **Manage extensions** button, which opens the Extensions section for installation and lifecycle management. ### Assistant build The assistant builds the extension in a connected GitHub repository and opens a pull request when the package is ready. - **GitHub repository** — Select the repository and base branch for the build. Use **Manage repositories** to add or remove allowed targets. - **Extension name** — Becomes the task, project, and pull-request title. - **Build brief** — Describe what the feature does, who uses it, and where it appears. The brief must contain at least 80 characters. - **Acceptance criteria** — List the observable behavior and release evidence required before the pull request is ready. Enter at least 20 characters. - **Start build** — Creates a queued Extension Builder task and confirms that it is ready to follow on the task board. - **Open task board** — Opens all current and completed assistant tasks. The build uses a locked workflow: clone the selected repository, seed the project from the versioned Cedros authoring kit, apply the extension-authoring contracts, validate and package the installable ZIP, run tests, open a pull request, and clean up the temporary workspace. The completed task records the pull request, branch, package path, checksum, test evidence, and GitHub download URL. The ZIP is committed to the build branch. Review and merge the pull request, then download the package from GitHub and upload it in **Extensions**. ### Editor prompt Use **Create editor prompt** when you want to work in Claude Code, Cursor, Codex, or another AI code editor. The handoff includes a versioned authoring kit generated from the canonical Cedros extension documentation. - **Kick off a build** offers **New extension** and **Existing codebase** starting points. It creates a two-pass prompt: orient and plan first, then implement, validate, package, and prepare release evidence. - **Audit existing work** creates a read-only contract audit with cited findings, severity, unknowns, host handoffs, and remediation order. - **Check release readiness** creates a read-only release gate with validation, package, smoke, checksum, launch, and rollback evidence. - **Download extension authoring kit** downloads a versioned ZIP for offline use. The same version-matched guide, individual documents, examples, scripts, WIT, and checksums are public from the Extension Authoring link under `/skill.md`, so the target repository does not need to contain the docs. `AUTHORING-KIT.json` records compatibility and SHA-256 checksums for the bundled source files. - **Copy prompt** copies the selected workflow prompt. The generated prompt starts at `https://cedros.ai/skill.md`, follows **Extension Authoring**, and uses the complete public version-matched guide and kit linked there. A downloaded local kit remains useful for offline work but is not required. The coding agent must stop rather than guess an API that is not published by that guide. ## Build an extension with Cedros 1. Confirm the intelligence provider and default GitHub credential in **Vault** are ready. 2. Connect or select a GitHub repository. 3. Name the extension and enter a specific build brief. 4. Click **Start build**. 5. Open the task board to review step progress, failures, and the final PR. 6. Review and merge the PR, then download its committed ZIP. 7. Upload the ZIP in the [Extensions](extensions.md) section. ## Create a prompt for your code editor 1. Click **Create editor prompt**. 2. Choose **Kick off a build**, **Audit existing work**, or **Check release readiness**. 3. For a kickoff, choose **New extension** or **Existing codebase**. 4. Describe the goal or add optional context. 5. Optionally download and unzip the extension authoring kit for offline work. 6. Click **Copy prompt**, then paste it into your editor. The agent follows the public Extension Authoring links for the current contract. ## Troubleshooting - **The assistant build asks for a provider** — Open **Providers** and connect an intelligence provider. The editor prompt remains available. - **The page is read-only** — Ask an administrator for **data:ops:write** access. - **GitHub setup fails** — Open **Vault** and complete the default GitHub credential. Never use the site-owner password as a GitHub or MCP token. - **No repository is available** — Click **Connect repository** and add an allowed `owner/repository` plus base branch. - **Start build reports that the description is too short** — Expand the build brief to at least 80 characters with users, workflows, important surfaces, and constraints. Add at least 20 characters of concrete acceptance criteria. - **A build step fails** — Open the task board and read the failed subtask. Test, validation, package, and PR failures stop the workflow instead of publishing a partial result. - **Copy prompt failed** — Select the prompt preview and copy it manually. - **Authoring kit download failed** — Confirm your `data:ops:write` permission and retry. The prompt remains available, but the coding agent must have one of the documented guide paths before it begins.