repeated-component-alignment

repeated-component-alignment is a skill for Claude Code, Codex from dembrandt/dembrandt-skills. It costs 114 tokens per session (2,392 once invoked), scanned A, original, MIT.

A layout guide for repeated interface items such as cards, rows, table cells, navigation items, or dashboard tiles. It treats each item as a set of fixed positions so matching items stay aligned even when their content differs in length.

In plain words
What is it for?
Use it when building card grids, search results, tables, feeds, menus, KPI tiles, or other repeated components. It helps define consistent slots for media, titles, values, and actions.
Why use it?
It prevents repeated components from looking uneven or shifting actions and values into different places. This makes lists and grids easier to scan and keeps variable content from breaking the layout.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 54repo +2 2d ago A scan Socket: passSnyk: passSkillSpector: pass 114 tokens original MIT

Good fit Use it when building card grids, search results, tables, feeds, menus, KPI tiles, or other repeated components. It helps define consistent slots for media, titles, values, and actions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dembrandt/dembrandt-skills/repeated-component-alignment
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add dembrandt/dembrandt-skills --skill repeated-component-alignment
Clone the repo
git clone --depth 1 https://github.com/dembrandt/dembrandt-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for repeated-component-alignment

README.md
[![agentmods](https://agentmods.dev/badge/skills/dembrandt/dembrandt-skills/repeated-component-alignment/github.svg)](https://agentmods.dev/skills/dembrandt/dembrandt-skills/repeated-component-alignment)
Your own site
<a href="https://agentmods.dev/skills/dembrandt/dembrandt-skills/repeated-component-alignment"><img src="https://agentmods.dev/badge/skills/dembrandt/dembrandt-skills/repeated-component-alignment/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for repeated-component-alignment

Your own site · 80×15
<a href="https://agentmods.dev/skills/dembrandt/dembrandt-skills/repeated-component-alignment"><img src="https://agentmods.dev/badge/skills/dembrandt/dembrandt-skills/repeated-component-alignment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 114 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,392 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 30 Jun 2026
  • Snyk pass 30 Jun 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00114 $0.02392
Opus 5 $0.00057 $0.01196
Sonnet 5 $0.00023 $0.00478
Haiku 4.5 $0.00011 $0.00239

Measured 12d ago against content hash f712fae2093e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

repeated-component-alignment scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/repeated-component-alignment/SKILL.md · 239 lines

How it starts

The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repeated Component Alignment

When a component is rendered many times — a card grid, a list, a table, a nav menu, a row of KPI tiles, a feed — it stops being a single box and becomes a pattern. The value of a pattern is rhythm: the eye learns the layout once and scans the same slot across every instance (the title row, the price row, the action row). Variable content length breaks that rhythm unless the component is built to absorb it.

The principle is general. A card is the most common case, but the same rule governs list rows, table cells, nav items, tiles, comment entries, dashboard widgets, search results — anything repeated. Treat each as a fixed slot model, not a free-form container.

The goal: content of any length, instances that look identical. This is partly content production (write to a target length) and partly layout engineering (build slots that tolerate the variance). This skill covers the layout half and where the two meet.


The Slot Model

Name the slots once and treat them as a contract every instance honours. A product card, as a worked example:

┌──────────────────────┐
│ [media]              │  ← fixed aspect ratio
│                      │
├──────────────────────┤
│ ● Badge              │  ← optional slot, space reserved
│ Title                │  ← clamp to N lines
│ Subtitle / meta      │
│                      │
│ Description text…    │  ← flexible slot, grows
│                      │
├──────────────────────┤
│ €19.99      Read more│  ← anchor, pinned to bottom
└──────────────────────┘

The same three rules apply to a list row (avatar · name · meta · status pinned right), a KPI tile (label · big number · trend pinned bottom), or a search result (title · url · snippet clamped):

  • Every slot has a fixed position, whether or not it has content in a given instance.
  • One slot absorbs the variance (usually the description/snippet). All others are fixed or clamped.
  • Anchor elements are pinned — the primary action or value (CTA, price, status, trend) sits at the same position in every instance regardless of how much content is above or beside it.

Read the full file on GitHub · 239 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 239 lines · 114 tokens per session scan A f712fae2093e

Subscribe to this mod's changes

repeated-component-alignment is a skill published in the GitHub repository dembrandt/dembrandt-skills (54 stars, last pushed 2d ago), licensed MIT. It adds 114 tokens to every session and 2,392 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

indian-gov-web-ui

A set of design and accessibility rules for Indian government websites, portals, and administrative panels, including required standards such as GIGW and WCAG.

Yashraj00700/indian-gov-ui-skills · 95 tokens

ux4g-design-system

Use when building or reviewing UI with UX4G — India's official government design system (ux4g.gov.in, cdn.ux4g.gov.in, ux4g-web-components). Covers the v3.0.18 token API, the 52 components, install paths for HTML/React/Angular/Flutter, and the interop hazards. Triggers include "UX4G", "ux4g-web-components"…

Yashraj00700/indian-gov-ui-skills · 147 tokens

ui-ux-laws

Priority-ordered rulebook of core UX/UI laws, cognitive-psychology principles, Nielsen's usability heuristics, and accessibility requirements that Claude must actively apply (not just cite) whenever it designs, builds, redesigns, reviews, or critiques any user interface — websites, web/mobile apps, dashboards, forms…

AmirGhl/ui-ux-laws · 203 tokens

accessibility

Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

addyosmani/web-quality-skills · 51 tokens

design-dna

Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides…

zanwei/design-dna · 192 tokens

extract-design-system

Extract design primitives from a public website and generate starter token files for your project.

arvindrk/extract-design-system · 20 tokens