kevinreber

Adopt Fable-class working discipline for this session — outcome-first communication, finish-the-turn autonomy, parallel tool use, faithful reporting. Use when the user says "/fable", "fable mode", "act like fable", or wants a smaller model (Opus, Sonnet) to work with the discipline of a Mythos-class model. Also invocable from other skills as a style preamble for long or high-stakes tasks.

Full workday recap across all tools — Jira, GitHub, Slack, Confluence, Google Docs, and Claude Code activity. Stores all data in SQLite with Turso sync for remote access. For Claude-only activity tracking, use /daily-review-v2 instead.

Claude Code activity tracking with SQLite/Turso storage — standup, weekly rollups, project reports, brag doc, friction tracking, goal tracking, heatmap, export. Data syncs to Turso for remote access. For full workday recap across all tools, use /daily-recap-v2 instead.

Transform a work-specific or company-specific skill/config into a generic, portable version. Replaces proprietary tools, internal URLs, and company references with generic equivalents while preserving the useful patterns and structure. Use when porting a work skill to the public config repo.

Sync ~/.claude/ global configs into this repo, sanitizing work-specific content (LinkedIn plugins, Captain MCP, work email, internal URLs). Use when the user wants to refresh this repo from their global Claude configs, pull in newly added skills/commands, or update sanitization rules. Two-pass flow with diff review before commit.

Deep discussion mode. No code changes, no file edits, no commands — pure thinking, exploration, and idea bouncing. Use when you want to explore a concept, design something, debate tradeoffs, or just think out loud. Claude will push back, ask questions, and present alternatives. Changes only happen if you explicitly say so.

Generate a smart commit message from staged or unstaged changes and create a commit. Use when the user wants to commit their work with a meaningful message.

Provide a deep, educational explanation of code. Use when the user wants to understand how code works, why it's designed a certain way, or learn about patterns and concepts used.

Create new REST API endpoints following project patterns. Use when adding API routes, creating actions/loaders, implementing CRUD operations, or when the user mentions API, endpoint, action, or REST.

Create React components using shadcn/ui patterns. Use when building UI components, forms, dialogs, buttons, or when the user mentions component, UI, form, dialog, modal, or styling.

Write Prisma database queries and server functions. Use when creating database operations, queries, migrations, or when the user mentions database, Prisma, query, model, or schema.

Write unit tests with Vitest and E2E tests with Playwright. Use when creating tests, writing test cases, setting up test fixtures, or when the user mentions test, testing, vitest, playwright, or coverage.

Create Remix routes with loaders and actions. Use when creating new pages, implementing route loaders/actions, handling navigation, or when the user mentions route, page, loader, action, or navigation.