Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

rust100k-build-performance

Estrellas1

Forks2

Actualizado11 de julio de 2026 a las 01:50

Apply Matklad Rust100k build-time, inline, workspace, and generic-boundary guidance to eph. Use when changing Rust crate structure, public generic APIs,

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

attunehq

attunehq/doteph

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

3 archivos

SKILL.md

readonly

name	rust100k-build-performance
description	Apply Matklad Rust100k build-time, inline, workspace, and generic-boundary guidance to eph. Use when changing Rust crate structure, public generic APIs,

Rust100k Build Performance

Keep Rust build time and hot-path performance visible together. This skill covers Matklad's Inline In Rust, Large Rust Workspaces, and Fast Rust Builds posts, with eph's small-project conflict decisions documented in .agents/skills/readme.md.

Workflow

Measure before tuning. For runtime changes use targeted command timings or smoke runs; for build changes use cargo timings, CI duration, or cargo metadata plus targeted cargo commands.
Treat #[inline] as cross-crate body exposure, not a magic speed switch. In applications, add it reactively after profiling or for tiny public wrappers.
Keep #[inline(always)] rare and evidence-backed. Prefer #[cold] or #[inline(never)] for error/cold paths only when profiling or layout concerns justify it.
For ergonomic generic public APIs, keep the generic wrapper thin and delegate immediately to a concrete implementation when compile-time bloat matters.
For eph's single-crate shape, prefer impl Trait or generics when they improve clarity or runtime performance. Split crates only when measurements or independent ownership boundaries justify it.
If eph becomes a workspace, use a flat crates/* layout, a virtual root manifest, folder names matching crate names, and a dedicated automation crate rather than scattered scripts.
Run cargo fmt --check, cargo test, and cargo clippy --all-targets -- -D warnings.

eph policy

Keep cargo fmt --check, cargo test, and cargo clippy --all-targets -- -D warnings as the ordinary gate.
Keep clippy lint groups in the crate roots explicit so the policy is visible outside the Git hook and Makefile.
Do not add compile-time-heavy abstractions for hypothetical reuse.
Prefer concrete data boundaries in shared internals, but allow impl Trait where it improves current clarity or runtime performance.
Treat release profile tuning as a measured change; document before/after latency and build-time impact.

Validation

cargo fmt --check
cargo clippy --all-targets -- -D warnings
cargo test -- --test-threads=1

Generic boundary and inline tradeoffs remain review rules. The crate-level lint attributes and CI commands are the executable policy.

Read references/article-notes.md for source notes and tool suggestions.

Más de este repositorio

mismo repositorio

using-eph

attunehq/doteph

Use when working in a repository that uses eph for ephemeral dev services (a `.eph` file exists, or `eph` is on PATH). Covers workspace detection, strict .eph parsing, auto-assigned ports, up/env/down/clean, roles, hooks, one-off commands, foreground and watch sessions, logs, and stale-workspace pruning.

names-are-not-type-safety

attunehq/doteph

Apply Alexis King's "Names are not type safety" advice in eph. Use when adding, reviewing, or refactoring Rust newtypes, wrapper structs, workspace or process identities, service names, paths, command text, state records, domain enums, smart constructors, or APIs that rely on naming conventions for correctness.

2026-07-111

parse-dont-validate

attunehq/doteph

Apply Alexis King's "Parse, don't validate" design rule in eph. Use when adding or reviewing Rust boundary code for .eph text, persisted JSON state, CLI arguments, environment variables, process identities, Compose output, release metadata, or any function that checks input validity before deeper processing.

2026-07-111

rust100k-architecture-docs

attunehq/doteph

Maintain eph's Rust architecture documentation in the Matklad Rust100k style. Use when changing module boundaries, the CLI/library split, parsing, workspace identity, lifecycle or state ownership, process control, pruning, bundled skills, updates, docs/developer-guide/architecture.md, docs/developer-guide/internals.md, or when reviewing whether code structure and architecture docs agree.

2026-07-111

rust100k-testing-discipline

attunehq/doteph

Apply Matklad Rust100k testing discipline to eph. Use when adding, reviewing, or reorganizing Rust tests, choosing unit versus Docker integration or stress coverage, designing fixtures, rejecting mocks, adding doctests, or changing Makefile and CI test coverage.

2026-07-111

Rust100k Build Performance

Workflow

Measure before tuning. For runtime changes use targeted command timings or smoke runs; for build changes use cargo timings, CI duration, or cargo metadata plus targeted cargo commands.

Treat #[inline] as cross-crate body exposure, not a magic speed switch. In applications, add it reactively after profiling or for tiny public wrappers.

Keep #[inline(always)] rare and evidence-backed. Prefer #[cold] or #[inline(never)] for error/cold paths only when profiling or layout concerns justify it.

For ergonomic generic public APIs, keep the generic wrapper thin and delegate immediately to a concrete implementation when compile-time bloat matters.

For eph's single-crate shape, prefer impl Trait or generics when they improve clarity or runtime performance. Split crates only when measurements or independent ownership boundaries justify it.

If eph becomes a workspace, use a flat crates/* layout, a virtual root manifest, folder names matching crate names, and a dedicated automation crate rather than scattered scripts.

Run cargo fmt --check, cargo test, and cargo clippy --all-targets -- -D warnings.

eph policy

Keep cargo fmt --check, cargo test, and cargo clippy --all-targets -- -D warnings as the ordinary gate.

Keep clippy lint groups in the crate roots explicit so the policy is visible outside the Git hook and Makefile.

Do not add compile-time-heavy abstractions for hypothetical reuse.

Prefer concrete data boundaries in shared internals, but allow impl Trait where it improves current clarity or runtime performance.

Treat release profile tuning as a measured change; document before/after latency and build-time impact.

Validation

cargo fmt --check cargo clippy --all-targets -- -D warnings cargo test -- --test-threads=1

Generic boundary and inline tradeoffs remain review rules. The crate-level lint attributes and CI commands are the executable policy.

Read references/article-notes.md for source notes and tool suggestions.