Skip to main content
Sixth Rules are persistent instructions Sixth follows on every task: your conventions, architecture notes, testing standards, anything you’d otherwise repeat in every prompt. They can apply to one project (workspace rules) or to everything you do (global rules).

​
The Rules, Workflows & Skills menu

Click the scales icon in the message box toolbar to open a menu with three tabs:
  • Rules — your global and workspace rules.
  • Workflows — reusable step-by-step workflows you run with /filename.
  • Skills — skills Sixth can load, plus Create with AI and Create Manually.
On the Rules and Workflows tabs, each file has an on/off switch, an edit button that opens it in the editor, and a delete button. Each section ends with a New rule file… (or New workflow file…) row: type a name (.md, .txt or no extension; no extension becomes .md) and press Enter to create it. Turned-off rules stay on disk but aren’t sent to the model.

​
Where rules live

Sixth reads Cursor and Windsurf rule files too, so a project that already has them works without changes. Turn them off from the menu if you don’t want them applied. You can also ask Sixth to write a rule for you from the current conversation with /newrule.

​
Using a .sixthrules folder

For more than one rule, make .sixthrules a folder. Sixth combines every Markdown file in it:
Number prefixes are optional; they just keep the files in order. With a folder you can switch individual rules on and off from the menu, for example a react.md rule only for frontend work.

​
Example rule

Example Sixth Rule

​
Tips

  • Be specific. “Use Zod for request validation in src/api” beats “validate inputs”.
  • Describe outcomes, not step-by-step procedures. Procedures belong in workflows or skills.
  • Commit workspace rules so your whole team gets the same behaviour.
  • Keep them short. Rules are sent with every request, so trim anything Sixth no longer needs.