playful-design/router

scope

Changes exactly what was asked, keeps what already worked and finishes every item in the message.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/playful-design/router --skill scope

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Scope

This skill holds an edit to the request. It reads the smallest literal meaning, keeps everything that already worked and accounts for every item the user sent.

The smallest reading wins

A change outside the named element is a finding unless the user asked for a sweep. One short question before a broad change is not a finding. Press hardest on short messages that point at one element, on batched messages and on refactors.

Deleting what nobody asked for belongs to restraint. Proving the change works belongs to verify.

Every ask gets an answer

Split the message into numbered items and add the open items from earlier turns. Close with the same list, each item done or not done with the reason. Doing the first of four asks is scope-list-every-ask.

The named element and nothing around it

Restate the target in a few words. "The card" means the card, not the page around it. Restyling the whole shell for a top bar request is scope-smallest-reading. When two readings fit, ask one short question.

Earlier instructions still stand

Before editing, read the user's earlier corrections in the thread and the rules in the repository. Re-adding something they removed is scope-remember-instructions. A value they gave, such as 16px of left padding, stays. Guessing a new one is scope-keep-given-values.

What worked keeps working

Before a refactor, list the features, buttons and states that exist now, then check each one after. A dropped back button is scope-keep-what-worked. When fixing one property, keep the others. Fixing a clip by removing the width animation is scope-no-collateral.

Unshipped work is done now

Work that has not shipped is not split into phases or marked out of scope without asking. A "phase 2" list is scope-no-phasing. While planning, plan only. Editing files before the plan is approved is scope-plan-means-plan.

An explanation is the answer

When the user asks how something works, explain it and wait. Answering "how does this work" with a diff is scope-explain-when-asked.

The pair

Every check is a pair. The broken line sits beside the line that replaces it.

RuleBrokenReplacement
scope-list-every-askThe first of four asks done, three droppedFour numbered items, each reported
scope-smallest-reading"Fix the top bar" restyles the whole shellOnly the top bar changes
scope-remember-instructionsDots the user removed come backEarlier turns read before editing
scope-keep-given-valuesLeft padding re-guessed as 12pxThe 16px the user gave
scope-keep-what-workedA refactor drops back and forward buttonsBefore and after feature list, both buttons kept
scope-no-collateralThe clip is fixed and the width animation is goneClip fixed, width animation kept
scope-no-phasing"Saved filters: phase 2"Built now, or one question
scope-plan-means-planFiles edited during planningPlan only until it is approved
scope-explain-when-asked"Explain how it works" answered with a diffAn explanation, then wait

Reporting

Severity. HIGH is a dropped feature, or an earlier instruction undone. MEDIUM is a change outside the named element, or an ask left unreported. LOW is a question asked where one reading was plain.

Format. One finding per root cause, citing the request when no file applies:

file:line - [rule-id] what is wrong
request 2 - [rule-id] what is wrong

Then a Rule | Count | Severity summary. Block when any HIGH remains, Approve otherwise. Never Approve a diff you did not read. Mark every check you could not run as Not verified.

同じリポジトリから

関連する Skills

すべての Skills
playful-design
コミュニティ

alignment

Measures a running page for edges, gaps, centring and radii that miss by a pixel or two, then judges visual weight and returns a numbered report with proof.

1時間の導入数
2
GitHub Stars
13
更新日
11月5日
playful-design
コミュニティ

animate

Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it animate at all, what purpose, which tool, which properties, which curve and duration, how it interrupts, how it exits. Writes the implementation. Use when asked to animate something, add motion, make a component feel alive, or build a transition. For critiquing existing motion use review-animations; for auditing a whole codebase use improve-animations.

1時間の導入数
2
GitHub Stars
13
更新日
11月5日
playful-design
コミュニティ

animate-expo

Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For web a

1時間の導入数
2
GitHub Stars
13
更新日
11月5日
playful-design
コミュニティ

animation-performance

Keep web animations inside the frame budget — animate composite-only properties, keep motion off the main thread when the page is busy, and find the cause when an animation drops frames. Covers the layout/paint/composite pipeline, cheaper property swaps, CSS vs WAAPI vs requestAnimationFrame, Motion's hardware-accelerated path, React re-rendering per frame, inherited CSS variable recalculation, blur cost, and when will-change actually helps. Use when an animation is janky, choppy, stutters, or d

1時間の導入数
2
GitHub Stars
13
更新日
11月5日