thejoaov

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.

Use when setting up or improving a GitHub Actions release workflow that generates release notes automatically using an LLM. Covers resolving the git tag range between releases, collecting commits, calling the Gemini API to group and summarize changes, stripping markdown fencing artifacts, and falling back to a plain commit list when no API key is available. Trigger when the user asks about automated release notes, AI changelog generation, or GitHub Actions release workflow.

Use when implementing any agent action that has an irreversible or externally visible side effect — sending a message, email, or notification; posting to a public channel; making a payment; deploying to production; deleting data; or calling a third-party API that cannot be undone. The agent must always draft and present the action for explicit user approval before executing it. Trigger when the user asks the agent to send, post, deploy, delete, or perform any action whose side effects cannot be rolled back.

Use when building or extending an Electron system tray application. Covers tray window creation, smart window positioning relative to the tray icon (top/bottom/left/right detection, multi-monitor, Linux fallback), macOS Dock hiding, always-on-top pop-up window behavior, blur-to-hide with cursor-in-tray guard, right-click context menu, and IPC handles for programmatic show/hide. Trigger when the user asks about Electron tray, menu bar app, system tray window, popover window positioning, or macOS menu bar app.

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.

Use when setting up, organizing, or reasoning about a TypeScript monorepo. Covers workspace managers (Bun, pnpm), Turborepo pipelines and caching, package boundary conventions (apps/packages/tooling tiers), dependency management with catalogs and version pinning, shared tooling packages, and cross-workspace build orchestration. Trigger when the user asks about monorepo structure, where to add a new package, how to configure Turborepo tasks, or how to manage shared dependencies.

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.