Menú
Add and configure a neovim plugin following the nix-based setup. Use when the user wants to add a new vim/neovim plugin.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | add-nvim-plugin |
| description | Add and configure a neovim plugin following the nix-based setup. Use when the user wants to add a new vim/neovim plugin. |
Add the neovim plugin: $ARGUMENTS
Follow the patterns documented in @docs/neovim-plugins.md
Find the plugin: Search nixpkgs for the plugin using nix search nixpkgs vimPlugins.<name>. If not found, check vimExtraPlugins.
<plugin-name>-<owner> (e.g., trouble-nvim-folke, conform-nvim-stevearc).Fetch plugin info: If a GitHub URL is provided, fetch it to understand dependencies and configuration options.
Add to neovim.nix: Add the plugin to home/neovim.nix in the appropriate category:
map optionalPlugin [...]map pluginWithConfig [...]Handle dependencies: Use pluginWithDeps if the plugin requires other plugins like nvim-web-devicons.
Create Lua config: If needed, create config/nvim/lua/shinzui/<plugin-pname>.lua.
CRITICAL: The filename MUST match the plugin's pname exactly because pluginWithConfig derives the Lua module name from it.
telescope-nvim.lua)trouble-nvim-folke.lua, lspsaga-nvim-nvimdev.lua)Example for vimExtraPlugins (e.g., pkgs.vimExtraPlugins.trouble-nvim-folke):
-- trouble.nvim
-- A pretty diagnostics list
-- https://github.com/folke/trouble.nvim
vim.cmd "packadd trouble-nvim-folke"
require("trouble").setup({})
Example for nixpkgs vimPlugins (e.g., telescope-nvim):
-- telescope.nvim
-- https://github.com/nvim-telescope/telescope.nvim
vim.cmd "packadd telescope-nvim"
require("telescope").setup({})
Summary: Report what was added and remind to run darwin-rebuild switch --flake .
Help author, validate, and edit mori/cookbook.dhall cookbook extension catalogs. Covers entry fields, content types, topics, imports, and validation rules. TRIGGER when: user wants to create, edit, or validate their mori/cookbook.dhall config.
Bootstrap a complete corpus project from a repo name — initializes git, adds upstream subtrees, writes mori.dhall and Justfile, validates, registers, and optionally sets up cookbook and documentation entries. TRIGGER when: user wants to create a corpus project, wrap upstream repos as subtrees, or set up a third-party code reading workspace.
Help author, validate, and edit mori.dhall project configuration files. Covers project identity, packages, dependencies, repositories, documentation, skills, and subagents. TRIGGER when: user wants to create, edit, or understand their mori.dhall config.
Create, implement, discuss, or update execution plans (ExecPlans) — self-contained design documents that guide a coding agent or novice through delivering a working feature or system change. Use when planning significant work, implementing from a plan, or recording design decisions. TRIGGER when: user wants to plan a feature, follow a plan, or manage ExecPlan documents.
Create and manage master plans that decompose large initiatives into multiple coordinated ExecPlans with dependencies and integration points. TRIGGER when: user wants to plan a large initiative, coordinate multiple exec-plans, or track multi-plan progress.
Create a new Bun/TypeScript derivation using bun2nix from a GitHub URL. Use when the user wants to package a JavaScript/TypeScript npm package as a Nix derivation.