CONTRIBUTING.md

# Contributing

Contributions should improve real writing behavior without turning personal preferences into universal rules. A change needs a concrete failure, a relevant source, or a short example that shows why the guidance should change.

## Propose a change

Include the following information:

- The kind of writing task affected.
- A short input that exposes the problem.
- The undesirable behavior.
- The meaning, voice, or constraint a good edit must preserve.
- A source link when the change comes from an external style guide.

Prefer a narrow decision rule with a justified exception over a blanket ban.

## Update the skill

Keep guidance needed for ordinary responses in `SKILL.md`. Put detailed, task-specific material in a directly linked reference and state when the agent should read it. Do not duplicate the same rule across several files.

When a source changes, revise the skill only if the change affects an agent's decisions. Update `references/sources.md` and describe the material change in the pull request.

Keep license text, attribution language, quotations, code, commands, and identifiers exact. Apply the skill to authored prose, not protected or literal content.

## Write the contribution

Use the skill on the pull request and any documentation you change. Lead with the change and include a brief example when it helps a reviewer see the effect.