Menu
Use right after the user publishes ivue to npm — installs the just-published version into a throwaway consumer repo and smoke-tests the runtime, the skill installer, and the tarball contents against the registry artifact, not the local build.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use when a docs_v2 blog post needs its 1200x630 banner image — compose an in-brand HTML file in this skill's banners/ directory and render it deterministically with npm run render:banner. Covers the design language, the pipeline, and the verification loop.
Use when writing or editing ivue `Reactive()` classes, converting a Vue component or composable to ivue, or resolving any `.value`-in-template, `defineExpose`/`reactive()` instance-typing, `ReactiveInstance`/`Instance`, `$watch`/`$watchEffect`, or namespace-export question, or any `Static()` capability-class / `$`-cached-static / anchor question — the operating manual for Vue 3 class-based reactivity where state is ref-getters, derived values are plain getters, and Refs/Computeds are `.value` everywhere.
Use when bumping the ivue package version, tagging a release, or preparing an npm publish — the repo's versioning/tagging conventions and the gates that must pass before a version is stamped.
Author and refactor TypeScript Node.js backends around static capability classes, mutable class namespaces, late dependency getters, lazy-bound static methods, native inheritance, and boot-time composition. Use for backend modules, circular imports, route or queue callbacks, plugin kernels, test doubles, and designs that would otherwise introduce DI tokens, decorators, forwardRef, or service instances that only hold methods.
Use when writing or editing any documentation in this repo — docs_v2 guide pages, README, invariants docs, sketch DESIGN/RESULTS files, or doc comments meant for readers. Encodes the house documentation style — timeless present tense with no edit-history residue, unpacked concepts over compressed jargon, ivue-standard code examples, and verified claims.
| name | verify-publish |
| description | Use right after the user publishes ivue to npm — installs the just-published version into a throwaway consumer repo and smoke-tests the runtime, the skill installer, and the tarball contents against the registry artifact, not the local build. |
The point: verify the artifact npm actually serves, not the local build. Local gates prove the source; this proves the tarball — files included, prepack ran, dist is current, the CLI works from a consumer's seat.
Fresh consumer repo in the scratchpad (never inside the ivue repo — its node_modules is shared with the macOS host):
mkdir -p <scratchpad>/ivue-consumer && cd <scratchpad>/ivue-consumer
npm init -y
npm install ivue vue
Version check — the installed version must equal the version just
published:
node -e "console.log(require('./node_modules/ivue/package.json').version)"
Tarball contents — ls node_modules/ivue must show dist,
bin, skills; dist/ must contain both entries in both formats —
index.es.js + index.cjs, extras.es.js + extras.cjs — and the
.d.ts files for each. Gzip dist/index.es.js (the 1.1 kB core) and
dist/extras.es.js, and confirm both match the release's measured
numbers.
Runtime smoke test — a smoke.mjs run with plain node,
importing from 'ivue' (the registry copy). Assert at minimum:
Reactive(X) === X (identity preservation)a.x === a.x)$watch fires (use { flush: 'sync' })$stopEffects() kills watchers AND resets cached cellsstopEffects() method, tear down, assert it
was never calledpropsWithDefaults wraps object/array defaults in factories;
isClass discriminatesAnd for the ivue/extras entry:
import { Static } from 'ivue/extras' resolves (ESM) and
require('ivue/extras') resolves (CJS) — same for the core entry;Static(X) returns a subclass of X and leaves X untouched;const method = Class.method; method() keeps this);Skill installer — in the consumer repo:
mkdir -p .claude # the installer detects footprints, never scaffolds
npx ivue skill
Then verify BOTH:
.claude/skills/ivue/SKILL.md exists and is byte-identical to
node_modules/ivue/skills/ivue/SKILL.md (diff is empty);prepack did not run or the publish went out from a dirty tree.Report the pass/fail table to the user with the measured size. Leave the consumer repo in the scratchpad — it evaporates with the session and must never be committed.