design-bible

design-bible is a skill for Claude Code from cenconq25/claude-code-app-studio. It costs 62 tokens per session (2,828 once invoked), scanned A, original, MIT.

A guided document that defines an app’s visual rules, including colors, text styles, spacing, shapes, shadows, motion, icons, and launch screens.

In plain words
What is it for?
Use it after the product concept is approved to establish the visual system before user-interface specifications and asset work.
Why use it?
It gives designers and developers one shared visual reference and reduces inconsistent styling across the app.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; names the AskUserQuestion tool.

Good fit Use it after the product concept is approved to establish the visual system before user-interface specifications and asset work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cenconq25/claude-code-app-studio/design-bible
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 cenconq25/claude-code-app-studio --skill design-bible
Clone the repo
git clone --depth 1 https://github.com/cenconq25/claude-code-app-studio

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 design-bible

README.md
[![agentmods](https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/design-bible/github.svg)](https://agentmods.dev/skills/cenconq25/claude-code-app-studio/design-bible)
Your own site
<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/design-bible"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/design-bible/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 design-bible

Your own site · 80×15
<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/design-bible"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/design-bible.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,828 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.00062 $0.02828
Opus 5 $0.00031 $0.01414
Sonnet 5 $0.00012 $0.00566
Haiku 4.5 $0.00006 $0.00283

Measured 5d ago against content hash 005994d69e8f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

design-bible 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 5d 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.

.claude/skills/design-bible/SKILL.md · 315 lines

How it starts

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

Design Bible

The Design Bible is the single source of truth for tokens. Every UX spec, every component, every asset must reference its tokens — no inline color hexes, no inline spacing values. This skill produces that file.

Output: design/design-bible.md


Purpose / When to Run

Run when:

  • design/concept.md is approved and design/design-bible.md does not exist
  • Visual identity needs to be tightened before UX work begins
  • The user wants to refresh the bible after a rebrand

The bible should exist before /map-systems and any /design-system UI section, so PRDs reference real tokens, not placeholders.

Inputs

  • design/concept.md (required)
  • .claude/docs/technical-preferences.md (for platform target — iOS HIG / Material 3 conventions affect token decisions)
  • Optional: existing partial design/design-bible.md

Outputs

  • design/design-bible.md — token definitions and identity
  • Optional: hands a token export task to /asset-spec for icon/splash generation prompts

Phase 1: Context

Read concept.md. Extract Section 6 (Tone & Visual Anchor) and the named reference apps. If concept doc is missing, stop.

Identify platform target from technical-preferences:

  • iOS only → use iOS HIG (Apple Human Interface Guidelines) sizing language
  • Android only → Material 3 sizing language
  • Both / cross-platform → describe both, with one canonical token system that maps to each

Optionally use WebSearch to fetch fresh visual reference for the named comp apps if their tone has shifted.


Phase 2: Skeleton

Write design/design-bible.md skeleton:

# Design Bible — <App Name>

> **Status**: In Design
> **Last Updated**: <date>
> **Platform target**: <iOS / Android / both>

## 1. Identity & Tone
[To be designed]

## 2. Color Tokens
[To be designed]

## 3. Typography Tokens
[To be designed]

## 4. Spacing & Layout
[To be designed]

## 5. Radius
[To be designed]

## 6. Elevation & Shadow
[To be designed]

## 7. Motion
[To be designed]

## 8. Iconography
[To be designed]

## 9. Imagery & Illustration
[To be designed]

## 10. App Icon
[To be designed]

## 11. Splash / Launch
[To be designed]

## 12. Dark Mode
[To be designed]

## 13. Accessibility
[To be designed]

## 14. Token Naming Conventions
[To be designed]

Read the full file on GitHub · 315 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. 5d ago First seen · 315 lines · 62 tokens per session scan A 005994d69e8f

Subscribe to this mod's changes

design-bible is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 2,828 once invoked, about $0.0003 per session on Opus 5. 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-09-03.

Related

Other skills, from other repositories

expo-design-system

Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when…

expo/skills · 181 tokens

display-glasses-with-jetpack-compose-glimmer

Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. This skill covers foundational Glimmer design principles, workflows for implementing Jetpack Compose Glimmer, and interaction models for the glasses form factor. Use this skill to build an…

android/skills · 91 tokens

flutter-build-responsive-layout

Use LayoutBuilder, MediaQuery, or Expanded/Flexible to create a layout that adapts to different screen sizes. Use when you need the UI to look good on both mobile and tablet/desktop form factors.

flutter/agent-plugins · 51 tokens

omh-apple-design

This is a Hermes-native apple-design workflow skill.

rlaope/oh-my-hermes · 73 tokens

axiom-audit-liquid-glass

Use when the user mentions Liquid Glass review, iOS 26 UI updates, toolbar improvements, or visual effect migration.

CharlesWiltgen/Axiom · 32 tokens

axiom-audit-ux-flow

Use when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.

CharlesWiltgen/Axiom · 43 tokens