kylesnowschwartz

Use when writing or editing a Slack message, email, pull request body, GitHub issue, Reddit post, agenda, or doc. Enforces a direct, warm, unfilled tone and removes AI tells. Always scores the final draft and runs a self-audit pass before delivery.

Reframe code design through functional programming principles for agent-assisted development. This skill SHOULD be used when the user says "think functional", "think FP", "make this pure", "separate effects", "where should this side effect go", "this function does too much", "how should I structure this for agents", "make this easier to review", "reduce context needed", or when planning module structure, store design, or code that agents will write and humans will review. Applies FP discipline within any language to maximize agent effectiveness and human reviewability.

Use when designing AI features and the real opportunity may be perception support, not delegated conversational work.

Lift-and-shift port of a repository, library, API, protocol, or other software artifact to a different language, runtime, or platform, with the original source available as a reference. This skill SHOULD be used when the user says "port from X to Y", "lift and shift", "rewrite in Go", "rewrite in Rust", "translate this codebase", "convert to TypeScript", "language migration", "rewrite in another language", "carry over the algorithms", "borrow techniques from", "dirty room", "dirty-room design", "sc-dirty-room", or wants to reimplement an existing artifact while studying its internals to preserve algorithms, data structures, or idioms worth keeping. NOT for legally-constrained reimplementation — use /sc-clean-room when copyright isolation matters.

Audit and improve project memory files (CLAUDE.md, AGENTS.md, .claude.local.md) — assess against a quality rubric, then apply additions and removals. This skill SHOULD be used when the user asks to audit, improve, edit, fix, tighten, rewrite, or update a memory file, or to check whether one is too long, stale, or bloated.

Clean-room reimplementation of a repository, library, API, protocol, or other software artifact. This skill SHOULD be used when the user wants to create a functionally equivalent implementation of an existing artifact without copying its internal design or expression. NOT for refactoring existing code.

This skill SHOULD be used for structured extraction or batch queries against JSON (use jq), YAML (use yq), or Markdown (use mq), and for advanced text search with ripgrep flags or pipe composition (use rg).

Use when multiple plausible approaches must be generated, tested, and compared against constraints before the user chooses.

Claude Code Hero Level 1: The Map Room -- explore the project's .claude/ directory and document what lives there

Claude Code Hero Level 2: The Tome of First Instructions -- create .claude/CLAUDE.md with real personal instructions

Claude Code Hero Level 0: The Threshold -- learn the basics of talking to Claude Code before entering the dungeon

Claude Code Hero Level 9: The Artificer's Workshop -- create a minimal Claude Code plugin (capstone)

Claude Code Hero progress report -- shows the learner's quest log with completed, current, and locked quests

Claude Code Hero Level 3: The Goblin Lair of Commands -- create a custom slash command in .claude/commands/

Claude Code Hero Level 4: The Warden's Keys -- configure permission rules in .claude/settings.json

Claude Code Hero Level 5: The Enchanted Inscription -- create a path-scoped rule in .claude/rules/

This skill should be used when the user asks to "QA browser changes", "verify a web UI", "test the browser flow", "check the page works", "validate the dev server", or wants end-to-end behavioral verification of web pages or web apps. Drives a real browser to navigate, snapshot, interact, and capture evidence — supports both agent-browser (preferred) and playwright-cli, picking whichever is installed.

This skill should be used when the user asks to "QA a CLI tool", "verify a command-line program", "check the binary's output", "validate exit codes", "compare against a golden file", or wants end-to-end behavioural verification of command-line tools. Drives a binary with representative inputs, captures stdout / stderr / exit code as separate evidence channels, asserts via golden-file comparison with volatile-field redaction.

This skill should be used when the user asks to "verify database state", "check what's in the database", "assert DB rows after the action", "validate the migration", or wants behavioural verification of database side effects. Snapshots database state before the action, exercises the system, snapshots after, and diffs structurally — ignoring volatile fields the spec does not assert. Used by primary-surface oracles (http-qa, cli-qa, library-qa) when a card asserts side-effect behaviour.

This skill should be used when the user asks to "QA an HTTP endpoint", "verify an API", "check the API behaves", "drive the API", "validate a route", or wants end-to-end behavioural verification of HTTP/JSON services. Drives a real running service with curl + jq, asserts on status / shape / headers / timing, captures the full request-response transcript as evidence, and distinguishes spec violations from flake.

This skill should be used when the user asks to "QA a library", "verify the package", "check the API behaves", "exercise the module", or wants end-to-end behavioural verification of an importable library or package (Go, Ruby, TypeScript, etc.). Writes a one-shot consumer program in scratch space, runs it against the library under test, observes structured output, and judges whether the behaviour matches the card's spec.

