Deep codebase exploration to fully understand the current project before starting work. Use this skill whenever the user says "onboarding", "onboard", "get familiar", "learn the codebase", "understand this repo", "context load", or at the start of a session when the user wants Claude to be fully prepared to work on the project. Also use when switching to an unfamiliar part of the codebase.
Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
Audit a ralphex/farm implementation plan (docs/plans/*.md) for self-containment and task concreteness before running it through ralphex or queuing it on ralphex-farm. ralphex runs every task and review in a FRESH session that re-reads only the plan (plus the committed repo and a progress log), so anything that tells the agent to "go read elsewhere", "match 1:1 with an external codebase", or just names a big outcome without saying how to build it silently wastes huge effort and may never converge. Fans out parallel auditor agents that check the plan against rules from real farm failures and returns a farm-ready / fix-these verdict. Use whenever a ralphex plan was just written or is about to be executed or queued - "audit this plan", "check my plan before the farm", "is this plan farm-ready", "review the plan before ralphex", or right after /ralphex-plan or /planning:make and before creating a farm ticket. Do NOT use to create plans (that is ralphex-plan) or operate the farm (that is ralphex-farm).
Cross-repo GitHub radar - a personal snapshot of the open pull requests and issues that involve you, run from any directory (account-wide, not tied to the current repo). Covers your own repos (every open PR/issue, any author) plus anywhere you are involved on other people's repos (authored, assigned, mentioned, or review-requested). Use this whenever the user wants a GitHub overview or status, asks what PRs or issues need their attention, what is waiting on them, what they have open on GitHub, what they might be forgetting, before standup, or when catching up after time away - including phrasings like "github radar", "my open PRs", "anything waiting on me on github", "what did I leave open", even if they don't name a specific repo. Also supports an optional single-repo scope - when the user names one repository ("github radar for turtle-hub", "what's open in pkarpovich/tuclaw", "PRs and issues in <repo>"), pass that repo and the report covers only it.
Work with ralphex-farm: an autonomous executor that polls Linear, picks up Todo issues whose description carries a `<!-- ralphex-farm -->` YAML block (repo + plan + branch, optional mode), runs ralphex against the named plan inside Docker, and opens a PR. Invoke whenever the user wants to: create a Linear ticket for a plan ("create a ralphex farm task", "add task for plan", "queue plan to the farm"), re-run or recover a failed task ("re-run", "recover", "review only", "move back to Todo"), add a new repository to the farm, trigger an immediate sync, debug why a ticket was not picked up, or answer questions about how the farm works. Also trigger on any mention of the `<!-- ralphex-farm -->` metadata block, repos.yaml in the farm context, `/var/ralphex/...` host paths, the farm's `/api/sync` or `/api/repos` endpoints, or Claude plugin provisioning in the farm.
Go 1.25+ development standards and coding conventions. Use when writing, reviewing, or refactoring Go code. Triggers on Go file creation/editing, code reviews, architecture decisions, testing strategies, error handling patterns, concurrency, or when user asks about Go best practices.
End-to-end preparation of a new Lego Cubes podcast episode (Pavel's Russian-language podcast about content + dev projects). Walks through 7 stages with check-ins — collect Content bullets from Tuclaw/Podcast files, fill the episode note, suggest an episode title in the established poetic style, find IMDB/Steam/Goodreads links, produce a LEGO-style cover image prompt for Nano Banana Pro, after the recording publish the .mp4 + .jpg + .nfo bundle to the NAS for Plex/Kodi, and finally archive the per-content impression files into References/. Trigger on any mention of preparing, assembling, filling, publishing, or archiving a Lego Cubes episode — including phrases like "prepare episode 30", "Lego Cubes 30", "the next episode", "fill out the episode note", "I recorded the podcast", "put it on the NAS", "make the nfo", "faststart the recording", "move impressions to References", "archive the episode", or a bare episode number with podcast context. Pavel typically writes these requests in Russian — same triggers app
Modern Python 3.13+ development standards and best practices. Use when writing, reviewing, or refactoring Python code. Triggers on Python file creation/editing, code reviews, architecture decisions, async patterns, type hints, testing strategies, or when user asks about Python best practices.