opsinjs
Contribute with Claude Code
A plain-language guide for clinicians and health scientists who want to improve opsinjs by asking Claude Code to make the change.
You do not need to be a software engineer. You describe the change in plain words, Claude Code makes it, and you check the result before anybody else sees it.
Who this is for
- You work in health: a doctor, a nurse, a pharmacist, a researcher or a student.
- You know a little React, or none at all.
- You have an idea, such as a calmer colour, larger text, or a component health apps keep needing.
What you need
- A free GitHub account.
- A Claude plan that includes Claude Code: Pro, Max, Team, Enterprise or a Console account. The free plan does not include it.
- A Mac, Windows or Linux computer, and about an hour for the first set-up.
How a change gets in
- Issue. You describe the idea on GitHub, and a maintainer agrees the approach before anybody writes code.
- Set up. You copy the project to your computer. You do this once.
- Plan. You tell Claude Code what you want, and it writes a plan before it changes anything.
- Change. Claude Code makes the change on its own branch.
- Check. You look at the result in your browser, and Claude Code runs the project's checks.
- Pull request. Claude Code sends the change to GitHub for review.
- Review. A maintainer reads it, may ask for changes, and merges it.
- Live. The site updates a few minutes after the merge.
Read next
| Page | Read it |
|---|---|
| Set up once | Before your first change |
| Make a change | For every change. It has the prompts to use |
| Three examples | To see a colour, a text size and a new component done start to finish |
| What not to do | Before your first change, and whenever you are unsure |
The rules every contributor follows are in CONTRIBUTING.md.