OpenSkillIndex← back to search
claude-codedevelopment

Claude-skill-registry describe-laws-and-style

Distinction between laws (invariants) and style (conventions). Load when determining if a constraint is a law or style.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/describe-laws-and-style" ~/.claude/skills/majiayu000-claude-skill-registry-describe-laws-and-style && rm -rf "$T"
manifest: skills/data/describe-laws-and-style/SKILL.md
tags
#law-detection#style-detection#constraint-analysis#code-quality#software-design
source content

Laws vs Style

Laws (

.ushabti/laws.md
):

  • Non-negotiable invariants that must hold across all Phases, implementations, and refactors
  • Examples: architectural boundaries, security constraints, correctness guarantees
  • Laws are absolute — any violation fails a Phase
  • Only Lawgiver defines or modifies laws

Style (

.ushabti/style.md
):

  • Conventions that govern how the system is built
  • Examples: directory layout, naming conventions, testing strategy, error handling
  • Style may evolve over time; laws should not
  • Only Artisan defines or modifies style
  • Style must never contradict laws