菜单
Change this theme with two gates — the user's approval of a written plan before any edit, and a vertical agent review after implementation. Use for any request that touches .dev/src, ucode/, htdocs/, root/, Makefile, vite.config.ts or CI.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/eamonxg/luci-theme-aurora --skill luci-change命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when developing an OpenWrt LuCI theme — editing ucode (.ut) templates, adding or loading CSS/JS/font/image assets, writing CSS animations or menu/drawer interactions, reviewing a theme PR for performance, or measuring TTFB, transfer size, memory, or dropped frames on router-served pages.
Verified facts about luci-base, uhttpd and this theme's own contract — boot order, template scope, L.require semantics, dispatch costs, caching headers, packaging rewrites, router invariants, budgets. Load before reviewing, changing or benchmarking anything in ucode/, .dev/src/, htdocs/ or before proposing a change to luci-base/uhttpd.
正在显示 SKILL.md
| name | luci-change |
| description | Change this theme with two gates — the user's approval of a written plan before any edit, and a vertical agent review after implementation. Use for any request that touches .dev/src, ucode/, htdocs/, root/, Makefile, vite.config.ts or CI. |
| argument-hint | <what to change> |
| disable-model-invocation | true |
Gate 1 is the user's explicit approval; gate 2 is the luci-vertical-review
workflow. No edit to a shipped or source path happens before gate 1, and the
guard-edits hook refuses it mechanically.
/upstream-rfc "<topic>" instead. If it only touches .dev/docs/,
skip to step 4 (docs are not guarded).luci-knowledge; read
references/aurora-contract.md and the section relevant to the files
involved; git log -8 --oneline -- <files>; the tests and budgets that
cover them.EnterPlanMode. The plan states: files to change; the
approach in ≤ 10 lines; budget impact (bytes per tests/build-performance.test.js,
per-request ubus/uci/fs calls, dispatches per navigation); floor it
depends on (OpenWrt/browser); risk and rollback; verification
(pnpm test, pnpm build, which bench if a device is reachable); that
it is one logical commit. Call ExitPlanMode — the user's selection is
gate 1. If plan mode is unavailable, put the same plan in
AskUserQuestion with options "Approve" / "Change the plan" and proceed
only on "Approve".printf '%s\n' <approved path prefixes> > .claude/.change-approved
(one prefix per line, exactly the paths in the approved plan).htdocs/ only through cd .dev && pnpm build.cd .dev && pnpm test && pnpm build; if budgets moved, update
the number in tests/build-performance.test.js and
.claude/skills/aurora-performance/references/aurora-budgets.md in the
same change with the measured value. Run the relevant bench when
.dev/.env names a reachable device; otherwise write "not measured on
device" in the report.luci-vertical-review with
{ base: "HEAD", scope: ".claude/.change-approved" }. Fix every
blocker/major it confirms; list minor ones. If a fix changed
behaviour, run it once more (two rounds maximum)..dev/decisions/<YYYY-MM-DD>-<slug>.md (git-ignored; header lines
Request, Decision: implemented | reverted | deferred, Commit: once
one exists) so the ledger outlives the session. rm -f .claude/.change-approved. Commit only when the user asks: one logical
change, short conventional subject, body carries the reasoning, no
session trailers. Never push.