- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add YunYouJun/valaxy --skill valaxy-theme -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add YunYouJun/valaxy --skill valaxy-theme -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add YunYouJun/valaxy --skill valaxy-theme -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add YunYouJun/valaxy --skill valaxy-theme -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/YunYouJun/valaxy/tree/HEAD/skills/valaxy-theme게시자 제공
Turn the user's visual direction into a source-distributed theme and a working demo. Read the theme contract before changing rendering or package entrypoints. Read the AK UI recipe only when the user chooses AK UI or an Arknights-inspired theme.
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.
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.link: dependencies in their manifests or lockfiles.Identify the blog audience, reading priorities, palette, typography and one distinctive structural idea. Preserve an explicitly requested style. If the brief is sparse, choose reasonable defaults and state them; ask only for a missing decision that materially changes the result.
Keep site identity and article content configurable. Use actual post metadata in archive counts, dates, tags and navigation. Build the reading experience alongside the homepage: a long article with headings, code, quotes, links, a table and an image must remain comfortable on mobile.
Separate the shell/navigation, homepage, post list, article frame and optional outline into focused Vue components. Use Vue 3 <script setup lang="ts">; prefer native interactions and the project's existing primitives. Expose only implemented theme options with types and defaults.
Follow the installed framework's ValaxyMain / ValaxyMd, layout and slot contracts. Keep browser-only effects in mounted/client-guarded code. Use Valaxy's post APIs rather than maintaining a separate hard-coded post list. Never include drafts in a production archive merely to make a demo look populated.
Inspect real package scripts for lint, type checking, tests and the demo build. For a new theme or rendering change, run an SSG build explicitly (valaxy build --ssg or a script that includes it); a successful SPA build is not SSG verification. Generate the demo’s Valaxy declarations before standalone type checking when required by the starter. Inspect desktop and mobile pages, internal navigation, article rendering, appearance switching, keyboard focus and empty states. Check console/hydration errors. Test a non-root Vite base when the theme is intended for subdirectory hosting. Build success alone does not verify appearance.
Pack the theme and verify its exported entries and required source directories. For changes to dependencies or exports, install the archive in a fresh consumer and build it. Update the README with supported layouts/options, development commands and actual compatibility. Report what was verified and what remains incomplete. Generating a theme does not itself publish it to npm or deploy a site.
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 V
---name: valaxy-themedescription: Create or evolve a runnable Valaxy theme from a design brief, reference site, or UI library. Use for…---# skills/valaxy-theme/SKILL.md개요
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.
FAQ
게시자에게서 skills/valaxy-theme/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/YunYouJun/valaxy에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.