playful-design/router

audit

Reviews a change, a session or a whole codebase against every skill in this collection and returns one ranked, numbered report.

ソースを見る

使い方

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

開始前の確認

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

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

Audit

This skill reviews work against every rule in this collection at once. It sends each concern to the skill that owns it and merges the results into one ranked report.

The report, not the rules

This skill owns no interface rule. It owns the scope, the order of review, consolidation and the verdict. Each finding cites the rule id from the skill that owns it. A finding needs evidence from the code, the running app or the thread, never taste alone.

The report format is in report.md.

1. State the scope

Name what is under review: the uncommitted diff, a branch, a pull request, this session's requests or the whole codebase. An audit with no stated scope is audit-state-the-scope.

2. Read the project's rules

Read AGENTS.md, CLAUDE.md and the editor rule folders. A written project rule outranks a default here. Flagging code that follows a written rule is audit-project-rules-first.

3. Run every skill

Check the scope against each skill and record what you inspected.

SkillCheck
verifyEach changed surface opened in the running app
scopeEvery request in the thread against the diff
reuseNew components, styles and icons against the shared package
restraintUnrequested UI, settings, fallbacks, dead code and narrating comments
copyEvery label, description and status string
proseEach changed post, breakdown or design note, when writing is in scope
defaultsSurfaces, type, sound, focus, names, forms, loading, hotkeys and dialogs
motionEvery transition, animation, gesture, exit and motion blur
colorText and field contrast in each theme, tokens inside components and the accent
gatherEach reference board: platform, links and the part to take
matchEach named reference, when the work copies one
ruleRepeated corrections with no written rule, and edits that break one
viewportsEach changed layout at every width, when layout is in scope
shipStray files, secrets, commits and checks, when git is in scope

Skipping a skill without saying why is audit-run-every-skill.

4. Merge by root cause

One cause that breaks rules in two skills is one finding with both ids. Five call sites with the same local fix is one finding with five locations. Listing each symptom on its own line is audit-one-row-per-cause.

5. Number the fixes and open the report

Rank findings by severity, then by reach. Number them so the user can answer "fix 1, 2 and 5".

Copy report.html to .audit/<scope>/index.html, an ignored folder and never the source tree. Write report.js beside it in the shape its header comment shows, then open it.

The report's look ships with the skill, so write data only. A page with its own markup or styles is audit-shipped-report.

The user marks findings with Pick and pastes them back with Copy Picks. Wait for the pick, then fix only the numbers chosen. Fixing everything before the user picks is audit-fix-what-was-picked.

The pair

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

RuleBrokenReplacement
audit-state-the-scope"Audited the app""Audited the uncommitted diff: 14 files"
audit-project-rules-firstA border flagged in a repo whose rules require itThe project rule cited, no finding
audit-run-every-skillcopy silently skipped"copy: no strings changed"
audit-one-row-per-causeFive rows for one missing primitive fixOne row, five locations
audit-shipped-reportA report page written from scratchreport.html copied, only report.js written
audit-fix-what-was-pickedAll 18 findings fixed unaskedThe numbers the user chose

Reporting

Use the severity ladder and format in report.md. Block when any HIGH remains, Approve otherwise. Never Approve work you did not open or read.

同じリポジトリから

関連する 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日