Contributors · Back to community

# The hands that ship the work.

Open Design is built by people, in public. Skills, DESIGN.md systems, plugins, docs: every commit is a brushstroke. Pick an issue, send a PR, and earn a one-of-one honor card the moment you're merged.

Plugin everything

## Open Design as a stage. Your work as the show.

The atelier is also a gallery. Helping you make the work is half the address; making sure the room comes to look is the other. Every piece you ship lands not in a vault but on a wall, where the world can find it.

I

### Anything can be a plugin.

Whatever the studio yields (content, a finished product, a template, a Skill, a workflow) can be folded back into a plugin. The registry accepts any shape; the door keeps no gatekeeper.

II

### Your debut piece, your induction.

The day your first piece lands in the registry, your name joins the wall. Not a visitor's badge. A permanent line on the contributor list, beside everyone who arrived before.

III

### Once it's in, it travels.

The registry at open-design.ai/plugins is only the threshold. From there the strongest pieces are carried outward: to X, to Discord's #showcase, to the newsletter, to the video reels. Each handoff widens the room; the world meets your hand.

IV

### Need a first stroke?

Walk the plugin registry. The works hung there are kindling for your own. Borrow the spark, then make the piece only your hand could.

The skill

### Let the agent ship for you.

For makers who'd rather not touch the code. The whole contribution lives in a single skill, spoken in plain language. The brushwork falls to the agent.

curl -sSL https://raw.githubusercontent.com/nexu-io/open-design/main/.claude/skills/od-contribute/install.sh | bash
01

#### Hand the line to the agent

Paste the command above into the agent within Open Design, or into whichever you already keep at hand: Claude Code, Codex, Cursor. It installs itself.

02

#### Wake the skill

Type `/od-contribute`, or simply tell the agent to run what you just installed. Either phrase opens the door.

03

#### Half a minute to the gallery

The agent walks the rest. Your piece is bound for the open-source repository in about thirty seconds; we review at first chance, and the moment it lands, the room meets your hand.

Steering the ship

## The maintainers.

Maintainers protect the direction and quality of Open Design: they review contributions, keep the standard coherent, and make room for more contributors to earn their place in the project.

Nagendhra-web
Maintainer

Nagendhra brings a data engineer's instinct for production truth: find the failure, measure the edge case, and fix it properly. In Open Design, that shows up in deploy preflight work, asset-bundling hardening, and Windows fixes that make the project feel trustworthy when contributors ship.

github
Sid-Qin
Maintainer

Sid is the generalist engineer with a designer's eye for detail: the kind of maintainer who notices both the broken CLI path and the crooked interaction affordance. In Open Design, Sid keeps export flows, plugin actions, Windows shims, MIME handling, and agent plumbing sharp enough for a community to build on.

github
All-time signal

## The contributors with deep roots.

A long-running record of talented contributors who keep turning ideas, fixes, and craft into the shared Open Design standard.

01 All-time contributor
Repository history
—
—

The long tail matters: design systems, docs fixes, examples, and small repairs are how an open design language becomes dependable.

—
Commits
#01
External rank
# Contributor Commits Rank
02
——→
03
——→
04
——→
05
——→
This week's signal

## Ten contributors leading this week.

A snapshot of sharp contributors landing PRs, improving the product, and making Open Design feel alive.

01 This week's leader
Last 7 days
—
—

A contributor taking the lead with focused, generous work.

#01
Rank
—
PRs · 7d
# Contributor PRs Rank
02
——→
03
——→
04
——→
05
——→
Pick your first contribution

## Open issues, tagged for you.

Live from label:“good first issue” on the Open Design repo. Comment on an issue to claim it, and a maintainer will assign it within a day.

—
good first issue
— →
—
good first issue
— →
—
good first issue
— →
Showing first — open good-first-issues See all on GitHub →
Four steps · any skill level

## From zero to merged, in an afternoon.

Whether you're a designer, a writer, an engineer, or someone who just spotted a typo, there's a contribution shape for you. Here's the path.

Step 01

### Find a spark.

Browse the good-first-issues list above, or open a new issue describing something you'd improve. Designers: DESIGN.md systems are the easiest entry.

Step 02

### Open a draft PR.

Fork, branch, push. Mark it draft. It signals you want feedback early. Mention which issue it closes. The CI is fast; bot-cards stays on its own branch.

Step 03

### Review with a human.

A maintainer reviews within 24h. We're kind, specific, and never gatekeep. If you're stuck, drop the PR link in Discord #help.

Step 04

### Merge → card.

The bot mints your honor card the moment you're merged and pushes it to the bot-cards branch. Share it on X with #OpenDesign, and we repost the best ones.

Read the contributing guide