juntag
Community@azishio · Japan
juntag (azishio) provides Rust-focused code minimalism skills: idiomatic Rust guidance, over-engineering audits, and technical debt ledgers.
Agent Skills by juntag
Showing 6 vetted skills indexed across 1 GitHub repositories.
anti-overengineering-help
Displays a quick-reference card for anti-overengineering skills and their always-on rules.
write-idiomatic-rust
Implements, reviews, and refactors idiomatic Rust code using vendored API guidelines and strict Clippy checks.
anti-overengineering-gain
Displays upstream benchmark results for the anti-overengineering ruleset as a plain-text scoreboard.
anti-overengineering-debt
Collects anti-overengineering comment markers into a grouped technical debt ledger report.
anti-overengineering
Enforces minimal code solutions by applying a YAGNI decision ladder to coding tasks.
anti-overengineering-review
Reviews codebases for over-engineering and reports deletable code, dependencies, and abstractions.
Frequently Asked Questions About juntag
FAQPage SchemaWhat tasks can I accomplish with juntag's anti-overengineering skills?▼
You can force the simplest working solution on any coding task, review a codebase or PR purely for over-engineering, harvest deferred shortcuts into a debt ledger, and view a scoreboard of measured impact: less code, less cost, more speed.
Who should use the write-idiomatic-rust skill?▼
Rust engineers implementing, fixing, reviewing, or refactoring code. It covers types, ownership, error design, function and method placement, dependency choices, Rust design guidelines and patterns, and resolving Clippy findings across public APIs and internal implementations.
How do I trigger the anti-overengineering review and debt skills?▼
Invoke /anti-overengineering-review or phrases like 'find bloat' or 'audit this codebase' for a one-shot complexity report. Use /anti-overengineering-debt or 'what did we defer' to generate the debt ledger. Neither applies changes.
When should I NOT use the anti-overengineering skill?▼
Do not use it for non-coding requests such as general knowledge, prose, translation, summaries, or recipes. It applies only to coding tasks: writing, adding, refactoring, fixing, reviewing, designing code, or choosing libraries and dependencies.
What does the anti-overengineering-gain skill show?▼
It displays a compact, one-shot scoreboard of the measured impact of the upstream ruleset the skills derive from: less code, less cost, more speed. It is not a persistent mode and does not report per-repository numbers.