playful-design/router

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.

Zobacz źródło

Jak używać

  1. Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
  2. W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
  3. Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/playful-design/router --skill alignment

Przed rozpoczęciem

  • Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
  • Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

Alignment

This skill checks a running page for things that are out of line or out of balance. It measures the rendered ink, confirms each finding in a zoomed screenshot and returns a numbered report.

Measured to the pixel, judged by eye

Lines, gaps, centres and radii are measured, never estimated. A miss of 1–4px is a finding, because it reads as a mistake while a 16px indent reads as intent. Visual weight has no number, so it is judged from the screenshot and shown as a crop.

Opening the running result belongs to verify. Comparing against a named reference belongs to match. Forcing hover, open and error states belongs to lab. Moving a fix into the shared component belongs to reuse. Rendering every width belongs to viewports.

1. Open the shipped render

Open the page at the viewport it ships at, with a device scale factor of 2. Check each theme and each state the user named. Reasoning from the CSS about where things should land is alignment-measure-the-render.

2. Run the measurement

Read the spacing scale from the project's tokens first. Run measure.js in the page through the browser's evaluate call, passing the scale as window.__alignmentOptions = { scale }.

It returns findings with a rule, the element, the measured values and a rectangle. Treat each as a candidate until step 3 confirms it.

3. Check the lines

Crop each candidate from the 2x screenshot and count the pixels. Drop any finding the pixels do not show.

Text, icons and controls that start a column share one x. A title 2px right of its description is alignment-shared-edge.

Repeated siblings sit at one gap. A list spaced 8, 8 then 12px is alignment-even-gaps. A deliberate group break is at least twice the gap.

Every padding, gap and margin is a step on the project's scale. A 6px padding on a 4px scale is alignment-on-scale.

4. Check the centres

Text in a control centres on its cap height and baseline, not its line box. Ink sitting 2px low in a button is alignment-ink-centre. Trim the box with text-box: trim-both cap alphabetic or balance the padding.

An icon beside a label centres on the label's cap height. An icon centred on the line box and sitting 1px low is alignment-icon-with-label.

Play icons, arrows and triangles carry their weight on one side. A play icon centred by its box that looks shifted left is alignment-optical-glyph. Nudge it and name the value, such as --play-nudge: 1px.

A nested surface's radius is the outer radius minus the inset. A 16px panel inside a 16px card at 8px inset is alignment-concentric-radius, and it takes 8px.

5. Judge the weight

Look at the screenshot at 1x and name what the eye lands on first. Compare icon strokes with the text's stem weight, filled icons beside outline icons and circles drawn the same size as squares.

Circles and triangles need roughly 10% more size than a square to read as equal. A 2px icon stroke beside 1.5px text stems is alignment-visual-weight.

6. Report with proof

Copy report.html to .alignment/<page>/index.html, an ignored folder and never the source tree. Save the 2x screenshot beside it and write report.js in the shape its header comment shows, then open it.

The report draws the numbered outlines and cuts each zoomed crop from that screenshot, so write data only. A report with its own markup or crops cut by hand is alignment-shipped-report. A finding with no measurement and no rect is alignment-annotated-proof.

7. Fix only when asked

The report is the deliverable. When the user asks for fixes, change the token or primitive behind each finding. Rerun the script and the screenshot, then report what cleared.

The pair

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

RuleBrokenReplacement
alignment-measure-the-render"The flex container centres it"Measured in the running page at 2x
alignment-shared-edgeTitle inset 2px from its descriptionBoth start on one ink line
alignment-even-gapsRows at 8, 8 and 12pxRows at 8, 8 and 8px
alignment-on-scalepadding: 6px on a 4px scalepadding: 8px
alignment-ink-centreLabel ink 2px low in its buttontext-box: trim-both cap alphabetic
alignment-icon-with-labelIcon centred on the line boxIcon centred on the cap height
alignment-optical-glyphPlay icon centred by its boxPlay icon nudged 1px right, named
alignment-concentric-radius16px panel in a 16px card at 8px inset8px panel radius
alignment-visual-weight2px icon stroke beside 1.5px stemsStroke matched to the text weight
alignment-annotated-proof"The button looks a bit off"Finding 3, 1.8px low, with the crop
alignment-shipped-reportCrops cut by hand into a page written from scratchreport.html copied, only report.js written

Reporting

Severity. HIGH is a miss visible at 1x on a primary surface, such as a heading column or a primary button. MEDIUM is a 1–2px miss, uneven gaps, a radius mismatch, a weight imbalance or a hand-built report. LOW is an off-scale value that still renders aligned.

Format. One finding per root cause, numbered to match the overlay:

1. file:line - [rule-id] what is wrong (measured values)

Cite the element from the script when the source line is not found. Then a Rule | Count | Severity summary. Block when any HIGH remains, Approve otherwise. Mark canvas, image and cross-origin content as Not verified.

z tego samego repozytorium

Więcej Skills

Wszystkie Skills
playful-design
Społeczność

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.

Instalacje / 1h
2
GitHub Stars
13
Aktualizacja
5 lis
playful-design
Społeczność

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

Instalacje / 1h
2
GitHub Stars
13
Aktualizacja
5 lis
playful-design
Społeczność

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

Instalacje / 1h
2
GitHub Stars
13
Aktualizacja
5 lis
playful-design
Społeczność

animation-vocabulary

Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.

Instalacje / 1h
2
GitHub Stars
13
Aktualizacja
5 lis