Menu
Process model, data flow, and feature placement guide for Anvil so agents can modify the right layer with minimal thrash.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Standard workflow for adding a new Anvil feature that spans shared contracts, IPC, preload, services, persistence, and renderer UI.
Add a new top-level renderer screen to Anvil and wire it into routing, navigation, and the existing workspace-gated shell.
Use for Azure cost analysis, right-sizing, FinOps, SKU selection, reserved instances, and detecting over-engineering. Grounded in Well-Architected Cost Optimisation pillar.
Use when designing a new Azure workload from scratch. Covers gold-standard architecture patterns, Landing Zones, service selection, IaC, observability, and DR. Avoids over-engineering.
Use when evaluating migration of existing systems to Azure. Covers lift-and-shift vs rearchitect decisions, the 5 Rs, phased migration planning, and Azure Migrate tooling.
Use for Azure architecture review, service selection, design decisions, and Well-Architected Framework guidance. Interactive consultant that challenges assumptions and cites Microsoft docs.
| name | architecture-overview |
| description | Process model, data flow, and feature placement guide for Anvil so agents can modify the right layer with minimal thrash. |
Anvil is a multi-process Electron app with a strict bridge between the UI and privileged code.
src/main/: privileged Node/Electron runtimesrc/preload/: typed bridge exposed as window.anvil plus window.brandsrc/renderer/: React UIsrc/shared/: shared types and IPC API contractsrc/main/db/: schema, inline migrations, and database bootstrapprompts/: persona and prompt assets used by AI workflowsmobile/: Expo Router companion app in the pnpm workspacevideo/: separate Remotion projectMost product features follow this path:
src/renderer/components/security/SecurityView.tsx.window.anvil from src/preload/index.ts.src/main/ipc/*.ipc.ts.src/main/services/*.service.ts.src/main/db/database.ts and the schema in src/main/db/schema.ts, or call external tools/APIs as needed.src/main/index.ts is the startup hub. It:
If a new privileged feature exists, it usually needs registration there.
src/main/ipc/: one registration file per feature areasrc/main/services/: core business logic and integrationssrc/main/services/repobase.service.ts and repobase-mcp.service.ts: repository indexing and Repobase integrationsrc/main/services/foundry.service.ts and llm.service.ts: LLM/provider behaviorsrc/main/services/workspace.service.ts: workspace persistence and repo groupingsrc/main/services/git.service.ts: git operations shared across flowssrc/main/services/terminal.service.ts: PTY session lifecyclesrc/renderer/App.tsx owns:
Feature screens live in src/renderer/components/ by area:
repos/chat/onboard/workitems/ba/security/codereview/docs/diagrams/adrs/automations/editor/diagnostics/governance/terminal/workspace/layout/Shared state is mostly held in:
src/renderer/contexts/WorkspaceContext.tsxsrc/renderer/contexts/ChatContext.tsxsrc/renderer/contexts/BrandContext.tsxsrc/renderer/contexts/BaContext.tsxThe schema in src/main/db/schema.ts covers:
Never silently rewrite historical migrations. Add a new target-version entry to MIGRATIONS in src/main/db/schema.ts and keep SCHEMA_VERSION aligned.
If you are:
src/shared/ipc-api.d.ts, then src/main/ipc/, src/preload/index.ts, and a new or updated servicesrc/renderer/components/, then wire src/renderer/App.tsx and likely src/renderer/components/layout/Sidebar.tsxsrc/renderer/contexts/WorkspaceContext.tsx, src/main/ipc/workspace.ipc.ts, and src/main/services/workspace.service.tssrc/main/services/onboard.service.ts, src/main/ipc/onboard.ipc.ts, and src/renderer/components/onboard/src/main/ipc/repo.ipc.ts, src/main/services/indexer.service.ts, repobase.service.ts, and repo summary persistenceKeep each layer honest: