spec-first-project-setup

spec-first-project-setup is a skill for Claude Code from sauravvarma/garage. It costs 115 tokens per session (4,799 once invoked), scanned A, original, MIT.

A setup guide that creates the documentation, design, and project-rule files needed before other project skills can be used.

In plain words
What is it for?
It helps start a new project or add structure to an existing one by creating specification documents, design folders, and a CLAUDE.md configuration file.
Why use it?
It prevents design, coding, and visual checks from starting without the shared project information they depend on.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md; mentions Claude Code.

Part of the garage plugin — 6 skills, 1 hook shipped together

Good fit It helps start a new project or add structure to an existing one by creating specification documents, design folders, and a CLAUDE.md configuration file.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sauravvarma/garage/spec-first-project-setup
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 sauravvarma/garage --skill spec-first-project-setup
Clone the repo
git clone --depth 1 https://github.com/sauravvarma/garage

Made for: Claude Code.

Or install garage, the plugin that ships this one along with the rest of its 6 skills, 1 hook.

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 spec-first-project-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/sauravvarma/garage/spec-first-project-setup.svg)](https://agentmods.dev/skills/sauravvarma/garage/spec-first-project-setup)
Your own site
<a href="https://agentmods.dev/skills/sauravvarma/garage/spec-first-project-setup"><img src="https://agentmods.dev/badge/skills/sauravvarma/garage/spec-first-project-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 115 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,799 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00115 $0.04799
Opus 5 $0.00057 $0.02400
Sonnet 5 $0.00023 $0.00960
Haiku 4.5 $0.00012 $0.00480

Measured 7d ago against content hash 4dd00e9e4199, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

spec-first-project-setup scanned grade A with 1 finding 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 7d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

**When the user provides a curl:**
skills/spec-first-project-setup/SKILL.md · 246 lines

How it starts

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

Spec-first project setup

Bootstrap the doc structure, design directory, and Claude Code configuration that the global engineering rules depend on. Creates the skeleton — the user fills in the values.

Companion skills

This skill scaffolds the artifacts that four sibling skills depend on. The intended workflow once setup is done:

Skill Stage Reads
/design-explore Discover or challenge design direction All design docs (treats them as living, can challenge)
/design-agent Generate production design variants All design docs (treats them as locked spec)
/code-agent Implement features CLAUDE.md, REPO-CONVENTIONS.md, COMPONENT-SPECS.md ([FEATURE]-IDEAS.md recommended per feature)
/visual-qa Verify rendered code against spec DESIGN-TOKENS.md, DESIGN-LANGUAGE.md, DESIGN-TAXONOMY.md

Each companion skill runs a "spec preflight" check on first invocation and tells the user to run /spec-first-project-setup if its required artifacts are missing.

When to use

  • Starting a new project from scratch.
  • Adding spec structure to an existing project that has none.
  • User asks to "set up docs", "scaffold specs", or "create project structure".

What it creates

docs/
├── BRIEF-AND-DIRECTION.md
├── DESIGN-LANGUAGE.md
├── DESIGN-TOKENS.md
├── COMPONENT-SPECS.md
├── DESIGN-TAXONOMY.md
├── REPO-CONVENTIONS.md       # Routing, parsing, state management, analytics patterns
├── [FEATURE]-IDEAS.md        # One per feature/page
└── mocks/                    # API response fixtures (optional)
    └── [endpoint-name].json
design/
└── .gitkeep
CLAUDE.md                      # Project-level Claude Code configuration
.claude/
└── rules/                     # Project-specific rules (if applicable)
    └── design-code-sync.md    # Only for projects with design artifacts

Templates

All file templates live in assets/templates/. Each "Create" step below copies a template into place, substituting placeholders (project name, feature name, design tool, file paths). Templates use [BRACKETS] for substitutions and <!-- HTML comments --> for guidance the user fills in later.

Read the full file on GitHub · 246 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. 7d ago First seen · 246 lines · 115 tokens per session scan A 4dd00e9e4199

Subscribe to this mod's changes

spec-first-project-setup is a skill published in the GitHub repository sauravvarma/garage (3 stars, last pushed 1mo ago), licensed MIT. It adds 115 tokens to every session and 4,799 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

designlang-tokens

Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.

Manavarya09/design-extract · 30 tokens

stakeholder-brief

Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…

murphytrueman/design-system-ops · 73 tokens

token-audit

Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…

murphytrueman/design-system-ops · 93 tokens

figma-variable-audit

Audit Figma variable collections against token architecture best practices. Trigger when someone says: audit my Figma variables, check my Figma tokens, are my variables structured correctly, Figma variable health, review my variable collections, variable naming check, or anything about auditing the quality or…

murphytrueman/design-system-ops · 67 tokens

governance-encoder

Convert governance policies into machine-executable JSON constraint files that AI agents and CI pipelines validate against automatically. This produces rule engine files in .ai/governance/, NOT narrative decision records or documentation. Trigger when someone says: encode governance rules, governance as code, automate…

murphytrueman/design-system-ops · 116 tokens

cicd-integration

Generate CI/CD pipeline configurations that automate design system quality checks — token validation, component linting, visual regression, accessibility scanning, and release gating. Produces ready-to-use pipeline files for GitHub Actions, GitLab CI, CircleCI, or Bitbucket Pipelines, configured to enforce the…

murphytrueman/design-system-ops · 177 tokens