create-design-system-rules
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.
Install with Tessl CLI
npx tessl i github:figma/mcp-server-guide --skill create-design-system-rules79
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent trigger term coverage and clear completeness. The explicit 'Use when' clause with multiple natural phrases makes it easy for Claude to select appropriately. The main weakness is that the capabilities could be more specific about what types of rules are generated.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (design system rules) and the action (generates custom rules for codebase), but lacks comprehensive detail about what specific rules are generated or what the output looks like. | 2 / 3 |
Completeness | Clearly answers both what (generates custom design system rules for codebase) and when (explicit 'Use when' clause with multiple trigger phrases). Also includes a helpful prerequisite about Figma MCP server connection. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases: 'create design system rules', 'generate rules for my project', 'set up design rules', 'customize design system guidelines', plus mentions Figma-to-code workflows which users would naturally reference. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific niche: design system rules + Figma-to-code workflows + MCP server requirement. Unlikely to conflict with generic code generation or design skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent actionable guidance with clear workflows and concrete examples for generating design system rules across multiple AI agents. However, it suffers significantly from verbosity - explaining concepts Claude already understands, providing excessive context, and including sections that could be condensed or moved to reference files. The core value is buried under unnecessary explanation.
Suggestions
Remove the 'What Are Design System Rules?' and 'Understanding Design System Rules' sections entirely - Claude understands these concepts
Consolidate the three detailed examples into a single representative example, moving others to a separate EXAMPLES.md file
Remove explanatory prose like 'the kind of expertise that experienced developers know' and 'The time invested in creating good rules pays off exponentially' - focus on instructions only
Move the 'Rule Categories and Examples' section to a separate RULE_TEMPLATES.md file and reference it from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400 lines, explaining concepts Claude already knows (what design system rules are, why they matter, basic workflow concepts). Sections like 'What Are Design System Rules?' and 'Understanding Design System Rules' are unnecessary padding that explain obvious concepts. | 1 / 3 |
Actionability | Despite verbosity, the skill provides highly actionable guidance with specific tool calls, concrete code examples, exact file paths for different agents, and copy-paste ready rule templates. The workflow steps are executable and the examples show complete implementations. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with explicit validation in Step 5. Each step has clear actions, the Figma MCP Integration Rules include a 'Required Flow (do not skip)' section with validation checkpoints, and the troubleshooting section addresses common failure modes. | 3 / 3 |
Progressive Disclosure | While the skill has good section organization with headers, it's largely monolithic with extensive inline content that could be split into separate files (e.g., rule templates, agent-specific configurations, examples). The external links at the end are appropriate but the main content is too dense. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (542 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata.version' is missing | Warning |
Total | 9 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.