Topic: homebrew
42 skills in this topic.
-
cross-platform
Cross-platform development patterns for macOS, Windows, and Linux
mylee04/code-notify 180
-
shell-scripting
Shell scripting best practices for cross-platform CLI tools
mylee04/code-notify 180
-
tokf-run
Compress verbose CLI output with tokf before returning results. Activates for git, cargo, npm, docker, go, gradle, kubectl, and other supported commands.
mpecan/tokf 147
-
tokf-filter
This skill should be used when the user asks to "create a filter", "write a tokf filter", "add a filter for <tool>", "how do I filter output", or needs guidance on tokf filter step types, templates, pipes, or placement conventions.
mpecan/tokf 147
-
tokf-discover
Find missed token savings in Claude Code sessions and create filters for unfiltered commands
mpecan/tokf 147
-
tokf-discover
Find missed token savings by scanning AI coding session files for commands that ran without tokf filtering.
mpecan/tokf 147
-
canvas-design
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
nicksp/dotfiles 434
-
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
nicksp/dotfiles 434
-
algorithmic-art
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
nicksp/dotfiles 434
-
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
nicksp/dotfiles 434
-
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
-
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
-
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
-
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-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-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
-
tooling-linear-cli
Manage Linear issues from the command line using the linear cli. This skill allows automating linear management.
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
-
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
-
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
-
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
-
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-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-commit
Suggest a conventional commit message for the current staged/unstaged changes. Use when the user asks to commit, wants a commit message, says "commit", or wants to stage and commit code changes.
jasonraimondi/dotfiles 18