fec-debug-framework

Diagnose frontend build, runtime, UI, and API issues with a structured workflow.

21|3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/bovinphang/frontend-craft --skill fec-debug-framework
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fec-debug-framework
Source: https://github.com/bovinphang/frontend-craft/tree/main/localized/zh-CN/skills/fec-debug-framework
Command: npx skills add https://github.com/bovinphang/frontend-craft --skill fec-debug-framework

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

诊断前端构建失败、运行时错误、UI异常、API/数据问题、白屏、请求失败等线上异常;通过证据驱动的分类、收集、假设、验证和修复流程定位故障,避免凭直觉扩大改动。

Core Features & Use Cases

  • 统一的五步工作流:分类、收集、假设、验证、修复与确认,确保可追溯的诊断过程
  • 支持构建、运行时、UI 与 API 问题的分类型诊断与证据收集
  • 产出结构化的诊断报告模板,便于团队快速复现与修复

Quick Start

启动诊断流程,在遇到前端问题时按步骤收集证据、提出假设、逐一验证并整理修复结果。

Frequently Asked Questions about fec-debug-framework

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose frontend build failures and runtime crashes systematically?

Diagnose frontend build failures and runtime crashes using a structured five-step evidence-driven workflow that classifies issues, collects data, forms hypotheses, verifies, and validates fixes to ensure traceability.

What is the best way to troubleshoot UI glitches and API data inconsistencies in modern web apps?

Troubleshooting UI glitches and API data inconsistencies requires an evidence-driven diagnostic workflow that enforces stepwise collection, hypothesis formulation, and verification to locate faults without relying on intuition.

How to fix frontend white screen and request failed errors step by step?

Fix frontend white screen and request failed errors through a structured diagnostic process: classify the issue, collect evidence, formulate hypotheses, verify each one, and apply a fix-and-validate cycle.

How do I produce a structured diagnostic report for frontend issues?

Produce a structured diagnostic report for frontend issues by executing the evidence-driven workflow that outputs a standardized template, ensuring your team can quickly reproduce and resolve the diagnosed anomalies.

Can I use this evidence-driven debugging workflow for all types of frontend problems?

You can use this evidence-driven debugging workflow for all frontend problems including build failures, runtime crashes, UI glitches, and API data inconsistencies across modern web apps to avoid expanding changes blindly.