clean-arch-solid-ddd

Guide for Tailwind CSS v4 patterns and best practices. Use when styling components with Tailwind CSS, creating responsive layouts, or working with Tailwind 4 features. Don't use for plain-CSS authoring, CSS-in-JS libraries (styled-components, emotion), or non-Tailwind utility frameworks.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

TanStack Router best practices for type-safe routing, data loading, search params, and navigation. Activate when building React applications with complex routing needs.

TanStack Start best practices for full-stack React applications. Server functions, middleware, SSR, authentication, and deployment patterns. Activate when building full-stack apps with TanStack Start.

Transform code, issues, or context into a detailed prompt/context for another LLM to fix or implement. Use when preparing comprehensive context for external LLM assistance, bug fixes, improvements, or feature implementations. Provides detailed context without implementation suggestions, letting the receiving LLM decide how to implement solutions. Focuses on "what" (problem, requirements, current state) not "how" (implementation approach).

ALWAYS USE THIS SKILL when handling persistent memory in this workspace, including task-start memory recall, explicit "remember" instructions, storing durable preferences/facts, and retrieving prior context. This skill owns the local memory workflow and CLI for init/sync/search/add/recent/stats.

Reviews completed task implementations against project code standards, TypeScript compilation, and test suites. Classifies issues by severity (critical, major, minor, positive) and generates a structured review artifact. Use when a task has been completed and needs quality validation before proceeding. Do not use for full code review of branches, QA testing, or bug fixing.

Implements feature tasks by loading required skills, reading PRD/TechSpec context, analyzing dependencies, and executing the implementation with tests. Marks tasks as complete in tasks.md and triggers the task-reviewer agent upon completion. Use when the user asks to implement a task, execute a task, or start working on a specific task number. Do not use for creating tasks, running QA, code review, or bug fixing.

Especialista em criação de ADRs (Architecture Decision Records) via entrevista estruturada. Use esta skill SEMPRE que o usuário quiser documentar uma decisão arquitetural, criar um ADR, registrar uma escolha técnica, documentar trade-offs de tecnologia, ou quando mencionar palavras como "ADR", "decisão de arquitetura", "registro de decisão", "architecture decision", "documentar decisão", "decisão técnica", "trade-off técnico" ou "por que escolhemos X". Invoque esta skill mesmo que o usuário não use o termo "ADR" explicitamente — se ele estiver tentando documentar formalmente uma escolha técnica, esta skill é a certa.

Cria listas de tarefas detalhadas e padronizadas a partir de um PRD e Tech Spec existentes. Use quando: criar tasks, detalhar tarefas de implementação, quebrar funcionalidade em entregáveis incrementais, gerar arquivos de tarefa individual com subtarefas e critérios de sucesso, planejar sequenciamento de desenvolvimento.

Performs comprehensive code review by analyzing git diff, verifying conformance with project rules, validating test suites, and checking adherence to Tech Spec and Tasks. Generates a structured code review report with severity-classified findings. Use when the user asks for a code review, wants to validate code quality, or needs pre-merge verification. Do not use for QA testing, bug fixing, or task implementation.

Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.

Cria Tech Specs completas e padronizadas a partir de um PRD existente. Use quando: criar tech spec, escrever especificação técnica, documentar decisões arquiteturais, traduzir requisitos em orientações de implementação, detalhar design de componentes e interfaces.

Cria PRDs (Product Requirements Documents) completos e padronizados. Use quando: criar PRD, escrever documento de requisitos, documentar funcionalidade, definir requisitos de produto, redigir especificação funcional.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

Generates C4 architecture diagrams (Context, Container, Component, Code) in PlantUML format from Feature Design Documents (FDDs). Use when users need architecture visualization, complete/update FDDs, or reference feature documentation requiring diagrams.

Generates technical Mermaid diagrams for Feature Design Documents (FDDs) and technical specifications. Creates focused, meaningful diagrams that enhance comprehension of architecture, flows, and system designs.