ReddRadar
Topic: configuration-management
54 skills in this topic.
-
polish
Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
AkaraChen/aghub 176
-
tooling-linear-cli
Manage Linear issues from the command line using the linear cli. This skill allows automating linear management.
jasonraimondi/dotfiles 18
-
typescript-better-auth-best-practices
Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.
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
-
design-copywriting
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
jasonraimondi/dotfiles 18
-
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
-
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
-
typescript-advanced-types
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
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-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
-
sync-linear-to-plan
Pull current state from Linear back into local ./plans/{slug}/ YAML files — updates status, assignee, priority, labels, and points. Also imports new issues created directly in Linear. Use when user says "pull from linear", "sync from linear", "update plan from linear", or wants local files to reflect Linear's current state.
jasonraimondi/dotfiles 18
-
sync-plan-to-linear
Sync a local ./plans/{slug}/ directory to Linear — creates or updates projects, documents, issues, and dependencies. Writes Linear IDs back to local YAML for idempotent re-syncs. Use when user says "sync to linear", "push to linear", "publish plan", or wants to mirror local plan state in Linear.
jasonraimondi/dotfiles 18
-
testing-tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
jasonraimondi/dotfiles 18
-
testing-vitest
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
jasonraimondi/dotfiles 18
-
tooling-agent-browser
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 requiring programmatic web interaction.
jasonraimondi/dotfiles 18
-
design-an-interface
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
jasonraimondi/dotfiles 18
-
tooling-pnpm
Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces, or managing dependencies with catalogs, patches, or overrides.
jasonraimondi/dotfiles 18