tailrocks-skills

Turn a rough idea into an enriched, evidence-backed proposal. Spawns parallel analysis to gather prior art, codebase touchpoints, constraints, risks, and alternative directions, then writes findings into a per-idea folder for you to review. Read-only — never writes code or the final plan (that is the tailrocks-research skill). Invoke explicitly with a short description of the idea.

Take a confirmed proposal direction and produce an incredibly detailed, self-contained implementation plan. Runs deep parallel research (web + codebase), records sourced evidence, then writes handoff plans a zero-context executor can follow — inside the same per-idea folder the tailrocks-propose skill created. Read-only on source; writes only plan and research files. Invoke explicitly with a proposal slug.

Strict, idiomatic Rust code guidance for writing, reviewing, and refactoring Rust — ownership, API design, errors, tests, docs, unsafe, and performance. Invoke explicitly for code-level work; for workspace, lint, toolchain, and tooling setup, use tailrocks-rust-project-setup.

Set up or audit a strict, modern Rust project — workspace and crate layout, lint/Clippy/rustfmt config, a pinned toolchain, mise tooling, and supply-chain and test gates. Invoke explicitly to scaffold or harden project structure and tooling; for code-level guidance, use tailrocks-rust-best-practices.