rigerc

This skill should be used when the user asks to "set up agentsmesh", "initialize agentsmesh", "configure agentsmesh", "generate AI tool configs", "sync AI coding configs", "import configs to agentsmesh", "add a target to agentsmesh", "create an agentsmesh rule", "create an agentsmesh agent", "create an agentsmesh command", "create an agentsmesh skill", "configure MCP in agentsmesh", "set up hooks in agentsmesh", "share AI configs across tools", "canonical config", or mentions agentsmesh.yaml.

Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.

Task management for AI agents across context windows. Use when agents need to track work, log progress, hand off state, and maintain context across sessions. Includes workflows for single-issue focus, multi-issue work sessions, and structured handoffs. Essential for AI-assisted development where context windows reset between sessions.

This skill should be used when the user asks to "set up agentsmesh", "initialize agentsmesh", "configure agentsmesh", "generate AI tool configs", "sync AI coding configs", "import configs to agentsmesh", "add a target to agentsmesh", "create an agentsmesh rule", "create an agentsmesh agent", "create an agentsmesh command", "create an agentsmesh skill", "configure MCP in agentsmesh", "set up hooks in agentsmesh", "share AI configs across tools", "canonical config", or mentions agentsmesh.yaml.

Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Use this skill when the user is working with the `copier` CLI tool specifically — generating a project from a copier template (`copier copy`), updating a copier-managed project (`copier update`), authoring a copier template (i.e. a Git repo with `copier.yml`), or configuring `copier.yml`. Also trigger for questions about `.copier-answers.yml`, `_tasks`, `_exclude`, or other copier-specific settings. Do NOT trigger for general Jinja2 templating, Flask/Django/Ansible templates, or other tools that happen to use Jinja.

Generates, explains, and debugs terminal UI applications using Charm's BubbleTea v2 framework for Go. Use when building TUI apps with the Elm Architecture, handling keyboard/mouse input, managing async commands, implementing progress bars, alternate screens, clipboard, or composing multi-view terminal programs. Covers Model/Update/View pattern, message routing, command batching, color detection, and external process execution.

Golang code style, formatting and conventions. Use when writing Go code, reviewing style, configuring linters, writing comments, or establishing project standards.

Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code.

Provides linting best practices and golangci-lint configuration for Go projects. Covers running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and managing linter settings. Use this skill whenever the user runs linters, configures golangci-lint, asks about lint warnings or suppressions, sets up code quality tooling, or asks which linters to enable for a Go project. Also use when the user mentions golangci-lint, go vet, staticcheck, revive, or any Go linting tool.

