fredrikaverpil/dotfiles.

aip

Google API Improvement Proposals (AIP) reference. Use BEFORE designing or reviewing APIs, protobuf definitions, or any work involving Google API design standards. Fetches relevant AIP rules from https://google.aip.dev for the task at hand.

gh-pr

>-

golang-style

Try to follow the proverbs:

neovim

Interact with the user's running Neovim instance via RPC. Use this skill when you need to execute Lua or Vimscript inside Neovim, query buffer state, send commands, or interact with the Neovim runtime in any way. Triggers when the user asks about their current Neovim session, wants to run something inside Neovim, or when you need to inspect Neovim state (buffers, windows, options, LSP, etc.). Also use when running inside a Neovim terminal and needing to communicate with the parent editor.

nix-install

Install Nix in the Claude Code web sandbox (the cloud environment) as a general-purpose package installer, then install packages from the Nix binary cache with no GitHub access. Use whenever a web session needs a tool that isn't preinstalled and isn't in a language registry (npm/pypi/crates/go) — Neovim, ripgrep, a compiler, anything in nixpkgs. Installs nix-bin via apt, configures single-user mode, and installs packages via nix-env against the nixpkgs channel tarball. Web-sandbox only.

nvim-config

>

nvim-install

Install Neovim and stand up the nvim-fredrik config in the Claude Code web sandbox (the cloud environment), where no Neovim exists. Use this before testing any Neovim config change in a web session, e.g. checking out a PR branch that touches nvim-fredrik and observing its runtime behavior. Installs Neovim via Nix from the binary cache with no GitHub access, wires the repo's config into place, launches Neovim headless with a listen socket, and exports $NVIM so the `neovim` RPC skill can drive it. Web-sandbox only.

nvim-plugin

Reference: https://neovim.io/doc/user/lua-plugin/

plan-interview

Before creating a plan, interview the user

pr-style

>-

proof

Provide proof to your claim(s)

skillify

You are capturing this session's repeatable process as a reusable skill.

smart

Run a task through three phases from a single main chat on the smart model (Fable, or Opus). The point is to keep expensive tokens on the judgment work — planning, verifying, reviewing — and delegate implementation and research to subagents that each carry their own pinned, cheaper model — **without** the token blow-up of agent teams.