alexei.dolgolyov/wled-screen-controller-mixed

Files

alexei.dolgolyov 3db7ba4b0e Fix DXcam engine and improve UI: loading spinners, template card gap

DXcam engine overhaul:
- Remove all user-facing config (device_idx, output_idx, output_color)
  since these are auto-resolved or hardcoded to RGB
- Use one-shot grab() mode with retry for reliability
- Lazily create camera per display via _ensure_camera()
- Clear dxcam global factory cache to prevent stale DXGI state

UI improvements:
- Replace "Loading..." text with CSS spinner animations
- Fix template card header gap on default cards (scope padding-right
  to cards with remove button only via :has selector)
- Add auto-restart server rule to CLAUDE.md

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-10 17:26:38 +03:00

3.1 KiB

Raw Blame History

Claude Instructions for WLED Screen Controller

CRITICAL: Git Commit and Push Policy

🚨 NEVER CREATE COMMITS WITHOUT EXPLICIT USER APPROVAL 🚨

🚨 NEVER PUSH TO REMOTE WITHOUT EXPLICIT USER APPROVAL 🚨

Strict Rules

DO NOT create commits automatically after making changes
DO NOT commit without being explicitly instructed by the user
DO NOT push to remote repository without explicit instruction
ALWAYS WAIT for the user to review changes and ask you to commit
ALWAYS ASK if you're unsure whether to commit

Workflow

Make code changes as requested
STOP - Inform user that changes are complete
WAIT - User reviews the changes
ONLY IF user explicitly says "commit" or "create a commit":
- Stage the files with git add
- Create the commit with a descriptive message
- STOP - Do NOT push
ONLY IF user explicitly says "push" or "commit and push":
- Push to remote repository

What Counts as Explicit Approval

✅ YES - These mean you can commit:

"commit"
"create a commit"
"commit these changes"
"git commit"

✅ YES - These mean you can push:

"push"
"commit and push"
"push to remote"
"git push"

❌ NO - These do NOT mean you should commit:

"that looks good"
"thanks"
"perfect"
User silence after you make changes
Completing a feature/fix

Example Bad Behavior (DON'T DO THIS)

❌ User: "Fix the MSS engine test issue"
❌ Claude: [fixes the issue]
❌ Claude: [automatically commits without asking]  <-- WRONG!

Example Good Behavior (DO THIS)

✅ User: "Fix the MSS engine test issue"
✅ Claude: [fixes the issue]
✅ Claude: "I've fixed the MSS engine test issue by adding auto-initialization..."
✅ [WAITS FOR USER]
✅ User: "Looks good, commit it"
✅ Claude: [now creates the commit]

IMPORTANT: Auto-Restart Server on Code Changes

Whenever server-side Python code is modified (any file under /server/src/), automatically restart the server so the changes take effect immediately. Do NOT wait for the user to ask for a restart.

Restart procedure

Stop the running Python process: powershell -Command "Get-Process -Name python -ErrorAction SilentlyContinue | Stop-Process -Force"
Start the server: powershell -Command "Set-Location 'c:\Users\Alexei\Documents\wled-screen-controller\server'; python -m wled_controller.main" (run in background)
Wait 3 seconds and check startup logs to confirm it's running

Project Structure

This is a monorepo containing:

/server - Python FastAPI backend (see server/CLAUDE.md for detailed instructions)
/client - Future frontend client (if applicable)

Working with Server

For detailed server-specific instructions (restart policy, testing, etc.), see:

server/CLAUDE.md

General Guidelines

Always test changes before marking as complete
Follow existing code style and patterns
Update documentation when changing behavior
Write clear, descriptive commit messages when explicitly instructed
Never make commits or pushes without explicit user approval

3.1 KiB Raw Blame History