contribute-catalog

Create and submit HyperFrames registry items as upstream PRs.

248|32|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/boraoztunc/skills --skill contribute-catalog-boraoztunc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contribute-catalog
Source: https://github.com/boraoztunc/skills/tree/main/contribute-catalog
Command: npx skills add https://github.com/boraoztunc/skills --skill contribute-catalog-boraoztunc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps contributors author new HyperFrames registry entries (blocks or components) and ship upstream PRs to the public catalog, ensuring a consistent, reviewable workflow from idea to merge.

Core Features & Use Cases

  • Provides a two-path workflow for blocks (registry/blocks) and components (registry/components).
  • Defines scaffolding, build, validation, preview, and ship steps, plus the required registry-item.json template and ID conventions.
  • Ensures entries follow the catalog standards and quality gates, simplifying collaboration and review.

Quick Start

Follow the steps to scaffold a new registry item and open a PR to the hyperframes registry.

Frequently Asked Questions about contribute-catalog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I contribute a new block or component to a public registry?

You contribute by scaffolding the correct directory structure, populating the registry-item.json template, passing linting validation, and opening an upstream pull request for review and merge.

What is the required directory structure for submitting HyperFrames registry items?

HyperFrames registry items require a specific directory structure separating blocks and components, alongside a properly formatted registry-item.json file defining the entry and its ID conventions.

What steps are involved in the workflow to ship a registry pull request?

The workflow to ship a registry pull request involves scaffolding the item, building, running validation and linting quality gates, previewing the output, and submitting the upstream PR.

Do I need to follow specific ID conventions when authoring registry templates?

Yes, authoring registry templates requires following specific ID conventions defined in the catalog standards to ensure your block or component passes the required quality gates during PR review.

Can I preview a registry component before opening an upstream pull request?

Yes, the workflow includes a preview step allowing you to validate your registry component locally and run linting checks before shipping the final upstream pull request to the public catalog.