anticapture-dashboard

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

Dashboard Package Guide

Use This Skill When

• You are editing files in apps/dashboard.
• You are adding or refactoring UI/features/routes.
• You are wiring data from the @anticapture/client REST hooks into the UI.
• You are updating dashboard tests or lint/type issues.

Package Snapshot

• Location: apps/dashboard
• Port: 3000
• Runtime: Next.js 16, React 19, Tailwind CSS 4, React Query 5 (via @anticapture/client REST SDK), wagmi 2, viem 2, Recharts 2
• Purpose: DAO governance analytics, risk assessment, and community tools
• DAOs: one config file per DAO in apps/dashboard/shared/dao-config/ — that directory is the current roster; don't hard-code DAO lists elsewhere

Commands

pnpm dashboard dev          # Start dev server on :3000
pnpm dashboard typecheck    # Type checking
pnpm dashboard lint         # Lint checking
pnpm dashboard lint:fix     # Auto-fix lint issues
pnpm dashboard test         # Run Jest unit tests
pnpm dashboard build        # Production build

Environment Variables (apps/dashboard/.env)

Variable	Required	Description
ANTICAPTURE_API_URL	yes	Gateful REST API base URL
NEXT_PUBLIC_WALLET_CONNECT_PROJECT_ID	yes	WalletConnect project ID
ERPC_URL	yes	eRPC dashboard project URL
ERPC_SECRET	yes	eRPC server-side auth
NEXT_PUBLIC_SITE_URL	no	Site URL for SEO/meta
RESEND_API_KEY	no	Resend email API key
RESEND_FROM_EMAIL	no	Sender email address
CONTACT_EMAIL	no	Recipient for contact form

Architecture

Principles

1. Server-First: Components are Server Components by default. Add "use client" only at interaction boundaries.
2. Features are self-contained: Each feature owns its components, hooks, utils, and types.
3. No cross-feature imports: Features must never import from other features. Move shared code to shared/.
4. Thin pages, rich features: Pages compose features; features own business logic.

Folder Structure

apps/dashboard/
├── app/                        # Next.js App Router (routing + composition only)
│   ├── (landing)/              # Public pages
│   ├── [daoId]/
│   │   ├── (shell)/            # Main DAO pages (sidebar layout)
│   │   │   ├── attack-profitability/
│   │   │   ├── holders-and-delegates/
│   │   │   ├── resilience-stages/
│   │   │   ├── risk-analysis/
│   │   │   └── token-distribution/
│   │   └── (nested)/governance/
│   └── api/
├── features/                   # Domain modules (business logic)
│   └── <feature-name>/
│       ├── components/
│       ├── hooks/
│       ├── types.ts
│       └── utils/
├── shared/                     # Cross-cutting concerns
│   ├── components/
│   │   ├── design-system/
│   │   ├── layout/
│   │   ├── charts/
│   │   └── icons/
│   ├── hooks/
│   ├── dao-config/
│   ├── types/
│   ├── constants/
│   ├── providers/
│   └── utils/
├── widgets/
└── public/

Placement Rules

What you're adding	Where it goes
New dashboard feature	features/<feature-name>/
Feature-specific component/hook/util	features/<feature>/...
Reusable UI component	shared/components/
Design system component	shared/components/design-system/
Layout component	shared/components/layout/
Shared hook or utility	shared/hooks/ or shared/utils/
Shared types	shared/types/
Next.js route	app/
Cross-page composed sections	widgets/

Workflow

1. Place code by ownership per the placement rules above.
2. Reuse existing shared components before adding new primitives.
3. Keep route-level composition in app/...; avoid pushing route concerns into low-level components.
4. Follow code conventions in ./references/code-conventions.md.
5. Follow engineering patterns in ./references/engineering-patterns.md.
6. Follow data/state/testing patterns in ./references/data-state-testing.md.
7. Verify:
   • pnpm dashboard typecheck
   • pnpm dashboard lint
   • pnpm dashboard test (when behavior changes)

Guardrails

• Do not add feature-specific logic into shared unless reused by multiple features.
• Prefer extending existing design-system/shared UI instead of creating near-duplicates.
• Server Components by default; add "use client" only at interactive boundaries.
• Do not run the indexer for dashboard tasks unless explicitly requested.
• Use @/* path aliases for all imports.