gsp-design-system

gsp-design-system is a skill for Claude Code from jubscodes/get-shit-pretty. It costs 0 tokens per session (1,616 once invoked), scanned A, original, MIT.

A codebase audit that finds and documents the existing design system, including its technology stack, components, design tokens, conventions, and known concerns.

In plain words
What is it for?
Use it to inventory an existing interface and create Markdown files describing how its visual system and components are organised.
Why use it?
It removes the need to manually search the codebase before changing or extending its interface. The shared documentation can be regenerated when the codebase changes.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: names the AskUserQuestion tool.

Good fit Use it to inventory an existing interface and create Markdown files describing how its visual system and components are organised.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jubscodes/get-shit-pretty/gsp-design-system
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jubscodes/get-shit-pretty --skill gsp-design-system
Clone the repo
git clone --depth 1 https://github.com/jubscodes/get-shit-pretty

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for gsp-design-system

README.md
[![agentmods](https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-design-system/github.svg)](https://agentmods.dev/skills/jubscodes/get-shit-pretty/gsp-design-system)
Your own site
<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gsp-design-system"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-design-system/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for gsp-design-system

Your own site · 80×15
<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gsp-design-system"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-design-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,616 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01616
Opus 5.5 $0.00000 $0.00646
Sonnet 5.5 $0.00000 $0.00323
Haiku 4.5 $0.00000 $0.00162

Measured 1mo ago against content hash 5dd10ba94e8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gsp-design-system scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

gsp/skills/gsp-design-system/SKILL.md · 159 lines

How it starts

The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Works two ways:

  1. Standalone — user runs /gsp-design-system for a quick workspace audit
  2. Building block — /gsp-start invokes this in the background during project setup

Output is workspace-level (not project-scoped), so it's shared across all projects and only needs to run once per codebase state change. Re-runnable — overwrites previous output.

Output: .design/system/{STACK,COMPONENTS,TOKENS,CONVENTIONS,CONCERNS}.md

<execution_context> @${CLAUDE_SKILL_DIR}/../../templates/system/STACK.md @${CLAUDE_SKILL_DIR}/../../templates/system/COMPONENTS.md @${CLAUDE_SKILL_DIR}/../../templates/system/TOKENS.md @${CLAUDE_SKILL_DIR}/../../templates/system/CONVENTIONS.md @${CLAUDE_SKILL_DIR}/../../templates/system/CONCERNS.md </execution_context>

mkdir -p .design/system

Step 1: Detect tech stack (→ STACK.md)

  1. Detect package manager & lockfile

    • Look for package.json, bun.lockb, pnpm-lock.yaml, yarn.lock, package-lock.json
  2. Read package.json

    • Framework, dependencies, devDependencies, scripts
  3. Detect config files

    • tsconfig.json / jsconfig.json — language, aliases
    • tailwind.config.* — styling, custom theme
    • next.config.* — Next.js
    • vite.config.* — Vite
    • app.json / expo.json — React Native / Expo
    • postcss.config.*, .eslintrc.*, .prettierrc.*
  4. Identify styling approach

    • Tailwind, CSS Modules, styled-components, StyleSheet, vanilla CSS
  5. Identify architecture patterns

    • Component style (functional, forwardRef, compound)
    • State management (Context, Zustand, Redux, Jotai)
    • Data fetching (Server Components, React Query, SWR)
    • Routing (App Router, Pages Router, Expo Router, React Router)
    • File organization (feature-based, type-based, flat)

Read the full file on GitHub · 159 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 159 lines · 0 tokens per session scan A 5dd10ba94e8e

Subscribe to this mod's changes

gsp-design-system is a skill published in the GitHub repository jubscodes/get-shit-pretty (55 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,616 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.