Single owner of everything under docs/architecture/ — ADRs, architecture and design documents, and architecture diagrams. Routes each deliverable to the right engine: /mermaid-architecture for Markdown-native diagrams, /drawio-architecture for editable .drawio diagrams, and the optional third-party archify skill for interactive standalone HTML diagrams (installed on demand via `npx skills add tt-a1i/archify`, only with explicit user approval). Use whenever architecture documentation, ADRs, or architecture diagrams must be created or updated.
by Iván
Central entry point of the afonsoft agent harness. Use when starting a new project, resuming an existing one, planning features/Epics/releases, or running any multi-step agent-driven work. Validates and reconciles SPECs (SDD), audits the codebase and harness for gaps (security, architecture, performance, hygiene), proposes improvements, fragments work into GitHub Issues, delegates implementation/QA/review to specialized skills, and re-validates everything until delivery. Also use to review unapproved SPECs, reconcile open GitHub Issues with code, or run a final gap check before closing a release.
Use when the user asks to connect an AI agent to external apps via Composio, or when Composio CLI or MCP setup fails.
Use when initializing or migrating an AI agent harness in a repository.
Use when turning approved plans, specs, PRDs, or Epics into trackable GitHub Issues.
Use when building a new MCP server in TypeScript, Python, or C# that exposes tools to LLMs.
Use when generating or editing draw.io/diagrams.net architecture diagrams via MCP or native XML.
Use when the user wants to configure, authenticate, or use Google NotebookLM via the nlm CLI or MCP.
Use when starting a new .NET/Blazor/Angular MVP project in an empty repository.
Use when generating or updating a project README.md or CHANGELOG.md.
Use when raising code quality or test coverage across a .NET, Java, or Python repository.
Use when analyzing SonarQube issues and turning them into SPEC SDDs for TDD implementation.
Use when the user needs to create or refine a feature SPEC SDD before implementation.
Use when fixing SonarQube code quality issues automatically across any language or framework — issue analysis, fix generation, unit tests, and coverage. Supports Community, Enterprise, and custom SonarQube deployments via environment variables. Do NOT use for general code review without SonarQube (use code-review-and-quality), for whole-repo quality interventions without SonarQube (use quality-test-implementation), or for non-SonarQube static analysis tools. Part of the afonsoft/skills collection.
Use when auditing a repository for evidence-backed gaps between code, SPECs, architecture, and documentation — before a release, after a review, or when the user asks what is missing or divergent. Confirmed gaps become Draft SPECs via write-specs, a tracked GitHub Epic via create-issues, and orchestrated execution via orchestrator, with an explicit approval gate before any external action.
Use when the user needs to create or refine a feature SPEC SDD before implementation.
Use when the user asks to implement an approved SPEC SDD using test-driven development.
Use when reviewing code before it merges, whether written by an agent or a human.
by afonsoft
Use when designing, redesigning, or improving a frontend interface in Angular, React, or Blazor. Use for landing pages, dashboards, components, forms, and responsive layouts that must work mobile-first and then scale to desktop.
by afonsoft
Use when generating, documenting, or updating architecture diagrams, flowcharts, sequence, ER, class, or state diagrams using Mermaid in docs/architecture/.
by afonsoft
Use when the user asks to implement an approved SPEC SDD using test-driven development.
Test-driven development using the approved SPEC SDD as the source of truth. Reads `.specs/SPEC-{YYYYMMDD}-{feature}.md`, turns requirements and acceptance criteria into red-green-refactor vertical slices. Use when implementing a feature or bugfix after the SPEC is approved. User-facing questions and recommendations must be in Portuguese (pt-BR). Part of the afonsoft/skills collection.
Use when the user asks to implement an approved SPEC SDD using test-driven development.
by afonsoft