Merge pull request #17 from CoolSpring8/agents-md-revision

Update AGENTS.md with development practices and coding guidelines

Author: CoolSpring8

AGENTS.md

@@ -3,28 +3,35 @@
 ## Project Structure & Module Organization
 
 - Source lives in `src/` (`index.tsx`, `App.tsx`, `index.css`). Build output goes to `dist/`.
-- Providers only in `index.tsx` (e.g., `MantineProvider`). `App.tsx` owns application state, while presentational pieces live in `src/components/`.
+- Providers only in `index.tsx` (e.g., `MantineProvider`). `App.tsx` coordinates views and settings; conversation state and snapshots live in the Zustand store (`src/tree/useConversationTree.ts`, `src/tree/types.ts`), and AI provider helpers live in `src/ai/openaiCompatible.ts`.
+- Components under `src/components/` include their own UI behavior (hover/edit states, popovers, menus) rather than being purely presentational.
 - Key config: `rsbuild.config.mjs`, `tsconfig.json`, `tailwind.config.js`, `postcss.config.js`, `biome.json`.
 
 ## Build, Test, and Development Commands
 
 - Install: `bun install` (use Bun for everything; a `bun.lock` is present).
 - Dev server: `bun dev` (Rsbuild) — starts hot‑reload and opens the browser.
 - Production build: `bun build-dist` — emits static assets to `dist/` (scripts/styles are inlined by Rsbuild config).
-- Preview production build: `bun preview` — serves the built output locally.
 
 ## Coding Style & Naming Conventions
 
-- Language: TypeScript + React 18; Tailwind for styling.
-- Indentation: one tab (Biome default). Keep code concise and self‑documenting.
+- Language: TypeScript + React 18; Mantine for UI; Tailwind for styling.
+- Indentation: one tab (Biome default) except for Markdown files where space indentation is used. Keep code concise and self‑documenting.
 - Formatting: use Biome. Run `bunx biome check --write .` to format and organize imports.
-- Components: prefer small presentational components in `src/components/`; keep core state and data flow inside `App.tsx`.
+- Type-checking: use tsc. Run `bunx tsc --noEmit` to check for type errors.
+- Components: keep UI logic close to the component (e.g., hover/edit toggles in `MessageItem`, menu interactions in `DiagramView`); shared conversation/tree logic belongs in the store.
 - CSS: prefer Tailwind utilities; add global styles in `src/index.css` only when necessary.
 
-## Testing Guidelines
+## Providers & Capabilities
 
-- No test runner is configured. Include clear manual verification steps in PRs; optional minimal tests (`*.test.ts(x)`) can land in a follow‑up.
-- Verify `bun build-dist` and core flows in README “Usage Tips”.
+- OpenAI-compatible: supports chat and text completion views.
+- Built-in AI (Chrome/Edge): chat-only; text view is disabled.
+
+## Validation & DevTools MCP
+
+- Assume `bun dev` is already running locally; don’t start it from the agent unless explicitly asked.
+- Use Chrome DevTools MCP to navigate to `http://localhost:8080/` to check the UI after changes.
+- Avoid shell curls to localhost unless the user explicitly requests; rely on MCP interactions for UI checks.
 
 ## Commit & Pull Request Guidelines