- Created GLOBAL_THEME_SYSTEM.md with complete theme specification - Added THEME_CONTEXT.md for quick AI assistant reference - Defined CyberMood design language (metallic, glass, neon aesthetics) - Provided ready-to-use templates (CSS variables, components, JS controller) - Planned multi-language support (en, fr, de, es) - Created 5-week implementation roadmap - Added 5 ready-to-use prompts for theme implementation - Updated network-modes module with travel mode support 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| architecture.md | ||
| claudeia-notes.md | ||
| context.md | ||
| conventions.md | ||
| prompting.md | ||
| README.md | ||
| requirements.md | ||
| rules.md | ||
| THEME_CONTEXT.md | ||
| workflows.md | ||
Codex Configuration for SecuBox OpenWrt
This .codex/ directory captures the working agreements for Codex when editing the SecuBox OpenWrt feed. Every section is sourced from the local documentation (README.md, DEVELOPMENT-GUIDELINES.md, CLAUDE.md, QUICK-START.md, DOCUMENTATION-INDEX.md, VALIDATION-GUIDE.md, PERMISSIONS-GUIDE.md, CODE-TEMPLATES.md, MODULE-IMPLEMENTATION-GUIDE.md, etc.) plus the .claude/ guidance. Follow these notes before touching any LuCI module, RPC backend, CSS, or deployment script.
Use these files as checkpoints:
context.md: what the suite is and how the repository is organizedrequirements.md: functional and non-functional expectationsarchitecture.md: how data flows between LuCI views, RPCD, and system servicesconventions.md: naming, packaging, ACL, CSS, and JavaScript standardsworkflows.md: validated procedures for setup, build, deploy, release, and debuggingrules.md: enforceable guardrails Codex must respect before shipping any changeprompting.md: templates for requesting contributions from Codex or other AIsclaudeia-notes.md: how the existing Claude guidance maps onto Codex rules
Always cross-check instructions here with the source docs referenced above. When documentation conflicts, prioritize: repository source files → .claude rules → markdown guides.
First 5 Commands to Run in this Repo
./secubox-tools/fix-permissions.sh --local— normalize RPCD (755) and web assets (644) before editing./secubox-tools/validate-modules.sh— run the 7 critical checks (RPCD names, menu paths, JSON, permissions, etc.)./secubox-tools/install-git-hooks.sh— installs the pre-push validator so mistakes are caught automatically./secubox-tools/local-build.sh validate— replicates the CI validation locally using the OpenWrt SDK cache./secubox-tools/local-build.sh build luci-app-<module>— builds the module you are changing (use the exact package name)
Refer back to this README whenever you onboard a new contributor or need to explain how .codex/ should be used in the SecuBox OpenWrt repository.