alyraffauf

alyraffauf/hoenn

Skill Claude Code

Restate the last message in plain human language, with no jargon.

alyraffauf/hoenn

Skill Claude CodeCodex

Review handwritten source code against the quality-code standards. Use only when the user explicitly invokes $code-qa. Do not infer use from an ordinary request to review, inspect, or explain code.

alyraffauf/hoenn

Skill Claude CodeCodex

Standardize all GitHub work via gh CLI (repos, issues, PRs, reviews, Actions, labels, releases). Trigger on any GitHub URL (incl. deep links like /pull/123, /issues/123.

alyraffauf/hoenn

Skill Claude CodeCodex

Use Nix for installing packages, adding tools, setting up dev environments, and resolving missing binaries. Prefer Nix over apt, dnf, or brew when nix is available. Nix provides the runtime; use language PMs (npm, pip, cargo) inside a nix shell for project deps.

alyraffauf/hoenn

Skill Claude CodeCodex

Standards for writing or modifying handwritten source code. Use when implementing code changes or reviewing handwritten code. Do not use for browsing, explanation, diagnosis without implementation, generated code, or vendored code.

alyraffauf/hoenn

Skill Claude CodeCodex

Explain a body of work plainly so a person actually understands it. Runs the how and why skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

alyraffauf/hoenn

Skill Claude Code

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

alyraffauf/hoenn

Skill Claude CodeCodex

Cut AI tells from any writing. Must always apply.

alyraffauf/hoenn

Skill Claude CodeCodex

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for…

alyraffauf/hoenn

Skill Claude CodeCodex

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics…