Files
BitwiseCmd/AGENTS.md
Borys Levytskyi c4877ac376 Bladerunner (#67)
* Introduce bladerunner theme

* Light neon glow

* Fix build error

* Different logo font and glow

* Neon glow on hover

* Make the theme to be easter egg

* Toggle lights via header

* Minor fixes

* Fix lint errors
2025-11-07 21:24:02 -05:00

22 lines
1.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
Agent Guidelines for This Repository
Scope
- These instructions apply to the entire repository.
Theme Styling Policy
- Centralize all theme-related CSS (e.g., `.light`, `.dark`, `.midnight`, `.bladerunner`, and future themes) in `src/index.css` only.
- Do NOT place theme-specific rules in component-scoped stylesheets (e.g., files under `src/shell/components/*.css`). Component CSS must remain theme-agnostic.
- If a component needs theme-dependent styling, add/adjust the selectors in `src/index.css` that target the components markup (e.g., `.app-root.<theme> .component-selector { ... }`).
- Prefer grouping theme rules together by theme block in `src/index.css` for readability and consistency.
Layout Rules
- Global layout modifiers that affect multiple views (e.g., centered vs. stretched layout) should also live in `src/index.css`.
Examples
- Good: `src/index.css``.bladerunner .top-links button { color: #ff7fb0 }`
- Avoid: `src/shell/components/TopLinks.css``.bladerunner .top-links button { ... }`
Testing
- After changing theme styles, verify all themes (Light/Dark/Midnight/Bladerunner) render legibly and that component CSS contains no theme-specific selectors.