Claude Code Plugins

Community-maintained marketplace

Feedback

Clean up shadcnblocks sections by removing inline typography styles and fixing heading hierarchy. Use after installing sections with install-sections. Removes text-xl, font-bold, tracking-tight from headings. Ensures proper h1 to h2 to h3 order and one h1 per page.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name remove-inline-styles
description Clean up shadcnblocks sections by removing inline typography styles and fixing heading hierarchy. Use after installing sections with install-sections. Removes text-xl, font-bold, tracking-tight from headings. Ensures proper h1 to h2 to h3 order and one h1 per page.

Style Cleanup

Remove inline typography styles from shadcnblocks sections and fix heading hierarchy.

Workflow

  1. Read Component - Load the section component file
  2. Remove Typography Classes - Strip inline styles from h1-h6
  3. Check Heading Hierarchy - Verify proper h1 > h2 > h3 order
  4. Fix Hierarchy Issues - Adjust heading levels if needed
  5. Verify Single H1 - Ensure only one h1 per page

Classes to REMOVE from h1-h6

See references/cleanup-rules.md for complete list.

Typography sizes:

  • text-4xl, text-5xl, text-6xl, text-7xl
  • text-3xl, text-2xl, text-xl, text-lg
  • uppercase, lowercase, capitalize

Font weights:

  • font-bold, font-semibold, font-medium, font-light

Letter spacing:

  • tracking-tight, tracking-wide, tracking-normal, tracking-tighter

Line height:

  • leading-tight, leading-snug, leading-normal, leading-relaxed

Text colors on headings:

  • bg-muted-foreground (when used with bg-clip-text)

Button styles:

  • Any custom button style which is not from the
  • e.g., bg-, text-, p-, m- on buttons

Border-Radius Classes to REMOVE

Remove from MOST elements (div, img, section, span, cards, etc.):

Standard rounded classes:

  • rounded-sm, rounded, rounded-md, rounded-lg, rounded-xl, rounded-2xl, rounded-3xl, rounded-full

Directional rounded classes:

  • rounded-t-*, rounded-b-*, rounded-l-*, rounded-r-*
  • rounded-tl-*, rounded-tr-*, rounded-bl-*, rounded-br-*

Arbitrary values:

  • rounded-[*] (any custom values like rounded-[0.75rem])

EXCEPTIONS - Keep rounded-* on:

Buttons (button.tsx):

  • Keep all rounded-* classes on buttons
  • Different variants need different radii (pill buttons = rounded-full)
  • Button styling is controlled in button.tsx, not globals.css

Avatars (avatar.tsx):

  • Keep rounded-full on avatar components
  • Avatars are always circular by design convention

KEEP these border classes:

  • border (basic border)
  • border-border (uses CSS variable)

WHY: Border-radius is controlled globally via --radius in globals.css The CSS rules in globals.css automatically apply correct border-radius to:

  • Cards and containers (--radius-lg)
  • Images (--radius-md)
  • Badges (--radius-sm)
  • Inputs (--radius-md)
  • Accordion items (--radius-md)
  • Navigation menus (--radius-sm)
  • Popovers and dialogs (--radius-lg)

Border Cleanup Example

// BEFORE
<div className="rounded-lg border p-4">
<img className="rounded-xl w-full" />
<section className="rounded-2xl bg-muted">

// AFTER
<div className="border p-4">
<img className="w-full" />
<section className="bg-muted">

Classes to KEEP

Layout:

  • flex, inline-flex, grid, block, inline-block
  • gap-, space-, items-, justify-

Responsive prefixes:

  • sm:, md:, lg:, xl:, 2xl:

Spacing:

  • p-, m-, px-, py-, pt-, pb-, pl-, pr-
  • mt-, mb-, ml-, mr-, mx-, my-

Colors on containers:

  • bg-muted, bg-primary, bg-secondary, bg-accent
  • text-muted-foreground (on p, span - not headings)

Other:

  • w-, h-, max-w-, min-h-
  • border-*
  • transition-, animate-, duration-*
  • relative, absolute, fixed, sticky

Heading Hierarchy Rules

  1. One H1 per page - Only the main page title uses h1
  2. Sequential order - h1 → h2 → h3 → h4 (no skipping)
  3. Section titles - Use h2 for section headings
  4. Subsections - Use h3 for subsection headings

Fixing Hierarchy

If a section has:

<h1>Section Title</h1>  // Wrong - should be h2
<h3>Feature</h3>         // Wrong - should follow h2

Change to:

<h2>Section Title</h2>  // Correct
<h3>Feature</h3>         // Now correct (follows h2)

Example Cleanup

Before:

<h1 className="text-5xl font-bold tracking-tight leading-tight">
  Page Title
</h1>
<h2 className="text-3xl font-semibold tracking-tight">
  Section Title
</h2>

After:

<h1>Page Title</h1>
<h2>Section Title</h2>

Output

  • Components with clean heading tags
  • Proper heading hierarchy
  • Typography controlled by globals.css