跳到正文
cccskills
免费在 GitHub 公开

state

Persistent state schema migration requirements — the one schema, one migration ladder, and the fail-fast host-map membership rule. Use when changing anything that is persisted.

中文简介正在准备中。当前显示原文说明。

juspay/kolu
查看安装方法

包含的文件（1）

  • SKILL.md2.1 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Persistent State (conf)

State is stored via conf in packages/server/src/state.ts, which owns the on-disk shape (PersistedStateSchema, internal to that file) and the migration ladder. Domain modules (preferences.ts, hostPersistence.ts) read and write their own keys against the shared store.

When changing what is persisted (any of the per-domain schemas — PreferencesSchema in packages/common/src/surface.ts, PersistedHostsSchema in packages/common/src/hostKey.ts), you must add a migration in state.ts's migrations object and bump SCHEMA_VERSION. Without a migration, existing users' state files silently lose or misinterpret data on schema changes.

The disk shape is one schema, one migration ladder, one source of truth. PersistedStateSchema is intentionally not exported; consumers go through the domain accessors (getPreferences(), getPersistedHosts()).

Host-map membership rides this store too — it is not a special case. The fleet you add via the selector strip persists as the hosts field of PersistedStateSchema, owned by hostPersistence.ts (its getPersistedHosts() reader + savePoolMembership() persist-hook shaper) and carried by the SAME schema + migration ladder as every other domain. It IS real user data (unlike preferences, a silent reset would eat the fleet), so it must never be silently emptied — and conf already guarantees that: a corrupt/unparseable store THROWS on read (clearInvalidConfig is false, conf 15's default), it does NOT reset to defaults. That fail-fast is exactly why hosts belongs in this store rather than a hand-rolled file. An invalid-but-parseable value (a hand-edited local, a duplicate) additionally fails loud where it's read — getPersistedHosts re-validates through PersistedHostsSchema (in kolu-common/hostKey) and throws, never silently normalizing. Changing the hosts shape takes a migration + SCHEMA_VERSION bump like any other domain.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护，适用 Google 的隐私权政策和服务条款。

同一仓库的技能

blog-post

免费

Write a kolu blog post grounded in the real build history — mine the Claude Code session logs behind a feature for the actual story (for large efforts, fan out over the transcripts with an ultracode workflow), draft it in the author's voice, and wire it into the Astro site. Use when asked to write a blog post or engineering essay about something that was built, especially one that should read as a narrative of what actually happened rather than invented marketing copy.

中文简介正在准备中。当前显示原文说明。

juspay/kolu822026年10月21日 更新

ci

免费

Run this repo's CI end-to-end — kolu's policy on top of the odu runner: banned opt-out flags, x86_64-linux pinning, pool upkeep, fail-fast surfacing, e2e timing evidence, and the green-gate. Triggers on "run CI", "drive CI", "re-run the pipeline", "close the red check", "warm the pool". Runner mechanics live in the `/odu` skill.

中文简介正在准备中。当前显示原文说明。

juspay/kolu822026年10月21日 更新

dev-server

免费

Launch the kolu dev server on two RANDOM free ports so it never collides with the running production `kolu.service`, remember the ports for the rest of the session, and tear down only the dev instance. Load before running the app locally — for evidence capture, driving a live kolu with the chrome-devtools MCP, or any `just dev` you'd otherwise run by hand. Triggers on "run kolu locally", "launch the dev server", "boot kolu", "drive a live kolu", "start the app to screenshot it", or before pointing chrome-devtools at a local kolu.

中文简介正在准备中。当前显示原文说明。

juspay/kolu822026年10月21日 更新

diataxis

免费

Classify, write, and audit documentation per Diátaxis (diataxis.fr) — the four-quadrant method (tutorials · how-to guides · reference · explanation). Encodes the compass as a decision procedure, each quadrant's contract as hard rules, and an executable mixed-mode audit. Project-agnostic; the per-repo doc-location mapping lives in a repo rule of the project's own (kolu: the Kolu overlay below). Use when writing any user-facing doc, structuring a docs site, or auditing existing docs for mixed modes.

中文简介正在准备中。当前显示原文说明。

juspay/kolu822026年10月21日 更新

dock-state

免费

The Dock's agent-state folds — one fenced source of truth in @kolu/terminal-vocab, the load-bearing order≠colour split, and the one "is something happening" question. Use when editing agentProjection or the canvas dock.

中文简介正在准备中。当前显示原文说明。

juspay/kolu822026年10月21日 更新

e2e-testing

免费

E2E test conventions — semantic selectors, arrange-steps that prove the process started, runtime markers that cannot match the shell echo, and absolute-path tool invocations. Use when writing or changing a .feature scenario under packages/tests.

中文简介正在准备中。当前显示原文说明。

juspay/kolu822026年10月21日 更新

查看 juspay 的全部技能

报告此技能的问题