valaxy-theme

1# Valaxy theme authoring
2 
3Turn the user's visual direction into a source-distributed theme and a working demo. Read [the theme contract](references/theme-contract.md) before changing rendering or package entrypoints. Read [the AK UI recipe](references/ak-ui.md) only when the user chooses AK UI or an Arknights-inspired theme.
4 
5## Skill and brief have different roles
6 
7This Skill supplies reusable framework knowledge and the development/verification workflow. The user's brief supplies this task's theme name, audience, visual direction, required pages and constraints. A brief generated by the docs is ordinary task input: preserve its choices, without treating its preset as a mandatory theme architecture. Do not ask the user for a second, full engineering prompt when this Skill is available.
8 
9For a new theme, establish the package/demo baseline and implement the reading experience. For an existing theme, inspect the requested change and preserve unrelated behavior, package identity and content. Do not re-run initialization or regenerate the whole theme for an iteration. Scale validation to what changed: style edits need affected-page checks; rendering, dependencies or exports need the corresponding build/package checks.
10 
11## Establish the baseline
12 
13- Inspect the current workspace, applicable AGENTS.md, package scripts, installed Valaxy version and exported types. Adapt an existing theme when that is the request.
14…