agentleFS
Sign inStart free
AhmiDarrowAhmiDarrow/RemedyAI/skills/webui-parity/SKILL.md

webui-parity

Skill5 starsChanged 23 days agoApache-2.0View on GitHub

When changing Grove, Studio, Settings, or chat chrome, keep WebUI (browser on :7400) at parity with Tauri. Grove unmounts off-surface; serve mounts SPA once at start. Use after any desktop/src UI change the owner will also see in the browser.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    CLI: do not add voice (or other GUI-only) commands unless the owner asks.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

WebUI parity (same SPA, different load path)

Desktop and WebUI share desktop/src/. Vite (tauri:dev) is always fresh. WebUI is whatever find_webui_dir() mounted at API start (prefer desktop/dist).

Checklist (every owner-visible UI change)

  1. Does Grove unmount? {surface === 'grove' && <GroveApp />} — Studio cannot use Grove’s hooks. Put speak/mic/status in App.tsx (or a shared hook used by both).
  2. Can Grove open Settings without leaving Grove? Logo menu / Ctrl+, / About must open the Grove Settings overlay (data-testid="grove-settings"). Do not switch to Studio. Do not add extra section buttons (the Voice button was a workaround for a broken logo menu).
  3. Is the control Tauri-only? isTauri() / native pickers need an HTML fallback (already true for attach). Voice (mic, speechSynthesis, /api/voice) works on localhost WebUI.
  4. CLI: do not add voice (or other GUI-only) commands unless the owner asks.
  5. Ship the SPA to WebUI: cd desktop && npm run build, stage dist → desktop/bin/webui if that tree is used, restart serve/Desktop, hard-refresh the browser. Refresh alone is not enough.

Voice (current)

  • Settings id voice — Simple: speak-replies; TTS/STT/smart-turn auto-download on first run. Advanced: STT, speed, smart-turn. Retry only if a download failed.
  • API: /api/voice/status|settings|install|speak|transcribe. install component=all retries every missing piece.
  • Owner reason; Advanced hint for pip.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free