Skip to content
cccskills
FreePublished on GitHub

consistency-check

Cross-document consistency check: detects GDD entities with conflicting stats, values, or formulas.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3 stars(GitHub 3 + cccskills 0)

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Consistency Check

Detects cross-document inconsistencies by comparing GDDs against entity registry (design/registry/entities.yaml). Grep-first: read registry once, then grep only matching names — no full document reads.

Run: after each new GDD, and before /architecture-decision. Output: conflict report + optional registry corrections.

Arguments

ModeBehavior
full / no argAll registered entries vs all GDDs
since-last-reviewOnly GDDs modified since last review report
entity:<name>One entity across all GDDs
item:<name>One item across all GDDs

Phase 1: Load Registry

Read design/registry/entities.yaml. Empty/missing → stop ("Run /design-system to populate"). Build lookup tables: entity_map, item_map, formula_map, constant_map.

Phase 2: Locate GDDs

Glob design/gdd/*.md (exclude game-concept, systems-index, game-pillars). For since-last-review: git log to find GDDs modified since last gdd-cross-review-*.md.

Phase 3: Grep-First Conflict Scan

For each registered entry, grep all in-scope GDDs for the name (-C 3 context). Extract values near the name and compare against registry.

ScanExtractCompare
EntityNumeric/categorical attributes, derived valuesRegistry attribute values
ItemSell price, weight, stack rules, categoryRegistry item values
FormulaVariable names, output range/capsRegistry formula vars + range
ConstantNumeric values near nameRegistry value

Classification: CONFLICT (different values), NOTE (mentioned but unverifiable).

Phase 4: Deep Investigation (conflicts only)

Full-section read of conflicting GDD. Determine: which GDD is correct (source field = authoritative owner), is registry stale (source GDD updated after registry), is this intentional design change?

Categories: 🔴 CONFLICT (different values, must resolve), ⚠️ STALE REGISTRY (source changed but registry not updated), ℹ️ UNVERIFIABLE (no comparable attribute stated).

Phase 5: Report

Registry entries checked + GDDs scanned + conflicts (entry/attribute/values/resolution needed) + stale entries (registry vs source GDD) + unverifiable references + clean entries count.

Verdict: PASS (no conflicts) or CONFLICTS FOUND (list resolution steps).

Phase 6: Registry Corrections

Stale entries → ask to update registry (update value, set revised date, comment old value). New entries in GDDs not in registry → ask to add (only if appears in 2+ GDDs). Never delete — set status: deprecated.

If 🔴 conflicts found → append to docs/consistency-failures.md (if exists): date, domain, docs involved, what happened, resolution, pattern/lesson.

Protocol

  • PASS → proceed to /architecture-decision
  • CONFLICTS FOUND → fix GDDs, re-run to confirm
  • Source GDD (per source: field) is authoritative owner
  • Run after each new GDD to catch issues early

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Plan, design, and implement A/B tests and experiments with statistical rigor. Covers hypothesis frameworks, sample sizing, metrics, and result analysis.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Web/mobile accessibility decision guide: WCAG 2.2 AA, ARIA, keyboard nav, focus management, contrast, testing. Use for: a11y, accessibility, wcag, aria, screen reader, keyboard, contrast.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Generate, iterate, and scale ad creative for paid advertising across Google, Meta, LinkedIn, and X. Covers platform specs, creative frameworks, and quality validation.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Musica interactiva para juegos: layering vertical, re-secuenciacion horizontal, stingers, reglas de transicion con sync points, y mapeo de estados de gameplay a musica. Usar para: musica adaptativa, sistema de musica dinamica, transiciones musicales, combat music.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Design multi-agent systems, create agent architectures, define communication patterns, and build autonomous agent workflows with structured evaluation frameworks.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, response formats, and quality loops.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

See all skills by SebastianLuser

Report a problem with this skill