FOUNDATION

Use when reviewing pending code changes (working tree + staged) before commit. Checks against FOUNDATION conventions, architecture layer rules, validates compilation, and flags violations of CLAUDE.md / development.md rules.

Creates a new FOUNDATION release — bumps version, updates CHANGELOG, SoftwareRelease.ttl, README, commits, tags, and publishes a GitHub release.

Start the FOUNDATION dev server (npm run tauri dev) under PM2 management. Use when the app is not running and Claude needs it up (MCP, QA, visual validation) or the user asks to start the server.

Restart the FOUNDATION dev server via PM2, with optional Vite/SvelteKit cache clean. Use after config changes, when the Vite SSR module runner goes zombie (transport invoke timed out), or when the user asks for a restart.

Stop the FOUNDATION dev server managed by PM2, including orphan child cleanup (FOUNDATION.exe / cargo). Use when the user asks to stop the server or Claude needs a clean shutdown.

Use when the user asks to check for available dependency updates in FOUNDATION — phrases like "verifica atualizações de dependências", "o que tem pra atualizar", "tem versão nova das libs", "deps desatualizadas". Runs the Rust deps-check binary (npm + Cargo) and presents the report. Same check that runs automatically on the first session of each day.

Use when the user (PO) asks to fix a Foundation bug by IRI — e.g. "fix bug foundation:Bug_123", "corrija o bug foundation:Bug_456", "resolva o bug <IRI>". Orchestrates the bug pipeline: `support` (investigation & technical dossier) → `architect` Modo Triagem **Briefing** (decide BE/FE/both and produce per-dev briefings) → dispatch `developer-backend` / `developer-frontend` with the briefings → `architect` Modo Triagem **Costura** (validate builds, consolidate `## Como testar`, move to Em Validação (QA)) → `qa` (validation gate before Concluído). Sub-agents cannot call other sub-agents in Claude — this skill (which runs in the main loop) IS the orchestrator. The PO never invokes devs directly; the bug is NEVER closed without QA validation. Always invoke this skill when the user mentions a bug IRI.

Use when the user (PO) asks to implement / develop a Foundation User Story that is already in status "Planejado" or "Pronto para Dev" — orchestrates execution by (1) calling the `architect` agent in Modo Execução **Briefing** to validate state, move the US to Em Progresso and produce per-dev briefings; (2) dispatching `developer-backend` and `developer-frontend` in parallel (or sequential when the plan says so) with the briefings; (3) calling the `architect` again in Modo Execução **Costura** with the dev returns to validate builds, consolidate `## Como testar` (merging UX's "Validação pelo usuário" checklist when present), log changelog and move the story to "Em Validação (QA)". Sub-agents cannot call other sub-agents in Claude — this skill (which runs in the main loop) IS the orchestrator. The PO never talks to devs directly; the skill mediates. Skill name follows entity-action convention.

Use when the user (PO) asks to plan a Foundation User Story (e.g. foundation:UserStory) — orchestrates planning by FIRST checking the UX heuristic (does the story touch interface?), calling the `ux` agent ahead of time when it does, then delegating to the `architect` agent in Modo Planejamento with the UX section already in hand. The architect analyzes Project + Feature + Story context, produces the architecture-level plan, stores it in foundation:implementationPlan and moves the story to status "Planejado". Sub-agents cannot call other sub-agents in Claude — this skill (which runs in the main loop) IS the orchestrator. The PO never talks to devs/UX directly; the skill mediates. Skill name follows entity-action convention.

Use when the user asks to reconcile a Foundation SoftwareFeature with the current codebase — investigates what is implemented, creates UserStories for capabilities that exist in code but not in the graph, marks UserStories as "Mudança Pendente" when the code drifted from the original AC, and flags stories that have no code at all. Skill name follows entity-action convention.

Use when the user asks to implement / develop a Foundation SoftwareFeature whose UserStories are already planned — orchestrates execution of each child story via /userstory-implement, then moves the Feature to "Testando" for user validation. Skill name follows entity-action convention.

Use when the user asks to plan a Foundation SoftwareFeature — orchestrates planning of all child UserStories via /userstory-plan, then moves the Feature from "Pendente" to "Planejado". Skill name follows entity-action convention.

Use when permanently removing a Foundation SoftwareFeature — lists all dependent UserStories and other backlinks, retracts each child UserStory, then retracts the Feature individual. Skill name follows entity-action convention.

Use when committing changes to FOUNDATION. Covers pre-commit validation, conventional commit format in Portuguese, and project-specific commit conventions.

Use when modifying an existing Foundation MCP tool — updating its handler logic, parameters, description, or input/output schema. Keeps the Rust template, the dispatch wiring, and the foundation:MCPTool individual in sync. NOT for creating new tools (use mcp-create) or removing them (use mcp-remove).

Creates a new Foundation MCP tool — implements the Rust handler, registers it in the tool template registry, dispatches it from the executor, and creates the foundation:MCPTool individual in the ontology.

Use when permanently removing a Foundation MCP tool — retracts the foundation:MCPTool individual, deletes the Rust handler, removes the ToolTemplate registration, and removes the dispatch branch.

Use when modifying an existing Foundation widget — updating its WidgetType ontology metadata (icon, default size, supported class, usage note) or its Svelte component logic. NOT for creating new widgets (use widget-create) or removing them (use widget-remove).

Creates a new Foundation blackboard widget — registers it in the ontology, scaffolds the Svelte component, and wires it into WidgetManager.

Use when permanently removing a Foundation widget — retracts the WidgetType individual, deletes the Svelte component file, and removes the WidgetManager dispatch branch.