feat: integrate TrueFi DAO (indexer + API)

.agents/skills/anticapture-design-system/references/auditing-checklist.md

@@ -18,7 +18,20 @@ Use this checklist when **updating an existing** design system component. Always
 - [ ] Read the `index.ts` re-export if present
 - [ ] Check for other components that import from the same shared types/styles
 
-### 3. Diff: Code vs Figma
+### 3. Audit Folder Structure
+
+Before touching any code, verify the component follows the hierarchy rule:
+
+- [ ] **Root composite** (`Component.tsx`) has `.stories.tsx` + `.figma.tsx` alongside it
+- [ ] **Sub-parts that are named Figma components** live in their own `component-name/` subfolder with `.stories.tsx` + `.figma.tsx`
+- [ ] **Internal building blocks** (only used by one parent, no independent Figma frame) are flat `.tsx` files inside the parent subfolder — no own subfolder, no stories, no figma
+- [ ] **`index.ts`** uses explicit named exports (`export { X }`, `export type { Y }`) — never `export *`
+- [ ] **`types.ts`** exists for shared prop types; inline prop types only acceptable when tied to a CVA variant object
+- [ ] **`cn()`** imported from `@/shared/utils/cn` (not `@/shared/utils`)
+- [ ] **No imports from `@/shared/components`** inside design-system components — use direct source paths to avoid circular deps
+- [ ] Component belongs in the correct category (`RadioButton` → `form/fields/`, not `buttons/`)
+
+### 4. Diff: Code vs Figma
 
 Compare what the code currently implements against what Figma defines:
 

.agents/skills/anticapture-design-system/references/new-component-checklist.md

@@ -72,6 +72,44 @@ Before building any sub-element from scratch, ask:
 | Standalone (one variant axis)     | `category/Component.tsx` + `Component.stories.tsx` + `Component.figma.tsx`                                                        |
 | A family with shared types/styles | `category/types.ts` + `category/styles.ts` + `category/component/Component.tsx` + `Component.stories.tsx` + `Component.figma.tsx` |
 
+### Composite vs internal sub-parts
+
+When a component has sub-parts (e.g. a Drawer with a header and body), apply this rule:
+
+**A sub-part gets its own named subfolder + `.stories.tsx` + `.figma.tsx` when:**
+
+- A consumer would use it directly (it appears in the public `index.ts`)
+- It exists as a named, documented component in Figma
+
+**A sub-part is a flat file inside the composite's folder when:**
+
+- It is only ever used by one parent composite (not re-exported publicly)
+- It is purely structural — renders one specific slot of its parent
+- It has no independent Figma frame
+
+> Ask yourself: "Does this appear in Figma as its own named component?" If yes → subfolder + stories + figma. If it's just a structural slot inside a bigger component → flat file.
+
+**Example — Drawer:**
+
+```
+drawer/
+├── Drawer.tsx                 ← composite root → stories + figma
+├── Drawer.stories.tsx
+├── Drawer.figma.tsx
+├── drawer-header/             ← composite sub-part → stories + figma
+│   ├── DrawerHeader.tsx
+│   ├── DrawerHeader.stories.tsx
+│   ├── DrawerHeader.figma.tsx
+│   ├── DrawerTitle.tsx        ← internal flat file (only used by DrawerHeader)
+│   ├── DrawerSubtitle.tsx
+│   ├── DrawerTabs.tsx
+│   └── DrawerCloseButton.tsx
+└── drawer-body/               ← composite sub-part → stories + figma
+    ├── DrawerBody.tsx
+    ├── DrawerBody.stories.tsx
+    └── DrawerBody.figma.tsx
+```
+
 ---
 
 ## 4. Create Files