fec-debug-frameworkUse when diagnosing frontend build failures, runtime errors, UI anomalies, API/data problems, white screens, request failures, or unexplained production exceptions; Chinese triggers include debugging, debug, troubleshooting, positioning, error reporting, exceptions, white screens, request failures.
Install via ClawdBot CLI:
clawdbot install bovinphang/fec-debug-frameworkGrade Fair — 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 Nov 17, 2026 · audit v1.0
Generated Nov 17, 2026
A team ships a release and users report a blank screen. The skill guides an engineer through classifying the issue as a runtime or API problem, collecting console stacks and store snapshots, forming hypotheses, and validating a minimal fix before rollout.
A pull request fails CI with type and dependency errors that differ from local behavior. The framework directs evidence collection on Node version, package manager, lockfile diff, and peer dependency conflicts, then tests hypotheses one at a time instead of blindly upgrading packages.
Dashboard metrics show stale or mismatched data. The skill walks through request waterfall capture, hop-by-hop inspection, cache policy checks, and curl reproduction to isolate whether the fault is in the frontend, interceptor, or backend layer.
A marketing site shows misaligned layout on tablet and mobile but not desktop. The skill instructs comparing screenshots, checking computed styles and DOM structure, and testing CSS specificity or missing breakpoint hypotheses using DevTools across multiple breakpoints.
A development team adopts the framework as an internal standard so junior engineers stop guessing and expanding change scope. The five-step loop (classify, collect, hypothesize, verify, fix) provides a repeatable checklist and a standard report format for postmortems.
Adopted by platform or frontend infrastructure teams as a mandated debugging protocol to reduce mean time to resolution and prevent risky broad changes. Training and onboarding materials can be built around the skill's report template and verification records.
Embedded into an AI coding assistant or support bot that classifies user-reported frontend issues, collects the right diagnostic evidence, and suggests testable hypotheses. The skill's strict constraints prevent the AI from guessing or disabling tests as a shortcut.
Integrated into observability or error-monitoring platforms to auto-generate diagnostic reports from console stacks, network traces, and store snapshots, then guide engineers through the verify loop with linked evidence.
💬 Integration Tip
Wire the skill into existing incident, CI, or monitoring workflows so evidence collection happens automatically and the diagnostic report template is used consistently; keep the one-variable-at-a-time verification rule enforced in tooling or review checklists to prevent scope creep.
Scored Nov 17, 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.