Browser & automation
acryl-change-plugin
Use when the user asks you to change, fix, improve, restyle, extend or remove an extension or plugin that already exists in ACRYL.
acryldev · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add acryldev/acryl --skill acryl-change-pluginAbout this skill
name: acryl-change-plugin description: Use when the user asks you to change, fix, improve, restyle, extend or remove an extension or plugin that already exists in ACRYL.
Change, improve or remove an ACRYL plugin
- Call acryl_list_plugins to find the plugin and the source directory it was installed from. If it is not listed the user may mean a built-in feature; say so instead of guessing.
- Read its files completely before editing, and the matching doc in {{pack}}/docs/README.md for the plugin type.
- Edit the source directory (never node_modules, never the pack). For UI changes edit client.js.
- Call acryl_install_plugin with the same directory: it updates in place. Read the result: if it has a "warning" the host code change needs an app restart unless the plugin uses the hot shim ({{pack}}/examples/packages/lifecycle-function-hot-shim/); if it has a "next" note, tell the user to reload.
- To remove a plugin call acryl_remove_plugin. Confirm with the user first if they did not clearly ask for it. Report what changed and whether it is live; never claim it works without the tool result.