Code Craft
Apply Jess's engineering conventions to architecture, boundary typing, error handling, and abstraction decisions.
- Skill ID
- jssblck/agents/code-craft
- Publisher
- jssblck
- Repository
- agents
- Installs
- 0
- Files
- 11
- Synced
- Sep 23, 2026
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
jssblck/agents/code-craftInstalls these files- SKILL.md
- agents/openai.yaml
- languages/go.md
- languages/python.md
- languages/rust.md
- languages/typescript.md
- principles/architecture-docs.md
- principles/errors-as-values.md
- principles/illegal-states.md
- principles/parse-dont-validate.md
- principles/simplicity.md
What this skill tells the agent
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.
More from jssblck
Use this skill in a project
Open any RiverX project, search the Skills panel for jssblck/agents/code-craft, and install it in one click.