fec-refactoringUse when restructuring existing frontend code while preserving observable behavior, including responsibility extraction, module movement, conditional simplification, API cleanup, or data organization. Do not use for new feature behavior, behavior-changing bug fixes, dependency or framework migration
Install via ClawdBot CLI:
clawdbot install bovinphang/fec-refactoringGrade 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 dashboard component has grown to 1,200 lines with data fetching, filtering, chart configuration, and table rendering mixed together. Before adding a new widget, the team uses fec-refactoring to extract responsibility-specific hooks and presentational components, verifying each step preserves the existing rendered states and network calls.
A growing frontend codebase has duplicated buttons, form controls, and modal implementations across feature folders. The skill is applied to move modules into a shared package, update imports, and verify that public exports, props, styling contracts, and accessibility behavior remain unchanged across all consumers.
A checkout flow contains nested ternaries and early-return conditions that make the UI states hard to reason about. A developer uses the skill to simplify the conditions while running characterization tests around payment, shipping, and error states to prove observable behavior is preserved.
A frontend API layer exposes overlapping helper functions, inconsistent error shapes, and unused parameters after several feature iterations. The refactoring skill guides renaming, consolidating, and removing private helpers while a contract test suite verifies network endpoints, headers, and error handling stay intact.
A Vue app mixes store state, composables, and component-local reactive state for the same domain data. The team uses the skill to move state boundaries and extract composables in small steps, using existing component tests and typechecking to confirm no user-visible data behavior changes.
Refactoring is applied by in-house product teams to reduce maintenance cost and delivery friction on their own frontend codebase. The skill standardizes review criteria, diff budgets, and evidence requirements so structural work does not silently change behavior.
Consultancies use the skill to assess and restructure inherited frontend code during due diligence, platform handoffs, or rescue projects. Behavior-preserving discipline and PASS/PARTIAL/NOT PROVEN reporting provide clients with defensible evidence of risk and progress.
Tool vendors can embed this workflow into IDE extensions, CI checks, or AI coding agents to enforce baseline verification, diff budgets, and rollback boundaries. Teams adopt the packaged methodology as part of their engineering standards and quality gates.
💬 Integration Tip
Pair the skill with existing test, typecheck, and lint commands so each refactoring step has an immediate narrow verification target. Start with a SAFE local extraction to validate the baseline-and-Diff-Budget workflow before attempting CAUTION or DANGER cross-module changes.
Scored Sep 29, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.