better-layout

作成者: jakubkrehel

グループ化、配置、読み順、レスポンシブ構造、翻訳後のテキスト用スペースを設定し、レイアウトがサイズ変更、翻訳、左右反転後も崩れないようにします。

npx skills add https://github.com/jakubkrehel/skills --skill better-layout

Layout

This skill sets grouping, alignment, spacing and responsive structure. It then stress-tests that structure by resizing it, translating it and mirroring it for RTL.

Write every fix in the project's styling system. The numbers below apply only where the project has no spacing scale or density system; otherwise use its tokens. A finding needs a failure you can show, such as a clip, an overlap, a broken mirror or a misread group. A value that differs from these starting points is not one.

Hit areas and focus behavior belong to better-accessibility. Radius and shadows belong to better-ui, and animation to better-motion. Line length, text spacing and truncation mechanics belong to better-typography. The words themselves belong to better-writing.

Group with space, not lines

Space groups first, background shapes second, separator lines last and only where space alone can't carry the structure. The gap between groups is at least 2× the gap within one, so 8px inside a group means 16px or more between groups. Recipes are in grouping-and-alignment.md.

Keep controls distinct from content

Give every interactive element a background shape, a border, an underline or a consistent placement zone such as a toolbar. A control styled like the static text beside it does not read as a control. See grouping-and-alignment.md.

Align to shared edges

Pick a small set of alignment edges and put everything on them. Use one project spacing step per level of nesting, where 16px is a useful default. See grouping-and-alignment.md.

Logical properties for anything that mirrors

Write direction-dependent layout as leading and trailing: margin-inline-start, padding-inline-end, inset-inline-start, text-align: start. Reserve physical left and right for physical geometry such as safe-area insets. The mapping table and the RTL progression rules are in grouping-and-alignment.md.

Order by importance

The most important content sits near the top and the leading edge. Within a row, identifying content leads and metadata and actions trail. Visual order matches DOM order, so never move content out of source sequence with order, row-reverse or grid placement. See grouping-and-alignment.md.

One primary action per view

Give each view one primary action. Once a view has more than 3 secondary actions, put them behind a menu. Prefer a short view that links deeper over one long view that shows everything at the top level. better-colors owns how color marks the primary action.

Hint at hidden content

Every piece of off-screen or collapsed content needs a visible cue. Use the project's established cue, let the next item peek 16–32px past the scroll edge or show a disclosure control.

A truncated value the user needs has a way to the full text: an expand control, a detail view or a tooltip that is also keyboard-reachable. Truncation mechanics are better-typography's. Recipes are in spacing-and-adaptivity.md.

Borderless controls need more clearance

Without an established density system, start with 12px between adjacent bordered or filled controls. Leave 24px between the visible glyphs of borderless text and icon controls, counting each button's own padding. Compact layouts may use less, as long as hit areas never overlap and the controls stay distinct. See spacing-and-adaptivity.md.

Inset buttons from the edges

In content layouts, keep full-width buttons inside the layout margins, starting near 16px inline on mobile. Edge-to-edge actions work when they follow established platform chrome, account for safe areas and stay distinguishable from system UI. See spacing-and-adaptivity.md.

Content bleeds, controls float

Backgrounds and media extend to the viewport edges. Controls and text stay inside the layout margins and safe areas. env(safe-area-inset-*) is non-zero only when the viewport meta includes viewport-fit=cover.

Content scrolls beneath sticky chrome. Set scroll-padding-block-start to the sticky header's height, so anchored targets and focused elements never land under it. See spacing-and-adaptivity.md.

Hold structure until it breaks

Breakpoints come from the content, not device presets. Keep the expanded layout until it stops fitting, then collapse. Prefer container queries for component-level adaptation, and test the smallest and largest supported sizes first. See spacing-and-adaptivity.md.

Plan for growth and clipping

Translated strings grow, and short ones grow proportionally more, so a one-word button label is the riskiest thing on the screen. Size text containers with max-width and min-height, never a fixed width or height, and let rows wrap. Test with pseudo-localization and one long-string locale such as German.

