ChrisTowles

Launch the blog post creation team — interviewer, researcher, voice reviewer, QA checker in parallel tmux panes

Ensures blog content matches the authentic, concise, experience-driven tone. Focuses on personal learning narratives, not authority positioning. Expert-to-expert voice that respects reader time.

Interviews the user about a blog post topic. Asks questions via SendMessage to gather scope, opinions, key points, and personal experiences for the draft.

Reviews blog post drafts for brand voice consistency. Applies blog-content-architect personality and brand-voice skill rules. Reports issues to leader.

Generate hero images for blog posts — analyzes content, crafts prompt, calls Gemini API, saves image, updates frontmatter. Replaces blog-image-prompt and blog-image-creator.

Brand Voice Skill — Chris Towles

Background Checks — fraud detection and consistency verification for home loan applications

Loan Market — market conditions and deal structure analyst for home loan applications

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.

Use towles-tool (`tt`) CLI for journaling and worktrees. Use when asked about "tt commands", "daily notes", "meeting notes", or worktree management.

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".

Take a desktop screenshot for visual validation. Use this skill when you need to verify UI changes, check the agentboard sidebar, validate TUI rendering, or confirm any visual state on screen. Trigger when the user says "take a screenshot", "show me the screen", "check the UI", "validate visually", or when you need to self-validate a visual change.

Set up a multi-clone repo folder structure with 5 slot clones for parallel Claude Code agent work. Use when the user says "set up multi-repo", "setup slots", "create repo slots", or wants to create the same folder pattern used for towles-tool-repos.

Opinionated TypeScript patterns for production-grade code — focused on type composition, Zod integration, and patterns Claude wouldn't suggest by default. Use this skill whenever writing new TypeScript files, reviewing TypeScript code, setting up TypeScript projects, refactoring TypeScript, or when the user asks about TypeScript patterns, conventions, or idioms. Also trigger when the user mentions types, interfaces, generics, Zod schemas, discriminated unions, branded types, or TypeScript configuration. Applies to .ts and .tsx files.