메뉴
Neovim config healthcheck for ~/.dotfiles/.config/nvim/ using lazy.nvim and GNU Stow. Use when the user wants to validate or repair Neovim, add/remove plugins, diagnose startup performance, fix keymaps/LSP, or modernize config. Prefer audit for whole-dotfiles reviews and shell-env for non-Neovim terminal config.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | neovim |
| description | Neovim config healthcheck for ~/.dotfiles/.config/nvim/ using lazy.nvim and GNU Stow. Use when the user wants to validate or repair Neovim, add/remove plugins, diagnose startup performance, fix keymaps/LSP, or modernize config. Prefer audit for whole-dotfiles reviews and shell-env for non-Neovim terminal config. |
Config lives at ~/.dotfiles/.config/nvim/, symlinked by GNU Stow, namespaced under kriscard/. Plugin manager is lazy.nvim.
~/.dotfiles/.config/nvim/
├── init.lua # Entry point — sources all modules
├── lua/kriscard/
│ ├── core/
│ │ ├── options.lua # vim.opt settings
│ │ ├── keymaps.lua # vim.keymap.set with {desc = "..."}
│ │ └── autocmds.lua # autocommands
│ └── plugins/ # lazy.nvim plugin specs (one file per plugin or group)
│ └── *.lua
Stow package: cd ~/.dotfiles && stow nvim (or whatever the package name is — check ls ~/.dotfiles).
references/config.md if needed.references/plugins.md.references/performance.md.Do not load all references.
:checkhealth " full diagnostic
:checkhealth lazy " plugin manager health
:checkhealth nvim-treesitter
:Lazy " plugin status dashboard
Done when health output is captured, any failing provider/plugin is named, and each issue has a fix or next diagnostic command.
lua/kriscard/plugins/.:Lazy sync.:checkhealth <plugin> when the plugin provides health checks.Done when the spec is in the Stow-managed source path, lazy.nvim can sync/load it, and any keymaps/commands include lazy-load boundaries.
Run :Lazy profile to see per-plugin load times. For CLI measurement:
nvim --headless --startuptime /tmp/nvim.log +q && sort -k2 -n /tmp/nvim.log | tail -20
Done when before/after startup measurements are recorded, top slow plugins or config files are named, and each recommendation maps to a lazy.nvim event, cmd, keys, or ft boundary or is marked needs deeper profiling.
Move from least destructive to most destructive:
:Lazy log — inspect recent install/update errors.:messages — capture Lua errors after startup.:Lazy sync — retry install/update when the error indicates missing or stale plugin state.:Lazy clean — remove unused plugins only after confirming they are no longer referenced.~/.local/share/nvim/lazy/<plugin> only as a last resort to force reinstall.Done when the error is reproduced or log output is captured, the least destructive applicable repair has run, and the next startup/checkhealth result is recorded.
opts = {} instead of config = function() require("x").setup({}) end where possible{desc = "..."} for which-key integrationevent = "BufReadPre"):verbose map <key> to check)vim.loader.enable() called in init.lua (bytecode cache, free perf)Completion gate: do not declare Neovim work done until the changed source path, validation command, and result are reported.
| Priority | Load when | Reference |
|---|---|---|
| High | Plugin recommendations, modern picks, what to add/remove, abandoned plugins | references/plugins.md |
| High | Startup time, lazy-loading strategies, profiling, which plugins are slow | references/performance.md |
| Medium | Config structure, best practices, common mistakes, keymaps, LSP setup | references/config.md |
Audit existing React Hook Form code for correctness, accessibility, validation, data ownership, submission, dirty-state, field-array, wizard, controlled-widget, and performance problems. Use when reviewing RHF forms, investigating form bugs or rerenders, or checking an RHF-heavy change. Read-only; use react-hook-form for implementation.
Build and modify React Hook Form forms. Use when React Hook Form is mentioned, imported, installed, or established by project conventions, including controlled widget integration, schema validation, fetched edit forms, conditional fields, multi-step wizards, field arrays, submission errors, and dirty-state handling. Use the react-hook-form-audit skill when the job is review rather than implementation.
Capture a concrete work or learning receipt in today's Obsidian note, then optionally hand it to tweet-today or blog. Use when the user says "save this for sharing", "capture this receipt", "tweet this now", or when close-day promotes an Idea Worth Sharing.
End-of-day Obsidian ritual: close the active focus loop, triage Ideas Worth Sharing, and confirm tomorrow's carry-forward. Use for "close my day", "end of day", "wrap up today", or /close-day.
Daily startup ritual for the Obsidian vault: create today's workday note, surface exact context, and require the user to choose one daily outcome and next action. Use for "start my day", "daily startup", "today's focus", or /daily.
Obsidian goals review for quarterly, monthly, or weekly goal notes. Use when the user asks to review goals, run an OKR check-in, update goals, set monthly goals, check whether goals are on track, or runs /goals.