Never park a critical action where resizing, zoom or scrolling clips it. Keep it in the normal flow or in stable chrome. See spacing-and-adaptivity.md.

Before you finish

Detection patternFix
grid-template-columns: … 1fr or a flex child holding long text or a wide table, overflowing its trackminmax(0, 1fr) on the track, min-width: 0 on the flex child
width: 100vwwidth: 100%; 100vw includes the scrollbar and scrolls horizontally on desktop
height: 100vh on a full-height mobile pane100dvh tracks the toolbar. The on-screen keyboard resizes only the visual viewport, so keep the bottom action in stable chrome
height: with a fixed length on a box holding textmin-height, or max-height with overflow-y: auto
@media (max-width: …) inside a reusable component@container on the component's parent
container-type: inline-size on a flex item, inline-block or absolute element with no widthGive it a definite width; size containment collapses a shrink-to-fit box to zero
env(safe-area-inset-*) with no viewport-fit=cover in the viewport metaAdd it, or the insets resolve to 0
inset-inline-* or *-inline-* combined with safe-area-inset-left or -rightPhysical left or right with the matching inset, plus a [dir="rtl"] override
float: left on mirrored UIfloat: inline-start
translateX or background-position: left on mirrored UIA [dir="rtl"] override; neither has a logical form
Sticky header with no scroll-padding-block-startSet it to the header height

Reporting

Verification. Without a browser, check logical properties in place of physical ones, container and media queries against the supported viewport list and DOM order against visual order. With one, check every supported width, 320px, 200% zoom and the RTL mirror. Report every check you could not run as Not verified.

A standalone review takes its severity ladder and format from reporting.md.

jakubkrehelのその他のスキル

better-accessibility
jakubkrehel
WCAG 2.2に照らして、キーボード操作とフォーカスの挙動、ARIA、アクセシブルネーム、フォーム、スクリーンリーダーへの通知、モーション、ズームをレビューして修正します。
developmenttestingcode-review
better-colors
jakubkrehel
パレットを生成し、セマンティックトークンに名前を付け、形式を変換し、コントラストを測定して、カラーシステムを構築・検証します。
designdevelopment
better-interface
jakubkrehel
アクセシビリティ、レイアウト、文章、タイポグラフィ、色、UIの仕上がり、モーションの観点から、画面、フロー、またはインターフェース全体をレビューし、優先順位付きのレポートを1つ返します。
designcode-reviewtesting
better-motion
jakubkrehel
何をアニメーションさせるかを判断して実装し、duration、easing、scale、distanceの正確な値と、enter、exit、アイコンの切り替え、共有レイアウトアニメーション、ドラッグのレシピを提供します。
designdevelopment
better-typography
jakubkrehel
文字の表示方法を設定・確認します。文字サイズのスケールや間隔から、フォント機能、折り返し、省略、句読点まで対応します。
designdevelopment
better-ui
jakubkrehel
境界線の角丸、光学的な配置、影、アイコンの状態に正確な値を指定して、表面やアイコンを磨き上げます。
designdevelopment
better-writing
jakubkrehel
ラベルやエラーメッセージから空の状態や確認メッセージまで、インターフェースの文言を作成・レビューし、プロダクトのトーンに合わせるとともに、次に何をすればよいかをユーザーに伝えます。
documentdesigncommunication
make-interfaces-feel-better
jakubkrehel
インターフェースを洗練されたものにするための設計エンジニアリングの原則。UIコンポーネントの構築、フロントエンドコードのレビュー、アニメーションの実装、ホバー状態、シャドウ、ボーダー、タイポグラフィ、マイクロインタラクション、出現・消滅アニメーション、またはあらゆるビジュアルディテール作業の際に使用します。UIの洗練、デザインの詳細、「見た目を良くしたい」「何か違う感じがする」、スタッガーアニメーション、ボーダー半径、光学的配置、フォントスムージング、タブラーニュメラル、画像のアウトライン、ボックスシャドウに反応します。
developmentdesign