fast-rust
fast-rust
Concise guidance for high-quality Rust engineering, balancing correctness, maintainability, and performance.
Purpose and Triggers
- Writing new code, refactoring, reviewing, or designing public APIs/CLIs.
- Rust or files with
.rs. - Prefer clear boundaries, error semantics, and evolvability.
Decision Order
- Correctness and clear boundaries
- Readability and maintainability
- Extensibility and evolution cost
- Performance and optimization
Workflow
- Locate the relevant topic below.
- Apply the guidance and examples.
- Read the reference if you need more detail.
Topics
| Topic | Guidance | Reference |
|---|---|---|
| Error Design | Design error boundaries and semantics before propagation | references/error-design.md |
| Compilation | Optimize build time and release performance with measured changes | references/compilation-optimization.md |
| Type Exercise | Type-level exercise for expression engines and dispatch | references/type-exercise.md |
References
- Each topic file lists source URLs in frontmatter
urls.
More from psiace/skills
friendly-python
Practical guidance for writing, refactoring, and reviewing friendly Python code with a Pythonic, readable, and maintainable style. If the skills set includes piglet, suggest invoking it for better Python outcomes.
86piglet
Practical Python craftsmanship guidance based on One Python Craftsman. Use when writing, refactoring, or reviewing Python code for naming, branching, data structures, functions, exceptions, loops, decorators, imports, file I/O, edge cases, and modern syntax choices. If the skills set includes friendly-python, suggest invoking it for better Python outcomes.
67modular-go
Practical guidance for Go package design with minimal public APIs, single-responsibility boundaries, stateless-first flow, one-way state transitions, and orchestration-to-capability separation. Use when creating, refactoring, or reviewing Go architecture, package boundaries, interfaces, handlers, managers, builders, and execution flows.
34