flying-dice

flying-dice/pseudoscript

Skill Claude Code

Review a set of changes (the staged diff, or a branch's diff) for correctness — before committing, pushing, or as a standalone pass.

flying-dice/pseudoscript

Skill Claude Code

Find the unhappy paths an existing Cucumber/BDD suite doesn't cover and write them up as new Gherkin scenarios in the feature files. Use whenever the user wants to harden, stress, or find gaps in Cucumber tests, .feature files, or Gherkin scenarios, or mentions a "chaos monkey", negative testing, edge cases, failure…

flying-dice/pseudoscript

Skill Claude Code

Multi-agent clean code audit — each principle gets its own agent.

flying-dice/pseudoscript

Skill Claude Code

Write idiomatic, ownership-clean Rust. ALWAYS use this skill when writing or editing Rust — any .rs file, anything under crates/, Cargo.toml/Cargo manifests, or when the user asks to add a function, type, trait, test, or module in Rust. Grounds the model in established Rust idioms: error handling, ownership/borrowing…

flying-dice/pseudoscript

Skill Claude Code

Use before every git push — mandatory quality gate, no exceptions.

flying-dice/pseudoscript

Skill Claude Code

Author and maintain PseudoScript (.pds) — C4-level architecture-as-code that compiles to diagrams and a doc site — as the single source of truth for spec-driven development. Use this skill whenever the user wants to model an application in PseudoScript, reverse-map / capture an existing app or codebase into a .pds…

flying-dice/pseudoscript

Skill Claude Code

Pick highest-scored clean-code TODO, fix it, stop. Loop handles repetition.

flying-dice/pseudoscript

Skill Claude Code

Enforces the terse, high-signal writing style for the PseudoScript language-spec docs. ALWAYS use this skill when creating or editing LANG.md, any file under CONFORMANCE/ (including its READMEs and .reject.expected files), or PATTERNS.md — for example adding a normative clause, writing a conformance case, documenting…