The-Artificer-of-Ciphers-LLC

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

Skill Claude CodeCodex

Apply Knuth's Optimization Principle when someone wants to optimize code before establishing it's a bottleneck, is using complex data structures for perceived performance, is making code harder to read "for speed", or is debating whether to optimize something that hasn't been profiled. Trigger on phrases like "I…

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

Skill Claude CodeCodex

Apply Lady Lovelace's Objection when discussing the creative or intellectual limits of software and AI, questions about whether machines can "truly" create or think, the nature of AI-generated art and writing, or debates about what computers can and cannot do autonomously. Trigger on phrases like "can AI really be…

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

Skill Claude CodeCodex

Apply the Law of Leaky Abstractions when someone is frustrated that a library, framework, or ORM isn't hiding complexity the way it promised, when debugging requires diving into implementation details that "shouldn't matter", or when deciding how much abstraction to build on top of something. Trigger on phrases like…

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

Skill Claude CodeCodex

Apply Linus's Law when discussing code review practices, open source contributions, bug finding strategies, security auditing, or the value of having more people look at code. Trigger on phrases like "should we do code reviews?", "we don't have time for reviews", "how do we find bugs faster?", "open source is more…

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

Skill Claude CodeCodex

Apply Moore's Law when discussing hardware capacity planning, compute cost trends, the feasibility of computationally intensive features, why software that was impractical five years ago is now possible, or the historical arc of what computers can do. Trigger on phrases like "this requires too much compute", "hardware…

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

Skill Claude CodeCodex

Apply Norvig's Law when evaluating growth claims about technology adoption, market size projections, "exponential growth" narratives, or headlines claiming a technology will "double" its reach when it's already dominant. Trigger on phrases like "X is growing exponentially", "this will double in the next year", "the…

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

Skill Claude CodeCodex

Apply Parkinson's Law when discussing project planning, sprint duration, deadline setting, scope creep, or why work seems to expand no matter how much time is allocated. Trigger on phrases like "we always use up all the time we're given", "if we give the team a month they'll take a month", "why does scope keep…

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

Skill Claude CodeCodex

Apply the Peter Principle when discussing promotions, career ladders, hiring for leadership roles, why managers sometimes struggle, or how to build healthy engineering organizations. Trigger on phrases like "we promoted our best engineer to manager", "they were great as an IC but struggling as a lead", "how should we…

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…