enhancedchannelmanager / frontend
CLAUDE.md89 starsChanged 4 months agoCC0-1.0View on GitHub
Full system architecture diagram: docs/architecture.md Coding conventions (naming, file pairing, components, hooks, CSS naming, state classes, API layer, tests): docs/style_guide.md is canonical. This file covers stack/structure orientation only — it defers to the style guide for any rule about how code should be written. Agents spawned into .claude/worktrees/agent-*/ find frontend/node_modules absent and npm/node unavailable. Fix it in one step from the worktree root: The script creates a writable frontend/node_modules directory with local .vite-temp and .vite dirs (prevents EACCES from root-owned…
- Deletes or force-pushes
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- backend/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
The file
We split this CLAUDE.md into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Add node to PATH. The correct fnm path on this host:
- Very specific: line 143
Test conventions (naming, AAA structure, colocation, MSW setup) live in docs/style_guide.md → Test Conventions, with deeper testing …
- Very specific: line 149
Run: npm test (Vitest + @testing-library/react)
- Very specific: line 160
Always clean /app/static/assets/ before copying — docker cp only adds files, never removes old bundles.
≈ “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.
Files
Frontend Agent Instructions
Full system architecture diagram:
docs/architecture.mdCoding conventions (naming, file pairing, components, hooks, CSS naming, state classes, API layer, tests):docs/style_guide.mdis canonical. This file covers stack/structure orientation only — it defers to the style guide for any rule about how code should be written.
Worktree workaround
Agents spawned into .claude/worktrees/agent-*/ find frontend/node_modules absent
and npm/node unavailable. Fix it in one step from the worktree root:
bash scripts/worktree-bootstrap.shThe script creates a writable frontend/node_modules directory with local .vite-temp
and .vite dirs (prevents EACCES from root-owned main checkout), symlinking all
packages and .bin from the main checkout. Plain-symlink bootstrap is NOT sufficient
— see docs/shipping.md → "Worktree quirks" for why.
Then invoke tooling via .bin directly (no npm run):
./frontend/node_modules/.bin/vitest run
./frontend/node_modules/.bin/eslint frontend/src --max-warnings 0
./frontend/node_modules/.bin/tsc --noEmit
./frontend/node_modules/.bin/vite buildAdd node to PATH. The correct fnm path on this host:
export PATH="$HOME/.local/share/fnm/node-versions/v24.13.0/installation/bin:./frontend/node_modules/.bin:$PATH"Note: fnm root is $HOME/.local/share/fnm/ — NOT $HOME/.fnm/ (that path does not
exist on this host).
Full explanation and root cause: docs/shipping.md → "Worktree quirks".
Framework & Stack
- React 18 + TypeScript (strict mode) + Vite build tool
- Entry:
src/main.tsx→AuthProvider→ProtectedRoute→App - Dev server: port 5173, proxies
/apitohttp://localhost:8000
Directory Structure
frontend/src/
├── App.tsx # Main app, centralized state via useState hooks
├── TabNavigation.tsx # Tab switching (data-tab attributes)
├── main.tsx # Entry point
├── index.css # CSS variables & theme
├── components/ # ~60+ components
│ ├── tabs/ # Tab content (M3UManagerTab, EPGManagerTab, etc.)
│ ├── channelPipeline/ # Rule builder (ActionEditor, ConditionEditor, RuleBuilder)
│ ├── ffmpegBuilder/ # FFmpeg configuration
│ ├── settings/ # Settings subsections
│ ├── CustomSelect.tsx/.css # Custom dropdown (replaces native <select>)
│ ├── ChannelsPane.tsx # Channel management (~274KB)
│ ├── ScheduledTasksSection.tsx
│ └── [modals, editors, panels...]
├── contexts/ # React Context providers
│ └── NotificationContext.tsx # Toast notification system
├── hooks/ # Custom hooks (~15 files)
│ ├── useAuth.tsx # Auth state
│ ├── useEditMode.ts # Edit mode with change tracking
│ ├── useChangeHistory.ts # Undo/redo
│ └── useAsyncOperation.ts # Async loading/error tracking
├── services/ # API layer
│ ├── api.ts # Main API client (~2600 lines)
│ ├── httpClient.ts # fetchJson(), buildQuery()
│ └── channelPipelineApi.ts # Channel Pipeline endpoints
├── types/ # TypeScript definitions
│ ├── index.ts # All shared types (~37KB)
│ └── channelPipeline.ts # Channel Pipeline types
└── utils/ # Utility functionsComponent Conventions
See docs/style_guide.md — sections Naming Conventions, Filenames,
and Module Organization → Frontend (React) — for the canonical rules
on file pairing, casing, the CustomSelect requirement, modal naming,
and Material Icons usage.
State Management
- No Redux — state centralized in
App.tsxviauseStatehooks, passed as props - Context for cross-cutting concerns:
AuthContext,NotificationContext - Custom hooks for complex logic:
useEditMode,useChangeHistory,useSelection - localStorage for persisted filters:
streamProviderFilters,streamGroupFilters
CSS & Styling
CSS naming, state classes, layer architecture, theme variables, and the
shared-class catalog live in docs/css_guidelines.md (authoritative for
CSS) with a summary in docs/style_guide.md → CSS Conventions.
Quick orientation only: theme variables live in :root in index.css,
the dark theme is the default, and each component owns its own .css
file (no CSS modules, no styled-components).
Tab Navigation
type TabId = 'm3u-manager' | 'epg-manager' | 'channel-manager' | 'guide' |
'logo-manager' | 'm3u-changes' | 'channel-pipeline' | 'journal' | 'stats' | 'settings'- Tabs have
data-tab={tab.id}attribute on buttons - Active state:
.tab-button.activeclass - Tab content lazy-loaded with
React.lazy()+Suspense - FFMPEG Builder tab also exists (id:
ffmpeg-builder)
Types
- Main types in
src/types/index.ts:Channel,Stream,EPGSource,ChannelGroup, etc. - Channel Pipeline types in
src/types/channelPipeline.ts:Action,Condition,Rule - Request types:
*CreateRequest,*UpdateRequest - Response types:
*Response
API Layer
Convention rules (named exports per endpoint, all HTTP via fetchJson())
are in docs/style_guide.md → Module Organization → Frontend (React).
Quick orientation:
// services/api.ts — named exports per endpoint
export async function getChannels(): Promise<Channel[]>
export async function getEPGSources(): Promise<EPGSource[]>
export async function getChannelGroups(): Promise<ChannelGroup[]>Endpoints match backend routes (e.g., /api/channels, /api/m3u).
Testing
Test conventions (naming, AAA structure, colocation, MSW setup) live in
docs/style_guide.md → Test Conventions, with deeper testing strategy
in docs/testing.md.
Quick commands:
- Run:
npm test(Vitest + @testing-library/react) - Run watch:
npm run test:watch
Build & Deploy
cd frontend && npm run build # Output to dist/
docker exec ecm-ecm-1 sh -c 'rm -rf /app/static/assets/*' # Clean stale bundles
docker cp dist/. ecm-ecm-1:/app/static/Always clean /app/static/assets/ before copying — docker cp only adds files, never removes old bundles.
CSS Class Patterns for E2E Tests
.channels-pane,.streams-pane— Main pane containers.tab-navigation,.tab-button— Tab nav.settings-tab,.settings-nav-item— Settings page.filter-active— Active filter indicator (logic: true when any filter is NOT showing all)data-testidattributes on key elements for stable E2E selectorsaction-inputclass for form fields in action editororder-number-inputclass for reorder number in card headers only
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.

