rvanbaalen
- 33 skills
- 0 followers
- 5 hours ago last updated
- ▌ Setup 2 · rvanbaalenOnboarding and configuration for the co-founder plugin. Use when the user needs to set up or reconfigure their co-founder workspace. Auto-invoked by the orchestrator on first run. Safe to re-run — detects existing config and asks before changing anything.
- ▌ Review 2 · rvanbaalenReview current state, progress, and priorities. Use when the user wants an overview of where things stand, or when the cofounder agent needs to assess progress. Surfaces insights and flags issues proactively.
- ▌ Pm · rvanbaalenProject manager — your delivery-focused partner for deadlines, estimates, and accountability. Invoke with /pm to start a session.
- ▌ Cpr · rvanbaalenUser-invokable only via /cpr. Commit, Push, and Release in one command. Commits all changes as non-interactive micro-commits (conventional commits), pushes to remote, runs a review-and-fix loop on the pushed changes, then handles the full release-please cycle: waits for the PR, merges it, and monitors the release workflow to completion. Do NOT auto-trigger this skill.
- ▌ Plan · rvanbaalenDefine milestones, tasks, and estimates. Scales from a quick task to a full project breakdown. Always attaches deadlines, always asks the user for estimates, and journals all changes.
- ▌ Setup · rvanbaalenProject onboarding and configuration for the PM plugin. Sets up project context, deadlines, and data scaffolding. Auto-invoked by the orchestrator on first run. Safe to re-run.
- ▌ Review · rvanbaalenOn-demand progress analysis. Timeline health, estimation accuracy, blocker history, anti-pattern report, overrule analysis, and recommendations.
- ▌ Browse · rvanbaalenFast headless browser for QA testing and site dogfooding. Navigate URLs, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when asked to "open in browser", "test the site", "take a screenshot", "dogfood this", or to verify a feature or deployment.
- ▌ Commit · rvanbaalenCommit changes using micro commits with conventional commit messages. Analyzes git diff, groups related files, and proposes commits for approval. Supports interactive and non-interactive (background) modes. Use when the user wants to commit their changes.
- ▌ Spar · rvanbaalenStress-test an idea or initiative through the business filter. Use when the user brings an idea, proposal, or "what if" to evaluate. Also invoked by the cofounder agent when it detects sparring context.
- ▌ Session End · rvanbaalenEnd-of-session wrap-up. Reads the journal to reconcile structured files, computes actual durations from timestamps, and dispatches background sub-agents for file updates.
- ▌ Reprioritize · rvanbaalenReshuffle tasks and priorities when stuck or drifting. Identifies the critical path and parks non-essential work to protect deadlines.
- ▌ Session Start · rvanbaalenBeginning-of-session check-in. Shows timeline health, validates alignment with the plan, and sets session intent. Writes SESSION_START to the journal.
- ▌ Status Report · rvanbaalenGenerate an export-ready status summary for clients, team leads, standups, or personal logs. Reads all state files and journals, formats for the target audience.
- ▌ Onboard · rvanbaalenBusiness intake conversation that grounds the co-founder in the actual business. Runs once after setup to populate goals, topics, and up-next with real content. Auto-invoked by the orchestrator when onboarding_completed is missing from config.
- ▌ Drill Me · rvanbaalenUse whenever the user has a plan, spec, RFC, ticket, design doc, or rough idea they want stress-tested before code is written. Triggers on "drill me", "interview me", "interrogate this plan", "stress test this", "what am I missing", "make sure we're aligned", "poke holes in this", "drill into this", "before I build this..." with an idea attached, or any time non-trivial work is about to start and pre-implementation alignment matters. Walks the design tree one branch at a time, asks one opinionated question per turn with a recommended answer, and explores the codebase instead of asking when the answer is already there. Continues until shared understanding is reached. Use this even when the user doesn't explicitly invoke the skill, as long as the situation matches — pre-implementation drilling is undertriggered by default.
- ▌ Teamwork · rvanbaalenRun a task with an agent team. Fable lead writes the spec and orchestrates. Build mode is an XP pair (xp-navigator, xp-driver, optional xp-ux and xp-senior) with an early draft PR; review mode fans out xp-reviewer teammates over a PR with distinct lenses and cross-verification. Pragmatic, capped review rounds. Use when the user invokes /teamwork for an issue, a feature, a PR to finish, or a PR to review.
- ▌ Check In · rvanbaalenRun a cadence-based check-in session (daily, weekly, monthly, or quarterly). Use when the user wants to check in, or when the cofounder agent detects a check-in session. Drives the conversation — don't wait for the user to set the agenda.
- ▌ Cofounder · rvanbaalenBusiness co-founder — your critical-thinking partner for prioritization, strategy, and accountability. Use when you want to check in, spar on ideas, review progress, or do focused business work. Type /cofounder to start a session.
- ▌ Make Issue · rvanbaalenCreate a new GitHub issue with guided template, type, and label selection. Gathers repo metadata, suggests labels, writes a well-structured issue body, and asks for confirmation before submitting.
- ▌ Action Brief · rvanbaalenCreate a scoped action brief from the current conversation. Use when a conversation produces something actionable that needs to be captured as a brief. Invoked by the cofounder agent or other skills when actions emerge.
- ▌ React Query · rvanbaalen bundleTanStack Query v5 skill with three modes — code review, v4→v5 migration assistance, and coding guidance while writing v5 code. Trigger whenever code imports from `@tanstack/react-query` or `@tanstack/react-query-devtools`, or uses `useQuery`, `useMutation`, `useSuspenseQuery`, `useSuspenseQueries`, `useSuspenseInfiniteQuery`, `useInfiniteQuery`, `useQueries`, `useMutationState`, `queryOptions`, `skipToken`, `QueryClient`, `QueryClientProvider`, `QueryCache`, `MutationCache`, or `HydrationBoundary`. Also trigger for: auditing React data fetching code, replacing `useEffect`/`useState` fetching patterns, implementing cache invalidation, optimistic updates, prefetching, infinite scroll or pagination, upgrading from React Query v4 to v5, Suspense integration, MSW testing setup for React Query, and authentication/token-refresh wiring around queries. When in doubt whether this skill applies to React data management code, use it.
- ▌ Disk Cleanup · rvanbaalen bundleMulti-step macOS disk-space cleanup that runs identify → propose → execute. Manual-only: invoke explicitly via /disk-cleanup. Frees space without losing data — covers caches, dev tooling (Docker, Node/nvm, Xcode & iOS simulators, Android SDK, Gradle, package managers), VMs, Ollama models, orphaned data from uninstalled apps, and full app uninstalls. Categorizes every candidate by safety tier, confirms anything that isn't pure cache, and thins Time Machine local snapshots last so the freed space is actually realized.
- ▌ Version Bump · rvanbaalenChecks for changed plugin/skill files in marketplace projects and suggests semver version bumps before pushing. Use this skill whenever the user wants to push changes (git push, "push this", "push to remote") and the working directory contains a .claude-plugin/marketplace.json file — even if the user doesn't mention versions. Also trigger when the user explicitly mentions version bumping, releasing plugins, or preparing marketplace updates.
- ▌ Open Markdown · rvanbaalenOffer to open markdown documents in mdreader after writing them. Trigger this skill whenever you write or create a markdown file that is a plan, spec, design document, architecture doc, implementation guide, proposal, RFC, or any substantive document meant to be read (not just a config snippet or small edit). Also trigger when the user asks to "open", "view", or "preview" a markdown file. Do NOT trigger for trivial edits to existing files (like fixing a typo in a README), code comments, or CLAUDE.md updates.
- ▌ Driverjs Guide · rvanbaalenComplete reference for implementing Driver.js (driver.js) product tours, element highlighting, onboarding flows, and contextual help overlays. Use this skill whenever the user mentions "driver.js", "driverjs", "product tour", "onboarding tour", "guided tour", "element highlighting", "walkthrough", "feature introduction", "spotlight overlay", or asks to build step-by-step user guides, interactive walkthroughs, or highlight-and-explain UI flows in web applications. Also trigger when the user wants to add tooltips that walk users through a page, create async/dynamic tours, or implement "turn off the lights" focus effects. Do NOT use for unrelated tooltip libraries (Tippy.js, Floating UI) or for general CSS overlay questions that don't involve guided tours.
- ▌ Lottie Animator · rvanbaalen bundleGenerates professional Lottie animations from static SVGs. Replaces After Effects for motion graphics. Use when the user asks to: animate logo, create lottie, svg animation, motion graphics, wiggle animation, bounce effect, rotate animation, pulse effect, entrance animation, loading animation, loop animation, icon animation, character animation, morphing, path drawing, trim path, walking animation, run cycle, walk cycle, frame-by-frame animation, sprite animation. Supports advanced bezier curves, shape modifiers, parenting, mattes, morphing, character rigs, and professional frame-by-frame animation techniques.
- ▌ Use Agentvision · rvanbaalen bundleControl the user's real macOS screen via the `agent-vision` CLI — session management, element targeting, and UI interaction on live windows. Triggers: user says "look at my screen", "use agent-vision", "the app/browser/simulator is open", "take a screenshot of my screen", "fill this form" (when app is already open), "check the UI", "watch the browser", "navigate to" (in an open app), "scroll through", "click on" (in a visible window), "I have X open", visual QA of running applications, iOS Simulator or Android emulator interaction, before/after visual comparison of live UI, or any task requiring real screen capture and control. NOT for: headless browser testing, Playwright/Puppeteer scripts, code-only reviews, file-based screenshots, or building screen capture features.
- ▌ Cloudflare Deploy · rvanbaalenSet up and deploy Astro websites to Cloudflare Workers with custom domains. Use this skill when the user wants to deploy a site to Cloudflare, set up Cloudflare Pages/Workers, configure wrangler.toml, add a custom domain, fix deployment issues, troubleshoot DNS for a Cloudflare-hosted site, or verify a deployment is working. Also use when you see @astrojs/cloudflare, wrangler.toml, or .workers.dev in the project.
- ▌ Design Principles · rvanbaalen bundleTrigger this skill whenever the user wants to design, review, critique, or improve a user interface, screen, flow, component, or product experience — including mockups, prototypes, web/app UI, and design feedback. Use it when the user says things like "review this design", "is this good UX", "help me design a screen/flow", "what's wrong with this interface", or asks for design direction. Do NOT trigger for purely backend, data, or non-UI work.
- ▌ Time Registration · rvanbaalenSummarize recent git work for time registration. Use when the user asks what they worked on, needs a time log, wants a work summary, asks about today's/yesterday's/last week's work, or invokes /time-registration:time-registration. Accepts an optional time period argument (defaults to today).
- ▌ Make Issue Comment · rvanbaalenPost a structured investigation/fix comment on the active GitHub PR capturing findings, root cause, proposed fix, and a progress checklist — and later update progress or mark the comment resolved. Proactively invoke whenever an investigation or debugging session on a PR branch has produced a concrete root cause plus a fix plan (even if the user hasn't asked yet) — the skill's first step is to *propose* posting the comment via AskUserQuestion, so firing it speculatively is cheap. Also invoke on explicit triggers like `/make-issue-comment`, "post this as a PR comment", "file these findings on the PR", "update the PR comment", or "mark that comment as resolved".
- ▌ Comment Conventions · rvanbaalen bundleLanguage-agnostic code commenting and docblock conventions. Trigger on every source-code Edit/Write in any language (JS/TS, Python, PHP, Ruby, Go, Rust, Java, Kotlin, Swift, C/C++, C#, Elixir, Lua, Shell, etc.) — even when the user has not mentioned comments, docblocks, JSDoc/TSDoc/PHPDoc, docstrings, or documentation. Governs every comment authored or modified, every new function/method/class/component (which must get a compliant docblock), every inline comment (which must stay terse — no prose walls, no business-logic essays, no "step 1 / step 2" narration in the code path), and any non-compliant docblock encountered in the file being edited (which must be fixed in place — no need to ask first, except when the existing docblock is unusually long and clearly intentional, in which case leave it alone). Apply to all code authoring across all languages, every time source code is touched. When in doubt whether this skill applies to a code edit, invoke it. Skip only for non-code files (JSON/YAML/TOML configs, mar