All authors
Claude Skills by xobotyi
github.com/xobotyi66 skills0 installs2 views
- ReleaseGitHub release creation for cc-foundry plugins: per-plugin tags, release notes as the changelog, post-merge publishing, and moving the released plugins' XERJ Corpus Hub pins. Invoke whenever task involves merging a pull request into master, releasing or publishing a plugin version, bumping plugin versions, writing release notes, or refreshing the Corpus Hub pins.Votes: 0GitHub stars: 23
- Output Style EngineeringDesign and maintain Claude Code output styles: choosing the mechanism, setting the frontmatter, and writing the role, voice, and rules the style installs in the system prompt.Votes: 0GitHub stars: 23
- Prompt EngineeringWrite and debug instruction text on any surface: requests, standing context such as CLAUDE.md, tool and schema descriptions, and prompts written for other model instances.Votes: 0GitHub stars: 23
- Prompt TerserRun a phased terseness pass over an existing prompt or skill and return a diff-proposal: mechanical wording and format cuts listed as applied, structural cuts gated behind a falsification check.Votes: 0GitHub stars: 23
- Skill EngineeringAuthor and maintain Agent Skills: routing metadata, body content, bundled references and scripts, evaluation, and distribution.Votes: 0GitHub stars: 23
- Subagent EngineeringDesign and maintain Claude Code subagents: the delegation decision, the frontmatter that governs a run, and the system prompt the agent wakes up with.Votes: 0GitHub stars: 23
- ObservabilityObservability discipline: structured logging, metrics instrumentation, distributed tracing, and signal correlation. Invoke whenever task involves any interaction with observability concerns — adding logging, designing metrics, instrumenting traces, correlating signals, reviewing instrumentation, or understanding when to use which pillar.Votes: 0GitHub stars: 23
- Otel TracingOpenTelemetry tracing discipline: correct spans, propagation, and semantic conventions produce useful traces. Invoke whenever task involves any interaction with distributed tracing — span creation, context propagation, instrumentation, sampling configuration, or OpenTelemetry SDK setup.Votes: 0GitHub stars: 23
- PrometheusPrometheus instrumentation discipline: right metric type, right name, right labels. Invoke whenever task involves any interaction with Prometheus metrics — instrumenting application code, writing PromQL queries, defining alerting or recording rules, choosing metric types, managing label cardinality, building exporters, or reviewing monitoring configuration.Votes: 0GitHub stars: 23
- StatsdStatsD metric instrumentation: push metrics over UDP, choose the right metric type, name consistently. Invoke whenever task involves any interaction with StatsD metrics — emitting counters, gauges, timers, histograms, sets, or distributions; configuring DogStatsD tags; tuning sampling rates; or integrating with Graphite, Prometheus, or Telegraf backends.Votes: 0GitHub stars: 23
- CliCLI application design: argument conventions, output streams, exit codes, configuration hierarchy, interactive modes, and terminal UX. Invoke whenever task involves any interaction with command-line tools or terminal applications — building, reviewing, debugging, or designing CLI interfaces.Votes: 0GitHub stars: 23
- Shell ScriptingShell script conventions, defensive patterns, and correctness rules: strict mode, quoting, portability, error handling, and common pitfalls. Invoke whenever task involves any interaction with shell scripts — writing, reviewing, debugging, or understanding .sh, .bash, .zsh files.Votes: 0GitHub stars: 23
- AccessibilityWeb accessibility discipline: semantic HTML first, ARIA only when needed, keyboard access always. Invoke whenever task involves any interaction with accessible web content -- writing, reviewing, refactoring, or debugging HTML/CSS/JS for WCAG compliance, ARIA usage, keyboard navigation, focus management, screen reader support, or accessible component patterns.Votes: 0GitHub stars: 23
- CssCSS conventions, layout systems, and modern patterns: predictable styles through low specificity and explicit cascade control. Invoke whenever task involves any interaction with CSS code — writing, reviewing, refactoring, debugging, or understanding stylesheets, SCSS, layout, or responsive design.Votes: 0GitHub stars: 23
- Frontend DesignDecide and verify what a web interface looks like: reuse of the existing design, color, type, layout, controls, states, and interface copy that trace to the product instead of a framework or model default.Votes: 0GitHub stars: 23
- ReactReact component discipline: pure components, minimal state, effects as escape hatches. Invoke whenever task involves any interaction with React code — writing, reviewing, refactoring, debugging, or understanding JSX, hooks, component architecture, state management, or performance optimization.Votes: 0GitHub stars: 23
- SvelteSvelte runes-first reactivity and SvelteKit fullstack conventions. Invoke whenever task involves any interaction with Svelte code — writing, reviewing, refactoring, debugging, or understanding .svelte, .svelte.js, .svelte.ts files and SvelteKit projects.Votes: 0GitHub stars: 23
- TailwindcssTailwind CSS v4 utility-first discipline: CSS-first configuration, design tokens via @theme, and principled class composition. Invoke whenever task involves any interaction with Tailwind CSS — writing, reviewing, refactoring, debugging, or understanding utility classes, theme configuration, custom utilities, dark mode, or Tailwind integration with frameworks.Votes: 0GitHub stars: 23
- VueVue 3 conventions, Composition API patterns, SFC structure, reactivity, composables, and TypeScript integration. Invoke whenever task involves any interaction with Vue code — writing, reviewing, refactoring, debugging, or understanding .vue files, composables, and Vue component architecture.Votes: 0GitHub stars: 23
- Commit MessageGit commit message conventions: structure, formatting, scoping, body content, breaking changes, trailers.Votes: 0GitHub stars: 23
- CommitGit commit workflow pipeline: atomic unit identification, commit ordering, quality gates, message validation, and post-commit verification.Votes: 0GitHub stars: 23
- Charm TuiWrite and review Charmbracelet v2 terminal UIs in Go: Bubble Tea programs, Bubbles components, Lip Gloss styling and layout, Huh forms, Glamour markdown, fang CLI entry, and TUI testing.Votes: 0GitHub stars: 23
- GolangWrite and review Go: idioms, error handling, concurrency, testing, project structure, the toolchain, and the language version a module's `go` directive permits.Votes: 0GitHub stars: 23
- TemplWrite and review templ templates: syntax, components, attributes, styling, JavaScript data passing, escaping and sanitization, code generation, and testing.Votes: 0GitHub stars: 23
- ZogWrite and review Zog schema validation in Go: schema shape, Parse against Validate, required and default semantics, tests and transforms, issue handling, and the zhttp, zjson, and zenv adapters.Votes: 0GitHub stars: 23
- AlertingGrafana unified alerting: rule types, evaluation lifecycle, state transitions, notification policies, contact points, silences, mute timings, recording rules, and alert/notification templates. Invoke whenever task involves any interaction with Grafana alerting — creating or editing alert rules, configuring contact points and routing, templating annotations or notifications, debugging alert state, or reviewing alerting configuration.Votes: 0GitHub stars: 23
- DashboardsGrafana dashboard authoring: JSON model (Classic and V2), panel types and selection, standard options, thresholds, value mappings, field overrides, transformations, variables (query/custom/interval/filter), repeating panels and rows, annotations, dashboard/panel/data links, and library panels. Invoke whenever task involves any interaction with Grafana dashboards — creating, editing, reviewing, debugging, or understanding dashboard configuration.Votes: 0GitHub stars: 23
- DatavizData visualization discipline for monitoring and observability dashboards: chart-type selection by data shape, encoding accuracy hierarchy (position > length > angle > area > color), pre-attentive attributes, Tufte data-ink, color theory (semantic conventions, Viridis, colorblind safety), dashboard layout and information hierarchy (F/Z-pattern, tiering), time-series conventions (baseline, interpolation, dual axes, stacking), observability frameworks (RED, USE, Four Golden Signals, SLO/SLI). I...Votes: 0GitHub stars: 23
- LogsqlVictoriaLogs LogsQL query language: filters (word, phrase, prefix, regexp, range, IPv4 range, exact, stream, time), pipe operators (stats, sort, fields, format, extract, unpack_json, unpack_logfmt, math, limit, top, uniq), stats functions, log stream filtering with Prometheus-style label selectors, field extraction, and performance patterns. Invoke whenever task involves any interaction with LogsQL — writing, debugging, optimizing, or reviewing VictoriaLogs queries.Votes: 0GitHub stars: 23
- MetricsqlVictoriaMetrics MetricsQL query language as a PromQL superset: rollup extensions, behavioral differences from PromQL (rate/increase semantics, implicit conversions, auto-aligned subqueries), label manipulation, WITH templates, keep_metric_names modifier, multiple-or filters, and query API enhancements. Invoke whenever task involves any interaction with MetricsQL or VictoriaMetrics queries — writing, debugging, optimizing, migrating PromQL to VictoriaMetrics, or reviewing.Votes: 0GitHub stars: 23
- PromqlPromQL query writing: selectors, operators, vector matching, functions, aggregations, histograms, subqueries, recording rules, alerting rules, and query optimization. Invoke whenever task involves any interaction with PromQL — writing, debugging, optimizing, reviewing, or explaining Prometheus queries for dashboards, alerts, recording rules, or ad-hoc exploration.Votes: 0GitHub stars: 23
- ProvisioningGrafana provisioning across all delivery methods: file provisioning YAML (datasources, dashboards, alerting), Kubernetes-style HTTP API, gcx CLI (replacing grafanactl), Terraform provider, Foundation SDK, Git Sync. Invoke whenever task involves any interaction with Grafana provisioning or observability-as-code — configuring datasources, managing dashboards or alerting resources as code, automating Grafana setup, choosing between IaC tools, migrating between approaches, or using the Grafana HT...Votes: 0GitHub stars: 23
- AnsibleWrite, review, and run Ansible: the ansible-core line a project pins, what the 2.19 templating engine refuses, which task results are claims rather than measurements, where a variable's value comes from, and what ansible-lint and Molecule prove.Votes: 0GitHub stars: 23
- ContainersDocker and Podman container management: Dockerfile optimization, multi-stage builds, Compose v2 orchestration, networking, volumes, security hardening, supply chain integrity, health checks, resource limits, Quadlet systemd integration, and debugging. Invoke whenever task involves any interaction with containers — writing Dockerfiles, configuring Compose, managing Podman Quadlets, reviewing container security, debugging container issues, or setting up image signing and scanning.Votes: 0GitHub stars: 23
- DevopsCarry an infrastructure change from intent to verified effect: what a change must carry before apply, what "applied" does not prove, which changes a revert cannot reverse, what a credential can do that the instruction never said, and the evidence that closes a change. Not how any one tool is written.Votes: 0GitHub stars: 23
- NetworkingWrite and review network configuration for self-hosted Linux infrastructure: what an nftables ruleset, a resolver zone, a reverse-proxy site, a forward-auth chain, a WireGuard or Tailscale tunnel, or an IDS rule does once loaded, where that differs from what the file reads. Not how a change is applied or verified.Votes: 0GitHub stars: 23
- ProxmoxProxmox VE administration: VM/LXC/OCI container provisioning, storage backends, networking/SDN, clustering, high availability, API automation, cloud-init templates, backups/PBS, PCIe passthrough, and vGPU. Invoke whenever task involves any interaction with Proxmox VE — configuring hosts, managing guests, designing storage or networking, writing automation scripts, planning clusters, troubleshooting, or reviewing PVE configurations.Votes: 0GitHub stars: 23
- BunWrite and review Bun: the Bun-native API surface against its `node:` equivalents, the HTTP and WebSocket server, file and process I/O, the shell, the data clients, `bun:test`, the bundler and compiled binaries, and the package manager.Votes: 0GitHub stars: 23
- JavascriptWrite and review JavaScript: declarations, equality and coercion, functions, objects, iteration, classes, async and promise semantics, ES modules, regular expressions, JSDoc typing, and the ECMAScript features a project's engine baseline permits.Votes: 0GitHub stars: 23
- NodejsWrite and review Node.js: the module system, package manifest, streams, event loop, process and worker lifecycle, the permission model, native TypeScript execution, `node:test`, and the runtime version `engines.node` permits.Votes: 0GitHub stars: 23
- TypescriptWrite and review TypeScript: the type system, strictness configuration, narrowing, generics, type-level patterns, declaration files, module resolution and `tsconfig`, and the release a project's compiler pins.Votes: 0GitHub stars: 23
- VitestWrite and review Vitest tests: structure, assertions, fixtures and lifecycle, the mocking surface and its hoisting rules, snapshots, configuration and projects, pools and isolation, coverage, type tests, and migration from Jest.Votes: 0GitHub stars: 23
- Issue WritingPrepare issues for repositories you do not maintain: route the report to the right channel, meet the project's evidence bar, and supply the elements maintainers want most. The user files it. Not for opening pull requests.Votes: 0GitHub stars: 23
- Pr ContributionPrepare pull requests for repositories you do not maintain: find the project's AI-contribution rules before writing code, earn a reviewer, and shape the change so a volunteer can say yes. The user opens the PR. Not for filing issues.Votes: 0GitHub stars: 23
- PestPest testing framework conventions and practices. Invoke whenever task involves any interaction with Pest — writing function-style tests (test/it/describe), the expect() expectation API, datasets, hooks, architecture/mutation/type-coverage/browser testing, Pest.php configuration, or running the pest CLI.Votes: 0GitHub stars: 23
- PhpPHP language conventions, modern idioms, and type system. Invoke whenever task involves any interaction with PHP code — writing, reviewing, refactoring, debugging, or understanding PHP projects.Votes: 0GitHub stars: 23
- PhpunitPHPUnit testing framework conventions and practices. Invoke whenever task involves any interaction with PHPUnit — writing tests, configuring PHPUnit, data providers, mocking, assertions, debugging test failures, or coverage.Votes: 0GitHub stars: 23
- Pytestpytest testing framework conventions and practices. Invoke whenever task involves any interaction with pytest — writing tests, configuring pytest, fixtures, parametrize, mocking, debugging test failures, or coverage.Votes: 0GitHub stars: 23
- PythonPython language conventions, modern idioms, and toolchain. Invoke whenever task involves any interaction with Python code — writing, reviewing, refactoring, debugging, or understanding Python projects.Votes: 0GitHub stars: 23
- Rust TestingRust testing conventions and frameworks: built-in #[test], integration, and doctest layout plus the cargo-nextest runner and the proptest, insta, criterion, mockall, and rstest ecosystem. Invoke whenever task involves any interaction with Rust tests — writing, running, configuring, or debugging tests in .rs files and Cargo projects.Votes: 0GitHub stars: 23