How do I install the Rule Writing skill?

Run npx skillmds@latest add millionco-react-doctor/rule-writing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rule Writing safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rule Writing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rule Writing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rule Writing?

millionco (@millionco-react-doctor) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rule Writing by millionco-react-doctor

Name: Rule Writing
Rating: 4.2 (5 reviews)
Author: millionco

Rule Writing

Implement React Doctor rules from a validated contract. Use when writing oxlint rules, planning syntax or control-flow detection, designing adversarial tests, reusing syntax tree utilities, or updating rule registration.

millionco Updated Sep 9, 2026

File contents

Write a rule

Implement the rule-research contract. If none exists, define a compact contract before editing.

Plan the detector

State the diagnostic condition, required syntax and bindings, unsupported cases, and adversarial tests. Keep this plan short when the user already requested implementation.

Before adding a helper, search for one to reuse:

bunx @rayhanadev/truffler "<symbol-or-behavior>" \
  packages/oxlint-plugin-react-doctor/src/plugin \
  --kind function,interface,type,constant --limit 20

Read docs/HOW_TO_WRITE_A_RULE.md, nearby rules, utilities, and tests.

Implement and test

Write detector pseudocode.
Add adversarial valid and invalid tests.
Implement only the contract's supported behavior.
Reuse utilities before creating new ones.
Update generated registration with repository commands.
Run focused tests and package checks.
Use rde-eval when real-code feedback could expose noise.
Hand the finished change to rule-validate.

Account for:

import aliases and shadowed bindings
nested functions that do not execute immediately
transparent JavaScript and TypeScript wrappers
dynamic computed properties
imported or unresolved values
framework escape hatches
control-flow paths required by the diagnostic claim
regressions found by reviews or evals

Keep uncertain cases quiet. Match the message to the condition the detector proves.

Run repository checks

Use @antfu/ni commands:

nr test
nr lint
nr typecheck
nr format
nr smoke:json-report

Use focused commands while iterating. Record each command that ran.

Report the implementation

Report changed rules, tests, registration, reused or added utilities, reported behavior, intentional non-goals, and validation results. End with the rule-validate handoff.

---name: rule-writingdescription: Implement React Doctor rules from a validated contract. Use when writing oxlint rules, planning syntax or control-flow detection, designing adversarial tests, reusing syntax tree utilities, or updating rule registration.--- # Write a rule Implement the `rule-research` contract. If none exists, define a compact contract before editing. ## Plan the detector State the diagnostic condition, required syntax and bindings, unsupported cases, and adversarial tests. Keep this plan short when the user already requested implementation. Before adding a helper, search for one to reuse: ```sh bunx @rayhanadev/truffler "<symbol-or-behavior>" \ packages/oxlint-plugin-react-doctor/src/plugin \ --kind function,interface,type,constant --limit 20 ``` Read `docs/HOW_TO_WRITE_A_RULE.md`, nearby rules, utilities, and tests. ## Implement and test 1. Write detector pseudocode. 2. Add adversarial valid and invalid tests. 3. Implement only the contract's supported behavior. 4. Reuse utilities before creating new ones. 5. Update generated registration with repository commands. 6. Run focused tests and package checks. 7. Use `rde-eval` when real-code feedback could expose noise. 8. Hand the finished change to `rule-validate`. Account for: - import aliases and shadowed bindings - nested functions that do not execute immediately - transparent JavaScript and TypeScript wrappers - dynamic computed properties - imported or unresolved values - framework escape hatches - control-flow paths required by the diagnostic claim - regressions found by reviews or evals Keep uncertain cases quiet. Match the message to the condition the detector proves. ## Run repository checks Use `@antfu/ni` commands: ```sh nr test nr lint nr typecheck nr format nr smoke:json-report ``` Use focused commands while iterating. Record each command that ran. ## Report the implementation Report changed rules, tests, registration, reused or added utilities, reported behavior, intentional non-goals, and validation results. End with the `rule-validate` handoff.

Frequently asked questions