105 skills · sorted by relevance
Enforces KISS/DRY/YAGNI during authoring and ad-hoc quality reviews. Pragmatic standards: concise, direct, no unnecessary comments. NOT for post-hoc diff/PR review (see mk:review); NOT for behavior-preserving simplification passes (see mk:simplify).
The English summary is being prepared. Showing the original description.
Diagnose and optimize timing-critical Chisel RTL for FPGA implementation while preserving cycle semantics. Use for Vivado timing bottlenecks, long ready or admission paths, queue and issue selection, free-list bank mapping, priority encoders, one-hot arbitration, wide muxes, late-arriving forwarding or override data, high-fanout controls, cross-module predicates, register-boundary changes, emitted-Verilog inspection, or routed-DCP A/B analysis. Also use when a source-level simplification needs proof that it changes timing without changing architectural state.
The English summary is being prepared. Showing the original description.
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
The English summary is being prepared. Showing the original description.
Review gate for correctness, reuse, and simplification. Produces a structured verdict with actionable findings. Trigger on any PR before merge, or on any agent-generated code before it is committed.
The English summary is being prepared. Showing the original description.
Review changed code for YAGNI, removable over-complexity, reuse, code quality, and efficiency, then apply worthwhile simplifications. Use when the user asks to simplify, clean up, tighten, de-hack recent changes, identify logic that can be dropped, or review whether added safeguards and edge-case handling are actually needed.
The English summary is being prepared. Showing the original description.
Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure
The English summary is being prepared. Showing the original description.
Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.
The English summary is being prepared. Showing the original description.
Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.
The English summary is being prepared. Showing the original description.
[Code Quality] Use when a workflow step or the user asks for code simplification for clarity and maintainability without changing behavior.
The English summary is being prepared. Showing the original description.
Mitigate incidental code complexity when control flow is tangled, nesting is deep, names are hard to parse, or reasoning requires cross-file hops. Use when a review stalls on readability, you need an analysis-first refactor plan before edits, or you want essential-vs-incidental verdicts, ranked simplification steps, a small structural sketch, and a TRACE assessment (analysis-only; no edits).
The English summary is being prepared. Showing the original description.
Mine a codebase for breakthrough, evidence-backed opportunities — features, additions, refactors, simplifications, DX, UX, reliability, performance, or architecture cleanup. Researches project reality first, then forces two escalation gates (reject the merely-adequate idea; expand ambition 10x then collapse to the smallest proof-bearing artifact). Outputs ranked opportunities, an escalation ledger, and one plan seed. Does not implement or create tickets.
The English summary is being prepared. Showing the original description.
Audit a codebase or subsystem for architecture simplification - shallow or pass-through modules, scattered concepts, naming drift, sibling workflows that disagree, weak test seams. Use when the user asks what to simplify or restructure. Not for a narrow fix or for implementing an already chosen design.
The English summary is being prepared. Showing the original description.
Use when working code feels heavier than it needs to be — deeply nested logic, long functions, unclear names, duplication after a merge, or a review that flagged complexity. Reduces complexity while preserving behavior exactly. Not for code you do not yet understand, or code you are about to rewrite.
The English summary is being prepared. Showing the original description.
Use when a concept is too abstract for the learner's current level and needs analogy-first teaching before complexity re-injection.
The English summary is being prepared. Showing the original description.
Analyze and optimize CLAUDE.md files for quality improvements and token reduction. Supports analysis-only, simplification-only, or full optimization modes. Use when asked to "review", "optimize", "simplify", "improve", "check", or "reduce tokens" in CLAUDE.md.
The English summary is being prepared. Showing the original description.
Explain a topic, piece of code, concept, or error for one fixed reader: a visually-oriented high school student who reasons logically and is curious. Leads with a figure chosen to fit the idea (a table, a Mermaid diagram, an ASCII sketch, or a local HTML page with SVG, Canvas, or 3D when the idea is spatial or moves), walks the cause-and-effect chain without skipping steps, names the real terms, and marks every simplification. Use when the user says 'ELI5', 'explain like I'm', 'dumb it down', 'break this down', 'simplify this', 'かみくだいて', '噛み砕いて', '図解して', '図で説明して', '高校生でも分かるように', or invokes /visual-eli. Do NOT use when the user names a different audience (a manager, a child, a specific person) or wants a document, a crash course, or a tutorial as the deliverable — use explainer for those.
The English summary is being prepared. Showing the original description.
Reduce time-to-first-API-call (TTFAC) by optimizing every step of the developer onboarding journey. This skill covers authentication simplification, sandbox environments, interactive documentation, an
The English summary is being prepared. Showing the original description.
Review a diff for clarity and safe simplifications, then optionally apply low-risk fixes.
The English summary is being prepared. Showing the original description.
機能を保持したまま不要な複雑性を排除し、コードの簡潔性と可読性を向上させる。30行超の関数や3段以上のネスト検出時に使用。
The English summary is being prepared. Showing the original description.
Review a diff for clarity and safe simplifications, then optionally apply low-risk fixes.
The English summary is being prepared. Showing the original description.
Review code for readability, then simplify it to be easy to follow and understand. Use this skill when the user wants to simplify code, improve readability, clean up for handoff, make code skimmable, reduce complexity, refactor for clarity, strip boilerplate, prepare code for future maintainers, or make a codebase easier to pick up. Trigger liberally — any request touching readability, simplification, cleanup, or "make this easier to understand" should use this skill. Also trigger when the user says things like "review this", "clean this up", "tidy this", "make this simpler", "reduce complexity", "flatten this", "strip the noise", or "I want to understand this code quickly next time I open it".
The English summary is being prepared. Showing the original description.
Fan six specialist reviewers (general correctness, silent failures, type design, test gaps, comment accuracy, simplification) out over the current diff, a branch, or a PR in parallel, then merge their findings into one deduplicated, ranked report. Use for a thorough review before merging. Not for editing code or approving on someone's behalf.
The English summary is being prepared. Showing the original description.
Unified pull request workflow: prepare a safe branch, run read-only review, fix Required findings, create/update a GitHub draft PR, and verify CI plus automated review comments. Subcommands: `create` (simplify + PR, skip code review), `review` (read-only findings only), `fix` (Required fixes + commit, no push), `simplify` (simplification only), `verify` (existing PR checks/reviews only). Use when creating or reviewing PRs, self-reviewing changes, simplifying PR changes, or requesting "PR作成", "レビュー", "簡素化". Do NOT use for responding to review comments or a lightweight review of the current working diff without the PR workflow (use the built-in /code-review instead).
The English summary is being prepared. Showing the original description.
TOP PRIORITY skill — find and immediately fix or remove every piece of wrong, outdated, or redundant information in ToolUniverse docs. Wrong code, broken links, incorrect counts, and overlapping instructions must be fixed or removed — never left in place. Runs five phases: (D) static method scan, (C) live code execution, (A) automated validation, (B) ToolUniverse audit, (E) less-is-more simplification. Core philosophy: each concept appears exactly once; remove don't add; no emojis; single setup entry point. Use when reviewing docs, before releases, after API changes, or when asked to audit, fix, or simplify documentation.
The English summary is being prepared. Showing the original description.