fec-debug
CommandFront-end problem diagnosis and repair: covering build failures, runtime errors, UI exceptions, and interface problems, using a…
Sync README, docs, environment variables, scripts, API/routing/component descriptions and deployment instructions from code and project sources of truth.
> /plugin marketplace add bovinphang/frontend-craft> /plugin install frontend-craft@frontend-craft
name: fec-doc-sync description: Sync README, docs, environment variables, scripts, API/routing/component descriptions and deployment instructions from code and project sources of truth.
Press `fec-doc-sync` to synchronize front-end project documents. Complex multi-language updates can be delegated to **`fec-doc-updater`**.
1. Read sources of truth: `package.json`, lockfile, config, `.env.example`, routes, API clients/server routes, types/schemas, components, tests, CI, build/deploy config. 2. Compare README, docs, ADR, changelog, example prompts, setup/deploy/env docs. 3. Update stable commands, environment variables, routing/API behavior, component descriptions, deployment steps, version constraints, and migration instructions. 4. Keep key information consistent across multi-language documents. 5. When the target warehouse itself is a skill/agent/command distribution warehouse, the capability table, metadata, runtime docs and marketplace description are also synchronized. 6. Run document consistency, typecheck, test, build or related packaging checks.
Summarize update scope, sources of fact, verification orders and translation risks that still require manual proofreading.
frontend-craft is a universal frontend plugin that brings the same opinionated engineering standards to all 15 AI coding assistants.
Front-end problem diagnosis and repair: covering build failures, runtime errors, UI exceptions, and interface problems, using a…
Initialize frontend-craft project template, rules or downgrade instructions according to the current AI runtime.
Unified front-end planning entrance - implementation/architecture plan or testing strategy. The implementation path is taken by…
Identify and clean up front-end dead code, unused exports, outdated components, styles and dependencies under validation…
Build an ordered behavior-preserving frontend refactoring plan from evidence without editing business code.
Execute controlled behavior-preserving frontend refactoring with small steps, verification, rollback, and proof reporting.
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.