Configuring a run
Coding style
Teach RTLBridge your house conventions once and have every module follow them.
Every team has conventions, and repeating them in every request is a waste of your typing. Set them once in Settings and they are applied to every generation, in every chat, from then on.
Where to set it
Open Settings from the sidebar and scroll to Coding style. Changes save when you press Save coding style; the form tells you when there is something unsaved.
The preset fields
| Field | Options |
|---|---|
| Naming convention | snake_case, camelCase, PascalCase |
| Reset style | Synchronous or asynchronous, active high or active low; four combinations |
| Comment density | Minimal, medium, verbose |
| FSM encoding | Binary, one-hot, Gray |
| Block style | Separate always_ff / always_comb, or classic always @(...). Verilog only; ignored for VHDL |
Every field starts on No preference, which leaves the choice to the model. Only set the ones you actually care about; a fully pinned-down style is not automatically a better one.
Additional preferences
Below the pickers is a free-text box of up to 2000 characters, appended to the generation prompt as-is. This is where the conventions that do not fit a dropdown go:
Prefix all parameters with P_ and all localparams with L_.
Register every module output; no combinational paths from input to output.
Avoid SystemVerilog interfaces; use explicit port lists.
Put the port list one signal per line, direction first.
Every always_ff block gets a one-line comment saying what it implements.- Write rules, not explanations. Short imperative lines work better than paragraphs.
- Keep it to conventions. Design requirements belong in the spec, where the testbench can see them.
- Anything you write here applies to every module, so leave out anything project-specific.
What wins when things disagree
Your spec beats your coding style. If your saved reset style is synchronous and a particular request asks for an asynchronous reset, the request wins; the saved value is a default, not a constraint.
Note
Values the server does not recognise are dropped silently rather than saved, and the form is refreshed with what was actually kept. If a selection appears to revert after saving, that is what happened.
Style and review time
The setting that saves the most review time is usually reset style, followed by block style. Both are things you would otherwise notice and correct on every single module.