waller-wallpaper-session
Helps manage wallpaper features and cross-layer domain changes in React/Tauri/Rust projects.
Install
mkdir -p .claude/skills/waller-wallpaper-session && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10284" && unzip -o skill.zip -d .claude/skills/waller-wallpaper-session && rm skill.zipInstalls to .claude/skills/waller-wallpaper-session
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Extend or debug the Wallpaper Session, monitor drafts, preview flows, editor flow, and profile composition across React, Tauri, and Rust. Use for monitor wallpaper features, profile bugs, preview issues, or domain-model changes.Key capabilities
- →Debug wallpaper preview loading and caching
- →Coordinate domain model changes across TypeScript and Rust
- →Update profile composition and validation rules
- →Manage monitor draft and fit-mode handling
- →Verify state consistency between frontend and backend
How it works
The workflow requires identifying whether changes affect the frontend state, the Tauri IPC seam, or the Rust native layer. It mandates updating both TypeScript and Rust validators simultaneously for domain changes.
Inputs & outputs
When to use waller-wallpaper-session
- →Debug wallpaper preview loading issues
- →Update profile validation rules
- →Coordinate domain model changes in Rust and TS
- →Modify monitor draft handling logic
About waller-wallpaper-session
Coordinates domain logic across TypeScript and Rust layers during wallpaper session development. It helps manage monitor drafts, preview loading, and profile validation to ensure state consistency between frontend and backend.
Extend or debug the Wallpaper Session, monitor drafts, preview flows, editor flow, and profile composition across React, Tauri, and Rust. Use for monitor wallpaper features, profile bugs, preview issues, or domain-model changes.
When not to use it
- →Changing profile validation on only one side of the JS/Rust boundary
- →Bypassing the Tauri IPC layer from components
Prerequisites
Limitations
- →Requires updating documentation when session flows or commands change
- →Preview state must be treated as part of the session contract, not UI-only
How it compares
Unlike manual debugging, this procedure enforces strict synchronization between Rust and TypeScript layers using specific markers and verification scripts.
Compared to similar skills
waller-wallpaper-session side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| waller-wallpaper-session (this skill) | 0 | 2mo | No flags | Intermediate |
| openui-forge-rust | 0 | 1mo | Review | Advanced |
| tauri | 0 | 5mo | No flags | Intermediate |
| tauri | 76 | 1mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
openui-forge-rust
OthmanAdi
OpenUI generative UI with Rust Axum backend. Async SSE streaming with reqwest and async-stream.
tauri
BiFangKNT
构建、调试与发布 Tauri v2 应用的工程化工作流。覆盖项目初始化（create-tauri-app）、前端与 Rust 命令通信（`#[tauri::command]` + `invoke`）、状态管理、Capabilities 权限建模、插件接入、跨平台构建与问题排查。当用户需求涉及“创建 Tauri 项目”“把 Web 前端接到 Rust 后端”“最小权限配置（fs/http/shell）”“接入 Tauri 官方插件”“执行 tauri dev/build”“排查 Tauri 构建或运行错误”时使用此 skill。
tauri
EpicenterHQ
Tauri path handling, cross-platform file operations, and API usage. Use when working with file paths in Tauri frontend code, accessing filesystem APIs, or handling platform differences in desktop apps.
debugging-streamlit
streamlit
Debug Streamlit frontend and backend changes using make debug with hot-reload. Use when testing code changes, investigating bugs, checking UI behavior, or needing screenshots of the running app.
rust-errors
EpicenterHQ
Rust to TypeScript error handling patterns for Tauri apps. Use when defining Rust errors that will be passed to TypeScript, handling Tauri command errors, or creating discriminated union error types.
hula-skill
HuLaSpark
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.