dotfiles

Ghostwriter, tutor and reviewer for Leandro's technical blog articles (leandronsp.com). Leandro writes 100% of the article, never the assistant. The assistant explains the underlying concepts (physics, math, CS), hands over passages to copy and adapt, reviews concisely, and standardizes structure (agenda, anchors, conclusion). Use when the user says "ghostwriter", "me ajuda no artigo", "revisa o artigo", "help me write", "tô escrevendo um artigo", "seja meu ghostwriter", "tutor do artigo", or is drafting a post in DevTUI.

Search and retrieve notes from the Obsidian vault. Use when the user wants to find notes, recall past ideas, get context on a topic, look up references, browse blog drafts, get live stream ideas, consolidate notes for writing, or load knowledge from their second brain into the conversation. Trigger on phrases like "check my notes", "what do I have on", "find in vault", "search notes", "load notes about", "bring me everything about", "consolidate", "briefing for", "ideia pra live", "what should I stream".

Create a standalone, self-contained interactive HTML explainer in an editorial style (deep navy canvas, one accent, hairlines, mono microtype) for a technical change, architecture decision, incident, data flow, or product behavior. Ships with Present mode (a keyboard-driven slide deck). Works in any project, any stack. Use when the user says "explainer", "create an explainer", "explain this visually", "make a shareable page", "interactive explainer", "write this up as a page", or "turn this into an explainer".

Automatically extract text from images using Tesseract when the model doesn't support images. This is a pi extension that hooks into before_agent_start and runs OCR transparently. No manual triggering needed. Only activates on vision-free models. Do NOT trigger manually — the extension handles it automatically.

Answer questions about personal finances by searching only the ~/vault/finance/ section of the Obsidian vault. Use when the user asks "quanto gastei", "como estou em [mês]", "qual minha despesa fixa", "posso gastar X", "forecast", "carteira", "minha situação financeira", or any question about their money, bills, cards, or investments.

Process credit card bills, bank statements, or screenshots, extract expenses, update current month snapshot and 6/12-month forecasts in the Obsidian finance vault. Use when the user shares faturas, extratos, prints, or asks to "atualizar finanças", "processar contas", "atualiza fatura", "roda forecast", "atualiza mês". Writes ONLY to ~/vault/finance/.

Senior engineer. Scouts the codebase, clarifies requirements, proposes test cases, then implements with strict TDD in 3 modes (agent-pair, solo, pair-with-me). Accepts a prompt, issue URL, PRD file, or no args. Use when: dev, implement, build this, code this, tdd, let's build, pick a task, next task, implement feature, start coding, pair, dojo.

Bug hunter. Reproduces bugs with failing tests (RED), then fixes with TDD. Accepts a prompt, issue URL, or bug description. Simpler than /dev, focused solely on fixing bugs. Use when: bugfix, fix bug, debug, broken, regression, failing, doesn't work, something's wrong, fix this.

Capture an insight, idea, or note into the Obsidian vault. Use when the user wants to save something for later, jot down an idea, record a TIL, start a blog draft, or log anything to their second brain. Trigger on phrases like "save this", "note this down", "I had an idea", "TIL", "remember this", "add to vault".

Run PageSpeed audit against a URL. Requires a URL argument. Use when the user says "pagespeed", "check performance", "audit the blog", "run lighthouse", "test page speed", or wants to catch performance issues.

Code review in 2 modes. Autonomous (default): spawns parallel security/performance/quality reviewers + red-team auditor, presents verdict. Pair: walks changed files one-by-one with you, collects comments, posts only on approval. Accepts prompt, GitHub/Linear URL, PRD path, or no args. Use when: review, code review, review PR, walk me through the PR, pair review, review together, security review, quality check.

Scout the current project, diff against existing CLAUDE.md and .claude/rules, propose updates to reflect stack and conventions. Idempotent. Does not copy user-level skills or agents (user-level always wins). Use when: sync, forge, tune, init project, bootstrap, prepare project, refresh rules.

Test TUI applications using tu (terminal-use). Launch apps in virtual terminals, take screenshots, type text, press keys, wait for conditions, and verify output. Use for smoke testing terminal UIs, interactive CLIs, and TUI apps. Trigger on phrases like "test the TUI", "terminal test", "tu test", "test in terminal", "smoke test the editor", "verify the UI".

Writing companion that watches a file or folder with fswatch, reads the article on every save, and gives concise feedback on grammar, context, and structure. Ghostwriter mode. Never writes content unless explicitly asked. Use when the user says "cms", "watch my writing", "review my article", "writing companion", "help me write", "watch this file", "ghost mode".

Summarize current work into a handoff file for another agent to continue. Creates a structured markdown briefing with context, progress, next steps, and key decisions. Use when: handoff, hand off, pass to next agent, agent handoff, save context, continue later, pick up later.

Git commit with conventional commits, optional draft PR. Small, incremental, human-written messages. Never mentions AI, agents, or Claude. Use when: commit, commit this, save changes, git commit, stage and commit, create PR, open PR, draft PR.

Product Owner. Scouts the codebase, understands a prompt, writes a comprehensive PRD focused on product requirements for business people. Stack-agnostic, works across Ruby, Elixir, Rust, JS, Bash projects. Use when: PRD, product requirements, feature spec, what should we build, scope this, plan feature, po, write requirements, user story.

Save session learnings to the Obsidian vault. Use at the end of a work session to capture what was learned, decided, or discovered. Trigger on phrases like "recap", "save session", "what did we learn", "wrap up".

Browser automation via agent-browser CLI. Navigate, snapshot, screenshot, click, fill, type, wait, eval, pdf. Use for visual verification, smoke testing, form interaction, and page inspection. Trigger on phrases like "check the browser", "take a screenshot", "test the page", "what does it look like", "verify the UI", "browser test", "open the app".

QA engineer that smoke-tests changes in the browser, validates behavior, plans fixes or test gaps, and updates documentation. Acts as a "second dev" focused on testing what was built. Use when ready to validate work before committing. Trigger on phrases like "qa", "smoke test", "test this", "validate", "check my work", "qa this", "acceptance test".