Menú
Find where something is configured in config.org, or determine the right place to add new config
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 | find-config |
| description | Find where something is configured in config.org, or determine the right place to add new config |
| argument-hint | <package, feature, or keybinding to find> |
| allowed-tools | Read, Grep |
Locate existing configuration or identify the correct insertion point for new config.
$ARGUMENTS
Grep config.org for the package/feature name (case-insensitive):
Grep config.org for: $ARGUMENTS
Also try related terms: the mode name, the command name, or the keybinding prefix.
Report results as a heading breadcrumb trail, e.g.:
* Tools > ** LSP > *** Python (line 842)
Show the relevant #+begin_src emacs-lisp block and surrounding org text.
Use this section map to recommend where new config belongs:
| Content type | Recommended heading |
|---|---|
| Look & feel, fonts, themes, modeline | * UI |
| Terminal, vterm, eshell, tmux | * Terminal |
| Org-mode, GTD, roam, agenda | * Workflows > ** Org |
| A programming language or LSP | * Languages > ** <Language> |
| Editor behaviour, evil, snippets | * Editor |
| External tools (docker, git, etc.) | * Tools |
| OS-specific tweaks | * OS |
| Keybindings (global or misc) | Bottom of relevant section |
Search for existing map! usage for the relevant mode:
Grep config.org for: map!.*<mode-or-prefix>
Doom map! syntax reference:
;; Global (normal state by default)
(map! "C-x f" #'my-function)
;; Leader key (SPC)
(map! :leader
:desc "Description" "k k" #'my-function)
;; Mode-local
(map! :map org-mode-map
:n "C-c t" #'org-todo)
;; Evil state flags: :n normal, :i insert, :v visual, :m motion, :o operator
Always return:
config.org* Tools > ** MagitAdd a new Emacs package to this doom config — packages.el declaration, config.org section, and doom sync
Run static analysis and byte-compile checks on the Doom config without opening Emacs
Systematically debug a doom emacs issue — errors, broken packages, slow startup, keybinding conflicts
Look up a Doom Emacs module's documentation, flags, and packages before configuring anything manually. Use this when the user asks about adding a feature, package, or integration to Doom.
Run doom sync after config changes and diagnose any errors
Update doom emacs and/or packages — runs doom upgrade, handles errors, summarizes what changed