design-rules — for Claude Code design-rules, claude-kit, community, for Claude Code, ide skills, design spec automation, spec quality evaluation, design checklist verification, phase-driven loading, ai coding standards

v1.0.0
GitHub

About this Skill

Perfect for AI Coding Agents needing structured design specifications and streamlined development processes. design-rules is a skill that establishes guidelines for AI coding agents to produce high-quality design specs, ensuring efficient development and reducing errors.

Features

Load design rules at startup using /designer command
Apply phase-driven loading for efficient spec development
Evaluate approach criteria using Spec Quality guidelines
Verify design specs with Design Checklist for self-verification
Ensure user gate verification before presenting designs

# Core Topics

for Claude Code design spec automation spec quality evaluation design checklist verification phase-driven loading ai coding standards
hex0xdeadbeef hex0xdeadbeef
[25]
[0]
Updated: 3/29/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
8/11
Quality Score
49
Canonical Locale
en
Detected Body Locale
en

Perfect for AI Coding Agents needing structured design specifications and streamlined development processes. design-rules is a skill that establishes guidelines for AI coding agents to produce high-quality design specs, ensuring efficient development and reducing errors.

Core Value

Empowers agents to produce high-quality design specs by following phase-driven guidelines, utilizing spec quality criteria, and avoiding anti-patterns, all while ensuring verifiable acceptance criteria and explicit risk mitigation using protocols like phase-driven loading and self-verification checklists.

Ideal Agent Persona

Perfect for AI Coding Agents needing structured design specifications and streamlined development processes.

↓ Capabilities Granted for design-rules

Automating design spec generation with phase-driven loading
Generating verifiable acceptance criteria for design specs
Debugging design specs using anti-pattern identification and spec quality criteria

! Prerequisites & Limits

  • Requires /designer command integration
  • Limited to design spec generation and review processes

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is design-rules?

Perfect for AI Coding Agents needing structured design specifications and streamlined development processes. design-rules is a skill that establishes guidelines for AI coding agents to produce high-quality design specs, ensuring efficient development and reducing errors.

How do I install design-rules?

Run the command: npx killer-skills add hex0xdeadbeef/claude-kit/design-rules. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for design-rules?

Key use cases include: Automating design spec generation with phase-driven loading, Generating verifiable acceptance criteria for design specs, Debugging design specs using anti-pattern identification and spec quality criteria.

Which IDEs are compatible with design-rules?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for design-rules?

Requires /designer command integration. Limited to design spec generation and review processes.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add hex0xdeadbeef/claude-kit/design-rules. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use design-rules immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

design-rules

Install design-rules, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Design Rules

Purpose

Guidelines for the /designer command to produce high-quality design specs that reduce plan-review iterations.

Instructions

Step 1: Load at /designer startup

Read this SKILL.md for overview. Supporting files loaded on-demand per phase.

Step 2: Use phase-driven loading

  • Phase 3 (PROPOSE) → read Spec Quality for approach evaluation criteria
  • Phase 4 (WRITE SPEC) → read Design Checklist for self-verification
  • Phase 5 (USER GATE) → verify checklist before presenting to user

Spec Quality Criteria

CriterionRequiredCheck
Context describes current stateYesNot just "add X" but "currently Y exists, need X because Z"
Scope has IN and OUTYesOUT items have explicit reasons
At least 2 approaches comparedYesWith pros/cons for each
Selected approach has rationaleYesReferences constraints from requirements
Key decisions are numberedYesEach has rationale and impact
Risks have severity and mitigationYesHIGH risks must have concrete mitigation
Acceptance criteria are verifiableYesEach can be checked as pass/fail

Anti-Patterns

Anti-PatternWhy BadFix
"The obvious approach is..."Skips exploration, may miss better optionsAlways compare at least 2
Spec without OUT scopeScope creep during planningExplicitly list what's excluded
Vague acceptance criteria ("works well")Can't verifyMake criteria concrete and testable
No risks identifiedEvery design has risksIdentify at least 1 per approach
Copying task description as contextNo analysisDescribe current state, not just goal

Common Issues

Designer skips CLARIFY phase

Cause: Task seems clear. Fix: Even "clear" tasks benefit from scope IN/OUT confirmation. At minimum, confirm scope.

User rejects all approaches

Cause: Missing constraint not captured. Fix: Ask: "What constraint am I missing?" — don't generate more approaches without new information.

References

Related Skills

Looking for an alternative to design-rules or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer