Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Skills: 10 cross-skill contradictions and 11 wrong facts or broken paths

オープン
#5,025 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
ドキュメント
明瞭さ
おおむね明確
活発さ
活発
技術スタック
markdown
領域
documentation

調査の方向性

Start by reading the cited SKILL.md files at the referenced commit and compare each conflict against the linked paths and sibling workflow guidance. Section 1 needs maintainer decisions before those changes can be made; section 2 lists proposed corrections across many skills. Done means the decisions are resolved and the documented rules and paths are consistent and valid.

索引モデルが issue の本文から書いたものです。

説明

documentation triage/needs-design

Verified against main at 2b82e39 (2026-10-04); line numbers refer to that commit. Short names drop the hyperframes- prefix (core = skills/hyperframes-core/SKILL.md, cli = skills/hyperframes-cli/SKILL.md, …). Unless a path is given, the line is in the skill's SKILL.md.

Why it matters. When two loaded skills give opposite rules, the agent picks one arbitrarily or stops to ask. When a path doesn't resolve, the agent gets a read error and stops, or improvises the missing doctrine. Users can't patch this locally: npx hyperframes skills update and hyperframes init (step 0 of every workflow) overwrite local edits.

Section 1 needs a maintainer decision. In section 2, each fix is one edit.

1. Contradictions between skills (needs a maintainer decision)

# Where Conflict Likely fix
1 core:56 vs animation:66, keyframes:56,77,112,259 core: "Building it inside an async callback (document.fonts.ready) is supported". animation and keyframes forbid building the timeline inside async / setTimeout / Promise. animation:66 also credits that ban to core's Non-Negotiable Rules, which don't contain it. Decide, then align the other two.
2 registry:72 vs studio:90-92, core:88 registry: "data-track-index — layer ordering (higher = in front)". studio and core: display only, it never changes what renders on top. registry:72 → "Studio timeline row; display only — use CSS z-index for layering".
3 figma:91 vs cli:176-180 figma tells the agent to run npx hyperframes events --skill=figma-motion … by hand. cli lists events under "Commands you should not run": "an agent has no reason to call it by hand". Move the beacon into a bundled script, or drop it from figma.
4 cli:24, general-video:120 vs keyframes:57,214,264, studio:139, motion-graphics:131-132, slideshow:511-521 cli: run check, "do not run a redundant standalone lint". The others run lint then check, and studio uses lint alone as its final gate. Align everything on check.
5 talking-head-recut:8, slideshow:14, embedded-captions:14, motion-graphics:16, faceless-explainer:8, music-to-video:8, pr-to-video:8, product-launch-video:8 vs general-video:17-23,150 and the step-0 init "Confirm with the user before running skills update" vs general-video running it unprompted. init updates the skills anyway. One consent rule for every workflow.
6 music-to-video:14 vs :161 :14, Steps 3 and 6 in autonomous mode: "post the summary as a heads-up and proceed instead of waiting". :161: render "only on approval (autonomous mode: the same, as the one kept question)". The sibling workflows keep the question: rewrite :14.
7 pr-to-video:178 vs faceless-explainer:128, product-launch-video:151 Pre-install registry blocks before dispatching workers (to avoid collisions) vs letting the parallel workers install them. Align on pre-install.
8 talking-head-recut:423-425 vs :1109-1110 The layout files cover 2 formats vs 3. Check the layout files and fix the wrong passage.
9 embedded-captions:51,95,134,177,226 vs :150-151,198 Cinematic-mode source file: plan.json, or cinematic.json → make-cinematic.cjs. Pick one.
10 audio:378-379 vs :138,386,391,476 "There is no static mode", while the same file describes one several times. Read carve.mjs, then align.

2. Wrong facts and broken paths (fix proposed)

# Where Now Proposed
11 studio:62-63 references/sub-compositions.md (not in studio) /hyperframes-core → references/sub-compositions.md
12 music-to-video:33 /media-use (references/bgm.md) /media-use (audio/references/bgm.md)
13 remotion-to-hyperframes:42 "When in doubt, default to … /general-video" (contradicts :12, its own description, and general-video's description) "When in doubt, return to /hyperframes; its intent layer picks the route."
14 registry:122 --tier on-device hard-coded (contradicts :127 and cli:92) --tier <the tier that answered>
15 talking-head-recut:541-543 vs :572-574 "copy-paste JSON snippet for … per-card layout field", while :572-574 says there is no card.layout field "… exact videoBounds + cardBounds; the storyboard records only card.zone". Drop "earlier versions … invented one" at :573.
16 talking-head-recut:251 "content can be a plain string…": the field is contentHints (:178) "contentHints can take any shape…"
17 talking-head-recut:547-550 "A common rhythm: … editorial … audit … whiteboard × pip × polaroid" (contradicts :433-434 and :455) Remove it, and say "Within the user's chosen style group you may vary the style per card…"
18 embedded-captions:277 "falls back per SKILL §transcription" (no such section) "falls back to an existing word-level transcript.json"
19 motion-graphics:111-114 node <SKILL_DIR>/phases/source/resolve.mjs … (the file doesn't exist; only guide.md does) Remove the block and keep "See phases/source/guide.md".
20 motion-graphics:101 The list of forms omits maps (listed at :54) Add / maps.
21 animation:76, creative:60-63, figma:97, slideshow:434,475 skills/<name>/scripts/… and skills/slideshow/references/… only resolve from the repo root, not from an installed skill <SKILL_DIR>/scripts/… and references/standalone-harness.md
主要言語
TypeScript
スター
54.1k
フォーク
4.9k
平均マージ
15時間 19分
マージ済み PR(30日)
769

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

heygen-com/hyperframes のほかの issue

heygen-com/hyperframes の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。