.dotfiles

review backend code against project documentation stored in /docs, identify discrepancies, ask which source should prevail for each discrepancy, update the documentation directly, and write a plan.md for the code changes. use when reconciling a backend repository with brd/prd/technical docs, especially when the docs live in /docs and the goal is to compare implementation with documented behavior before planning code work.

Use the codebase knowledge graph for structural code queries. Triggers on: explore the codebase, understand the architecture, what functions exist, show me the structure, who calls this function, what does X call, trace the call chain, find callers of, show dependencies, impact analysis, dead code, unused functions, high fan-out, refactor candidates, code quality audit, graph query syntax, Cypher query examples, edge types, how to use search_graph.

Apply consistent coding standards for Dash Python web applications. Use when creating new pages, registering pages, writing callbacks, building components, or structuring a Dash app. Based on the Pure webapp reference architecture. Covers: (1) page registration with dash.register_page, (2) callback organization and registration patterns, (3) function-based component conventions, (4) layout with Container/Row/Col grid system, (5) configuration with Pydantic BaseSettings, (6) naming conventions for IDs, CSS classes, and functions.

Run the five git diagnostics from the "Git Commands I Run Before Reading Any Code" essay to audit churn, bug density, velocity, and emergency work. Use when the user needs a repeatable repo health report built from those commands (hotspots, contributor breakdown, bug clusters, velocity curve, and revert frequency).

Write or update a HANDOFF.md document so the next agent with fresh context can continue in-progress work. Use when the user wants to hand off, checkpoint, or summarize work for a future session or agent. Triggers on: write a handoff, create handoff doc, /handoff, summarize progress for next session, checkpoint this work, create a handoff so I can continue later.

Maintain, ingest, query, and lint the LTP Obsidian vault wiki at /mnt/c/Users/joao.barbosa/LTP. Use when the user asks to ingest a note or source into the wiki, query the wiki for information, lint/health-check the wiki, bootstrap the wiki structure for the first time, or organize/synthesize vault notes. Triggers on: ingest this, add to wiki, what does the wiki say about X, query the wiki, lint the wiki, organize my notes, bootstrap the wiki, update the wiki.

Strict LTPLABS Plotly design-system guidance for reusing existing components, preserving the template structure, following curated documentation, and deciding when a new component needs UX-UI approval. Use when working in this repo on UI composition, component selection, documentation-driven implementation, or any task that may require a new component.

Use this skill when the user asks to "write an MR message", "generate a merge request description", "draft an MR", "write a PR message", or wants to prepare a merge/pull request description for the current branch. Analyzes the diff between the current branch and a target branch.

Pragmatic senior engineer code review. Reviews code for structure, dead code, over-engineering, and SOLID violations — but only the ones that actually matter. Uses codebase-memory to map call graphs and find unused symbols before reading the code. Outputs short, actionable findings grouped by severity. Use when: user asks for a code review, asks to review changed files, asks to check for dead code or over-engineering, invokes /pragmatic-review, or asks "is this code clean / solid / well-structured?".