mblua

Crear, abrir y mantener un JSON canónico conversacional en VisualSpecs, con componentes y relaciones que se actualizan mientras avanza una charla, sin modificar el código ni la configuración de la aplicación. Usar cuando el usuario quiera visualizar una idea viva en VisualSpecs o pida levantar la app apuntando a un canónico.

Before asking the user to choose between two or more options that differ in anything visual, spatial, or UI/layout-related, first build a quick self-contained HTML artifact that shows the CURRENT state and each option side by side (with a selector to switch), to scale and with honest metrics, so the user decides with the picture in front of them. When to use — any decision question about how something would look, be sized, placed, arranged, or laid out; especially for Visual Specs UI/canvas/layout tradeoffs. Load right before an AskUserQuestion whose options a person could see.

Start, verify, and open the local Visual Specs application from whatever CodebaseConstellation checkout the caller is working in. Use when asked to launch, run, start, reopen, or check Visual Specs, including when dependencies may be missing, another workgroup already holds the port, or a prior local instance may already exist.

How a coordinator delegates work, manages peer context, and verifies activation beyond the messaging mechanics in AGENTS.md.

Git, issue-branch, PR and version mechanics for Visual Specs repositories. Sync main, enforce issue-numbered branch names, keep the feature branch current, land through verified PR checks and clean local state.

Canonical Visual Specs delivery workflow. Confirm the change, assign one owner per artifact, use the constructive and adversarial gates, and land an issue-backed branch through a verified PR.

How a coordinator scopes a new request before delegating. Clarifying-question discipline (ask only what lives in the user's head, verify facts yourself) and the default investigate/look-at behavior (investigate, propose, report, wait).

Coordinate AgentsCommander file-based messaging and delegation to team peers, including a mandatory clean-context boundary before every new assignment and context preservation for same-task follow-ups. Use whenever a coordinator assigns, delegates, reviews, follows up with, or sends work to a team member.

How the Root Agent offers Agency Agents role templates before creating any specialist agent: the mandatory offer, describing Agency Agents from real local data only (never invented), the bounded skip exceptions, the agency-templates CLI flow, and handling a missing template cache.

Audit where governance instructions belong (Role.md, skill, global policy, workflow docs, memory, or an agent-boundary change); enforce minimal verbosity in roles and skills. Diagnostic by default.

Ship current branch to main — commit, push, update from origin/main, merge, cleanup. Use when done with a feature/fix branch.