Skip to content

nexu-io/open-design / .claude/skills/od-contribute

od-contribute

Unverified

One-click contribution flow for OpenDesign (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship my OD skill, ship my OD design system, translate OD docs, report an OD bug, od-contribute.

FileKindSize
SKILL.mdskill md13.8 KB
agents/openai.yamlconfig650 B
install.shexecutablescript5.1 KB
references/design-system-anatomy.mdmarkdown2.0 KB
references/newcomer-tone.mdmarkdown2.7 KB
references/od-repo-map.mdmarkdown2.2 KB
references/skill-anatomy.mdmarkdown2.3 KB
scripts/check-prereqs.shexecutablescript4.1 KB
scripts/config.shexecutablescript2.4 KB
scripts/create-issue.shexecutablescript3.7 KB
scripts/create-pr.shexecutablescript3.8 KB
scripts/discover-doc-gaps.shexecutablescript4.0 KB
scripts/discover-i18n-gaps.shexecutablescript4.8 KB
scripts/setup-workspace.shexecutablescript3.4 KB
scripts/validate-design-system.shexecutablescript3.3 KB
scripts/validate-markdown.shexecutablescript6.9 KB
scripts/validate-skill-submission.shexecutablescript5.0 KB
templates/ISSUE-BODY-bug.mdmarkdown450 B
templates/PR-BODY-design-system.mdmarkdown1.1 KB
templates/PR-BODY-docs.mdmarkdown723 B
templates/PR-BODY-i18n.mdmarkdown1.2 KB
templates/PR-BODY-skill.mdmarkdown1016 B

references/newcomer-tone.md

View on GitHub
# Newcomer tone — voice rules for PR / issue text

Per user feedback ([[feedback_outreach_minimal]]), keep it minimal. The PR body is the **only** place we get to shape the maintainer's first impression of this contributor — make it warm, brief, and useful.

## Hard rules

1. **Always end the PR body with two things:**
   - "👋 This is my first OD contribution." (or a similar one-line warmth)
   - The OD Discord invite: <https://discord.gg/qhbcCH8Am4> (read from `OD_DISCORD_INVITE` env, never hardcode)
2. **Never claim more than the PR actually does.** A typo fix is a typo fix — don't dress it up as "improving documentation quality" or list 5 fake checkboxes.
3. **Plain language only.** No "ergonomic", "DX", "stakeholder", "stack rank". Talk like a friendly user, not a startup blog.
4. **No emojis except the opening 👋 and one optional 🎨 / 🌍 / 📝 / 🐛 in the title or first line.** OD is design-loving but the maintainers read a *lot* of PRs.

## Soft rules

- Lead with **what changed**, not why or how. Maintainers can read the diff for the how.
- "Why" gets at most 2–3 sentences. If it needs more, the work is too big for this skill — open an issue instead.
- One screenshot if the change is visible. Zero is fine.
- The "checklist" should reflect what the validator actually checked, not a generic ceremonial list.

## Anti-patterns (do not do these)

- **Don't** write an "ask" section. Don't say "please review when you have time" — the PR is the ask.
- **Don't** invite the maintainer to call / DM you. Discord is the channel.
- **Don't** apologize. ("Sorry if this isn't right" — the maintainer will tell you if it isn't.)
- **Don't** include a "TL;DR" — if the summary needs a TL;DR, the summary is too long.

## Title conventions (for `git commit` and `gh pr create --title`)

| Type | Format | Example |
|---|---|---|
| Skill | `Add Skill: <name>` | `Add Skill: invoice-template` |
| Design System | `Add Design System: <brand>` | `Add Design System: notion` |
| i18n | `Translate <doc> to <Lang>` | `Translate QUICKSTART to Spanish` |
| i18n (refresh) | `Update <Lang> translation of <doc>` | `Update zh-CN translation of README` |
| Docs typo | `Fix typo in <file>` | `Fix typo in README.md` |
| Docs other | `<verb> <noun> in <where>` | `Clarify daemon setup in QUICKSTART` |
| Bug (issue title) | `<observed> on <surface>` | `Preview iframe is blank on Safari 17` |

## When to ask before writing

If the user wants to ship something whose tone is unusual (a manifesto blog post, a contentious refactor, naming a brand after a real company without rights), pause and ask the user. Better to skip the PR than ship something the maintainer will close politely.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall