acryldev Build an ACRYL extension
- Read {{pack}}/docs/start-here/this-runtime.md completely (contracts, delivery).
- Decide WHERE it mounts and on which surfaces: read {{pack}}/docs/maps/mount-points.md (CLI has terminal overlays; Web and Desktop have client slots; tools, commands, prompts and skills work everywhere). Ask or check which surface the user is on if it matters (the router and acryl_workspace_status help). For an unfamiliar kind of plugin see {{pack}}/docs/maps/taxonomy.md.
- Pick the plugin type(s) the feature needs and open the matching doc from {{pack}}/docs/README.md (tool, service, event hook, config, prompt, client UI, host route, tui command). Read it completely and follow its cross-references.
- Open the closest working example in {{pack}}/example-plugins/README.md and read every file of it. Copy it into a NEW directory /.acryl-extensions// (outside the pack) and change it. Never guess a plugin's shape from memory.
- Write the package (package.json, cordis.patch.yml, index.js, and client.js for UI). Declare honestly in package.json:
"acryl": { "apiVersion": 1, "permissions": [...] }(fs.read, fs.write, net, shell, secrets, ui); the human sees the permissions before a new extension is installed. Write it under<workspace>/.acryl-extensions/<name>/(this project) or<ACRYL home>/extensions/<name>/(all projects and surfaces on this home). - Call the acryl_install_plugin tool with the ABSOLUTE path of that directory. Read its result. Fix the named cause and call it again if it fails; it undoes failed installs.
- Tell the user what you built, whether it is live, and (for UI) that they should reload the page or window. Do not claim it works before the tool result says so. You cannot publish to the marketplace; say what remains if the user wants that.