.files

Use when drafting, writing, or filing a Linear ticket/issue, or asked for a Linear title/body/description.

Use when drafting, writing, or opening a pull request (gh pr create), or asked for a PR title/body/description.

Writing voice for authored prose — PR bodies, Linear tickets, review comments, commit messages.

Hand a file to the user's running editor and block until they finish editing it. Use whenever a draft (PR body, ticket, commit message, any generated file) needs the user's review before you act on it, or when a task says "open this in my editor/vim/nvim".

Clojure style guidelines. Activate before writing or editing Clojure code

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Write clj-kondo hooks for custom macros using the hooks API and rewrite-clj nodes. Use when creating, editing, or debugging clj-kondo hooks, writing analyze-call or macroexpand hooks, or registering custom lint warnings.

Use for browser testing/automation via Chrome DevTools Protocol (cdp-cli).

User's Evaluate Clojure code via nREPL using clj-nrepl-eval. Use this if the project doesn't provide its own eval. Use when you need to test code, check if edited files compile, verify function behavior, or interact with a running REPL session.

Compact Konsta UI React reference. Use this first for source-grounded component roles and the highest-signal props from the local reference files. Open the per-component reference files for colors, defaults, forwarded HTML props, types, event handlers, class-name hooks, theme variants, and full details.

Output lists of locations as vim quickfix lists.