skills

Full lifecycle for planning and documenting a new feature. Use when starting a new feature, writing a PRD from scratch with an interview, creating a technical spike for unknowns, or generating an implementation task checklist. Covers the spike → PRD → tasks workflow with versioned, non-destructive documents under docs/[feature-name]/. Trigger when the user says "plan a feature", "let's start a new feature", "write a spike", "create tasks for this", or when entering Plan mode.

Synthesize the current conversation into a PRD saved under docs/. Use after discussing a feature or change with the agent — no interview, just capture what has already been decided, surface open questions, and write the document. Trigger when the user says "write a PRD", "document this", "save this as a spec", or after a design discussion that needs to be captured before implementation starts.

Use when scaffolding, working in, or reasoning about a Better-T-Stack (BTS) project. Covers the standard BTS monorepo layout, technology choices and personal defaults (ORM, database, auth, package manager, linting), and how the stack options compose. Trigger when the user asks about BTS setup, technology choices within a BTS project, or how to extend a BTS scaffold with additional packages or patterns.

Use when reviewing, correcting, or auditing a Brazilian academic paper (TCC, dissertação, artigo, monografia) for conformance with ABNT standards (NBR 14724, NBR 6023, NBR 10520, NBR 6028) implemented via abnTeX2, and for orthographic and stylistic correctness in Portuguese (pt-BR). Covers formatting rules (margins, font, spacing, pagination), document structure (capa, folha de rosto, sumário, elementos pré/pós-textuais), citations, references, figures, tables, quadros, appendices, and academic writing register. Trigger when the user asks to review, correct, proofread, or check a LaTeX TCC or academic paper against ABNT norms.

Use when writing or setting up a Brazilian academic paper (TCC, dissertação, artigo) in LaTeX following ABNT standards via abnTeX2. Covers project structure, the LuaLaTeX + Mermaid diagram rendering workflow, Makefile build (PDF + DOCX via Pandoc), GitHub Actions CI, and the Markdown-first drafting approach. Trigger when the user asks about LaTeX for academic papers, ABNT formatting, abnTeX2, compiling a monograph, or embedding diagrams in a thesis.

Use when analyzing the results of a machine learning classification experiment and generating a comparative report. Covers constructing a structured prompt from holdout and cross-validation metrics across multiple models, calling Gemini or Ollama, and saving the output as a Markdown report. Trigger when the user asks how to summarize ML experiment results, generate an analysis report from model metrics, or compare classifiers automatically.

Use when designing or implementing the API layer of a fullstack TypeScript application. Covers the thin-transport pattern (tRPC or ORPC as HTTP transport only), request-scoped context injection, service classes as the business logic layer, and the provider/adapter pattern for external integrations. Applies regardless of whether the HTTP transport is tRPC, ORPC, Express, Fastify, or Hono — the service layer and provider pattern are transport-agnostic. Trigger when the user asks about where to put business logic, how to structure API routes, how to inject context (auth session, db, services), or how to abstract external dependencies.