At a glance

1 · What is claimed?

Only the report text below — no validator has restated it as checkable claims yet.

2 · What does it affect?

Not yet mapped to any requirement or component.

3 · Is it reproducible?

No validation has been run yet.

4 · What remains unclear?

• Not validated yet: no claims, no reproducer.

5 · What happens next?

Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

### What do you need?

First off, thank you for creating Omarchy!

I'm opening this issue to propose an idea that could take the customization to the next level: linking Omarchy themes with browser userstyles.

The core idea is to automatically enable/disable a corresponding userstyle (e.g., via the [Stylus](https://add0n.com/stylus.html) browser extension) whenever the Omarchy theme is switched.

I'm not an expert on the implementation details. I'm not sure how feasible it is within the scope of the project. But I wanted to put it out there for consideration.

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.