hula-skill
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.
When & Why to Use This Skill
The HuLa project skill is a specialized full-stack development assistant designed to streamline engineering workflows within the HuLa repository. It provides expert-level support for a modern tech stack including Vue 3, Vite, and UnoCSS on the frontend, and Tauri v2, Rust, and SeaORM on the backend. By leveraging repository-specific templates and automated scripts, it ensures architectural consistency, accelerates feature implementation, and simplifies complex build and release processes for both desktop and mobile platforms.
Use Cases
- Frontend Development: Rapidly scaffolding new views and components using Vue 3, Naive UI, or Vant while adhering to established UnoCSS styling patterns and Pinia store structures.
- Backend Engineering: Implementing high-performance backend logic and database interactions using Rust, Tauri v2 commands, and SeaORM/SQLite integration.
- Full-stack Synchronization: Coordinating changes across the entire stack, ensuring frontend UI components and backend Rust commands are perfectly aligned and documented.
- Build and Release Management: Executing standardized build procedures and checklists to ensure stable releases across different operating systems and platforms.
- Repository Context Mapping: Utilizing specialized Python scripts to quickly map out Tauri commands and frontend usage for faster debugging and impact analysis.
| 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
- Identify scope and platform.
- Locate similar code paths and follow existing patterns.
- Apply changes using repo conventions and available templates.
- Update related layers (routes, stores, commands) when needed.
- Propose or run checks/tests only when requested.
Scope Routing
- Frontend: read
references/frontend.mdandreferences/overview.md; useassets/templates/view-desktop.vue,assets/templates/view-mobile.vue,assets/templates/pinia-store.tsas starters. - Backend: read
references/backend.mdandreferences/overview.md; useassets/templates/tauri-command.rs. - Fullstack: read
references/fullstack.mdplus frontend/backend references; useassets/templates/tauri-command.ts. - Build/Release: read
references/build-release.mdandreferences/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.