styled-components

styled-components is a skill for Claude Code, Codex from 12-Studio/Tackl. It costs 47 tokens per session (723 once invoked), scanned A, original, MIT.

A project-specific guide for styling React components with styled-components, a library that defines component styles in JavaScript or TypeScript, using the Tackl design system.

In plain words
What is it for?
Use it when creating or changing React component styles, responsive layouts, typography, theme tokens, or Tackl-based UI components.
Why use it?
It keeps styling in the expected files and applies the project's shared colors, typography, spacing, responsive breakpoints, and component primitives consistently.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/12-studio/tackl/styled-components
Any agent
npx skills add 12-Studio/Tackl --skill styled-components
Clone the repo
git clone --depth 1 https://github.com/12-Studio/Tackl

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 styled-components

README.md
[![agentmods](https://agentmods.dev/badge/skills/12-studio/tackl/styled-components.svg)](https://agentmods.dev/skills/12-studio/tackl/styled-components)
Your own site
<a href="https://agentmods.dev/skills/12-studio/tackl/styled-components"><img src="https://agentmods.dev/badge/skills/12-studio/tackl/styled-components.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 723 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00047 $0.00723
Opus 5 $0.00023 $0.00362
Sonnet 5 $0.00009 $0.00145
Haiku 4.5 $0.00005 $0.00072

Measured 3d ago against content hash ec26d951a60b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

styled-components 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 3d 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/styling/styled-components/SKILL.md · 95 lines

How it starts

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

Styled Components (Tackl)

File structure

Every component folder:

ComponentName/
  index.tsx       # Logic + JSX only — no styled definitions
  styles.ts       # All styled-components
  interface.ts  # Props types

Import styles as a namespace:

import * as S from './styles';

const Hero = (props: HeroProps) => <S.Jacket {...props}>...</S.Jacket>;

Rules

  1. Never put styled-components in index.tsx.
  2. Never use Tailwind, CSS modules, inline styles, or SASS for component styling.
  3. Use Tackl primitives from @theme/tackl (Section, Header, Div, etc.) as styled bases.
  4. Use Tackl type styles from @tackl/type for typography (headlineL, bodyL, captionS).
  5. Use theme helpers: getBrand, getGlobal, getRadius, getEase, getFont, getFontWeight.
  6. Mobile-first responsive styles via bp.l / bp.m / bp.s from @theme/tackl.
  7. Pass styling props with $ prefix (transient props) to avoid DOM leakage.

styles.ts template

// Imports
// ------------
import { Section } from '@tackl';
import {} from '@tackl/type';
import styled, { css } from 'styled-components';
import { getBrand } from '@theme/tackl';

// Interfaces
// ------------
interface StylesInterface {
	$isActive?: boolean;
}

// Exports
// ------------
export const Jacket = styled(Section)<StylesInterface>(
	props => css`
		display: flex;
		padding: 1rem;
		background: ${getBrand('c1')};
		opacity: ${props.$isActive ? 1 : 0.6};
	`
);

Naming

Use descriptive layout names — not generic wrappers:

  • Jacket — outermost container
  • Wrapper — inner layout shell
  • Content — text/media area
  • Coat — overlay or secondary layer

Theme access

Global theme lives in src/theme/index.ts. Access in styled-components via props.theme or Tackl getters.

ThemeProvider wraps the app in app/(site)/Client.tsx. GlobalStyle is applied there.

SSR

StyledComponentsRegistry in src/utils/registry.jsx handles SSR style collection. Client components using styled-components must render inside this registry (already wired in Client.tsx).

Read the full file on GitHub · 95 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. 3d ago First seen · 95 lines · 47 tokens per session scan A ec26d951a60b

Subscribe to this mod's changes

styled-components is a skill published in the GitHub repository 12-Studio/Tackl (10 stars, last pushed 7d ago), licensed MIT. It adds 47 tokens to every session and 723 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

nextjs-shadcn

Creates Next.js frontends with shadcn/ui. Use when building React UIs, components, pages, or applications with shadcn, Tailwind, or modern frontend patterns. Also use when the user asks to create a new Next.js project, add UI components, style pages, or build any web interface — even if they don't mention shadcn…

laguagu/claude-code-nextjs-skills · 80 tokens

igniteui-react-customize-theme

This skill customizes Ignite UI for React component styling using CSS custom properties and the full theming system and should be used when applying brand colors, dark mode, component-level overrides, or scoped themes in a React application.

IgniteUI/igniteui-react · 50 tokens

nextjs-nextra-starter-distill-zh

蒸馏并应用当前仓库的 Next.js Nextra 启动模板架构、已实现功能、二次开发扩展点与迁移模式。适用于理解本项目、继续二次开发、修改 docs/landing/i18n/theme/auth/UI 行为,或把这些 Next.js 16 + Nextra 4 + Tailwind CSS 4 模式复用到其他项目。.

pdsuwwz/nextjs-nextra-starter · 97 tokens

frontend-development

Next.js frontend app development patterns with App Router, Tailwind CSS v4, Zustand, and TanStack Query. Use when creating pages, components, or API routes in the frontend app.

Ampli-Group/agentic-mobile-blueprint · 41 tokens

react-doctor

Use when finishing a feature, fixing a bug, before committing React code, or when the user types /doctor, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canonical playbook.

darkroomengineering/satus · 70 tokens

frontend-code-review

Review React, Next.js App Router, TypeScript, Tailwind CSS, shadcn/ui, TanStack Query, and frontend UI code. Use when reviewing a PR, branch, diff, page, component, hook, Server Action, route handler, or API client; debugging frontend behavior; assessing production readiness; or checking runtime bugs, client/server…

DNM03/frontend-code-review · 102 tokens