blockful

Use for apps/api work: adding or changing REST controllers, services, repositories, mappers, clients, schema mapping, or API tests.

Use for apps/dashboard work: routes, features, shared components/hooks, styling, data-fetching wiring, and dashboard tests.

Use for apps/gateful work: REST aggregation of DAO APIs, Hono + zod-openapi routing, DAO source discovery (DAO_API_*), proxying, caching, circuit breaker, and gateway tests.

Use when preparing a PR — adding a changeset, choosing bump types, empty changesets, API-contract changes, or understanding the version/release flow.

Use when adding a new DAO to the Anticapture platform. Covers all five components — indexer, API, gateway, dashboard, and enum sync — with a step-by-step checklist.

Use when adding a new DAO to the Anticapture dashboard. Walks through enum registration, config creation, quorum label, icon setup, and wiring — with exact file paths and a worked example (FLUID).

Use when you need to hit the running local stack (API, gateful, dashboard, indexer) to test or verify a change. Covers scripts/dev.sh, hot reload, and the ports each service listens on.

Use when writing, reviewing, or improving tests for any package in the Anticapture monorepo. Covers unit, integration, and E2E tests.

Review a DAO governance proposal. Use when the user shares a Tally or Anticapture URL (live proposal or draft), asks to review a proposal, or wants to verify calldata. Detects the phase automatically from the URL and runs the full review workflow.

Scaffold a new DAO into the governance calldata verification system. Creates directory structure, interfaces, base test class, and registry entry. Use when adding support for a new DAO.

Render UI in the user's browser. Two tools — show_ui for asking the user a question that needs a structured answer back (forms, pickers, confirmations, dashboards-as-input, multi-step wizards), and show_html for showing a rich visualization the user just looks at (reports, dashboards, charts, infographics, comparison tables, slides). Trigger on "show me", "ask me", "let me pick", "confirm before you", "give me a dashboard", "render a chart", "show a report" — anything that beats plain text in chat. Rule: if anything has to come back from the user, show_ui. If the user just looks, show_html.