fec-code-smellsUse 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.
Install via ClawdBot CLI:
clawdbot install bovinphang/fec-code-smellsGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/bovinphang/frontend-craftAudited Sep 29, 2026 · audit v1.0
Generated Sep 29, 2026
A product team inherits a five-year-old React codebase and must decide which modules to refactor before adding new features. The agent diagnoses structural problems using the smell catalog and false-positive checks, producing evidence-backed findings per file and symbol. Engineering leadership uses confidence, impact, and priority ratings to sequence the refactoring backlog without touching business code during diagnosis.
Before migrating an Angular app to a modern framework, an architecture team commissions a structural health audit. The agent identifies change-coupled modules, god components, and duplicated logic with concrete evidence, then maps each smell to candidate refactorings. The migration plan is scoped based on HIGH and MEDIUM confidence findings only.
A platform team wants to raise code review standards without blocking delivery on subjective opinions. The agent runs diagnosis in CI-like fashion on changed files, reporting smells with location, evidence, and false-positive considerations. Reviewers use the structured finding contract to discuss concrete evidence instead of style preferences.
A private equity firm performs due diligence on a software company and needs an objective read on frontend maintainability risk. The agent produces smell findings with priority and candidate refactorings across the codebase. The resulting report informs valuation adjustments and post-acquisition remediation estimates.
A digital agency takes over maintenance of a client's frontend application from another vendor. The agent documents structural smells, change-coupling evidence, and likely refactoring candidates so the new team understands risk hotspots. The client receives a transparent diagnosis-only report with no business-code edits.
A command-line diagnostic tool distributed freely to individual developers, with the code-smell detection engine bundled as a plugin. Adoption grows through GitHub stars and community contributions. Monetization comes from optional paid support, hosted dashboards, and enterprise policy packs.
A cloud platform continuously analyzes connected repositories and surfaces smell findings, confidence scores, and prioritized refactoring candidates. Teams subscribe per seat or per repository and receive dashboards, trend tracking, and pull-request annotations. Higher tiers unlock custom smell catalogs and integration with issue trackers.
Consulting firms use the skill internally to deliver structured frontend maintainability audits as fixed-price engagements. Deliverables include a prioritized findings report, refactoring roadmap, and optional follow-up remediation sprints. The diagnosis-only posture keeps engagements scoped and audit-friendly before any code changes.
💬 Integration Tip
Run the skill in diagnosis-only mode first and require every finding to include location, evidence, and false-positive notes before any refactoring is scheduled; treat LOW-confidence findings as investigation prompts rather than automatic-edit signals.
Scored Sep 29, 2026
Use when building UI with shadcn/ui components, Tailwind CSS layouts, form patterns with react-hook-form and zod, theming, dark mode, sidebar layouts, mobile navigation, or any shadcn component question.
Tailwind reference tool. Use when working with tailwind in frontend contexts.
A product creation skill based on the "Bee Website Builder" Open API. It is used to create a new product under a specified site language and product group, w...
A product update skill based on the "Bee Website Builder" Open API. It is used to update an existing product under a specified site language and supports upd...
Build WCAG 2.1 AA compliant websites with semantic HTML, proper ARIA, focus management, and screen reader support. Includes color contrast (4.5:1 text), keyboard navigation, form labels, and live regions. Use when implementing accessible interfaces, fixing screen reader issues, keyboard navigation, or troubleshooting "focus outline missing", "aria-label required", "insufficient contrast".
Use when building Vue 3 applications with Composition API, Nuxt 3, or Quasar. Invoke for Pinia, TypeScript, PWA, Capacitor mobile apps, Vite configuration.