stoa / control-plane-ui
CLAUDE.md9 starsChanged 7 months agoApache-2.0View on GitHub
Détail on-demand: .claude/docs/code-style-typescript.md, testing-standards.md.
- Installs packages
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- cli/CLAUDE.mdCLAUDE.md
- control-plane-api/CLAUDE.mdCLAUDE.md
- e2e/CLAUDE.mdCLAUDE.md
- portal/CLAUDE.mdCLAUDE.md
- stoa-gateway/CLAUDE.mdCLAUDE.md
- analyticsSkill
- cartoSkill
- ci-debugSkill
- ci-fixSkill
- competitive-watchSkill
- councilSkill
- decomposeSkill
- extractSkill
- fill-cycleSkill
- generate-backlogSkill
- impactSkill
- memory-consolidateSkill
- monitor-cdSkill
- parallel-reviewSkill
- pr-guardianSkill
- rewriteSkill
- roadmapSkill
- spec-drivenSkill
- sync-planSkill
- verify-megaSkill
The file
Files
Console UI (Control Plane)
Overview
React admin console for API Providers. Manage tenants, APIs, deployments, subscriptions, gateways, and platform configuration.
Tech Stack
- React 18.2, TypeScript, Vite
- TanStack React Query 5, Zustand (state), Axios
- react-oidc-context (Keycloak auth), oidc-client-ts
- Tailwind CSS 3.4, Lucide icons
- vitest + React Testing Library
Directory Structure
src/
├── main.tsx # Vite entry point
├── App.tsx # Root component with routing
├── config.ts # Keycloak OIDC config
├── components/ # Reusable UI components (Layout, SyncStatusBadge, etc.)
├── pages/ # Page modules (Tenants, APIs, Deployments, Gateways, etc.)
├── services/ # API client (api.ts)
├── hooks/ # Custom React hooks
├── contexts/ # Auth/OIDC context
└── types/ # TypeScript type definitionsDevelopment
npm install
npm start # Dev server (Vite)
npm run test # vitest
npm run lint # eslint (max-warnings 100)
npm run format:check # prettier
npm run build # Production buildKey Patterns
- Functional components + hooks only
- Keycloak OIDC via react-oidc-context
- TanStack Query for server state
- Zustand for client state
- Path alias:
@/*maps tosrc/*
Dependencies
- Depends on: control-plane-api (REST API), Keycloak (auth)
- Depended on by: nothing (end-user UI)
OIDC Client
- Client ID:
control-plane-ui - Session storage:
sessionStorage(not localStorage)
Règles
Détail on-demand: .claude/docs/code-style-typescript.md, testing-standards.md.
- Prettier: line 100, single quotes, semi, trailing es5, LF.
- ESLint max-warnings: 100 (ratchet, jamais augmenter).
- Components fonctionnels + hooks. Pas de classes. React 18 strict. Node 20.
- vitest (PAS Jest). Path alias
@/*→src/*. tsconfig.app.jsonexclut**/*.test.ts(x). Build:tsc -p tsconfig.app.json.- Persona Rule: composants RBAC-conditional testés pour les 4 personas (cpi-admin, tenant-admin, devops, viewer).
- Helpers-First: utiliser
src/test/helpers.tsx(createAuthMock,renderWithProviders). Jamais inlinevi.mock('AuthContext'). vi.clearAllMocks()ne reset PAS les implementations. Re-init dansbeforeEach.- Boundary Integrity: MSW pour intercept fetch, pas 8
vi.mock()+getByText('Dashboard'). data-testidobligatoire sur nouveaux components. Convention<section>-<element>[-<variant>].- Changement visuel UI → update golden baselines dans la MÊME PR.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

