---
name: atomic-css
description: Specialized assistant for implementing and maintaining atomic CSS utilities in the DWP Hours Tracker frontend.
title: atomic-css
canonical_url: https://skilld.dev/gh/corey-alix/dwp-hours/atomic-css
last_updated: 2026-10-07T01:30:59.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install corey-alix/dwp-hours/atomic-css`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/atomic-css`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/corey-alix/dwp-hours/atomic-css) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/atomic-css`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/atomic-css --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/atomic-css --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Atomic CSS

## Description

Specialized assistant for implementing and maintaining atomic CSS utilities in the DWP Hours Tracker frontend, following Tailwind-like conventions with token-based CSS custom properties for maintainable, consistent styling.

## Naming Conventions

When creating new atomic CSS utilities, follow the Tailwind CSS naming conventions as documented at https://tailwind.build/classes. Key patterns include:

- **Layout**:
  - Display: `block`, `inline`, `flex`, `grid`, `hidden`
  - Position: `static`, `relative`, `absolute`, `fixed`
  - Flexbox: `flex`, `flex-row`, `flex-col`, `justify-start`, `justify-center`, `justify-end`, `justify-between`, `items-start`, `items-center`, `items-end`, `flex-1`, `flex-auto`
  - Grid: `grid`, `grid-cols-1` to `grid-cols-12`, `grid-rows-*`, `gap-0` to `gap-16`, `col-span-*`, `row-span-*`

- **Spacing**:
  - Padding: `p-0` to `p-16` for all sides, `px-*`/`py-*` for horizontal/vertical, `pt-*`/`pr-*`/`pb-*`/`pl-*` for individual sides
  - Margin: Same pattern as padding with `m-*`, `mx-*`, `my-*`, `mt-*`, `mr-*`, `mb-*`, `ml-*`

- **Colors**: `bg-*`, `text-*`, `border-*` using token-based names like `bg-color-surface`, `text-color-on-surface`, `border-color-outline`

- **Typography**:
  - Text size: `text-xs`, `text-sm`, `text-base`, `text-lg`, `text-xl` up to `text-9xl`
  - Font weight: `font-thin`, `font-light`, `font-normal`, `font-medium`, `font-semibold`, `font-bold`, `font-extrabold`, `font-black`
  - Line height: `leading-none`, `leading-tight`, `leading-snug`, `leading-normal`, `leading-relaxed`, `leading-loose`
  - Text alignment: `text-left`, `text-center`, `text-right`, `text-justify`

- **Borders**: `border`, `border-*` (width), `border-t`, `border-r`, `border-b`, `border-l`, `rounded`, `rounded-*` (sm, md, lg, xl, full), `border-solid`, `border-dashed`, `border-dotted`

- **Effects**: `shadow`, `shadow-sm`, `shadow-md`, `shadow-lg`, `shadow-xl`, `opacity-0` to `opacity-100`

Use kebab-case for multi-word tokens and maintain consistency with existing utilities.

## Trigger

Activate when users need to:

- Create new atomic CSS utility classes (background, border, padding, margin, etc.)
- Apply Tailwind-like styling to web components
- Integrate token-based colors and spacing from tokens.css
- Maintain and extend the atomic.css file
- Style components with utility-first approach

## Response Pattern

1. Analyze the styling requirement and identify which utilities are needed (background, border, padding, etc.)
2. Check existing utilities in client/atomic.css to avoid duplication
3. Define new utilities using CSS custom properties (--color-_, --space-_, etc.) from tokens.css
4. Follow the naming conventions outlined in the Naming Conventions section (e.g., bg-color-surface, p-4, rounded-lg)
5. Apply utilities to HTML elements using class attributes in index.html
6. Test styling in browser and ensure responsiveness and accessibility
7. Update documentation if new patterns are established

## Examples

- "Add background color utility for surface using tokens"
- "Create padding utility classes for card spacing"
- "Style the PTO employee info card with Tailwind-like classes"
- "Implement border radius utilities for components"
- "Add margin utilities for layout spacing"

## Additional Context

- Integrates with tokens.css for consistent theming and design system compliance
- Utilities follow Tailwind CSS naming conventions for familiarity
- Works alongside web-components-assistant for component-specific styling
- Maintains atomic design principles: single-purpose, reusable classes
- Supports responsive design through utility combinations
- Located in client/atomic.css file</content>
  <parameter name="filePath">/home/ca0v/code/corey-alix/dwp-hours/mars/.github/skills/atomic-css/SKILL.md
