alexei.dolgolyov/wled-screen-controller-mixed

Files

Validate / validate (push) Failing after 8s

Details

Add capture template system with in-memory defaults and split device settings UI

- Generate default templates (MSS, DXcam, WGC) in memory from EngineRegistry at startup
- Only persist user-created templates to JSON, skip defaults on load/save
- Add capture_template_id to Device model and DeviceCreate schema
- Remember last used template in localStorage, use it for new devices with fallback
- Split Device Settings dialog into General Settings and Capture Settings
- Add capture settings button (🎬) to device card
- Separate default and custom templates with visual separator in Templates tab
- Add capture engine integration to ProcessorManager
- Add CLAUDE.md with git commit/push policy and server restart instructions
- Add en/ru localization for all new UI elements

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

2026-02-10 02:43:49 +03:00

2.4 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]

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

2.4 KiB Raw Blame History