Loading...
Loading...
Found 53 Skills
Find, rank, and safely remove accidental codebase complexity by proving real consumers, dynamic entrypoints, compatibility obligations, duplicate representations, speculative surfaces, and lifecycle ownership. Use when asked to simplify or clean up a repository, reclaim code entropy, reduce over-engineering or redundancy, find deletion candidates, collapse duplicate state/APIs, remove dead or added-then-abandoned code beyond static-tool output, or implement an evidence-backed simplification pass in any language or stack. Also trigger for 代码化简、熵回收、删代码、清理冗余、收敛抽象、去除过度设计. Do not use as a performance audit unless simplification is the stated goal.
Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure
Use when running a scheduled mechanical maintenance pass over a repo — dead code removal, useless-test pruning, layering-violation fixes, duplicate unification, logic bugfixing, logic simplification, or excess-abstraction flattening. Invoked as `/cadence:maintenance-routine <archetype>`, typically from a scheduler (cron, a CI schedule, or an agent workbench's time trigger). One archetype per invocation; opens PRs and never merges. NOT for reviewing a PR (use pr-review), NOT for ad-hoc refactoring the user asked for directly.
Analyzes cyclomatic and cognitive complexity, identifies overly complex functions. Use when assessing code complexity or identifying functions that need simplification.
Expert patterns for simplifying 3D games to 2D including dimension reduction strategies, camera flattening, physics conversion, 3D-to-sprite art pipeline, and control simplification. Use when porting 3D to 2D, creating 2D versions for mobile, or prototyping. Trigger keywords: CharacterBody3D to CharacterBody2D, Camera3D to Camera2D, Vector3 to Vector2, flatten Z-axis, orthogonal projection, 3D to sprite conversion, performance optimization.
Ruby refactoring guidelines from community best practices. This skill should be used when refactoring, reviewing, or restructuring Ruby code to improve design, readability, and maintainability. Triggers on tasks involving code smells, method extraction, conditional simplification, coupling reduction, design patterns, or Ruby idiom adoption.
Deep code simplification, refactoring, and quality refinement. Analyzes structural complexity, anti-patterns, and readability debt, then applies targeted refactoring preserving exact behavior. Language-agnostic: Python, Go, TypeScript/JavaScript, Rust. Use this skill when the goal is simplification and clarity rather than bug-finding. Triggers on: "simplify this code", "clean up my code", "refactor for clarity", "reduce complexity", "make this more readable", "code quality pass", "tech debt cleanup", "run the code refiner", "simplify recent changes", "this code is messy", "too much nesting", "this function is too long", "clean this up before I PR it", "tidy up my code", cyclomatic complexity, cognitive complexity, code smells.
Make dense or complex information easier to understand, navigate, remember, and act on through clear layers, concrete examples, and visible progress. Use when the user explicitly invokes Focus Friendly; requests focus-oriented simplification, chunking, pacing, mapping, or reorientation; reports overwhelm, trouble reading or focusing, task-initiation difficulty, or losing their place in the current task; asks whether those difficulties prove ADHD; or asks for help navigating long, structurally complex material that genuinely needs a map. Do not invoke merely because a request mentions ADHD or asks for summarization, teaching, planning, research, or routine coding; those tasks need an explicit focus or navigation signal.
Perform a refactor pass focused on simplicity after recent changes. Use when the user asks for a refactor/cleanup pass, simplification, or dead-code removal and expects build/tests to verify behavior.
Comprehensive reference for LINE MINI App — Service Messages, Common Profile Quick Fill, In-App Purchase, Console setup (3 internal channels), submission review, and performance guidelines for web apps running inside LINE as an enhanced LIFF platform. This skill should be used when the user asks to "build a LINE MINI App", "send a service message", "set up Common Profile Quick Fill", "implement in-app purchase", "configure MINI App Console", "submit MINI App for review", or mentions LINE MINI App, Service Messages, notification token, Common Profile, IAP purchase flow, 3 internal channels, consent simplification, Custom Path, custom share messages, or verified vs unverified MINI App. Always use this skill whenever the user mentions LINE MINI App, mini apps in LINE, or enhanced LIFF features like service messages or in-app purchase, even if they don't explicitly say "MINI App".
Philosophy-aware PR reviews checking alignment with amplihack principles. Use when reviewing PRs to ensure ruthless simplicity, modular design, and zero-BS implementation. Suggests simplifications, identifies over-engineering, verifies brick module structure. Posts detailed, constructive review comments with specific file:line references.
Run a complete repository-native, spec-anchored development loop inspired by DeepSeek Harness. Use for feature development, bug fixes, simplification, architecture, process, or testing work that changes behavior, contracts, structure, test strategy, durable formats, or decision rationale; when asked to write, review, continue, implement, reject, supersede, archive, or verify a spec/Agent Note/RFC/ADR; or when code, tests, current-state docs, and decision rationale must converge in one change. Also use for read-only spec-to-code drift checks. Do not create a spec for a purely mechanical local edit that changes none of those things.