docs: Promote frame-boundary pause and pause-before-setup guidance in pause-point skill

[hatayama]

Summary

• The pause-point skill's Quick Check Template now states, up front, that a hit pauses at the next frame boundary (not instantly) and that self-progressing games need to be paused before scenario setup.

User Impact

• These two semantics were previously documented only in later, easy-to-miss sections (Fast-Progressing Games, captured-variables.md), so callers reading only the Quick Check Template misread a hit as an instantaneous stop and could lose a scenario to a self-progressing game consuming it before their setup input arrived.
• Both points now appear right where the workflow is first read, pointing to the existing detailed sections for more.

Changes

• Added two sentences to the Quick Check Template in SKILL.md, right after the numbered workflow steps.
• Regenerated the .claude/.agents skill copies via uloop skills install --claude --agents.
• No wording changes to the existing Fast-Progressing Games section or captured-variables.md; this is purely additive.

Verification

• Docs-only change: diff confirms the source SKILL.md and the two generated skill copies are byte-identical.

[coderabbitai]

Warning

Review limit reached

@hatayama, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: b2e1c0ca-c656-486b-a007-e6cc3b7129bd

📥 Commits

Reviewing files that changed from the base of the PR and between a32092e and cbb737f.

📒 Files selected for processing (3)

• .agents/skills/uloop-pause-point/SKILL.md
• .claude/skills/uloop-pause-point/SKILL.md
• Packages/src/Editor/CliOnlyTools~/PausePoint/Skill/SKILL.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/pause-point-skill-quick-check-guidance

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}