An Agent Skill that gives AI coding assistants (Claude Code and compatible tools) expert knowledge of building web apps with wcstack — @wcstack/state, @wcstack/router, @wcstack/signals, and the wcs-* I/O node components.
With this skill installed, asking your AI assistant to "build an app with wcstack" produces apps with correct data-wcs binding syntax, proper CDN loading, and the project's standards-first, zero-config, buildless conventions — instead of hallucinated APIs.
skills/wcstack-app/
├── SKILL.md # Workflow, invariants, cheat sheet, the most
│ # frequent failures
└── references/
├── state-binding.md # Full data-wcs syntax, comment bindings, filters,
│ # delegated events + #direct, command-/event-tokens,
│ # $behavior, $watch, spread rules, $recursion / **,
│ # accumulation over time, keyed selection ($eq*),
│ # split entries, 3.x code, the pitfall checklist
├── router-and-scaffold.md # SPA routing, layouts, guards, autoloader,
│ # index.html skeleton + SPA server fallback
├── io-node-catalog.md # wcBindable catalog of 52 wcs-* tags
│ # + signals quick reference
├── forms.md # a page that is mostly a form: the IME, fields that
│ # format, autofill, reset, rows, own form controls
├── long-lists.md # a long list: infinite scroll, a filter and a page on
│ # its way, rows, a window of rows, coming back
├── device-apis.md # the screen and the sensors: a tap, is it there, the
│ # iPhone's question, fullscreen, pickers, passwords
├── islands.md # a page wcstack does not own: htmx / Turbo,
│ # inserted markup, history caches, widgets
├── frameworks.md # wcs-* elements in a React / Vue / Svelte / Solid app
├── verification.md # the lint in depth, wcs-schema / wcs-tsc, console
│ # messages, DevTools, headless tests, SSR
└── versions.md # a page pinned to an older 4.x release
The skill uses progressive disclosure: SKILL.md stays small — the workflow, the invariants and the most frequent failures, about 20 KB — and the references load only when the matching phase is reached. Keep it that way when adding to the skill:
- New knowledge goes into the reference of its area (a failure into that reference's pitfalls), not into
SKILL.md.SKILL.mdnames a failure only if authors of most apps meet it. - The skill describes one release, the one in its stamp. Write a behaviour as it is in that release, with no "since 4.x" / "up to 4.x" notes; what a page pinned to an older 4.x release does differently goes in
references/versions.md.
/plugin marketplace add wcstack/wcstack-skill
/plugin install wcstack-app@wcstack
Copy skills/wcstack-app/ into:
~/.claude/skills/wcstack-app/— personal, available in every project, or<project>/.claude/skills/wcstack-app/— project-scoped.
The plugin version tracks the wcstack release the content was last verified against (currently 4.26.0). The SKILL.md frontmatter carries the same stamp as metadata.wcstack-version.
Pages that must stay on wcstack 3.x pin the major in their CDN URLs (https://esm.run/@wcstack/state@3/auto) and use a skill release verified against 3.5.4 (the v3.5.4 tag of this repository).
The wcstack monorepo (package READMEs, examples/, docs/, and source) is the ground truth; wcstack.github.io is the project landing page. When wcstack protocols change — data-wcs syntax, wc-bindable / command-token / event-token, router attributes — the references here must be updated to match. PRs that fix drift against a released wcstack version are welcome.