Agent skill

CSS Architecture Skill: BEM, SMACSS and CSS-in-JS

The css-architecture skill gives an AI coding agent BEM naming, SMACSS, styled components, CSS variables and a utility-first pattern for organizing large stylesheets.

Install
git clone https://github.com/aj-geddes/useful-ai-prompts.git
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the css-architecture skill?

The css-architecture skill is a SKILL.md folder inside aj-geddes/useful-ai-prompts. It teaches an AI coding agent to organize CSS with BEM, SMACSS and CSS-in-JS, and points to reference guides for CSS variables and a utility-first Tailwind pattern. It also ships one TSX component template.

The css-architecture skill is one folder in aj-geddes/useful-ai-prompts, a library of AI prompts and agent skills. Its SKILL.md is short. It names the methods, shows a BEM button, and hands the detail to five reference guides.

The frontmatter describes it as organizing CSS with BEM, SMACSS and CSS-in-JS patterns, for scalable, maintainable styling systems with proper naming conventions. Its guides span plain CSS, styled components and Tailwind style utilities.

What your agent gets to work from

  • A Quick Start in plain CSS: a .button block, a .button__icon element and a .button--primary modifier with its own hover color.
  • Five reference guides: BEM, SMACSS, CSS-in-JS with styled components, CSS custom properties and a utility-first Tailwind pattern.
  • A templates/component-template.tsx file as a starting point for a component.
  • A When to Use list: large stylesheets, component-based styling, design systems and multi-team work.

How the BEM example is laid out

In the Quick Start, the block is the standalone component, the element is a part of it, and the modifier is a variant. That gives class names such as .button, .button__icon and .button--primary, each tied to a single role in the component.

Who the css-architecture skill is for

Best for

  • Teams that share a stylesheet and need one naming convention, since multiple team collaboration is a listed use case.
  • Design system work where components need consistent class names. Pair it with the uiux-design-system skill for the system layer.
  • Projects changing approach, for example from CSS modules to utility classes, which converting CSS modules to Tailwind covers as its own job.

Not for

  • Anyone who wants strict, opinionated rules. The main file's best practices are general: follow established patterns, add documentation and test before deploying.
  • Choosing colors, type or layout. It organizes code and does not set a visual direction. For responsive layout, see frontend responsive UI.
  • Linting or enforcement. The skill folder holds references and one template, with no scripts or checkers.

Use it with UiChemy

Composer, UiChemy's AI visual editor, writes real HTML, CSS and JS inside Elementor or Gutenberg, so a clear class naming scheme makes that code easier to review. Click Get Started on uichemy.com.