Scss Standards logo

Scss Standards

Community
c-kick
scss-standards

SCSS and CSS architecture standards. Apply when working with CSS, SCSS, styling architecture, component styles, tokens, or compiled stylesheet organization.

Overview

Publisherc-kick
Repositoryhnl-agent-skills
Skill namescss-standards
Stars
56
Forks
4
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by c-kick on GitHub. Read the source before you install it.

Installation

Install the Scss Standards AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/c-kick/hnl-agent-skills/tree/master/scss-standards
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/c-kick/hnl-agent-skills.git /tmp/hnl-agent-skills
mkdir -p .claude/skills
cp -r /tmp/hnl-agent-skills/scss-standards .claude/skills/scss-standards
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Scss Standards in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Scss Standards on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Scss Standards is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

SCSS Standards & CSS Architecture

Apply when working with CSS, SCSS, or styling in this project.

Architecture Overview

A well-structured SCSS project separates concerns into entry points, components, tools, and tokens. Adapt the structure below to match the project's naming conventions.

Main entry points (compiled via bundler):

FileOutputPurpose
assets/css/components.scsscomponents.cssFrontend styles
assets/css/backend.scssbackend.cssAdmin/editor styles

Recommended directory structure:

assets/css/
├── components/          # BEM components (_*.scss)
├── tools/               # Mixins, utilities, RFS
├── libs/                # Third-party styles
├── _variables.scss      # Design tokens, breakpoints
├── _colors.scss         # Color system
├── _helpers.scss        # Utility classes (loaded last)
└── _reboot.scss         # CSS reset / normalization

Build Commands

bash
# Main build (via bundler)
npm run build

# Compile individual standalone SCSS files (sass CLI)
npx sass path/to/{name}.scss path/to/{name}.css

# Minified version
npx sass path/to/{name}.scss path/to/{name}.min.css --style=compressed

Standalone Component CSS (Lazy-loaded)

Components with custom styles can have co-located SCSS files that compile separately from the main bundle:

  • These are not in the bundler — compile manually with npx sass
  • The template system should load these CSS files on demand when the component is rendered

Module System

Use @use with namespacing (not deprecated @import):

scss
@use "shared" as components-base;
@use "../tools/mixins" as mixins;

// Access via namespace
@include components-base.transition-properties { ... }
@include mixins.media-breakpoint-down(md) { ... }

Exception: Helper/utility files may use @import in the main entry point to ensure they cascade last for utility overrides.

Performance Patterns

Expensive Properties to Avoid Animating

  • backdrop-filter — GPU recomposite every frame
  • box-shadow — triggers repaint

Preferred Pattern: Opacity on Pseudo-element

scss
// BAD: Animating backdrop-filter
transition: backdrop-filter 300ms ease;

// GOOD: Static filter, animate opacity
&::before {
  content: '';
  position: absolute;
  inset: 0;
  backdrop-filter: blur(5px);
  opacity: 0;
  transition: opacity 300ms ease;
}
&.active::before {
  opacity: 1;
}

Color System

Use CSS custom properties for the color system. OKLCH is recommended for perceptual uniformity:

scss
// Colors exposed as CSS custom properties
--color-primary, --color-secondary, --color-accent, etc.

// With variants
--color-primary--darker, --color-primary--lighter

// Alpha control via CSS variable
--bg-alpha-value: 0.5;

Common Mixins

Provide project mixins for responsive breakpoints, typography, and component patterns:

scss
@include mixins.media-breakpoint-down(md) { }
@include mixins.media-breakpoint-up(lg) { }
@include mixins.border-radius('large', 'bottom');
@include mixins.transition-properties { }
@include mixins.text-font;
@include mixins.heading-font;

Breakpoints

scss
$grid-breakpoints: (
  xs: 0,
  sm: 576px,
  md: 768px,
  lg: 992px,
  xl: 1200px,
  xxl: 1400px,
  xxxl: 1600px
);

Frequently asked questions

What does the Scss Standards AI skill do?

SCSS and CSS architecture standards. Apply when working with CSS, SCSS, styling architecture, component styles, tokens, or compiled stylesheet organization.

Why use Scss Standards on TypingMind?

Because you install it once and use it with any model. Scss Standards is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Scss Standards in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/c-kick/hnl-agent-skills/tree/master/scss-standards. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Scss Standards?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Scss Standards?

As many as you like. As long as a model supports skills, you can use Scss Standards with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Scss Standards AI skill free?

It is published on GitHub by c-kick. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