Files
spec-coding-skills/.codex/skills/miaobao-jianying-alignment/SKILL.md
T

83 lines
3.0 KiB
Markdown

---
name: miaobao-jianying-alignment
description: Use when a Miaobao video-editing issue, spec, or implementation says 对齐剪映, CapCut, 剪映初剪, jianying-alignment, capcut-alignment, miaobao-video-benchmark, or needs real Jianying Pro behavior as the validation standard.
---
# 秒爆 Jianying Alignment
## Goal
Derive 秒爆 video-editing rules from real Jianying Pro/CapCut behavior before
drafting issues, specs, tests, or implementation plans.
Do not treat "对齐剪映" as a slogan. Turn it into observed rules, evidence,
invalid cases, and acceptance checks.
## Use When
- User says 对齐剪映, 剪映初剪, CapCut, Jianying, or asks whether 秒爆 video
editing matches mainstream editor behavior.
- A video-editing issue depends on timeline, track, clip, trim, transition,
snapping, overlap, linking, resource-library, property-panel, or export
behavior.
- Existing 秒爆 behavior feels plausible but needs a competitor truth surface
before filing an issue or writing code.
## Required Gates
- Real Jianying gate: operate Jianying Pro with Computer Use for the relevant
flow unless the user explicitly says it is unavailable. Screenshots supplied
by the user are useful evidence, but are not enough for a benchmark claim.
- Research gate: when public documentation helps, prefer official CapCut/Jianying
docs or stable public tutorials. Public docs supplement the desktop probe;
they do not replace it.
- Evidence gate: capture the actual Jianying state used for the conclusion.
Activate the app before screenshotting; discard screenshots that capture
Codex or another foreground app.
- Classification gate: mark each conclusion as 【实测】, 【资料】, 【推断】, or
【未验证+原因】.
## Probe Modes
- Semantic UX probe: use Computer Use screenshots and state inspection for
questions like "where is transition added", "what panel opens on selection",
or "does the timeline show default placeholders".
- Quantified interaction probe: when rules involve drag thresholds, snapping,
overlap handling, dead zones, or layout coordinates, use the
`probing-macos-gui` method: AXUIElement readouts first, Quartz CGEvent drags,
operation -> readout -> judgement, and bidirectional threshold checks.
- Existing local tools, when present: `~/code/real_product/miaobao/scripts/jianying-probe/`
(`ax_jy.py`, `drag.py`) and `jianying-timeline-report.md`.
## Output Shape
Return a compact benchmark block before any issue/spec:
```text
剪映验证结论:
- 【实测】...
- 【资料】...
- 【推断】...
- 【未验证+原因】...
秒爆差距:
- ...
可落地规则:
- 数据模型:
- UI 入口:
- 无效场景:
- 验收标准:
证据:
- local screenshot/report paths or uploaded asset links
```
## Handoff
- For bug capture, pass the benchmark block into `miaobao-capture-bug`.
- For implementation/acceptance, pass the rules into `miaobao-issue-acceptance`
before tests or code changes.
- Do not create/update issues or edit code from this skill without the relevant
downstream skill's confirmation gate.