question is "is this schema good" rather than "is this change safe". |
| `senior-frontend-engineering` | Design | Review or ship a React/component/SPA/Vite frontend change — state ownership, React rendering correctness, loading/empty/error states
documentation lead | Documentation, a report, a README, or an ADR needs writing |
| **Pixel** | Frontend Developer in Eric's pod | React, TypeScript, or Tailwind UI components must be built |
| **Diesel** | Backend
Protocol (MCP) servers from OpenAPI/Swagger schemas. The system uses a microservices architecture with separate frontend, backend API, background worker, Redis queue, and PostgreSQL database - all orchestrated via Docker Compose.
## Architecture
111mo agoReviewMountCreate a free account to mount
definitions, scripts, and manifest.
> **Note:** Users can add their own agents (e.g., `@backend-coder`, `@frontend-coder`) via `/copilot-init` based on their project's needs. See `docs/creating-agents.md` for guidance
Overview
This is a **3-tier Azure application** demonstrating enterprise patterns with passwordless authentication:
- **Frontend** (`app/`): React + TypeScript + Vite SPA deployed as Azure Static Web App
- **Backend API** (`api/`): Microsoft
variables. NEVER place secrets in client-side code, config files committed to git, or frontend bundles.
- Confidential data (email, PII, private messages) MUST be encrypted at rest and in transit
request path into a queue consumer.
Never put a provider API key in the frontend. Proxy through a Worker and
keep the key in `wrangler secret put`.
Full limits, workflow
Foundry agent
DEMO: deterministic C# composer
```
- Data flows left-to-right only. The frontend is mode-blind (LIVE vs DEMO).
- **Tools call data over HTTP** through the mock API surface
Example tasks:
- "Get last 50 lines from the backend container"
- "Summarize incidents for the frontend container"
- "Run triage_incident on backend"
## Workflow Examples
**Incident response (full flow):**
1. Call `docker
ALWAYS** create ALL mandatory documents at each phase boundary.
5. Code **MUST** live in `frontend/` or `backend/`. No other code directories.
6. When the user says "build X" → Start with
Design System & Frontend Guidelines
> **Drop-in file.** Place this `CLAUDE.md` in a project root (or merge it into an existing one) and Claude Code will load it automatically. It defines
project has no backend that already covers it. That includes:
- an API the frontend calls
- AI processing such as extraction, summaries, classification or generation
- research, search or scraping
- storing data
Laravel-based personal planning system with task management, user profiles, and Jira integration.
- Frontend uses Inertia.js, TypeScript, and Vite for SPA experience.
- Dockerized development via Laravel Sail for consistency