菜单
Use towles-tool (`tt`) CLI for journaling and worktrees. Use when asked about "tt commands", "daily notes", "meeting notes", or worktree management.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Build, run, and screenshot the Towles Tool desktop app (Tauri 2 + WebKitGTK shell). Use when asked to run, start, build, test, or screenshot the app, or to launch it for the user to check.
Onboard a git repo onto tt worktree tasks — unique per-task ports, env templating, and Claude Code worktree hooks. Use when the user asks to "onboard this repo for tasks", "set up tt tasks", "make worktrees get unique ports", "wire the worktree hooks", or when a repo's tasks render an empty `.env` and it needs per-task ports. Requires the `tt` CLI on PATH.
Visual design language ("Folder Rail" style) for new or restyled UI in the Towles Tool desktop app (apps/client) — color tokens, agent-status semantics, folder/session hierarchy, spacing, glyphs, Tailwind recipes. Use when adding a new screen/component, restyling an existing one, or the user asks about the app's look, the "folder rail", status dots/colors, or the repo→folder→session hierarchy. Not needed for logic-only changes to already-styled components.
Project recipe for driving the real Tauri shell (apps/client) to verify a UI/IPC change end-to-end, rather than only running tests/typecheck. Use as the handle for the generic verify skill in this repo.
General-purpose usability/UX design rules for building or reviewing any UI — matching user mental models, reducing decisions, visible affordances, forgiving forms, actionable errors, and a pre-ship usability checklist. Use when designing a new screen or flow, adding a confirmation dialog, writing button/error copy, deciding whether something needs a setting, or reviewing a UI for usability before shipping. This governs behavior and flow; for this app's specific color/typography/layout system see the folder-rail-ui skill instead.
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
| name | towles-tool |
| description | Use towles-tool (`tt`) CLI for journaling and worktrees. Use when asked about "tt commands", "daily notes", "meeting notes", or worktree management. |
| user_invocable | true |
Personal CLI toolkit. Binary: tt
Config: ~/.config/towles-tool/towles-tool.settings.json
tt journal daily-notes # Weekly file, daily sections (alias: tt today)
tt journal meeting # Meeting notes
tt journal note # General notes
tt journal jot "text" # Append a timestamped bullet to today's note
tt journal list # Recent entries
tt journal search TEXT # Search entries
tt task init # Onboard a repo: template, gitignore .env, worktree hooks, primary .env
tt task new "Do the thing" --repo myrepo -b feat/thing # board task + branch-named worktree + rendered .env
tt task new "Do the thing" --repo myrepo --goal "..." # goal shown on the Board card under the title
tt task ls # Fleet: main checkout + tasks, branch, dirty, ports
tt task env <name> # (Re)render a checkout's .env (or `primary`) — idempotent, keeps claims
tt task ports # Repo's port picture: every checkout's claims + registry, each probed (`--probe <port>` for one)
tt task rm <name> # Guarded removal
tt task clean # Remove every merged/gone task
rm/clean run a task's declared TT_TASK_TEARDOWN command (from its
rendered .env) against the worktree right before removing it — for
whatever a task's TT_TASK_SETUP started that the built-in docker
compose/container sweep can't find on its own (e.g. a compose stack not
named after the task). Unset by default; declare it per-repo in
.env.example.