Menu

Individual skill

layout-reviewing

0upvotes

Layout review criteria: fidelity to a source such as Figma or a screenshot, consistency with the project where no source exists, required viewport and state evidence, and visual defects in spacing, typography, color, assets, and responsive reflow. Use whenever an implemented web layout is reviewed or checked against its design or across screen widths. Implementing or fixing a layout uses layout-writing.

skills/layout-reviewing/SKILL.md

Read pinned source

Source commit ca44595f459eb84086cec8ed04d47f57bab945f3

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
303
Repository last updated
Oct 21, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Layout Reviewing

Judge the supplied implementation and prepared evidence. You may challenge the visual approach,
responsive behavior, or treatment of states and propose a stronger alternative within the supplied
scope. Do not replace an intentional source value with personal taste.

## Review Basis

- Where an exact source exists, it controls defined geometry, spacing, color, typography, crop,
  effects, layering, content placement, and responsive states.
- Where no source exists, use repository rules, the same component in other states, neighboring
  UI, tokens, and established components as the review standard.
- For a partial source, keep these responsibilities separate. General design conventions do not
  override values the source defines intentionally.
Back to top