The-Artificer-of-Ciphers-LLC/skills-from-the-artificer

The-Artificer-of-Ciphers-LLC/skills-from-the-artificer

Skill Claude CodeCodex

Apply Postel's Law when designing APIs, data interchange formats, network protocols, input validation, or any interface that will receive data from other systems or users. Trigger on phrases like "how strict should our API be?", "should we accept slightly malformed input?", "what should we send vs. accept?", "how do…

The-Artificer-of-Ciphers-LLC/skills-from-the-artificer

Skill Claude CodeCodex

Rubber duck debugging session. Use when the user is stuck on a bug and can't find the cause, says "I don't understand why this isn't working", "help me think through this", "talk me through this bug", or "rubber duck". Also use when a developer has been debugging for >20 minutes without progress — the duck is most…

The-Artificer-of-Ciphers-LLC/skills-from-the-artificer

Skill Claude CodeCodex

Apply the Shirky Principle when analyzing why legacy systems persist, why incumbents resist disruptive solutions, why organizations seem to make self-defeating decisions, or why a tool or institution appears to be prolonging the problem it was meant to solve. Trigger on phrases like "why do they keep the old system…

The-Artificer-of-Ciphers-LLC/skills-from-the-artificer

Skill Claude CodeCodex

Dispatcher for the Artificer laws-of-software collection. Given a proposed change, fix, diff, design, or decision, classify it and invoke the relevant law/principle skill(s) — instead of recalling all 24 individually. Use when the user says "cross-reference against the Artificer laws", "which laws apply here?", "run…

The-Artificer-of-Ciphers-LLC/skills-from-the-artificer

Skill Claude CodeCodex

Test-driven bug fixing — reproduce before you fix. Use this skill whenever the user reports a bug, describes unexpected behavior, says something is broken, mentions a regression, or asks you to fix an error. This includes phrases like "this is broken", "X doesn't work", "there's a bug in", "getting an error when", "it…

The-Artificer-of-Ciphers-LLC/skills-from-the-artificer

Skill Claude CodeCodex

Use when you receive findings, a report, or any factual claims back from a subagent/Task before you act on them — re-validate every claim against a primary source (the code itself, the memory directory, CONTEXT.md, docs/ and docs/adr/, context7 library docs, package/API references, or a language spec) instead of…

The-Artificer-of-Ciphers-LLC/skills-from-the-artificer

Skill Claude CodeCodex

Apply Wirth's Law when discussing software performance, application bloat, why software feels slower despite hardware improvements, resource usage in modern applications, or the relationship between software quality and hardware progress. Trigger on phrases like "why is this app so slow?", "software is getting…

The-Artificer-of-Ciphers-LLC/skills-from-the-artificer

Skill Claude CodeCodex

Apply Zawinski's Law when discussing feature creep, scope expansion, the tendency for software to grow beyond its original purpose, or when evaluating whether to add a communication feature to a non-communication product. Trigger on phrases like "should we add messaging?", "every app becomes a platform", "our product…

The-Artificer-of-Ciphers-LLC/skills-from-the-artificer

Skill Claude Code

A full PreToolUse/PostToolUse hook suite that machine-enforces a project's workflow rules instead of leaving them as prose — a passing test-runner verdict bound to the exact commit sha before push, no local node --test, Memtrace-first code discovery, no-defer artifact gating for long directives, and a family of guards…