Skip to content
opsinjs
Edit this page

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

  1. You work in health: a doctor, a nurse, a pharmacist, a researcher or a student.
  2. You know a little React, or none at all.
  3. You have an idea, such as a calmer colour, larger text, or a component health apps keep needing.

What you need

  1. A free GitHub account.
  2. A Claude plan that includes Claude Code: Pro, Max, Team, Enterprise or a Console account. The free plan does not include it.
  3. A Mac, Windows or Linux computer, and about an hour for the first set-up.

How a change gets in

  1. Issue. You describe the idea on GitHub, and a maintainer agrees the approach before anybody writes code.
  2. Set up. You copy the project to your computer. You do this once.
  3. Plan. You tell Claude Code what you want, and it writes a plan before it changes anything.
  4. Change. Claude Code makes the change on its own branch.
  5. Check. You look at the result in your browser, and Claude Code runs the project's checks.
  6. Pull request. Claude Code sends the change to GitHub for review.
  7. Review. A maintainer reads it, may ask for changes, and merges it.
  8. Live. The site updates a few minutes after the merge.
PageRead it
Set up onceBefore your first change
Make a changeFor every change. It has the prompts to use
Three examplesTo see a colour, a text size and a new component done start to finish
What not to doBefore your first change, and whenever you are unsure

The rules every contributor follows are in CONTRIBUTING.md.