hula-skill — Claude Code skill: what it does, how to install
A repo skill for HuLa: Vue 3 frontend, Tauri v2 and Rust backend, full-stack paths, release work. It asks which scope to switch on before touching code.
Apache-2.0 ★ 7,877 updated 2026-10-29
npx skills add HuLaSpark/HuLa --skill hula-skill -a claude-codeWhat hula-skill does
Start by naming a scope: frontend, backend, fullstack or build-release. The skill also asks about platform (desktop or mobile) and the spot you want changed, whether that is a view, a component, a store or a command.
Each scope brings starter files. Vue views for desktop and mobile, a Pinia store, a Rust Tauri command, a TypeScript wrapper for end-to-end work. Reference docs cover the stack, folder layout and aliases, along with a checklist per scope.
Two helper scripts read the repo so you don't have to. One counts views and stores and prints where they live; the other lists Tauri commands next to the frontend invoke calls. Templates and checklists describe HuLa's own layout, so in another codebase they point at nothing.
What it helps with
- scaffold a view for both desktop and mobile
- add a Pinia store that matches the existing ones
- map Tauri commands to their invoke calls
- walk a release checklist before building
- carry one change from a Vue form down to a Rust command
Example prompts for the agent
- Add a settings view to HuLa, frontend scope, desktop platform.
- List the Tauri commands in HuLa and where the frontend invokes them.
- HuLa, backend scope: I need an export command for chat history.
How to install hula-skill
1Skills CLI (Vercel)
npx skills add HuLaSpark/HuLa --skill hula-skill -a claude-code2Manually: put the files in place
~/.claude/skills/hula-skill/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/hula-skill/
1Skills CLI (Vercel)
npx skills add HuLaSpark/HuLa --skill hula-skill -a codex2Manually: put the files in place
.agents/skills/hula-skill/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add HuLaSpark/HuLa --skill hula-skill -a cursor2Manually: put the files in place
.cursor/skills/hula-skill/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install HuLaSpark/HuLa skills/hula-skill2Manually: put the files in place
.github/skills/hula-skill/SKILL.md1Skills CLI (Vercel)
npx skills add HuLaSpark/HuLa --skill hula-skill -a gemini-cli2Platform CLI
gemini skills install https://github.com/HuLaSpark/HuLa --path skills/hula-skillManually: put the files in place
.devin/skills/hula-skill/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add HuLaSpark/HuLa --skill hula-skill -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about hula-skill
How do I install hula-skill in Claude Code?
Run npx skills add HuLaSpark/HuLa --skill hula-skill -a claude-code. The skill file lands at ~/.claude/skills/hula-skill/SKILL.md.
What does hula-skill do?
It keeps edits to HuLa in line with the repo's own conventions: Vue and Rust templates, reminders to update routes, stores and commands, checklists for builds and releases.
Does it help with code outside HuLa?
Its templates, references and checklists target this repository only. Pointed at a different project, they have nothing to attach to.
Source text
SKILL.md · Apache-2.0
--- name: hula-skill description: "HuLa project skill for frontend (Vue 3 + Vite + UnoCSS + Naive UI/Vant), backend (Tauri v2 + Rust + SeaORM/SQLite), full-stack flows, and build/release work. Use when the user mentions hula or HuLa or requests changes in this repository; after triggering, ask which scope (frontend/backend/fullstack/build-release) to enable." --- # HuLa Skill ## Overview Enable consistent changes across the HuLa frontend, backend, full-stack flows, and build/release tasks with repo-specific conventions and resources. ## Activation Gate Ask which scope to enable: frontend, backend, fullstack, or build-release. Confirm platform (desktop or mobile), target area (view/component/store/command), and any constraints before editing. ## Workflow 1. Identify scope and platform. 2. Locate similar code paths and follow existing patterns. 3. Apply changes using repo conventions and available templates. 4. Update related layers (routes, stores, commands) when needed. 5. Propose or run checks/tests only when requested. ## Scope Routing - Frontend: read `references/frontend.md` and `references/overview.md`; use `assets/templates/view-desktop.vue`, `assets/templates/view-mobile.vue`, `assets/templates/pinia-store.ts` as starters. - Backend: read `references/backend.md` and `references/overview.md`; use `assets/templates/tauri-command.rs`. - Fullstack: read `references/fullstack.md` plus frontend/backend references; use `assets/templates/tauri-command.ts`. - Build/Release: read `references/build-release.md` and `references/checklists.md`. ## Scripts Use `scripts/hula_summary.py` for quick repo context (views/stores counts and paths). Use `scripts/hula_tauri_map.py` to list Tauri commands and frontend invoke usage. ## References Use `references/overview.md` for stack, directories, aliases, and global conventions. Use `references/checklists.md` for per-scope checklists.
© HuLaSpark · Apache-2.0 · HuLaSpark/HuLa