prompts.chatprompts.chatprompts.chat
BotsPromptsSkillsWorkflowsCategoriesTagsPromptmastersTaste
BookFor KidsDevelopers
Login
CC0 2026 prompts.chat
DeepWikiHow to...DocsAPIPrivacyTermsSupportAboutGitHub

Maintenance Prompt for Design System

Use this prompt periodically (monthly, or after major feature additions) to keep the CLAUDE.md in sync with the actual codebase. It performs a diff between the documented design system and the current code, flagging drift.

N
@gokbeyinac
8 months agoMarch 13, 2026 at 06:32 AM
Design•DesignUI/UX
1

Content

Variables
You are a design system auditor performing a sync check. Compare the current CLAUDE.md design system documentation against the actual codebase and produce a drift report. ## Inputs - **CLAUDE.md:** - **Current codebase:** ## Check For: 1. **New undocumented tokens** - Color values in code not in CLAUDE.md - Spacing values used but not defined - New font sizes or weights 2. **Deprecated tokens still in code** - Tokens documented as deprecated but still used - Count of remaining usages per deprecated token 3. **New undocumented components** - Components created after last CLAUDE.md update - Missing from component library section 4. **Modified components** - Props changed (added/removed/renamed) - New variants not documented - Visual changes (different tokens consumed) 5. **Broken references** - CLAUDE.md references tokens that no longer exist - File paths that have changed - Import paths that are outdated 6. **Convention violations** - Code that breaks CLAUDE.md rules (inline colors, missing focus states, etc.) - Count and location of each violation type ## Output A markdown report with: - **Summary stats:** X new tokens, Y deprecated, Z modified components - **Action items** prioritized by severity (breaking → inconsistent → cosmetic) - **Updated CLAUDE.md sections** ready to copy-paste (only the changed parts)

Related Prompts

Design System Extraction Prompt Kit

Text

This prompt instructs Claude to crawl the entire codebase and extract every design-related token, pattern, and component into a raw inventory. It produces a structured JSON audit, not a design system yet, just the raw material. Run this first before any organization or documentation happens. When to use: At the very start, when you have a working codebase but no documented design system.

N@gokbeyinac
2

Component Documentation

Text

Generates detailed documentation for each component in the design system. This is not just a props table — it includes usage guidelines, do/don't examples, accessibility requirements, and the specific tokens each component consumes. The output becomes the component section of the CLAUDE.md.

Comments (0)

N@gokbeyinac
0

CLAUDE.md Assembly

Text

This is the final assembly prompt. It takes all outputs from Phases 1-3 and compiles them into a single, production-ready CLAUDE.md file. The file is structured so that AI assistants can parse it efficiently — with explicit rules, token tables, component specs, and a "Quick Reference" section for the most commonly needed information.

N@gokbeyinac
0

Create STYLE_GUIDE.md

Text

This prompt assists users in creating a comprehensive STYLE_GUIDE.md for their projects. It covers essential sections such as color palette, typography, spacing, and more, ensuring a detailed and consistent style system. Users can also include example component design references.

I@ilker
4