website-design-system
- Repo stars 136
- Author updated Live
- Author repo envilder
- Domain
- Design
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @macalbert · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: website-design-system
description: >- Rules and patterns for the Envilder website's pure CSS design system. The site uses data-them…
category: design
runtime: no special runtime
---
# website-design-system output preview
## PART A: Task fit
- Use case: >- Rules and patterns for the Envilder website's pure CSS design system. The site uses data-theme attribute on <html>. Two themes are supported: | Theme | Selector | Palette | runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to Use / Themes / Rules” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “>- Rules and patterns for the Envilder website's pure CSS design system. The site uses data-theme attribute on <html>. Two themes are supported: | Theme | Selector | Palette | runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “When to Use / Themes / Rules” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “When to Use / Themes / Rules”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: website-design-system
description: >- Rules and patterns for the Envilder website's pure CSS design system. The site uses data-them…
category: design
source: macalbert/envilder
---
# website-design-system
## When to use
- >- Rules and patterns for the Envilder website's pure CSS design system. The site uses data-theme attribute on <html>.…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to Use / Themes / Rules” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "website-design-system" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to Use / Themes / Rules
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Website Design System
Rules and patterns for the Envilder website's pure CSS design system.
When to Use
- Creating new Astro components or page sections
- Adding or modifying CSS (global or scoped)
- Choosing between existing utility classes
- Defining new CSS variables
- Reviewing PRs that touch website styling
Themes
The site uses data-theme attribute on <html>. Two themes are supported:
| Theme | Selector | Palette |
|---|---|---|
| Retro (default) | :root |
Game Boy green |
| Light | [data-theme="light"] |
Warm neutrals |
Rules
- All colors MUST use CSS variables — never hardcode hex values
- New variables MUST be defined in both
:root(retro) and[data-theme="light"]blocks inglobal.css - Never modify the theme switcher mechanism or its localStorage key
/* ✓ Correct */
color: var(--color-text);
background: var(--color-bg);
/* ✗ NEVER */
color: #8bac0f;
background: #1a1a2e;Responsive Breakpoints
Mobile-first approach. Default styles target mobile; expand with min-width.
| Breakpoint | Target | Pattern |
|---|---|---|
| Default | Mobile | Single column, compact spacing |
min-width: 640px |
Tablet | 2-column grids, expanded spacing |
min-width: 1024px |
Desktop | 3-4 column grids, full layout |
Grid Utilities
Use existing grid classes: .grid-2, .grid-3, .grid-4.
Spacing & Layout
Use the spacing scale defined in global.css:
- Variables:
--space-xsthrough--space-4xl - Container max-width:
--max-width(1200px)
Typography
| Use | Font | Access |
|---|---|---|
| Section titles / pixel style | Press Start 2P | Via .pixel-card h3 or custom class |
| Body text | Inter | Default (inherited) |
| Code / terminal | JetBrains Mono | <code>, <pre>, or mono class |
- Use
clamp()for fluid typography - Never use fixed
pxfont sizes
Component Patterns
Reuse existing CSS classes for visual consistency:
| Class | Purpose |
|---|---|
.pixel-card |
Bordered cards with pixel corner notches |
.pixel-icon |
Emoji with pixelated filter |
.pixel-shadow |
4px offset retro shadow |
.badge |
Small label badges |
.pixel-divider |
Section separator |
.scanlines |
CRT overlay effect (use sparingly) |
.section |
Standard section wrapper with vertical padding |
File Locations
| What | Where |
|---|---|
| Global CSS | src/website/src/styles/global.css |
| Components | src/website/src/components/*.astro |
| Layout | src/website/src/layouts/BaseLayout.astro |
Constraints
- DO NOT install CSS frameworks or UI libraries — use existing pure CSS
- DO NOT hardcode colors — always CSS variables from
global.css - DO NOT use fixed pixel font sizes — use
clamp()or relative units - DO NOT break existing responsive layouts when adding new sections
- DO NOT add JavaScript frameworks (React, Vue) — Astro components +
<script>tags only - ONLY add new CSS variables if defined in both theme blocks
Decide Fit First
Design Intent
How To Use It
Boundaries And Review