composer-plugin-dev
/composer-plugin-dev
Composer plugin in its own repository, outside the dxos monorepo: build it, load it into the user's Composer from a local dev server, and optionally test it through the agent debug port or publish it to their private registry. Use when creating or changing such a plugin, trying one in a deployed Composer, or publishing one privately.
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 6
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Composer plugin in its own repository, outside the dxos monorepo: build it, load it into the user's Composer from a local dev server, and optionally test it through the agent debug port or publish it to their private registry. Use when creating or changing such a plugin, trying one in a deployed Composer, or publishing one privately.
Original author description
Composer plugin in its own repository, outside the dxos monorepo: build it, load it into the user's Composer from a local dev server, and optionally test it through the agent debug port or publish it to their private registry. Use when creating or changing such a plugin, trying one in a deployed Composer, or publishing one privately.
How it works
- 1. Pin the toolchain
- 2. Build
- 3. Load the dev server
- 4. Try it
SKILL.md preview
---
name: composer-plugin-dev
description: Composer plugin in its own repository, outside the dxos monorepo: build it, load it into the user's Composer from a local dev server, and optionally test it through the agent debug port or publish it to their private registry. Use when creating or changing such a plugin, trying one in a deployed Composer, or publishing one privately.
---
# Composer plugin development
You build a plugin in the user's repository and load it into the **target**: the Composer the user
has open in their browser. The user enables your dev server in the target and
tries the plugin there.
Two steps end in a **handoff**: something only the user can do in the target. Say exactly what to
click and what they should see, and wait for them.
Two add-ons extend the flow; take each only when its condition holds:
- [DEBUG-PORT.md](DEBUG-PORT.md): the user wants you to test the plugin yourself in the target.
- [PUBLISHING.md](PUBLISHING.md): the user asks to publish the plugin or install it from the
registry.
Before step 1, put Node `>=22.12` on `PATH` for every command. In a new repository, `git init` and
write a `.gitignore` naming `.dxos/`, `node_modules/` and `dist/`.
When a command fails, look it up in [REFERENCE.md](REFERENCE.md).
## 1. Pin the toolchain
The target supplies `@dxos/*`, `react` and `effect` to the plugin at runtime, so compile against an
API-compatible build: the newest `main` commit with packages on pkg.pr.new. Find its first 7
characters, `<commit7>`, and save `{ "commit": "<commit7>" }` as
`.dxos/target.json`:
```bash
node --input-type=module -e 'const r = await fetch("https://api.github.com/repos/dxos/dxos/commits?sha=main&per_page=30"); for (const c of await r.json()) { const s = c.sha.slice(0, 7); if ((await fetch(`https://pkg.pr.new/dxos/dxos/@dxos/app-framework@${s}`, { method: "HEAD" })).ok) { console.log(s); break; } }'
```
Use 7 characters everywhere; a longer SHA installs a second copy of the SDK.
Fetch the plugin guide for that commit, and follow it for every file you write:
```bash
mkdir -p .dxos && g=https://raw.githubusercontent.com/dxos/dxos/<commit7>/docs/src/content/docs/docs
curl -fsSL $g/plex/publishing-plugins.md -o .dxos/guide.md || curl -fsSL $g/composer/publishing-plugins.md -o .dxos/guide.md
```
A new plugin starts from the guide's "Example: a plugin with its own navtree group"; read the
"Things to know" list after it before writing code. In an existing plugin, change only the
dependency pins.
Pin `package.json`:
- `@dxos/*`: `https://pkg.pr.new/dxos/dxos/@dxos/<name>@<commit7>`, in this form even where the
guide shows another. The example needs `app-framework`, `app-graph` and `app-toolkit`; add a
package when you import from it.
- `effect`, `react`, `react-dom`: the exact version the pinned `@dxos/app-framework` declares
(`~19.3.1` → `19.3.1`):
```bash
curl -fsSL https://pkg.pr.new/dxos/dxos/@dxos/app-framework@<commit7> | tar -xzO package/package.json \
| node -e 'let s="";process.stdin.on("data",d=>s+=d).on("end",()=>{const p=JSON.parse(s);const a={...p.peerDependencies,...p.dependencies};for(const k of ["effect","react","react-dom"])console.log(k,a[k])})'
```
- `@types/react`: the newest release with `react`'s major and minor (`npm view @types/react
versions`). Its releases lag `react`'s, so `react`'s own version may not exist.
- Other devDependencies: the guide's, as written.
Install with `npm install --legacy-peer-deps`. Without the flag, npm takes peers of the pkg.pr.new
packages from the npm registry, and their `react` ranges conflict.
**Done when** the install succeeds, this lists exactly one path per package, and `npx tsc --noEmit`
exits 0:
```bash
find node_modules -path '*node_modules/effect/package.json' -o -path '*node_modules/react/package.json' -o -path '*node_modules/react-dom/package.json'
```
## 2. Build
```bash
npx vite build
cat <outDir>/manifest.json
```
`<outDir>` is `build.outDir` in `vite.config.ts`.
**Done when** `manifest.json` names the plugin's key and version.
## 3. Load the dev server
Start Vite's dev server in the background. `composerPlugin` serves
`http://localhost:3967/manifest.json` from it:
```bash
npx vite
```
**Handoff:** in the target, the user opens the gear in the left rail, then **Plugins**. Under **Dev
Server** they leave the Manifest URL at its default and click **Enable**. If Chrome asks to let the
page look for and connect to devices on the local network, they click **Allow**: the dev server is on
`localhost`. Composer loads the plugin from the dev server now and on every reload until they click
**Disable**.
**Done when** the user sees the plugin in the target, where the guide's example says it appears.
## 4. Try it
Give the user a checklist: one line per behaviour they asked for, saying what to click and what they
should see. Write each so a naive implementation fails it: "a button that changes the number" means
clicking it several times and seeing the number change each time.
**Handoff:** the user works through the checklist and reports back.
On a report of a failure:
1. Edit, and run `npx tsc --noEmit`.
2. Ask the user to reload the target. The dev server serves the new source, so there is nothing to
rebuild.
**Done when** the user confirms every line of the checklist on one reload with no edits in between.
The work ends here, with the plugin running from the dev server, unless the user asks to publish.
Files in this package (4)
- DEBUG-PORT.md 8 KB
- PUBLISHING.md 3 KB
- REFERENCE.md 5 KB
- SKILL.md 5 KB
Versions
The database has no other skills named composer-plugin-dev.
Database snapshot: 13.11.2026 · package version 7dc0b06c767d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100composer-dev-env
Run a local Composer against the shared EDGE dev environment over HTTPS at https://local.composer.space/, sign in with a passkey, and connect the dev MCP server (mcp.dev.dxos.network) so the agent can read and write the same dev spaces. Use when asked to point local Composer at… - 100composer-qa
Run the executable QA of a `.mdl` spec — a `test QA-n`, a `suite`, or every suite carrying a tag — against a Composer dev server you start, driving each step as one operation call through the agent debug port, judging every step by the UI snapshot, and writing a per-run report.… - 100composer-packages
Use when building or maintaining a Composer library — versioning, Laravel integration, autoloading, publishing to private registries — even when the user says 'release a new version'. - 100composer-tooling
Composer conventions for any PHP project: dependency management, version constraints, PSR-4 autoloading, scripts, platform requirements, and the composer.json vs composer.lock contract. Stack-agnostic — referenced by every PHP plugin in the marketplace. Use this skill to: - Read… - 100cursor-advanced-composer
Manage advanced Cursor Composer techniques for complex edits. Triggers on "advanced composer", "composer patterns", "multi-file generation", "composer refactoring". Use when working with cursor advanced composer functionality. Trigger with phrases like "cursor advanced… - 100php-composer-conventions
ACTIVATE when modifying composer.json, adding/updating dependencies, or running composer commands. ACTIVATE for 'composer require', 'composer update', version constraints. Covers: caret versioning policy, forbidden patterns (*, dev-master, exact versions), internal package…