playful-design/router

restraint

Ships the smallest thing that does the job and deletes what nobody asked for.

ソースを見る

使い方

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

開始前の確認

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

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

Restraint

This skill cuts a change down to the ask. It removes extra interface, options and code and treats "remove" as delete.

Build the ask

An element, option or code path the user did not ask for is a finding unless the ask needs it to work. Work that has not shipped carries no backwards compatibility. A cut the user has not approved is a proposal, not an edit.

Label wording belongs to copy. Reusing an existing part belongs to reuse.

Nothing beside the ask

Add no sections, badges, counts, captions, footers, icons inside buttons, sounds or decorative effects the user did not request. A count badge on every row is restraint-no-unrequested-ui.

No feedback the screen already gives

Do not add a toast or a dialog for an action whose result is already on screen. That is restraint-no-redundant-feedback.

The smallest build that works

Use the native element before a custom one, one app before a monorepo and a fixed value before a setting. A custom video player where <video controls> works is restraint-smallest-build. A preference nobody will change is restraint-no-needless-setting.

No defensive code before release

Keep no legacy branch and no compatibility shim in unshipped work. That is restraint-no-legacy. Do not add a fallback for a value that is always set. That is restraint-no-fallbacks.

Remove means delete

When the user says remove, delete the code and its styles, variables, routes and menu entries. "Deferred for review" is restraint-delete-dont-defer. A removed package that leaves its variables in theme.css is restraint-remove-the-trail.

Asked for a cleanup, list unused files, exports, styles, dependencies and leftover prototypes. Delete them once approved.

Comments state constraints or go

Delete comments that narrate the code. Keep one only when it states a constraint the code cannot show. A narrating comment is restraint-no-narrating-comments.

The pair

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

RuleBrokenReplacement
restraint-no-unrequested-uiA count badge on every rowNo badge
restraint-no-redundant-feedbackA toast after a move the user can seeNo toast
restraint-smallest-buildA custom video player<video controls>
restraint-no-needless-settingA preference for a gap nobody changesA fixed --gap
restraint-no-legacyA legacy branch kept "for safety"Deleted
restraint-no-fallbacksvalue ?? defaultValue for a value that is always setvalue
restraint-delete-dont-defer"Deferred for your review"Deleted, or one question
restraint-remove-the-trailA removed package's variables left in theme.cssThe variables removed with it
restraint-no-narrating-comments// Render the headerNo comment

Reporting

Severity. HIGH is a feature, setting or code path nobody asked for, or a "removed" item that still exists. MEDIUM is a fallback, a legacy branch or a leftover variable. LOW is a narrating comment.

Format. One finding per root cause:

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

Then a Rule | Count | Severity summary. Block when any HIGH remains, Approve otherwise. Never Approve a file 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日