section-layout-systems
Design non-generic website section layouts. Use when a page needs alternatives to card grids, bento overuse, generic feature blocks, repetitive centered sections, bland stat strips, or template-like section sequencing.
npx skills add TheGoat395/Codex-Skills --skill section-layout-systems --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Section Layout Systems ## Purpose Match section layout to content shape instead of defaulting to cards. ## Required Use Use this skill when the trigger description applies. Keep the `SKILL.md` lean, then read `references/section-layout-systems-guide.md` for concrete rules before planning or editing a meaningful website change. ## Operating Contract 1. Inspect before coding when code exists. 2. Convert vague taste into concrete rules. 3. Explain planned files before major changes unless the user clearly said to proceed. 4. Build, inspect, polish, and verify. 5. Report commands run, files changed, and anything not tested. ## Detailed Guide Read `references/section-layout-systems-guide.md` when this skill is active for a build, redesign, review, or implementation plan.
- Purpose
- Required Use
- Operating Contract
- Detailed Guide
What does the section-layout-systems skill do?
Design non-generic website section layouts. Use when a page needs alternatives to card grids, bento overuse, generic feature blocks, repetitive centered sections, bland stat strips, or template-like section sequencing.
How do I install it?
Run `npx skills add TheGoat395/Codex-Skills --skill section-layout-systems --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From TheGoat395/Codex-Skills, a repository with 115 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
