contribute-cataloglisted

Author a new HyperFrames registry block (caption style, VFX block, transition, lower third) or component (text effect, overlay, snippet) and ship it as an upstream PR to the hyperframes repo. Use ONLY when the user wants to CONTRIBUTE to the public catalog — for in-project caption/transition authoring use the `hyperframes` skill, for installing existing registry items use the `hyperframes-registry` skill.
frankxai/claude-skills-library · ★ 15 · AI & Automation · score 67

Install: claude install-skill frankxai/claude-skills-library

# Contribute to HyperFrames Registry Guide the user from idea to merged PR for a new registry block or component. ## Workflow ``` 1. Clarify → 2. Scaffold → 3. Build → 4. Validate → 5. Preview → 6. Ship ``` ### Step 1: Clarify Ask what they're building. The registry has two item types: - **Block** (`registry/blocks/`, type `hyperframes:block`) — a full standalone composition with fixed dimensions and duration. Caption styles, VFX effects, title cards, lower thirds. - **Component** (`registry/components/`, type `hyperframes:component`) — a reusable snippet with no fixed dimensions or duration. CSS effects, text treatments, overlays that adapt to any composition size. Then ask: - One-sentence description of the effect - Visual reference (URL, screenshot, or description) - Who uses this and when? ### Step 2: Scaffold Create the registry structure: **For blocks:** ``` registry/blocks/{block-name}/ {block-name}.html registry-item.json ``` **For components:** ``` registry/components/{component-name}/ {component-name}.html registry-item.json ``` **Naming convention:** | Item name | ID prefix | Example IDs | | ---------------- | --------- | ---------------------- | | `cap-hormozi` | `hz` | `hz-cg-0`, `hz-cw-3` | | `cap-typewriter` | `tw` | `tw-cg-0`, `tw-ch-0-5` | | `vfx-chrome` | `vc` | `vc-canvas` | Use a 2-3 letter prefix. ALL element IDs must use this prefix to avoid collisions in sub-compositions. **r