ap_sales_agent

Auditor independiente. Toma T-{n}-result.md + corre tests él mismo (NO se fía del dev). Spawna agents auditor-{be,fe,agentic} según surface del ticket. Veredicto: APPROVED | CHANGES_REQUESTED | ESCALATED. Self-fix triviales (lint/typo/format) cap 2 iter. Diseño/security/arch → escala. Cuando todos tickets del story audit-passed, escribe REVIEW-final.md. Activa cuando user dice: '/auditor', 'auditá T-N', 'revisá ticket', 'verdict'.

Architect orchestrator Nicolify. Lee 01-spec.md + 02-design-{ui,agentic}.md. Decide qué surfaces toca (BE/FE/agentic). Spawna sub-architects en paralelo (/architect-be, /architect-fe, /architect-agentic). Reúne sus 03-arch-*.md y produce 04-tickets.yaml ordenado con dependencias + owner_eligibility (qwen vs Opus) + acceptance criteria + quality gates. Activa cuando user dice: '/architect', 'diseñemos la arq', 'tickets', 'qué tickets salen', 'arquitectura técnica', 'cómo lo construimos técnicamente'.

Sub-architect Frontend. Invocado por /architect orchestrator. Lee 01-spec.md + 02-design-ui.md + story YAML. Produce 03-arch-fe.md con: routes, components FSD-Lite, hooks React Query, Zod schemas, types TS, tests Vitest+Playwright, server-first boundaries. Activa cuando /architect spawna o user dice: '/architect-fe', 'arq frontend', 'diseña FE'.

Sub-architect Backend. Invocado por /architect orchestrator. Lee 01-spec.md + (02-design-ui.md si mixed) + story YAML. Produce 03-arch-be.md con: endpoints, DTOs Pydantic, SQLA models, migrations idempotent, services, repositories, tests requeridos, cross-cutting (tenant isolation, currency, master-data, PII). Cross-module audit obligatorio. Activa cuando /architect spawna o user dice: '/architect-be', 'arq backend', 'diseña BE'.

Sub-architect Agentic. Invocado por /architect orchestrator cuando story toca copilot/sales_agent. Lee 01-spec.md + 02-design-agentic.md + story YAML. Produce 03-arch-agentic.md con: tools defs (Pydantic schema), prompt slot architecture, LangGraph state, eval suite path, personas/rubrics asignados, observabilidad (trace + cost), trial policy. Carga sales-agent-expert, copilot-expert, tessl__langgraph, claude-api. Activa cuando /architect spawna o user dice: '/architect-agentic', 'arq del agente', 'diseña agentic'.

Generate, audit, and compress AI-optimized documentation for codebases. This skill applies research-backed principles from three peer-reviewed papers to create documentation that maximizes AI agent performance instead of degrading it. Use this skill whenever the user asks to "write docs", "create a CLAUDE.md", "document a module", "audit documentation", "compress docs", "optimize docs for AI", "write module docs", "create domain documentation", "review doc quality", or mentions documentation bloat, token waste, or AI context efficiency. Also trigger when the user references "ai-docs principles", "telegram style docs", or wants to apply the "Lost in the Middle", "Less is More", or "AGENTS.md" research findings.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components.

Tailwind CSS patterns and conventions for frontend apps. Use when writing component styles, layouts, or working with CSS classes.

Especialista Senior en Frontend (Next.js, React, Tailwind, FSD) para la construcción de interfaces. Úsalo cuando el usuario pida "nueva funcionalidad", "modifica el front", "crea un componente", "actualiza el diseño" o "refactoriza la UI".

Especialista Senior en Python, FastAPI y Domain-Driven Design (DDD) para backend. Úsalo cuando necesites crear endpoints, modificar lógica de negocio, diseñar entidades, actualizar servicios o trabajar con bases de datos.

Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.