This skill should be used when the user asks to "verify a log line appears", "wait for the log message", "check the audit log", "assert async behaviour from the log", or wants behavioural verification of asynchronous side effects observable only through a log file or stream. Tails a log file with bounded waiting, asserts pattern presence with history-vs-tail semantics and occurrence counts, fails fast when the log stops growing. Used by primary-surface oracles (http-qa, cli-qa, library-qa) when a card asserts log-emission behaviour.

Break down work into board cards for ralph-ban orchestration. This skill should be used when the user has a plan, design doc, or clear requirement to decompose into epics and tasks with EARS specs. Triggers on "plan this", "create cards", "break this down", "decompose into tasks", "rb-planning", "put this on the board", or when a design doc from /rb-brainstorm needs to become actionable work. Creates cards via bl CLI with specs, priorities, dependencies, and epic grouping.

This skill should be used when the user asks to "QA changes", "verify this works", "test the build", "check if this runs", "validate changes in tmux", or wants end-to-end verification of code changes by running builds, tests, and applications in tmux.

Delegate a coding task to a visible Codex agent running in a tmux pane via TCM, driven end-to-end by workflow scripts (spawn → watch → result as one Workflow call), instead of a backgrounded /codex:rescue job. Use for implementation work that changes the tree (MO-002 routing: repo-gets-changes → visible pane), when Kyle asks to "watch" a delegation, or for parallel worktree delegations. NOT for read-only investigation/review/second opinions whose output Fable consumes directly — use /codex:rescue for those. Headless or tmux-less contexts: fall back to /codex:rescue.

Close the finished TCM codex delegate tmux windows left over from tcm-delegate-codex runs. Use ONLY when Kyle explicitly asks to tidy up / clean up / close the delegate windows (or "TCM codex shells"). Do NOT invoke proactively just because a delegation finished — tcm-delegate-codex leaves windows open until Kyle says otherwise. Scoped to the current tmux session by default; --all-sessions widens it. Requires the TCM server on localhost:7391.

MUST use this skill when the user mentions plugins, hooks, skills, commands, agents, MCP servers, LSP servers, marketplaces, plugin.json, SKILL.md, .mcp.json, .local.md, allowed-tools, frontmatter, PreToolUse, PostToolUse, SessionStart, event schemas, prompt-based hooks, plugin settings, output styles, headless mode, CI mode, CLAUDE_PLUGIN_ROOT, auto-discovery, or any aspect of extending Claude Code. Use INSTEAD OF answering from general knowledge. Also use when writing hooks for settings.json, configuring MCP servers outside plugins, or comparing skills vs commands, since this skill contains the authoritative reference for these Claude Code extension mechanisms.

This skill should be used when the user asks to "sync with upstream", "update from Claude Code", "check for Claude Code changes", "update plugin-dev docs", "sync with latest CC release", "what changed in Claude Code", "audit against upstream", "bring docs up to date", "check upstream changelog", "sync plugin-dev with Claude Code", "update compatibility", or needs to bring plugin-dev documentation current with recent Claude Code releases.

This skill should be used when implementing slash commands that execute without Claude API calls. Use when: adding a new /bumper-* command, understanding why commands return "block" responses, debugging UserPromptSubmit hooks, or learning the pattern for instant command execution. Keywords: UserPromptSubmit, block decision, hook response, slash command implementation.

Kyle's reading library and book engine. Use for ANYTHING book-related: getting a recommendation or "what should I read next / something like X / a cozy short read"; retrieving or downloading a book and sending a copy to his Kindle; adding a book he's read to his reading-list library; or maintaining/inspecting the library (enrich covers, rebuild recommendations, show his taste profile). Drives the local, keyless `shelf` engine — never invents titles, ISBNs, or book facts.

Send a one-shot letter to agents working in another repo on this machine, delivered when their next session starts. Use when the user says "send a letter to <repo>", "leave a note for the <project> agents", "tell the <other repo>'s agent about this", or wants a point picked up next time someone works in another local project.

Jira integration via jira-cli. Use when: searching issues, viewing issue details, creating issues, transitioning status, adding comments, logging work, managing sprints, managing boards, linking issues, formatting descriptions with wiki markup, converting Markdown to Jira format, or using bug/feature templates. Keywords: jira issue, jira ticket, jira format, wiki markup, jira syntax. Requires jira-cli installed via `brew install jira-cli`.

This skill should be used when the user mentions the Wasteland, HOP federation, DoltHub federation, dolt, rigs, stamps, wanted board, completions, MVR protocol, or HOP protocol. Also when they want to join a wasteland, browse available work, post tasks, claim work, submit completions, check reputation, or create a new wasteland.