菜单
Write or revise `intelligence-tests/*.it.md` task cards for agent-driven end-to-end validation in this Runelight repo. Use when the user asks to add, edit, or design `.it.md` intelligence test scenarios or expected user experiences.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | write-intelligence-test |
| description | Write or revise `intelligence-tests/*.it.md` task cards for agent-driven end-to-end validation in this Runelight repo. Use when the user asks to add, edit, or design `.it.md` intelligence test scenarios or expected user experiences. |
Write .it.md files as task cards for a future agent to execute.
An intelligence test is an agent-driven end-to-end check written in natural language. It tells a capable agent what product behavior or user experience to validate, then lets the agent choose the concrete commands, browser steps, HTTP checks, edits, and observations from repo context.
Make the test boundary obvious:
Do not write a tutorial, rationale, runner syntax, or implementation commentary. Do not assume an already-prepared local project proves setup behavior unless the task explicitly says to test that prepared project.
Intelligence tests can be heavier than unit tests. Prefer grouping related goals into one realistic flow when they share setup, dev server, browser session, or temporary files. Use them for behavior that unit tests do poorly: setup outcomes, cross-system integration, dev-server/runtime behavior, multi-step user workflows, generated artifacts, and user-visible product experience.
Keep the file short and direct. Trust the executing agent to choose commands and tools from the repo context.
Install, upgrade, or ensure Runelight preview/capture integration in a TypeScript React project or TypeScript Vue 3 project. Use when a project asks for "install Runelight", "set up Runelight", "upgrade Runelight", or "update Runelight"; this bootstrap skill detects the host, wires the integration, and verifies end-to-end.
Write, edit, or review Runelight React components in .g.tsx files. Use when working on React/TSX .g protocol components, GFrames, createGScopeHook, createGProvider, provider variants, JSX branch coverage, or React Runelight authoring diagnostics.
Write, edit, or review Runelight Vue SFC components in .g.vue files. Use when working on Vue .g protocol components, <g:frames>, template-first scope frames, Vite Vue preview, or Vue Runelight authoring diagnostics.
Polish Runelight-covered GUI through a required explicit sync before editing, then a red-team observe-edit-reobserve loop that works from product surface model down to details one confirmed point at a time. Use when the user asks to polish, refine, improve visual quality, clean up UI details, or make an existing `.g.tsx` / `.g.vue` interface feel better.
Refactor existing React TSX into production .g.tsx UI models without preview wrappers.
Refactor existing Vue 3 TypeScript SFCs into production .g.vue UI models without preview wrappers.
