agentleFS
Aniket-508Aniket-508/termcn/.agents/skills/launch-shadcn-registry/SKILL.md

launch-shadcn-registry

Skill1.2k starsChanged 4 months agoMITView on GitHub

Launch and promote a custom shadcn/ui registry end-to-end: validate registry.json, prepare the official shadcn-ui/ui directory PR, community directory PRs (registry.directory, shadcntemplates, birobirobiro/awesome-shadcn-ui, bytefer/awesome-shadcn-ui), and draft social posts for Reddit r/shadcn, X, Dev.to, and Hacker News. Use whenever the user says "launch my registry", "list on shadcn directory", "submit to awesome-shadcn-ui", "announce my shadcn registry", "registry.directory PR", or wants to promote a new @scope registry — even if they do not say "launch-shadcn-registry" explicitly.

  • Commits and pushes

3 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 9 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read references/preflight.md and run validation before generating any PRs.

    line 60
  2. Very specific:

    Use feat(registry): add <scope> for official shadcn-ui/ui (matches PR #10896).

    line 99
  3. Very specific:

    Use gh for all GitHub operations.

    line 103
  4. Distinctive:

    Read platform references and produce ready-to-paste drafts (user posts manually):

    line 144
  5. Distinctive:

    After PRs are open or merged:

    line 159
  6. Distinctive:

    After official merge, suggest updating social drafts to mention "now listed in the shadcn registry directory"

    line 163
  7. Distinctive:

    If a PR is rejected, read maintainer feedback and adjust description or registry format — do not resubmit unchanged

    line 164
  8. Distinctive:

    Never submit to directories before preflight passes

    line 168
  9. Distinctive:

    Never claim listings are live until PRs are merged

    line 169
  10. Distinctive:

    Never auto-post to Reddit, X, Dev.to, or HN — drafts only

    line 170
  11. Very specific:

    Keep official directory.json entry at the end of the array (append only)

    line 171
  12. Distinctive:

    Ask: "Open PRs to all 5 repos?"

    line 184

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Launch shadcn Registry

Orchestrate listing and announcing a custom shadcn/ui registry across official and community directories, then draft platform-specific social posts.

Before You Start

Confirm the user wants a full launch or a subset (e.g. official directory only, or social drafts only). Default to the full workflow unless they narrow scope.

Collect or infer a registry profile. If missing fields, ask before generating artifacts. Use templates/registry-profile.example.json as the shape; validate against templates/registry-profile.schema.json.

Required profile fields:

FieldPurpose
scopeRegistry scope, e.g. @ogimagecn
nameDisplay name
homepageMarketing/docs URL
registryBaseUrlBase URL for JSON files (no trailing slash)
componentUrlPatternURL pattern with {name} placeholder, e.g. https://example.com/r/{name}.json
descriptionOne sentence (≤160 chars) for directories
descriptionLong2–3 sentences for awesome lists and social
githubUrlSource repo
githubUsernameFor avatar URLs and filenames
distributionopen-source or premium
categoriesTags for shadcntemplates / awesome lists
installExamplee.g. npx shadcn@latest add @scope/component-name
logoInline SVG string for official directory (optional but recommended)
registryIndexPathPath to registry index relative to registryBaseUrl, defaults to /registry.json (optional)
sampleComponentsArray of component slugs to validate during preflight, e.g. ["og-image"] (optional)
featuresBullet points for shadcntemplates and social posts (optional)

Workflow Overview

Copy this checklist and track progress:

Launch Progress:
- [ ] Phase 1: Preflight validation
- [ ] Phase 2: Generate directory artifacts
- [ ] Phase 3: Open GitHub PRs (user approval per PR)
- [ ] Phase 4: Draft social posts
- [ ] Phase 5: Post-launch follow-up

Phase 1: Preflight

Read references/preflight.md and run validation before generating any PRs.

bash scripts/validate-registry.sh <registryBaseUrl> [sample-component-name]

Fix all blockers before continuing. Common failures:

  • registry.json not public or wrong path
  • Component JSON 404
  • Duplicate @scope in official directory
  • description too long or marketing-heavy for official listing

Fetch the official directory to check duplicates:

curl -fsSL https://raw.githubusercontent.com/shadcn-ui/ui/main/apps/v4/registry/directory.json | grep -i "<scope>"

Phase 2: Generate Artifacts

From the registry profile, generate all submission files. Read the relevant reference only for targets the user wants:

TargetReferenceOutput
Official shadcn-ui/uireferences/shadcn-ui-official.mdJSON entry + PR body
registry.directoryreferences/registry-directory.mdJSON entry + PR body
shadcntemplatesreferences/shadcntemplates.mdcontent/{author}-{name}.md
birobirobiro awesomereferences/awesome-birobirobiro.mdREADME table row
bytefer awesomereferences/awesome-bytefer.mdREADME table row

Present artifacts grouped by repo. Include:

  1. Exact file path to create or edit
  2. Full content to add (not diffs alone)
  3. Suggested PR title and body

PR title convention

Use feat(registry): add <scope> for official shadcn-ui/ui (matches PR #10896). Use docs: add <name> to <section> for awesome lists and feat: add <name> registry for registry.directory.

Phase 3: Open GitHub PRs

Use gh for all GitHub operations. Ask the user before creating each PR unless they explicitly asked to open all PRs.

Standard fork-and-PR flow per repo:

# Example: official shadcn-ui/ui
gh repo fork shadcn-ui/ui --clone=false
git clone https://github.com/<user>/ui.git /tmp/ui-registry-pr
cd /tmp/ui-registry-pr
git remote add upstream https://github.com/shadcn-ui/ui.git
git fetch upstream && git checkout -b feat/<scope>-directory upstream/main
# edit apps/v4/registry/directory.json — append entry at end of array
git add apps/v4/registry/directory.json
git commit -m "feat(registry): add <scope>"
git push -u origin HEAD
gh pr create --repo shadcn-ui/ui --title "feat(registry): add <scope>" --body "$(cat <<'EOF'
## Summary
Adds <scope> to the community registry directory.

- **Registry URL**: `<componentUrlPattern>`
- **Homepage**: <homepage>
- **Description**: <description>

## Test plan
- [ ] `curl <registryBaseUrl>/registry.json` returns valid JSON
- [ ] `npx shadcn@latest add <installExample>` installs successfully
EOF
)"

Recommended PR order:

  1. Official shadcn-ui/ui (highest leverage; may take maintainer review)
  2. rbadillap/registry.directory
  3. shadcnblocks/shadcntemplates
  4. birobirobiro/awesome-shadcn-ui and bytefer/awesome-shadcn-ui (can be parallel)

Track PR URLs in the launch checklist. Do not draft social posts as "published" until the registry is live and at least one directory listing is merged or submitted.

Phase 4: Social Drafts

Read platform references and produce ready-to-paste drafts (user posts manually):

PlatformReference
Reddit r/shadcnreferences/social/reddit.md
Xreferences/social/x.md
Dev.toreferences/social/devto.md
Hacker Newsreferences/social/hackernews.md

Tailor each draft from the registry profile. Include the install command, homepage, and GitHub link. Avoid hype; lead with the concrete problem the registry solves.

Timing: Draft social posts after preflight passes. Suggest posting after the official directory PR is merged (or at minimum after registry.json is live).

Phase 5: Post-Launch

After PRs are open or merged:

  1. Share PR links with the user in a summary table (repo, PR URL, status)
  2. Remind user to respond to review comments within 48h
  3. After official merge, suggest updating social drafts to mention "now listed in the shadcn registry directory"
  4. If a PR is rejected, read maintainer feedback and adjust description or registry format — do not resubmit unchanged

Rules

  • Never submit to directories before preflight passes
  • Never claim listings are live until PRs are merged
  • Never auto-post to Reddit, X, Dev.to, or HN — drafts only
  • Keep official directory.json entry at the end of the array (append only)
  • One registry profile drives all artifacts — do not invent different descriptions per platform without user approval
  • For premium registries on shadcntemplates, note the one-free / $100 multi-premium policy; do not promise approval

Example

User: "Launch @ogimagecn — https://ogimagecn.vercel.app"

Agent:

  1. Build profile from site + curl https://ogimagecn.vercel.app/r/registry.json
  2. Run validate-registry.sh https://ogimagecn.vercel.app og-image
  3. Generate JSON for official directory, registry.directory, shadcntemplates markdown, awesome list rows
  4. Ask: "Open PRs to all 5 repos?"
  5. On approval, create PRs via gh
  6. Deliver Reddit, X, Dev.to, and HN drafts

Additional Resources

  • Registry profile schema: templates/registry-profile.schema.json
  • Example profile: templates/registry-profile.example.json
  • Validation script: scripts/validate-registry.sh

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.