菜单
Use when reorganizing frontend files in apps/web, classifying components vs non-components, applying folder/naming conventions, and adding top-of-file Purpose headers for faster human/AI navigation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when changing System Journey Viewer local persistence shape or semantics (localStorage UI preferences, layout persistence, snapshots, recents), including backward compatibility, storage key versioning/migration logic, tests, and user-facing behavior safeguards.
Use when capturing or regenerating System Journey Viewer visual demos and screenshots with Playwright, including local dev server setup, deterministic showcase loading, presentation/journey playback automation, and media artifact validation for README/docs/help gallery.
Use when changing System Journey Viewer export behavior (SVG, PNG, PDF, GIF, MP4, animated SVG) or presentation/player capture flows, including validation of export tests, capture state restoration, format-specific constraints, and demo-gallery impacts.
Use when tuning System Journey Viewer light/dark themes, node/text color presets, palette defaults, and visual contrast/readability in canvas, inspector, showcase/tutorial examples, or desktop shell UI.
Use when syncing System Journey Viewer documentation after feature or workflow changes, covering WORKLOG, AI_STATE, SJV Script spec, help content, README, and naming consistency (especially SJV Script terminology and English UI/docs text).
Use when updating the System Journey Viewer showcase or tutorial workspaces, including EN/PT variants, notes, drilldowns, semantic edge/journey naming, demo coverage of features, and corresponding tests/help menu entry behavior.
| name | sjv-file-atlas-and-header-conventions |
| description | Use when reorganizing frontend files in apps/web, classifying components vs non-components, applying folder/naming conventions, and adding top-of-file Purpose headers for faster human/AI navigation. |
Use this skill when a task involves structural refactors, file moves, naming consistency, or readability conventions in apps/web.
docs/FILE_ATLAS.md first.components/ React-only.diagram/*, layout/*, windowing/*, etc.).Purpose: headers.git mv (preserve history).Purpose: headers on touched files.docs/FILE_ATLAS.md.npm --workspace @sjv/web run lintnpm --workspace @sjv/web run test:runnpm --workspace @sjv/web run builddocs/WORKLOG.md and docs/AI_STATE.md.src/components/<group>/PascalCase.tsxsrc/diagram/<edges|nodes|player>/camelCase.tssrc/layout/*src/windowing/**.test.ts[x]Purpose:.imports, exports, etc.).components/ because they were originally created near UI code.PascalCase utility modules or camelCase React components).