Claude Skills by gethamster

Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \\\"open a website\\\", \\\"fill out a form\\\", \\\"click a button\\\", \\\"take a screenshot\\\", \\\"scrape data from a page\\\", \\\"test this web app\\\", \\\"login to a site\\\", \\\"automate browser actions\\\", or any task ...

Audit a feature, branch, or PR diff for analytics instrumentation coverage. Verifies that every state-changing action (server action, BullMQ processor, domain entity create/update/delete, paywall/billing transition) fires a typed `trackServerEvent` or `tracker.track*` call. Use proactively before opening a PR, during code review, or whenever a new feature is added under apps/web/app, apps/ai/src/modules, or apps/sync/src/modules. The CI gate (typed event names) prevents untyped events from sh...

Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it animate at all, what purpose, which tool, which properties, which curve and duration, how it interrupts, how it exits. Writes the implementation. Use when asked to animate something, add motion, make a component feel alive, or build a transition. For critiquing existing motion use review-animations; for auditing a whole codebase use improve-animations.

Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term (\\\"the bouncy thing when a popover opens\\\" → Pop in; \\\"the iOS rubber-band scroll\\\" → Rubber-banding). Use when the user asks \\\"what's it called when…\\\", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.

Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.

Write the current-state blueprint for a feature or system from a brief or decision artifact, capturing narrative intent, trade-offs, and consequences. Use when you need to document why something was built, how it works, and what constraints it creates.

Guides users through writing a strong method: purpose, prerequisites, steps, validation, troubleshooting.

Guides users through writing a strong routine: triggers, schedules, instructions, and action steps.

Guides users through writing a strong skill: trigger conditions, core guidance, examples, anti-patterns.

Create a new Supabase data backfill, dedup, or one-off data correction script for Hamster Studio in apps/web/supabase/scripts/. Use whenever the user asks for a backfill script, data migration script, dedup script, one-off data fix, repair job, or anything that needs to mutate production data outside of a regular schema migration. Provides a battle-tested template with dry-run-by-default safety, paginated reads, chunked writes, append-only audit logging, and auto-generated rollback SQL. Trigg...

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Decompose a compressed goal, one-liner strategy, or multi-clause mandate into a goal-framework-agnostic hierarchy: goals with measurement stories, strategies as bets, measures with leading/lagging tags, and initiatives/briefs born on a need-to-make basis. Produces testable success criteria, option matrices, a chosen solve path, sequencing, and hard constraints — without implementing unless asked.

Governs the alignment voting gate between direction and delivery. Enforces that no brief enters delivery without explicit team alignment. Use when calling for alignment, interpreting vote results, or deciding if a brief is ready for delivery.

Build terminal user interfaces with Go and Bubbletea framework. Use for creating TUI apps with the Elm architecture, dual-pane layouts, accordion modes, mouse/keyboard handling, Lipgloss styling, and reusable components. Includes production-ready templates, effects library, and battle-tested layout patterns from real projects.

BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.

Use 1000+ external apps via Composio - either directly through the CLI or by building AI agents and apps with the SDK

Make decision lineage explicit by linking product-state blueprints to decision records and marking which decisions shaped which parts of the product.

Write a longform X article announcing a method, a group of skills and routines packaged as a single approach in Hamster, such as a workflow methodology, a framework with its skills, or a bundle upgrading popular third-party skills with routines. Use this skill whenever Eyal wants an article about a method, a methodology piece, a \\\"here's our whole approach to X\\\" article, or the umbrella piece that ties existing skill and routine articles together. Requires a source pack from find-source-...

Write a longform X article announcing a routine, a skill running on autopilot in Hamster, whether it automates one of our skills or upgrades a popular third-party skill with automation. Use this skill whenever Eyal wants an article about a routine, about automating a skill, about \\\"running [skill] on a schedule\\\", or wants the follow-up piece after a skill article that introduces the automated version. Requires a source pack from find-source-material and a routine spec from create-routine...

Take a skill (ours or a popular third-party one) and design the routine that runs it automatically in Hamster, producing a complete routine spec with trigger, autonomous prompt, guardrails, and success criteria. Use this skill whenever Eyal wants to automate a skill, put a skill on a schedule, \\\"turn [skill] into a routine\\\", upgrade a popular skill with automation, or needs the routine spec that a routine article will be written about. Also use it when someone asks what a skill would loo...

Write a longform X article launching or covering a skill (a Hamster library skill, one of our own, or a popular third-party skill like show-me or /teach), in the proven format that opens with real posts proving the pain, announces the skill, tours what's inside with a visual per component, and closes with exact invocations to try. Use this skill whenever Eyal wants an article, longform post, or launch piece about a skill, says \\\"write the article for [skill]\\\", wants to cover someone else...

On brief.status = \"approved\":

Routine trigger that flags methods for review when workflows change or on a quarterly cadence.

Routine trigger that flags skills for review when conventions change or on a quarterly cadence.

Guide creating goal-linked routines that monitor health, nudge owners, and create briefs when goals drift. Enforces the closed loop: goals → routines monitor → nudges inform discovery → work informs direction. Routines nudge — they never decide. Use when creating or configuring a routine that monitors goal health or initiative status, or when a user asks to automate goal monitoring or set up alerts for drifting goals.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Get most of the value for a small fraction of the time, deliberately and with the blind spot named. Use before any expensive repeated activity — slow validation or build cycles, broad searches, large agent fan-outs, exhaustive captures, big sampling runs, reading a whole codebase — or whenever someone says this is too slow, speed it up, we need to go faster, or just give me the gist.

This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use whenever creating a brief for a NEW feature. This will add feature flag requirements into the brief

Search a codebase or UI for places that don't animate but should, and reject everything that shouldn't. Read-only; it proposes motion with exact values, it does not implement it. Use when the user asks \\\"what could be animated here?\\\" or wants to \\\"make this feel more alive\\\". For fixing existing animations, use improve-animations or review-animations instead.

Research X and Reddit for real posts, complaints, prior art, and credits to power a Hamster launch article about a skill, routine, or method. Use this skill whenever Eyal is starting an article about a skill/routine/method, asks to \\\"find posts about X pain,\\\" wants social proof for a problem, needs prior art to credit, or invokes any of the create-*-article skills (this skill is their required first phase). Also use it when evaluating whether a third-party skill is worth writing about, s...

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

Guides the now/next/later focus system for initiatives. Focus is a third dimension independent of state and health. Now must stay small (5-7 max). The routine suggests, the team decides. Use when setting or changing an initiative's focus, when the focus routine detects overcrowding or misplacement, or when reviewing focus alignment in the weekly meeting.

Stacked pull requests with GitHub's native gh-stack CLI: when to stack, how to build/submit/sync a stack, responding to mid-stack review feedback, and Hamster-specific rules (dev base, one migration per PR, merge commits). Use when a change is too big for one reviewable PR or when planning multi-wave delivery.

Create and publish safe feature branches and pull requests, including Hamster brief-aware branch names and PR links. Use for branch creation, any git commit/push, PR creation, workflow dispatch, or CI debugging.

Prevent tagging wrong GitHub users by always resolving usernames from git log or team membership before @-mentioning anyone in GitHub comments, PRs, or issues.

Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: \\\"Index this repo\\\", \\\"Reanalyze the codebase\\\", \\\"Generate a wiki\\\"

Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \\\"Why is X failing?\\\", \\\"Where does this error come from?\\\", \\\"Trace this bug\\\"

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \\\"How does X work?\\\", \\\"What calls this function?\\\", \\\"Show me the auth flow\\\"

Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \\\"What GitNexus tools are available?\\\", \\\"How do I use GitNexus?\\\"

Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \\\"Is it safe to change X?\\\", \\\"What depends on this?\\\", \\\"What will break?\\\"

Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: \\\"Rename this function\\\", \\\"Extract this into a module\\\", \\\"Refactor this class\\\", \\\"Move this to a separate file\\\"

Python evaluation framework for Hamster Studio. Use when working in packages/glass-box/ — running replay experiments, monitoring Sentry data, training classifiers, or writing tests for any glass-box module.

Guides the weekly goal review meeting: compare goals vs initiatives, prioritize newly unblocked work, assign owners. Enforces the 'one weekly meeting' principle — 30 minutes of decisions, not 45 minutes of status. Use when running a weekly goal review, planning meeting, or direction review.

Guides the construction of OGSM goals — choosing units, direction, aggregation, baseline, and target. Enforces that every measurable goal has a metric with all 5 components. Validates that the measurement story is honest (not vanity). Flags goals with no linked initiatives (unanchored goals are wishes). Use when creating or editing a goal in the OGSM framework, setting up goals or OKRs, or reviewing whether a goal is well-formed.

Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems. Invoke for goroutines, channels, Go generics, gRPC integration.

Thoroughly flesh out an idea by exploring, then asking several questions to resolve ambiguous concepts

Ad platform pixel and conversion tracking for LinkedIn and Reddit. Use when adding conversion events, modifying tracking pixels, or working with ad platform integrations.