Skip to content
Conduit

skill

rulesmith

Write AI coding rules once; generate CLAUDE.md, AGENTS.md, .cursorrules, .clinerules and CONVENTIONS.md, and fail CI on drift.

iskra-astudillo/rulesmithcommunitylistedunreviewed

Set up

Skills are installed by placing their folder where your agent loads skills.

The download comes from github.com/iskra-astudillo/rulesmith itself, not from our server, so what you get is exactly what its author published.

Install instructions come from the README

Skills do not use an MCP config. Follow the steps in the README below.

README

synced Nov 5, 2026

rulesmith

Write your team's AI coding rules once. Generate CLAUDE.md, AGENTS.md, .cursorrules, .clinerules and Aider's CONVENTIONS.md from that one source.

Every coding agent reads its own rules file. Teams that use more than one agent end up with five copies of the same standards, edited by hand, drifting apart. rulesmith keeps one spec (rulesmith.json), composes it from tested rule blocks, renders each agent's native file, and fails CI when a generated file has drifted.

Pure Python standard library. No network calls, no API keys.

$ rulesmith init --team "Acme Platform" --stack python,react --sector saas --compliance soc2
wrote rulesmith.json
$ rulesmith render
wrote ./.clinerules
wrote ./CLAUDE.md
wrote ./.cursorrules
wrote ./AGENTS.md
wrote ./CONVENTIONS.md
$ rulesmith check
ok: generated files match rulesmith.json

See examples/ for the exact output of that run.

Install

pipx install git+https://github.com/iskra-astudillo/rulesmith
# or, from a clone:
python -m rulesmith_cli list

Python 3.8 or newer. No dependencies. The command is rulesmith; the package name is rulesmith-cli.

Commands

CommandWhat it does
rulesmith initWrites rulesmith.json from --team, --stack, --sector, --compliance.
rulesmith renderWrites the agent files next to the spec (or --out DIR). --agent claude limits it to one.
rulesmith checkExits 1 if any generated file is missing or differs from the spec. Use it in CI.
rulesmith listShows the supported stacks, sectors, compliance sets and agents.

Rule blocks

  • Safety baseline (on by default): no destructive operations without human approval, no inline secrets, safety gates fail closed, money math carries units, changes are revertable.
  • Code quality: validate external data against a schema, re-read rotated secrets, fix a whole class of issue rather than the first instance, verify before claiming done.
  • Stacks: go, node, python, rails, react, sql, typescript.
  • Industries: ai-agent, ecommerce, fintech, healthcare, saas.
  • Compliance: gdpr, hipaa, pci, soc2.
  • Team rules: anything in extra_rules is appended verbatim.
{
  "team": "Acme Platform",
  "sector": "saas",
  "stacks": ["python", "react"],
  "compliance": "soc2",
  "include_baseline": true,
  "extra_rules": ["All public endpoints are documented in openapi.yaml."]
}

CI

- run: pipx run --spec git+https://github.com/iskra-astudillo/rulesmith rulesmith check

The check compares each file byte for byte with a fresh render, so a hand edit to CLAUDE.md fails the build and the fix is to change the spec.

Agent skill

SKILL.md lets Claude Code, Codex or Cursor maintain the spec themselves: edit rulesmith.json, render, check, commit both together.

Why the safety baseline looks like this

The baseline rules come from the failure modes that recur in AI-written code: a gate that fails open when its flag is missing, a secret pasted inline, a destructive command run without approval, a fix applied to the first instance of a bug and not the rest. The companion tool bugclass-detectors detects several of these in Python code.

Hosted version

RuleSmith generates the same files in the browser.

License

MIT. See LICENSE.

↑↓ navigate openesc close