fstermann

How-to for non-trivial UI/styling work in starlib. Use when adding or changing component visuals, layout chrome, tokens, themes, or anything touching globals.css, tailwind utilities, or files under src/components/ui/*.

Debug the live Starlib.app desktop application. Use when: diagnosing issues in the installed/bundled Tauri app, viewing sidecar logs, inspecting the webview, checking backend health, or troubleshooting the production build running from /Applications/Starlib.app.

Use when the user wants a plan to get from today's codebase to a substantially different end-state, especially when that destination is fuzzy or stated as a solution rather than an outcome. Covers refactors, migrations, re-architectures, rewrites, and large multi-step features. Trigger on "help me plan/scope this", "how should I approach", "what's the roadmap for", or a named solution ("migrate to X", "rebuild as Y") whose underlying goal is unstated. Skip single decisions, one-step changes, and plans that are already concrete.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".