Go (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives (New vs NewTypeName, isConnected vs connected, ErrNotFound vs NotFoundError, StatusReady vs StatusUnknown at iota 0), debating Go package names (utils/helpers anti-patterns), or asking about Go naming best practices. Also trigger when the user mentions MixedCaps vs snake_case, ALL_CAPS constants, Get-prefix on getters, or error string casing. Do NOT use for general Go implementation questions that don't involve naming decisions.

Recommends production-ready Golang libraries and frameworks. Apply when the user explicitly asks for library suggestions, wants to compare alternatives, needs to choose a library for a specific task, or when a new dependency is being added to the project.

Provides a guide for setting up Golang project layouts and workspaces. Use this whenever starting a new Go project, organizing an existing codebase, setting up a monorepo with multiple packages, creating CLI tools with multiple main packages, or deciding on directory structure. Apply this for any Go project initialization or restructuring work.

This skill should be used when user asks to "create a Home Assistant add-on", "scaffold an add-on", "wrap a Docker image for HA", "convert a Docker app to Home Assistant", "configure ingress for an add-on", "add ports to an add-on", "choose a base image for an HA add-on", "set up a sidebar panel in Home Assistant", "should I use ingress or ports", "add a webui button", "test an add-on locally", or "analyze a Docker image for add-on creation". Also activates when user mentions config.yaml, build.yaml, ingress_port, ports_description, s6-overlay, or bashio in the context of Home Assistant add-on development.

This skill should be used when the user asks to "create a hook", "generate a hook", "build a new hook", "write a hook script", "make a PreToolUse/PostToolUse hook", or wants to create automated Claude Code hooks for validation, logging, security, or workflow automation.

This skill should be used when the user asks to "use bashio", "read config with bashio", "log messages in an add-on", "call the Supervisor API", or mentions bashio functions, Home Assistant add-on development, or s6-overlay scripts.

This skill should be used when the user asks to "create a Dockerfile", "write a Dockerfile", "build a Docker image", "containerize an application", "optimize a Dockerfile", or mentions Dockerfiles, container images, multi-stage builds, or Docker best practices.

This skill should be used when the user asks to "create a gomplate template", "work with gomplate", "use gomplate datasources", "configure gomplate", "fix gomplate template", "debug gomplate syntax", "create .gomplate.yaml", or mentions gomplate templating, Go templates with datasources, or template rendering with external data.

This skill should be used when the user asks to "setup commitlint", "configure commitlint", "add commit linting", "create commitlint config", "lint commit messages", "setup husky for commits", "add commit-msg hook", "validate commits", or mentions commitlint, conventional commits, commit conventions, or commit message validation.

This skill should be used when the user asks to "setup release-please", "configure release-please", "create release automation", "bootstrap release-please", "add release-please to repo", "automate releases with release-please", or mentions release-please, GitHub release automation, or conventional commits based releasing.

This skill should be used when the user asks to "write a bash script", "create a shell script", "write a deployment script", "help with shell scripting", "review this bash script", "fix shell script style", or mentions bash, shell, or scripting tasks. Provides comprehensive guidance based on the Google Shell Style Guide.

This skill should be used when the user asks to "create an agent", "generate an agent", "build a new subagent", "make an agent for Claude Code", or wants to create autonomous agent configurations for Claude Code or plugins.

Generates, explains, and debugs terminal UI applications using Charm's BubbleTea v2 framework for Go. Use when building TUI apps with the Elm Architecture, handling keyboard/mouse input, managing async commands, implementing progress bars, alternate screens, clipboard, or composing multi-view terminal programs. Covers Model/Update/View pattern, message routing, command batching, color detection, and external process execution.

Generates, explains, and debugs CLI applications using Cobra (github.com/spf13/cobra) for Go. Use when building command-line tools with subcommands, flags, persistent flags, hooks, shell completions, help generation, argument validation, or migrating from other CLI libraries. Covers Command struct, AddCommand, flags (local/persistent), PreRun/PostRun hooks, ValidArgs, completions for bash/zsh/fish/powershell, and integration with viper.

Guide for using the figlet-go library to generate ASCII art text in Go applications. Use when working with the figlet-go package, creating ASCII art output, rendering animated ASCII art, or integrating FIGlet functionality into Go CLI tools. Covers rendering, fonts, colors, animations, and configuration.

Applies Google's Go Style Guide when writing, reviewing, or refactoring Go code. Covers naming conventions, formatting, error handling, package design, and testing patterns to produce readable, idiomatic, maintainable Go. Use when writing new Go code, reviewing Go PRs, or auditing a Go codebase for style issues.

Generates, explains, and debugs interactive terminal form and prompt code using Charm's huh v2 library for Go (charm.land/huh/v2). Use when building CLI tools that need user input via forms, single-field prompts, multi-step wizards, dynamic forms that react to earlier answers, accessible prompts for screen readers, or loading spinners. Covers all field types (Input, Text, Select, MultiSelect, Confirm, Note, FilePicker), Form/Group composition, dynamic Func variants, BubbleTea integration, themes, layouts, accessibility mode, keymaps, and the standalone spinner package. Import path: charm.land/huh/v2.

Generates, explains, and debugs configuration management code using the koanf Go library (github.com/knadh/koanf/v2). Use when building Go applications that need to load configuration from files (YAML, TOML, JSON, HCL, dotenv), environment variables, command-line flags, remote stores (Vault, Consul, etcd, S3, AWS AppConfig/ParameterStore), or in-memory sources. Covers provider chaining, config merging, struct unmarshaling, file watching, default values, custom parsers/providers, and migration from viper.

Generates, explains, and debugs structured logging code using zerolog (github.com/rs/zerolog) for Go. Use when writing zero-allocation JSON loggers, configuring log levels, adding structured fields, setting up console/file/multi writers, implementing hooks, using context-based logging, sampling high-volume logs, or logging errors with stack traces.

Analyze codebase with repomix, search skillshare for relevant skills, and recommend top 5

Reference codebase for Pi Extensions. Use this skill when you need to understand the structure, implementation patterns, or code details of the Pi Extensions project.

Initialize non-obvious modular rules for the codebase

Plan and add as task

Generates, explains, and debugs CLI applications using Cobra (github.com/spf13/cobra) for Go. Use when building command-line tools with subcommands, flags, persistent flags, hooks, shell completions, help generation, argument validation, or migrating from other CLI libraries. Covers Command struct, AddCommand, flags (local/persistent), PreRun/PostRun hooks, ValidArgs, completions for bash/zsh/fish/powershell, and integration with viper.

Applies Google's Go Style Guide when writing, reviewing, or refactoring Go code. Covers naming conventions, formatting, error handling, package design, and testing patterns to produce readable, idiomatic, maintainable Go. Use when writing new Go code, reviewing Go PRs, or auditing a Go codebase for style issues.

Write proper Go documentation comments for packages, types, funcs, consts, and vars. Use when writing, reviewing, or improving godoc comments. Covers naming conventions, syntax (headings, links, lists, code blocks), and common mistakes.

Generates, explains, and debugs configuration management code using the koanf Go library (github.com/knadh/koanf/v2). Use when building Go applications that need to load configuration from files (YAML, TOML, JSON, HCL, dotenv), environment variables, command-line flags, remote stores (Vault, Consul, etcd, S3, AWS AppConfig/ParameterStore), or in-memory sources. Covers provider chaining, config merging, struct unmarshaling, file watching, default values, custom parsers/providers, and migration from viper.

Build complex generic types, utility types, and type-level functions. Specializes in advanced TypeScript type system programming with generics, conditional types, mapped types, and template literals. Use for type system challenges and creating reusable type utilities.

Generate Claude Code modular rules in .claude/rules/ that are short, succinct, and optimized for LLM coding agents with path-specific scoping support

Generate comprehensive, type-safe tests for TypeScript code. Detects test framework (Jest, Vitest, Playwright, Cypress) and creates appropriate unit, integration, or E2E tests with proper typing, mocking, and coverage. Use when writing tests, increasing coverage, or testing new features.

Automatically infer and generate TypeScript types from runtime data, API responses, JSON samples, or existing JavaScript code. Use when encountering untyped data, API responses, or when converting JavaScript to TypeScript.

Create and manage project templates with Copier, a Python-based scaffolding tool. Use this skill whenever the user: - Wants to generate projects from templates (copier copy) - Needs to keep projects updated with template changes (copier update) - Is creating or maintaining a template itself (copier.yml, Jinja2 templates, tasks, migrations) - Has questions about template workflows, version management, or conditional prompts - Wants to re-apply a template to a project (copier recopy) - Needs help with .copier-answers.yml or template configuration Use Copier when working with project scaffolding, template versioning, or batch project generation. This skill covers creating templates with conditional questions, post-copy tasks, Jinja2 templating, and intelligent project updates.

Just command runner expertise, Justfile syntax, recipe development, and cross-platform task automation. Covers recipe patterns, parameters, modules, settings, shebang recipes for multi-language scripts, and workflow integration. Use when user mentions just, justfile, recipes, command runner, task automation, project commands, or needs help writing executable project documentation.

Task management for AI agents across context windows. Use when agents need to track work, log progress, hand off state, and maintain context across sessions. Includes workflows for single-issue focus, multi-issue work sessions, and structured handoffs. Essential for AI-assisted development where context windows reset between sessions.

GoReleaser OSS 配置与发布最佳实践，适用于梳理 top-level keys、发布平台支持、CI 触发链路、metadata/hooks 使用与常见坑。

Use this skill when the user is working with the `copier` CLI tool specifically — generating a project from a copier template (`copier copy`), updating a copier-managed project (`copier update`), authoring a copier template (i.e. a Git repo with `copier.yml`), or configuring `copier.yml`. Also trigger for questions about `.copier-answers.yml`, `_tasks`, `_exclude`, or other copier-specific settings. Do NOT trigger for general Jinja2 templating, Flask/Django/Ansible templates, or other tools that happen to use Jinja.

This skill should be used when the user asks to "create an agent", "generate an agent", "build a new subagent", "make an agent for Claude Code", or wants to create autonomous agent configurations for Claude Code or plugins.

Comprehensive reference for markdown-site development with Convex, React, and Vite. Use when working on content sync, frontmatter configuration, Convex queries/mutations, or full-stack features.