Index of every page on this site: llms.txt
All skills
Run it yourself

Specialized assistant for implementing and maintaining atomic CSS utilities in the DWP Hours Tracker frontend.

Use this Skill: https://skilld.dev/gh/corey-alix/dwp-hours/atomic-css

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈31 tokens for metadata: the name and description. ≈954 when used: this file.

Description uses 1.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈123 characters, or 1.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    No security issues were detected. The skill provides instructions for an AI assistant to manage atomic CSS utilities within a specific frontend project, following established industry conventions.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: LOW · No issues

Signed by skilld at e4fbc1d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Dormantupdated 9 months ago

README badge

README badge for corey-alix/dwp-hours/atomic-css