CSS Flexbox Layout Documenter skill for Claude and Codex
Writes the documentation a teammate needs to change a Flexbox layout safely: what it is for, what each container and item property does, how it responds at…
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
Use when an existing Flexbox layout needs written documentation covering its purpose, container and item settings, breakpoints, and what is safe to change. Do not use for fixing a broken layout, generating new CSS, or writing a general Flexbox tutorial. Related topics: coding, css.
What it will ask you for
- Flex container selector (free text, e.g. ".site-nav")
- Flex item selectors (longer free text)
- Main axis direction (choose one: row, row-reverse, column, column-reverse)
- Wrap behaviour (choose one: nowrap, wrap, wrap-reverse)
- Properties that matter in this layout (choose any: justify-content, align-items, align-content, gap, order, flex-grow, flex-shrink, flex-basis)
- Layout use case (free text, e.g. "navigation bar or card grid or form row")
- Responsive breakpoints (longer free text)
How it works
- State the layout's purpose and the invariant that must hold, in two sentences a new teammate can repeat.
- Tabulate container properties with value and reason, then item properties, flagging every exception to the pattern and why it exists.
- Describe each breakpoint by what the user sees change, with the declarations that cause it.
- Write the Safe to change and Will break the layout lists from the properties documented above.
- Produce a minimal HTML snippet and a CSS block that reproduce the layout in a sandbox.
What you get
A Markdown document with sections Overview, Container Settings (table), Item Settings (table), Responsive Adjustments, Safe to Change, Will Break the Layout, and Example with fenced HTML and CSS blocks.
What it watches out for
- Restating declarations without the reason, which tells the next developer nothing about whether they can change them.
- Skipping the nth-child or order exceptions; those are exactly the rules that surprise someone editing the layout later.
- Documenting breakpoints as code only, when the useful fact is what the user sees change at that width.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.