---name: code-craftdescription: Apply Jess's engineering conventions to architecture, boundary typing, error handling, and abstraction decisions.user-invocable: trueargument-hint: [rust|typescript|go|python] [target]---

Code craft

Use the repository's current instructions and established conventions. Apply these defaults where the requested change needs a design decision; they do not authorize unrelated restructuring or new tooling.

Read the reference for the decision in scope:

Decision	Reference
Represent states and domain identities	Illegal states
Decode external input into useful types	Parse, don't validate
Model recoverable errors and required gates	Errors as values
Choose an abstraction or investigate performance	Simplicity
Maintain module boundaries and their documentation	Architecture docs

Read a language reference only when its idioms, concurrency, or tooling details matter: TypeScript, Rust, Go, or Python.

Use testing-craft for test-design decisions. Repository setup belongs to project-bootstrap when that setup is requested. Follow the project's required verification; reviews do not automatically require a full test suite.

Adapted from leonardomso/rust-skills (MIT), Matklad's Rust100k series, and Alexis King's writing on parsing and type safety.