agentleFS
Sign inStart free
stoa-platformstoa-platform/stoa/portal/CLAUDE.md

stoa / portal

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

The file

We split this CLAUDE.md into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No Zustand — uses Context/Hooks for state

    line 44
  2. Distinctive:

    Test-Adjacency: nouveau component = tests dans la MÊME PR.

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

Developer Portal

Overview

React portal for API Consumers. Browse API catalog, subscribe to APIs, test endpoints, manage API keys, and view documentation.

Tech Stack

  • React 18.2, TypeScript, Vite
  • TanStack React Query, Axios
  • react-oidc-context (Keycloak auth), oidc-client-ts
  • Tailwind CSS, 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/          # 14 component directories
├── pages/               # Pages (Subscriptions, APIs, Tests, Documentation, etc.)
├── services/            # 17 service files (catalog, subscription, integration, etc.)
├── hooks/               # 10+ custom hooks
├── contexts/            # Auth context
├── types/               # TypeScript types
└── utils/               # Helper utilities

Development

npm install
npm run dev             # Dev server (Vite)
npm run test            # vitest
npm run test:coverage   # vitest with coverage
npm run lint            # eslint (max-warnings 0)
npm run format:check    # prettier
npm run build           # Production build

Differences from Console UI

  • Consumer-facing (catalog, subscriptions) vs. Provider-facing (admin, deployments)
  • More services (17 vs 7) — richer API integration
  • Has utils/ directory
  • Stricter lint threshold (0 warnings vs 105 for Console)
  • No Zustand — uses Context/Hooks for state

Dependencies

  • Depends on: control-plane-api (REST API), Keycloak (auth)
  • Depended on by: nothing (end-user UI)

OIDC Client

  • Client ID: stoa-portal
  • Session storage: sessionStorage

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: 0. jsx-a11y plugin actif.
  • Components fonctionnels + hooks. React 18 strict. Node 20.
  • vitest (PAS Jest). Path alias @/* → src/*. Build: tsc -p tsconfig.app.json.
  • Test-Adjacency: nouveau component = tests dans la MÊME PR.
  • Helpers-First: src/test/helpers.tsx (createAuthMock, renderWithProviders). Jamais inline mocks.
  • vi.clearAllMocks() ne reset PAS les implementations. Re-init dans beforeEach.
  • Boundary Integrity: MSW pour intercept fetch. Jamais mocker la boundary sous test.
  • data-testid obligatoire. Changement visuel → update goldens MÊME PR.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free