.rules Feature?

[kibarik]

I’ve got an idea that could make Onlook even more powerful — adding a .rules feature, similar to what Cursor has. It would let users define rules or guidelines that the system always follows.

Why it’s useful:

• Keeps style and quality consistent across the project
• Makes results more predictable and stable
• Helps teams move faster since rules can be set up front
• Improves platform output quality without technical changes — just through better prompt design

On top of that, it could open the door for a projects/Hub ecosystem with personalized rule sets, similar to what’s being done here: awesome-cursorrules.

I think this could really boost collaboration and workflows in Onlook.
What do you think? Or maybe you already have something like this planned/implemented inside?

[Kitenite]

@kibarik , definitely interesting. Wonder if this is something that should be done per project or per user/team? Likely both...
I'm thinking of 2 patterns:

1. Have it in the project code like a CLAUDE.md and let the agent refer to and update it as needed.
2. Have it in the database so that it can be used across projects (later teams) and users.

I like the idea of a hybrid, we have user-level rules that stay in database and an in-code rule that the agent can refer to. It also makes templates more useful because they can have existing rules attached.

(AGENTS.md)