Menu
SkillsMP has collected 35 skills from fbosch/dotfiles. Open a skill to review its source and details.
Showing 35 of 35 collected skills.
Write, edit, copyedit, or unslop human-facing prose while preserving the user's canonical voice from `~/.config/opencode/TONE.md`. Use for documentation, READMEs, PR descriptions, commit-message bodies, changelogs, issue summaries, long-form explanations,…
TypeScript pattern matching with ts-pattern for exhaustive branching, data selection, and runtime shape checks. Use when implementing or refactoring conditionals over discriminated unions, tuple combinations, nested object shapes, reducer/state-machine…
ASCII diagram patterns for architecture, workflows, file trees, and data visualizations. Use when creating terminal-rendered diagrams, box-drawing layouts, progress bars, swimlanes, or blast radius visualizations.
Simplify and refine code for clarity, consistency, and maintainability while preserving exact behavior. Use to clean up recently written or modified code, reduce nesting and redundant abstractions, apply project coding standards, or improve readability…
Use when exploring or modifying a codebase and you need a cheap structural map of files, directories, imports, exports, or direct members before reading full source.
Build, refactor, review, debug, test, or migrate XState state machines, actor systems, and `@xstate/store` state management in JavaScript or TypeScript. Use whenever a repository imports `xstate`, a core framework adapter such as `@xstate/react`, or any…
Author, refactor, or review Lua used as program configuration in this dotfiles repo. Use when editing or evaluating Lua config layers such as .config/nvim/, .config/wezterm/, Hypr Lua helpers, or future Lua-backed dotfiles, especially shared Lua style, module…
Split large repository tasks into safe, independently executable work units and coordinate bounded OpenCode subagents. Use when a request involves a large repetitive migration, audit, cleanup, test addition, documentation update, lint backlog, or similar work…
Write effective pull request description bodies that explain what changed, why it changed, reviewer focus, validation, and risk. Use when creating, reviewing, or improving PR descriptions for internal work, OSS contributions, infra changes, migrations, or WIP…
Author, review, debug, port, and package code that explicitly runs under GJS (GNOME JavaScript), including GNOME Shell extensions and JavaScript or TypeScript projects using `gi://`, `resource:///org/gnome/`, legacy `imports.gi`, `GObject.registerClass()`,…
Design, implement, refactor, or review line-oriented command-line interfaces across any language or renderer. Use when changing commands, flags, help, prompts, confirmations, progress, errors, warnings, results, lists, tables, output layout, colors,…
Identify and validate runtime hot paths with profiling evidence. Use when locating a hotspot or bottleneck, profiling CPU, latency, allocations, GC, I/O, or contention, or deciding what code to optimize.
Use when a repository contains a `justfile` or `.justfile` and work should flow through `just` recipes instead of ad-hoc shell commands. Covers recipe discovery, execution, debugging, and concise recipe authoring/refactoring for repeatable project tasks.
Offer optional 10-15 minute deliberate learning exercises during AI-assisted coding. Use when the user asks for a learning opportunity, deliberate practice, retrieval check-in, prediction exercise, teach-back, or when substantial work created a good moment to…
Audit and safely clean low-value, redundant, misleading, flaky, over-mocked, or AI-generated unit tests. Use when asked to clean useless tests, prune test suites, remove redundant tests, audit low-value tests, improve test signal, clean brittle snapshots,…
Use when creating, editing, reviewing, or troubleshooting devenv.sh developer environments, including devenv.nix, devenv.yaml, packages, languages, services, tasks, scripts, processes, tests, GitHub Actions, containers, MCP/LSP integration, or reproducible…
Recognize, design, and refactor toward deep modules: small, stable interfaces hiding substantial cohesive implementation complexity. Use when reviewing or changing module boundaries, APIs, SDKs, React components, hooks, services, CLI commands, package…
Configure and troubleshoot Hyprland safely in this dotfiles repo. Use when adding or changing monitor, bind, input, workspace, window rule, layer rule, layout, animation, env, startup, or runtime behavior in `.config/hypr/*.conf`, and when diagnosing config…
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type. Use when user asks to create README, add README section, update README, review README documentation, improve…
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…
Create, review, or refactor AGENTS.md files so they stay minimal and high-signal. Use when asked to write/edit AGENTS.md, trim bloated agent context files, fix stale instructions, reduce token bloat, or audit instruction clarity. Handles minimal root…
Author OpenCode custom slash commands as markdown files. Use when creating, editing, or reviewing commands in ~/.config/opencode/commands/ or .opencode/commands/. Covers frontmatter (description, model, agent, subtask), prompt syntax (!`shell`, $ARGUMENTS,…
Design and implement effective subagent patterns in OpenCode. Use when creating custom agents, orchestrating multi-agent workflows, delegating batch processing tasks, optimizing tool permissions to avoid approval spam, selecting appropriate models for agents,…
Diagnose and fix Hyprland runtime problems in this dotfiles repo. Use when behavior is wrong despite valid config, including layer-shell stacking/input issues, missing keybind effects, monitor/workspace anomalies, window-rule mismatches, startup race…
Use when building, testing, and deploying JavaScript/TypeScript applications. Reach for Bun when you need to run scripts, manage dependencies, bundle code, or test applications with a single unified tool.
Run a Linear issue from intake to PR with explicit delivery gates. Use when the user asks to work a Linear ticket (id or URL), create or switch a WorkTrunk worktree or branch, implement requested changes, run local format or lint checks, and ship with commit,…
Run one-off Linux CLI tools from nixpkgs without installing them globally. Use when a task hits command-not-found or missing executable errors, or when an ephemeral tool should be run via `nix run` (or comma) instead of adding system dependencies.
Contract-first API and interface design for stable integrations. Use when creating or changing endpoints, public types, config formats, module boundaries, error models, pagination contracts, or versioned compatibility behavior.
Staged deprecation and migration planning for contract changes. Use when replacing or removing APIs, config formats, CLI flags, commands, data schemas, or defaults that existing consumers may rely on.
Threat-model-first hardening for app and API changes. Use when work touches untrusted input, auth/session logic, secrets, sensitive data paths, file upload, webhooks, or third-party integrations.
Create or update Vicinae extensions in this repo. Use when implementing new extensions, adding commands/preferences, wiring React Query + Vicinae Cache, or standardizing ActionPanel UX/shortcuts, build/lint workflows, and structure to match existing patterns…
TypeScript tsconfig.json expert. Use when: - Explaining what tsconfig options mean or do - Configuring tsconfig for a specific use case (Node.js app, bundler project, npm library, monorepo, React app, strict mode) - Diagnosing tsconfig-related errors or…
Evaluate Agent Skill design quality against official specifications and best practices. Use when reviewing, auditing, or improving SKILL.md files and skill packages. Provides multi-dimensional scoring and actionable improvement suggestions.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Expert guidance for TypeScript/JSDoc documentation decisions. Use when (1) documenting public library APIs for consumers, (2) deciding what to document vs skip for different audiences, (3) writing documentation for complex types or error handling, (4) setting…