hoop / webapp
CLAUDE.md848 starsChanged 24 days agoMITView on GitHub
Status: This is the legacy ClojureScript app, being migrated to React in ../webapp_v2/. New pages should be built in webapp_v2/; touch this codebase only to maintain not-yet-migrated pages. See the root CLAUDE.md ("Frontend Migration in Progress") and webapp_v2/CONTEXT_MIGRATION.md for the split.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- sidecar/CLAUDE.mdCLAUDE.md
- webapp_v2/CLAUDE.mdCLAUDE.md
- build-ticketSkill
- evidenceSkill
- gcp-marketplace-publishSkill
- shapeSkill
- support-agentSkill
The file
Show its rules and text
We split this CLAUDE.md into the rules it gives an agent
27 rules. About 0 are common, 17 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈17
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
After a CLJS change, hard-reload the browser tab (Vite proxies the bundle and can't HMR it)
- Distinctive: line 11
ClojureScript: Follow idiomatic ClojureScript style
- Very specific: line 13
Components: Prefer small, reusable components in webapp.components.*
- Very specific: line 14
Use full Reagent (functional components) instead of create-class
- Distinctive: line 15
Follow colocation pattern - keep related code close together (see newer code examples)
- Distinctive: line 16
State Management: Use re-frame for app state with proper subscriptions/events
- Very specific: line 17
Avoid dereferencing atoms (@) in the first layer - add atoms in the first layer and call them in the second layer
- Distinctive: line 18
Keep code organization clean by maintaining proper atom usage patterns
- Very specific: line 19
CSS: Use Tailwind utility classes, see tailwind.config.js
- Distinctive: line 20
Error Handling: Use re-frame effects for async error handling
- Distinctive: line 21
Naming: Use kebab-case for functions/variables, PascalCase for React components
- Distinctive: line 23
UI Components: Prefer using existing components from the codebase
- Distinctive: line 24
Modal/Dialog: Use app's modal system with re-frame events (:modal->open/:modal->close)
- Distinctive: line 25
Accessibility: Ensure basic W3C accessibility standards
- Very specific: line 26
Add proper label attributes for form inputs
- Distinctive: line 28
Follow W3C best practices for users with visual impairments
- Very specific: line 31
Import Pattern: Import Radix components from "@radix-ui/themes" using the :refer syntax
- Very specific: line 32
Usage Pattern: Use Reagent interop syntax [:> Component {}] for Radix components
- Very specific: line 42
Styling: Use Radix's built-in props (:size, :variant, :color) and Tailwind for custom styling
- Very specific: line 48
Screen readers: Use semantic HTML and Radix primitives where they provide roles/labels.
- Distinctive: line 50
Mindset: When implementing UI, default to asking whether keyboard and screen-reader users can complete the same tasks.
- Distinctive: line 54
Use existing UI components when possible before creating new ones
- Distinctive: line 55
Follow existing event/subscription patterns for state management
- Very specific: line 77
Namespacing: Use namespaced keywords (e.g., :module-name/event-name)
- Distinctive: line 85
Prefer concise and objective responses
- Distinctive: line 87
Use real code examples from the project whenever possible
- Distinctive: line 88
When suggesting changes, consider the impact on existing structure
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 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.
Files
HOOP WebApp Development Guidelines
Status: This is the legacy ClojureScript app, being migrated to React in
../webapp_v2/. New pages should be built inwebapp_v2/; touch this codebase only to maintain not-yet-migrated pages. See the rootCLAUDE.md("Frontend Migration in Progress") andwebapp_v2/CONTEXT_MIGRATION.mdfor the split.
Commands
- Dev (shadow-cljs on :8280):
cd webapp && npm run dev - Build bundle into the gateway:
make build-dev-webapp(from repo root) - After a CLJS change, hard-reload the browser tab (Vite proxies the bundle and can't HMR it)
Code Style Guidelines
- ClojureScript: Follow idiomatic ClojureScript style
- Namespaces: Organized by feature (connections, webclient, components)
- Components: Prefer small, reusable components in
webapp.components.*- Use full Reagent (functional components) instead of
create-class - Follow colocation pattern - keep related code close together (see newer code examples)
- Use full Reagent (functional components) instead of
- State Management: Use re-frame for app state with proper subscriptions/events
- Avoid dereferencing atoms (
@) in the first layer - add atoms in the first layer and call them in the second layer - Keep code organization clean by maintaining proper atom usage patterns
- Avoid dereferencing atoms (
- CSS: Use Tailwind utility classes, see tailwind.config.js
- Error Handling: Use re-frame effects for async error handling
- Naming: Use kebab-case for functions/variables, PascalCase for React components
- Imports: Group by source (external JS libraries first, then ClojureScript)
- UI Components: Prefer using existing components from the codebase
- Modal/Dialog: Use app's modal system with re-frame events (:modal->open/:modal->close)
- Accessibility: Ensure basic W3C accessibility standards
- Add proper
labelattributes for form inputs - Include
alttext for images - Follow W3C best practices for users with visual impairments
- Add proper
Radix UI Components
- Import Pattern: Import Radix components from "@radix-ui/themes" using the
:refersyntax - Usage Pattern: Use Reagent interop syntax
[:> Component {}]for Radix components - Common Components:
Box- For layout containers with spacing (e.g.,:class "space-y-radix-7")Flex- For flexbox layoutsGrid- For grid layouts, commonly using span patterns likespan-2/span-5Table- Use full table components (Table.Root,Table.Header,Table.Body)Text/Heading- For typography with consistent sizingBadge- For status indicatorsButton- For actions with consistent stylingSelect- For dropdown selections
- Styling: Use Radix's built-in props (
:size,:variant,:color) and Tailwind for custom styling - Reference Components: Copy only from a feature that is still CLJS-owned. Migrated trees stay on disk for a while after their React replacement ships, so "the file exists" is not evidence it is live — check the routing table in
../webapp_v2/CONTEXT_MIGRATION.md("All CLJS Routes") before using anything as a reference. As of this writingwebapp.features.runbooks.*qualifies; guardrails, jira-templates, access-control, access-request and ai-session-analyzer do not — all five are React now. Only jira-templates still has a full dead tree on disk; the rest were deleted by EVL-147 / EVL-184 / EVL-228, andwebapp.features.ai-session-analyzer.*is down to a trimmedevents.cljs/subs.cljsplus the three session-analysis cards.
Accessibility
- Baseline: Ship basic accessibility on every UI change—keyboard navigation and screen-reader support are not optional extras.
- Keyboard: Interactive controls must be reachable and operable with Tab / Shift+Tab; preserve a sensible focus order; visible focus states; avoid trapping focus except in modals (then follow the modal pattern and restore focus on close).
- Screen readers: Use semantic HTML and Radix primitives where they provide roles/labels; associate labels with inputs; use
aria-*when semantics alone are insufficient. - Images and icons: Meaningful images need descriptive
alttext; decorative images/icons should use emptyalt=""(or equivalentaria-hiddenwhen appropriate) so assistive tech can skip them. Do not leaveimgwithout an intentional alt decision. - Mindset: When implementing UI, default to asking whether keyboard and screen-reader users can complete the same tasks; fix gaps in the same change when feasible.
Common Patterns
- New features should follow existing patterns in similar components
- Use existing UI components when possible before creating new ones
- Follow existing event/subscription patterns for state management
- For forms and tables, refer to the runbooks implementation (verify it is still CLJS-owned first — see "Reference Components" above)
Module Organization
- Feature Modules: Organize features in their own directories with local
events.cljsandsubs.cljs - Structure Pattern:
src/webapp/ ├── features/ │ └── feature_name/ │ ├── events.cljs # re-frame events │ ├── subs.cljs # re-frame subscriptions │ └── views/ # UI components └── module_name/ ├── events.cljs # Module-specific events ├── subs.cljs # Module-specific subscriptions ├── main.cljs # Main component └── *.cljs # Other module files - Global vs Local:
/src/webapp/events/and/src/webapp/subs.cljsare for GLOBAL events/subs only- Feature/module-specific events and subs should live within their module directory
- Namespacing: Use namespaced keywords (e.g.,
:module-name/event-name) - Initial State: Define in
/src/webapp/db.cljsunder the module key - Examples: See
webapp.features.runbooks.*andwebapp.audit_logs.*(webapp.features.access_request.*andwebapp.features.ai_session_analyzer.*used to be the canonical examples; both moved to React — the first is gone, the second is down to a trimmedevents.cljs/subs.cljs)
Response Guidelines
- Prefer concise and objective responses
- Focus on project architecture and patterns (ClojureScript, Reagent, re-frame, Radix UI)
- Use real code examples from the project whenever possible
- When suggesting changes, consider the impact on existing structure
- Maintain colocation pattern and keep related code organized together
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.

