Unified front-end planning entrance - implementation/architecture plan or testing strategy. The implementation path is taken by default; when the user clearly wants test plan, coverage matrix, test layering, risk-to-test, etc., the complete test strategy is output.
Create a standard directory structure and template files for pages, features, or components according to project specifications. Usage: /fec-scaffold , such as /fec-scaffold page UserDetail.
Use front-end TDD workflow to implement functions, fix bugs, or refactor logic: first write failing tests, then implement minimal code, and then refactor.
Runs after a tool call finishes for Write, Edit and MultiEdit tool calls, executing fec-format-changed-file.js via node. From bovinphang/frontend-craft.
A front-end accessibility review guide for checking whether websites and interfaces work for people with disabilities, including keyboard and screen-reader users. It uses WCAG 2.2 AA, a set of web accessibility guidelines, as its reference.
A project adaptation workflow for studying another system and redesigning selected ideas or practices for the current project. It treats the other system as a source of inspiration and evidence rather than a codebase to copy.
A guide for connecting front-end code to back-end APIs, including typed clients, authentication, errors, uploads, and live connections such as SSE or WebSockets.
A document that explains what a front-end screen needs from a back-end team: data, user actions, states, permissions, validation, and business rules. It describes the need without deciding the API or database design.
A guide for choosing and implementing browser storage, which lets a website keep data on a user’s device. It covers localStorage, sessionStorage, IndexedDB, cookies, offline data, security, and cleanup.
A guide for building and reviewing browser graphics with Canvas 2D, Three.js, WebGL, React Three Fiber, and GLSL shaders. Canvas is a browser drawing surface, while WebGL and Three.js support GPU-based 3D graphics.
A guide for writing and reviewing front-end unit, component, and lightweight integration tests. These tests check small pieces of code and UI behavior without running a full browser journey.
A frontend guide for handling data that comes from a server, including typed requests, caching, refreshing, pagination, and updates. Server state means data owned by an API rather than by a page’s local controls.
A step-by-step method for finding the cause of front-end build failures, browser errors, broken screens, failed requests, or incorrect data. It separates build, runtime, visual, and API problems and uses evidence to test possible causes.
A frontend dependency-upgrade guide for planning and reviewing package updates, migrations, lockfile changes, security fixes, and major framework upgrades.
A workflow for keeping front-end project documentation aligned with the code and configuration that actually exist. It checks sources such as package files, routes, API clients, schemas, tests, continuous-integration settings, deployment files, and environment examples.
An editable workflow for making technical diagrams in draw.io (also called diagrams.net), with the original .drawio file saved alongside exported images or documents. It covers architecture, database, UML, sequence, flow, machine-learning, and code-structure diagrams.
A standard for real-browser end-to-end tests, which test complete user journeys across pages rather than isolated functions. It covers Playwright or Cypress, reusable page objects, test data, continuous-integration reports, screenshots, traces, videos, and unstable tests.