Menu

Individual skill

valaxy-theme

0upvotes

Create or evolve a runnable Valaxy theme from a design brief, reference site, or UI library. Use for valaxy-theme-* packages, AI theme generation, theme starter customization, or adapting AK UI to a Valaxy blog. Covers theme contracts, demo content, packaging, SSR and browser verification. Use the general valaxy Skill for site configuration or article editing without theme development.

skills/valaxy-theme/SKILL.md

Read pinned source

Source commit 3e13c49d364cd9f883437566e7cb1069c1f2e6ea

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 3, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,126
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Valaxy theme authoring

Turn 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.

## Skill and brief have different roles

This 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.

For 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.

## Establish the baseline

- Inspect the current workspace, applicable AGENTS.md, package scripts, installed Valaxy version and exported types. Adapt an existing theme when that is the request.
- For a new independent theme, use https://github.com/valaxyjs/valaxy-theme-starter in a new directory. Its `theme/` package and `demo/` consumer are the starting point. If `theme:init` exists, run `pnpm theme:init <name>` inside the new workspace, adding `--owner <owner>` only when the repository owner is known; otherwise update package references and `theme` configuration together. Run `pnpm install` after renaming.