metaldrummer610

---

name: linear-story-quality description: >- Validate Linear issue quality for AI-autonomous execution. Use when assessing story readiness, checking issue quality, validating before execution, or when about to start work on a Linear issue. Also use after drafting a new Linear issue to self-check before saving. Enforces hard gates (objective, acceptance criteria, affected areas) and scores soft criteria (edge cases, scope, dependencies, approach). allowed-tools: Read, Glob, Grep, mcp__plugin_linear_linear__get_issue, mcp__plugin_linear_linear__save_issue, mcp__plugin_linear_linear__list_issues

metaldrummer610

Gemini Added Memories

• The user prefers using the 'buf' tool for Protobuf/gRPC management (linting, breaking change detection, and code generation) in their Go and Python projects.
• The user prefers using the latest versions of libraries and tools. I should actively perform web searches to verify 'bleeding edge' methods and patterns rather than relying on potentially outdated internal knowledge.
• The user strictly follows Inversion of Control (IoC). Dependencies must always be created outside the unit of code and injected (constructor injection) to facilitate mocking.
• In Go files, the user prefers this specific order: 1) Struct Definition, 2) Constructor (e.g., NewService), 3) Public Methods, 4) Private Methods.
• In Go, the user follows the 'Consumer-Driven Interface' pattern: define interfaces for dependencies locally at the top of the file, including only the specific methods used by that struct.
• In Go, the user uses zerolog for logging. ctx context.Context must always be the first argume

metaldrummer610

autocmd VimEnter * NERDTree
nmap <silent> <c-n> :NERDTreeToggle<CR>
let g:NERDTreeWinPos = "left"

set pastetoggle=<F2>
nmap <F3> gg=G

set nu
au! FileType javascript