Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.
Coding
Code Smells
Try itUse when diagnosing structural maintainability problems in existing frontend code before deciding how to refactor it, especially when evidence, false-positive checks, and candidate transformations are needed without editing business code.
What it does
Overview Diagnose structural problems from concrete evidence. A smell is a prompt to investigate, not proof that code must change.
The skill document
Code Smell Diagnosis
Overview
Diagnose structural problems from concrete evidence. A smell is a prompt to investigate, not proof that code must change.
Procedure
- Establish the requested scope and project facts.
- Collect concrete structural and change-coupling evidence.
- Match evidence against the smell catalog.
- Apply false-positive checks.
- Report confidence, impact, and candidates from the mapping guide.
- If the request is diagnosis-only, do not modify business code.
Finding Contract
Every finding states location, evidence, smell ID/name, impact, confidence (HIGH, MEDIUM, LOW), candidate refactorings, priority, and material false-positive considerations. LOW confidence is never an automatic-edit signal.
Quick Reference
| Need | Reference |
|---|---|
| Standard 24-smell model | Smell catalog |
| Evidence and false positives | Detection guide |
| Candidate refactorings | Smell-to-refactoring map |
Common Mistakes
- Treating a metric threshold as proof.
- Reporting a smell without a file/symbol and evidence.
- Treating every loop, switch, comment, wrapper, or pipeline as defective.
- Editing code when the user asked for diagnosis only.
Related skills
Run Git operations — commits, branches, merges, rebases, conflict resolution, and recovery — with safety rules enforced.
Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.
Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.
Write, debug, and tune Playwright specs with locator strategy, trace diagnosis, and CI-aware timeouts.
Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.
More from bovinphang
Browse all skillsGenerate or edit diagrams, visual assets, and image workflows with reviewable PNG self-checks and bounded self-repair.
Use when creating editable technical diagrams with draw.io / diagrams.net sources, including architecture diagrams, ERD, UML, sequence diagrams, flowcharts, ML model diagrams, official shape lookup, brand symbols, Graphviz auto-layout, codebase structure maps, .drawio validation, or draw.io CLI expo
Use when building, reviewing, or improving frontend UI that needs product-specific design direction, design-system generation, Master/Page overrides, distinctive visual identity, anti-generic interface choices, first-screen hierarchy, UI polish, chart UX, interaction states, responsive behavior, or
Use when creating or reviewing Next.js 14+ App Router projects, file routes, layouts, server/client component boundaries, SSR/SSG/ISR, streaming, metadata, middleware, server actions, or Next-specific data fetching. For generic client React component architecture, apply the project's React conventio
Use when creating, reviewing, or restructuring frontend monorepos with pnpm workspace, Turborepo, Nx, multi-package dependency boundaries, task orchestration, package naming, or package publishing; Chinese triggers include monorepo, workspace, multi-package.
Use when creating or reviewing Nuxt 3 projects, file routes, pages, layouts, SSR/SSG/SPA behavior, Nuxt data fetching, route middleware, plugins, modules, server routes, or Nuxt-specific Vue 3 conventions. For generic Vue component architecture, apply the project's Vue conventions separately; Chines