nexu-io/open-design / .claude/skills/od-contribute
od-contribute
UnverifiedOne-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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.8 KB |
| agents/openai.yaml | config | 650 B |
| install.shexecutable | script | 5.1 KB |
| references/design-system-anatomy.md | markdown | 2.0 KB |
| references/newcomer-tone.md | markdown | 2.7 KB |
| references/od-repo-map.md | markdown | 2.2 KB |
| references/skill-anatomy.md | markdown | 2.3 KB |
| scripts/check-prereqs.shexecutable | script | 4.1 KB |
| scripts/config.shexecutable | script | 2.4 KB |
| scripts/create-issue.shexecutable | script | 3.7 KB |
| scripts/create-pr.shexecutable | script | 3.8 KB |
| scripts/discover-doc-gaps.shexecutable | script | 4.0 KB |
| scripts/discover-i18n-gaps.shexecutable | script | 4.8 KB |
| scripts/setup-workspace.shexecutable | script | 3.4 KB |
| scripts/validate-design-system.shexecutable | script | 3.3 KB |
| scripts/validate-markdown.shexecutable | script | 6.9 KB |
| scripts/validate-skill-submission.shexecutable | script | 5.0 KB |
| templates/ISSUE-BODY-bug.md | markdown | 450 B |
| templates/PR-BODY-design-system.md | markdown | 1.1 KB |
| templates/PR-BODY-docs.md | markdown | 723 B |
| templates/PR-BODY-i18n.md | markdown | 1.2 KB |
| templates/PR-BODY-skill.md | markdown | 1016 B |
references/design-system-anatomy.md
View on GitHub# What an OD design-system folder looks like
Reference for the `od-contribute` skill's `validate-design-system.sh` step.
> **Authoritative source**: read 1–2 existing folders under `design-systems/` in `nexu-io/open-design` at runtime — the conventions evolve as new systems land.
## Minimum viable design system
```
design-systems/<brand-slug>/
└── DESIGN.md # required — the brand brief OD loads
```
A few systems include extras: `components.html`, `tokens.css`. These are optional, referenced from `DESIGN.md` if present.
## DESIGN.md structure (observed convention)
H1 with the brand name, then a blockquote with category + one-sentence pitch, then numbered H2 sections. Looking at established systems (`airbnb`, `apple`, etc.), the typical section list is:
```markdown
# Design System Inspired by <Brand>
> Category: <e.g. E-Commerce & Retail>
> <one-sentence pitch>
## 1. Visual Theme & Atmosphere
## 2. Color Palette & Roles
## 3. Typography
## 4. Layout & Spacing
## 5. Components
## 6. Motion & Interaction
## 7. Iconography & Imagery
## 8. Voice & Tone
## 9. Edge Cases & Variations
```
Section ordering and exact titles vary — the validator only checks **structural overlap with reference systems**, not exact heading text. ≥30% overlap with the union of headings from existing systems is enough to pass.
## What the validator actually enforces
1. File is non-empty and has at least one H1.
2. ≥30% heading overlap with reference DESIGN.md files (when references are passed in).
3. No `../` relative paths that would resolve outside `design-systems/<brand>/`.
That's deliberately loose — DESIGN.md is a creative brief, not a schema.
## Don'ts
- Don't reference assets outside the brand folder.
- Don't paste binary fonts; use a CSS `@font-face` reference and let OD resolve at runtime.
- Don't use real customer logos / proprietary brand assets you don't have rights to (the validator won't catch this — it's a maintainer-review concern).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |