pseudoscript

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 model, drive development from a model (write the spec first, implement from it), capture business rules as code while keeping infrastructure (repositories, HTTP/controllers, persistence, queues, external APIs) as black boxes, write Gherkin-style `feature` behaviour specs, or reconstitute / generate a real implementation from a model. Trigger it on mentions of PseudoScript, `.pds`, "architecture as code", "C4 as code", "model the system", "spec-driven", "turn this app/codebase into pseudocode", or "what does the model say it should do" — even if the user doesn't name the language explicitly.

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

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 modes, or unhappy paths. Trigger even on a casual "think of ways to break this" or "what are we not testing?" about a BDD codebase.

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

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, iterators, the type system, API design, and the clippy/rustfmt baseline. Trigger even when the user doesn't say "idiomatic" — any Rust authoring task qualifies.

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

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

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 a pattern, or drafting a decisions/ entry. Also use it when asked to review, de-waffle, tighten, or proofread a diff touching these files, or whenever prose in them risks drifting into hedging, ceremony, future tense, rhetorical flourish, or restating a cross-reference. Trigger even if the user doesn't name the style explicitly — any writing task on these three artifacts qualifies.