Build, debug, and modify applications using the Slice.js component framework (slicejs-web-framework v4.x). Use this skill whenever the user mentions Slice.js, slicejs, slice components, slice.build, slice.events, slice.context, slice.router, sliceConfig.json, or asks to write code inside a Slice.js project โ even if they don't name the framework. Also trigger on custom elements with extends HTMLElement plus init/update/beforeDestroy, slice.attachTemplate, the three-file Visual pattern (.js + .html + .css), the slice CLI (init, dev, build, component create, get), the src/public/ folder for static assets, npm packages via bare imports, or App Shell + MultiRoute / Single-View SPA architectures. Slice has very specific conventions (DOM is only available after slice.attachTemplate, props go through setters, slice.build is async, route params use ${param} not :param, npm packages are imported by bare specifier from node_modules, components must be registered in components.js) that don't match React/Vue/Svelte intui
Author and edit the official Slice.js documentation in THIS repo (slicejs_docs). Use whenever writing, editing, or restructuring docs here: adding a new page under markdown/, updating an existing guide/API/lifecycle page, deciding a page's frontmatter/section/order, wiring a page into the sidebar/routes, or matching the house dev-oriented voice. Triggers on requests like "document this in the docs", "add a docs page for X", "update the update()/lifecycle/context docs", "write the guide for <feature>", or any change to markdown/**/*.md in this repo.