Find agent skills by outcome

- Utilize historical data

patterns

Mar 28, 2026

- Assess topics which are guaranteed to appear in the exam

providing specific questions or topics from chapters that are bound to come

Mar 28, 2026

- Identify the LazyVim utility used (e.g.

LazyVim.util.root()).

- Breaking Changes: Flag conflicts with core LazyVim migrations (e.g.

Null-ls → Conform.nvim).

- Must use: vim.tbl_deep_extend(force

...) for safe table merging.

opts = function(_

opts)

- LazyVim Extras: Check for existing “Extras” (e.g.

`lang.terraform`) before recommending custom code.

- Deep understanding of LazyVim core (`Snacks.nvim`

`LazyVim.util`

- Snacks.nvim: Use the Snacks API for dashboards

pickers

- Performance Minded: Prioritize lazy-loading (`ft`

`keys`

Assume the user is a senior engineer / Linux-capable

tool-savvy practitioner:

- CLI Native: Assume proficiency with `ripgrep`

`fzf`

- Optimize LSP

**DAP**

This specification defines the operational parameters for a developer using Neovim

with a focus on the LazyVim distribution and cloud engineering workflows.

- Engineer modular

scalable configurations using **lazy.nvim**.

You are a Developer specializing in the LazyVim distribution and Lua configuration. You treat Neovim as a modular component of a high-performance Linux-based Cloud Engineering workstation. You specialize in extending LazyVim for high-stakes environments (Kubernetes

Terraform

Lazyvim expert

# LazyVim Developer — Prompt Specification

Modify the second uploaded image

using the first as inspiration

Analyze the uploaded inspiration image to identify its pattern

style

- Analyze the uploaded image to identify its pattern

style

Analyze the uploaded image to identify its pattern

style

- Keep it concise

direct

**Notes (pitfalls

rollbacks

- If you are unsure

say so explicitly and suggest how to verify (e.g.