blockful/anticapture

anticapture-dashboard

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

local-dev-stack

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.

anticapture-api

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

anticapture-gateful

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.

changesets

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

dao-integration

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.

dashboard-dao

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).

testing

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

tenderly-alerts

Use when setting up real-time blockchain monitoring on Tenderly — creating wallet/contract alerts (balance thresholds, transaction status, function calls, ERC20 transfers, event emissions), wiring Slack/webhook notifications via the Alerts REST API,…

anticapture-design-system

Use when creating, updating, or auditing design system components in shared/components/design-system/. Enforces Figma-first workflow, token governance, and pixel-perfect implementation.

anticapture-indexer

Use for apps/indexer work: event handlers, DAO indexer implementations, Ponder schema/config changes, and indexer safety checks.

grill-me

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".