/fec-smell

Diagnose frontend code smells with evidence and candidate refactorings without changing business code.

Boost this command

bovinphang@bovinphang

GitHub

From plugin

frontend-craft

2111 skills14 agents11 commands5 hooks

Install

> /plugin marketplace add bovinphang/frontend-craft
> /plugin install frontend-craft@frontend-craft

How it fires

How this command gets triggered: by you, by Claude, or both.

Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/fec-smell

Context preview

What this command does when you run it.

Diagnose frontend code smells with evidence and candidate refactorings without changing business code.

Command definition

fec-smell.md

name: fec-smell
description: Diagnose frontend code smells with evidence and candidate refactorings without changing business code.

Use this command for **DIAGNOSE ONLY** analysis. Do not modify business code.

Workflow

1. Discover the requested scope, project/framework facts, and current diff. 2. Collect concrete evidence about ownership, duplication, change coupling, data flow, control flow, and public boundaries. 3. Match evidence against the 24-smell catalog and run false-positive checks. 4. For each finding report: `Location`, `Evidence`, `Impact`, `Smell`, `Confidence`, `Candidates`, `Priority`, and `False-positive check`. 5. LOW-confidence findings remain open questions and must not become automatic edits. 6. Save the result to `reports/refactoring/smell-YYYY-MM-DD-HHmmss.md`.

Metrics such as LOC or complexity may focus investigation but are not sufficient proof by themselves.

Read it on GitHub ↗

Ships withfrontend-craft

frontend-craft is a universal frontend plugin that brings the same opinionated engineering standards to all 15 AI coding assistants.

Get the whole plugin

Stats

TypeScript JavaScript Node React Next.js

+7 tags

Vue CSS Markdown Anthropic MCP Figma Vite

Stars

Forks

Active