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/skill-anatomy.md
View on GitHub# What an OD skill folder looks like
Reference for the `od-contribute` skill's `validate-skill-submission.sh` step and for guiding a user through assembling a Skill submission.
> **Authoritative source**: read 1–2 existing folders under `skills/` in `nexu-io/open-design` at runtime — conventions evolve faster than this doc.
## Minimum viable skill
```
skills/<your-skill>/
└── SKILL.md # required, must have YAML frontmatter
```
That's it. Many of the simplest skills in OD are exactly that: one Markdown file in one folder.
## Frontmatter — what `validate-skill-submission.sh` requires
```yaml
---
name: <kebab-case-slug> # required; usually matches the folder name
description: | # required; one paragraph; what the skill does in user terms
Generate and iterate ad creative including headlines, descriptions, and primary text.
triggers: # optional but strongly recommended
- "ad creative"
- "ad headline"
od: # optional; OD-specific metadata
mode: design-system # or other modes; check existing skills
category: <category-slug>
upstream: "https://github.com/..." # if the skill was lifted from somewhere
---
```
**Required by validator**: `name`, `description`. Everything else is convention.
## Body conventions (after the frontmatter)
Looking at existing skills, the typical body has:
1. `# <skill-name>` H1.
2. A one-line "what it does" sentence.
3. Optional `## Source` block when adapted from upstream (with attribution).
4. `## How to use` with one or two example prompts the user might type.
## When a skill folder needs more than `SKILL.md`
- **Reference assets** — long prompt fragments, example outputs, image references — go alongside `SKILL.md` in the same folder, referenced via relative paths in `SKILL.md`.
- **Subfolders** are fine: the validator only requires that every relative reference inside `SKILL.md` resolves and that no path escapes the skill folder.
## Don'ts
- Don't put runtime code in here. Skills are *content* — Markdown + maybe assets. Code adapters live in `apps/daemon/src/`.
- Don't reference files outside `skills/<your-skill>/` — that breaks portability.
- Don't put binaries you don't need (the lighter the folder, the easier the review).
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 |