kriscard
@kriscard
Public Skills
Lazy.nvim Optimization
by kriscard
"Neovim/lazy.nvim: Use ONLY for lazy.nvim specific issues - startup profiling, lazy-loading specs, plugin priorities. For general Neovim, use neovim-best-practices."
Obsidian Operations Skill
by kriscard
Use when performing ANY Obsidian vault operations: reading notes, creating files, appending content, searching, or listing files. Covers CLI-first approach with MCP fallback. Essential for all Obsidian-related commands and agents. Trigger phrases: "obsidian", "vault", "create note", "read note", "append to note", "search vault", "list files", "daily note", "periodic note", "TIL note"
Vault Structure & Configuration
by kriscard
"Obsidian: Reference for user's vault folders, tags, and templates. Load when needing vault layout context for note operations."
prompt-engineer
by kriscard
"AI/LLM: Use when crafting system prompts, optimizing LLM outputs, or improving agent instructions. NOT for general coding."
senior-architect
by kriscard
"Architecture: Use when designing system architecture, creating C4 diagrams, evaluating tech trade-offs, or writing ADRs. NOT for implementation details or coding."
conference-talk-builder
by kriscard
"Content: Use when structuring conference talks or creating iA Presenter slides. NOT for written blog posts or docs."
Dotfiles Optimizer
by kriscard
"Dotfiles: Use when optimizing shell configs (zsh, tmux, git), auditing dotfiles security, or improving dev environment. NOT for application configs."
Assistant
by kriscard
"Workflow: Use for /standup, /weekly-summary, /context-save, /staff-progress, or Staff Engineer career tracking. NOT for general coding help."
claude-code-analyzer
by kriscard
"Claude Code: Use when analyzing plugin structure, checking Claude Code config, or finding community resources."
doc-coauthoring
by kriscard
"Content: Use when co-authoring RFCs, proposals, ADRs, or decision documents. NOT for blog posts or implementation specs."
studio-startup
by kriscard
"Startup: Use for /studio-startup:new or when starting a new project/MVP from scratch. Orchestrates full workflow. NOT for existing codebases."
Chrome DevTools
by kriscard
"Browser: Use when inspecting pages, checking console errors, analyzing network requests, or running performance traces. NOT for writing frontend code."
commit
by kriscard
"Git: Use for /commit or when committing changes with semantic messages. NOT for PR creation (use /pr) or branch management."
Neovim Best Practices
by kriscard
"Neovim: Use when configuring Neovim, writing Lua plugins, or setting up LSP. NOT for VS Code, other editors, or lazy.nvim specifics."
code-assistant
by kriscard
"Development: Use when writing, debugging, or refactoring code. Orchestrates specialist agents (TypeScript, React, etc). NOT for architecture decisions."
Obsidian Workflows & Second Brain Methodology
by kriscard
"Obsidian: Use when organizing vault with PARA method, PKM workflows, or note-taking systems. NOT for vault-specific structure (use vault-structure)."
react-best-practices
by kriscard
"React: Use when auditing React components for performance, re-renders, or bundle size. NOT for Vue, Angular, or general TypeScript."
ideation
by kriscard
"Ideation: Use for /ideation or when organizing messy brain dumps into structured specs. NOT for existing tickets (use /spec instead)."
blog-writer
by kriscard
"Content: Use when writing technical blog posts from scattered notes or ideas. NOT for documentation, specs, or talks."
ai-engineer
by kriscard
"AI/LLM: Use when building RAG pipelines, vector search, LLM integrations, or agent orchestration. NOT for general backend or API development."
Interactive Teaching
by kriscard
"Learning: Use for /learn sessions or when user explicitly asks to be taught step-by-step. NOT for quick answers or general help."
Dotfiles Best Practices
by kriscard
"Dotfiles: Reference knowledge for modern CLI tools and shell best practices. Loaded by dotfiles-optimizer when needed."
Template Usage & Application Patterns
by kriscard
"Obsidian: Use when selecting or applying note templates. NOT for general vault organization (use obsidian-workflows)."