Skip to content

Develop with rules

The /developing-with-rules workflow guides AI-assisted development from the start. Straion selects the rules most relevant to your task, validates your existing spec or plan against those rules, builds an implementation plan constrained by those rules, generates code under those constraints, and then validates the output before you commit.

The result: compliant code, without manual cross-referencing of your team’s standards.

  • Turning a spec or task into production-ready code
  • Avoiding rework caused by non-compliant AI output

Trigger the skill directly:

/developing-with-rules I want to add a password reset flow using email verification

If you prefer not to use the slash command, you can phrase the request naturally and Claude will invoke the Straion skill automatically:

Implement and validate the following task using Straion: [task description]
Use Straion to build [feature description]

Straion queries your rules and matches rules to the task context, the feature description, the files involved, and any metadata in the task. Only rules relevant to this specific work are included, so the AI is not overloaded with irrelevant constraints.

If you provide a spec or existing task definition, Straion validates it against the matched rules before planning begins. This catches gaps or conflicts at the cheapest possible stage — before any code is written. See Validate specs for details on how this works.

Straion produces an implementation plan and validates it against the matched rules. Each step in the plan is checked for rule compliance before code generation starts. See Validate implementation plans for details on the plan validation report.

The AI generates code using the matched rules and any sample code they contain as explicit constraints. This replaces generic AI defaults with your team’s actual patterns.

After code is generated, Straion validates the output against the same matched rules and produces a validation report. Issues are surfaced before you commit, not during code review. See Validate code for details on the code validation report.

/developing-with-rules Implement issue #123
/developing-with-rules Here's my spec, validate and implement it: [paste spec]

Break down into tasks without implementing yet

Section titled “Break down into tasks without implementing yet”
/developing-with-rules Break down this spec into tasks, don't implement yet: [paste spec]