Index of every page on this site: llms.txt
All skills
jakubkrehel avatar

/better-layout

@672ae44
by Jakub Kreheljakubkrehel/skills12k stars
484
Run it yourself

Sets grouping, alignment, reading order, responsive structure and room for translated text, so a layout holds up when it is resized, translated or mirrored.

Use this Skill: https://skilld.dev/gh/jakubkrehel/skills/better-layout

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈43 tokens for metadata: the name and description. ≈1.9k when used: this file. ≈2.7k more on demand in 4 files.

Description uses 2.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈172 characters, or 2.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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 pattern Fix
grid-template-columns: … 1fr or a flex child holding long text or a wide table, overflowing its track minmax(0, 1fr) on the track, min-width: 0 on the flex child
width: 100vw width: 100%; 100vw includes the scrollbar and scrolls horizontally on desktop
height: 100vh on a full-height mobile pane 100dvh 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 text min-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 width Give 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 meta Add it, or the insets resolve to 0
inset-inline-* or *-inline-* combined with safe-area-inset-left or -right Physical left or right with the matching inset, plus a [dir="rtl"] override
float: left on mirrored UI float: inline-start
translateX or background-position: left on mirrored UI A [dir="rtl"] override; neither has a logical form
Sticky header with no scroll-padding-block-start Set 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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1d3 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    The skill provides comprehensive guidelines for the agent to optimize CSS layouts and is functionally safe, containing no malicious scripts, external dependencies, or obfuscated content. It possesses a standard indirect prompt injection surface inherent to coding assistants that process and modify project source code.

  • Socket3d

    No alerts

  • Snyk1d

    Risk: LOW · No issues

Signed by skilld at 672ae44. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 days ago

README badge

README badge for jakubkrehel/skills/better-layout