Sponsored by

Find leads on Reddit on auto pilot

Topic: homebrew

42 skills in this topic.

design-state-machine-design Statechart and state machine modeling for lifecycle and behavior specification
jasonraimondi/dotfiles 18
frontend-css-best-practices Produce idiomatic, browser-aware modern CSS with progressive-enhancement fallbacks for CSS, Tailwind, and Svelte styling tasks. Use for layout, spacing, typography, color/theming, animation, responsive/container-query work, selector/specificity cleanup, and interactive UI styling. Do not use for non-styling business logic or design critique without code edits.
jasonraimondi/dotfiles 18
frontend-react-doctor Run after making React changes to catch issues early. Use when reviewing code, finishing a feature, or fixing bugs in a React project.
jasonraimondi/dotfiles 18
frontend-svelte5-best-practices Svelte 5 runes, snippets, SvelteKit patterns, and modern best practices. Use when creating, editing, reviewing, or refactoring .svelte components, .svelte.ts/.svelte.js modules, or SvelteKit applications. Triggers on: runes ($state, $derived, $effect, $props, $bindable, $inspect), snippets ({#snippet}, {@render}), event handling, SvelteKit data loading, form actions, Svelte 4→5 migration, TypeScript props, generic components, SSR state isolation, performance, or component testing.
jasonraimondi/dotfiles 18
implement-issue Implement one or more plan issues end-to-end with proper branching, testing, and status tracking via YAML workflow states. When issues are synced to Linear, updates both local YAML and Linear.
jasonraimondi/dotfiles 18
implement-prd Work through a PRD's issues in dependency order using YAML workflow states, AFK/HITL routing, and proper status tracking. When synced to Linear, updates both local YAML and Linear.
jasonraimondi/dotfiles 18
iot-homeassistant-best-practices Home Assistant automation, helper, script, and device control best practices. Enforces native HA constructs over Jinja2 templates and safe refactoring workflows. TRIGGER WHEN: - Creating or editing HA automations, scripts, or scenes - Choosing between template sensors and built-in helpers - Writing triggers, conditions, waits, or selecting automation modes - Setting up Zigbee button/remote automations (ZHA or Zigbee2MQTT) - Renaming entities or migrating device_id to entity_id - Agent uses Jinja2 templates where native constructs exist - Agent uses device_id instead of entity_id - Agent picks wrong automation mode (e.g., single for motion lights)
jasonraimondi/dotfiles 18
meta-optimize-skill-md Reviews and improves existing skills by auditing clarity, trigger quality, workflow completeness, and instruction density, then rewriting SKILL.md with minimal-drift improvements. Use when user asks to improve a skill, review SKILL.md, optimize skill prompts, tighten skill descriptions, or refactor skill documentation.
jasonraimondi/dotfiles 18
write-a-skill Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
jasonraimondi/dotfiles 18
planning-interview-me Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "interview me".
jasonraimondi/dotfiles 18
planning-prd-to-issues Break a PRD into independently grabbable issues using thin vertical slices, writing structured YAML files to ./plans/{slug}/issues/. Use when user says "break this down", "create issues", "decompose the PRD", or wants to convert a PRD into actionable work items.
jasonraimondi/dotfiles 18
planning-ralph Ralph Wiggum AI — autonomous PRD-driven development agent. Use when the user says "ralph", wants to work through issues, or wants autonomous feature implementation from a plans/ directory.
jasonraimondi/dotfiles 18
planning-review-prd Review a PRD and its issues as a principal software engineer. Checks track coverage, step quality, point limits, tdd/headed flags, missing edge cases, dependency ordering, and architectural gaps. Auto-fixes mechanical issues, asks about non-obvious concerns. Use when user says "review my plan", "review the PRD", "check my issues", or wants feedback on plans/ output.
jasonraimondi/dotfiles 18
planning-write-a-prd Create a PRD by interviewing the user, exploring the codebase, and writing a structured YAML plan to ./plans/{slug}/prd.yaml. Use when user says "write a PRD", "plan this feature", "create a plan", or wants structured project planning.
jasonraimondi/dotfiles 18
planning-write-an-issue Create a single issue by interviewing the user, exploring the codebase, and writing a structured YAML issue file. Use when user says "write an issue", "create an issue", "add an issue", or wants to define a single work item — either standalone or inside an existing plan.
jasonraimondi/dotfiles 18
doc-coauthoring Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
janbiasi/.dotfiles 5
test-driven-development Use when implementing any feature or bugfix, before writing implementation code
janbiasi/.dotfiles 5
next-best-practices Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
janbiasi/.dotfiles 5