agentleFS
jcanizalezjcanizalez/vibegrid/.claude/skills/vorn-extension-author/SKILL.md

vorn-extension-author

Skill25 starsChanged 27 days agoMITView on GitHub

Write, change or review a Vorn extension (a program, a Wasm component or one-shot commands), including the ones Vorn ships from vorn-run/extensions. Use for anything touching a vorn-extension.toml, the extension API's version, or what an extension may call.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read docs/extensions.md first, then docs/wasm-extensions.md for components and the element tree.

    line 8
  2. Very specific:

    One API, vorn:extension@1.0: Never add another api id. Every manifest sets api = "vorn:extension@1.0".

    line 14
  3. Very specific:

    A built-in builds on vorn-extension-sdk alone: No other path dependency, no vorn_extension_sdk::bindings or ::guest.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Writing a Vorn extension

Read docs/extensions.md first, then docs/wasm-extensions.md for components and the element tree. The API is defined once, in packages/core/crates/extensions/wit/extension.wit.

The rules

  1. One API, vorn:extension@1.0. Never add another api id. Every manifest sets api = "vorn:extension@1.0"; vorn = ">=1.0" is optional and is a range of API versions, not of Vorn releases.
  2. Public only. An extension, Vorn's own included, calls only the methods in CORE_METHODS (gate.rs) and listens only to CORE_EVENTS (events.rs), each under the permission its manifest declares. If it needs something the API cannot do, add it to the API (WIT, gate.rs, docs), never a private path.
  3. A built-in builds on vorn-extension-sdk alone. No other path dependency, no vorn_extension_sdk::bindings or ::guest. An exception goes in packages/core/freeze.toml with a one-line reason.
  4. The core stays frozen. A new place where a core or host crate names a built-in (its id, its crate or its vornd module) fails cargo test -p vorn-extensions --test freeze until it is listed in freeze.toml under [exceptions.hooks] with a reason. Prefer moving the behaviour behind the public API.
  5. Versioning. A minor version only adds. Changing or removing anything is a major: bump the WIT package, wit/stdio.json (VORN_UPDATE_WIT=1 cargo test -p vorn-extensions publishes_the_mapping) and every manifest, and say so in the PR.
  6. Handshake. A program checks guest.init's ctx.api and refuses a Vorn older than it was built for with a message naming both versions; a component is checked by vornd before linking.
  7. Own workflows only. Seeded workflow ids and unseed prefixes start with <extension id>:, and workflow.run runs only those. Running another's workflow, or seeding a script, agent or undeclared step, needs process.run.

Checks

cargo test --profile ci -p vorn-extensions --test freeze
cargo test --profile ci -p vorn-extensions --lib compat

A manifest error names its field and line; keep it that way in any new field you add to manifest/file.rs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.