fec-accessibility-chec…
Use when reviewing or improving frontend accessibility, semantic structure, keyboard support, focus management, ARIA labels,…
Use when synchronizing frontend project documentation with source-of-truth files such as package.json, lockfiles, config, env examples, routes, API clients or server routes, schemas, components, tests, CI, build/deploy config, ADRs, changelogs, or migration notes. Do not use for
Claude Code
$ npx -y skills add bovinphang/frontend-craft --skill fec-doc-sync --agent claude-code
Codex
$ npx skills add bovinphang/frontend-craft --skill fec-doc-sync -a codex -y
Cursor
$ npx skills add bovinphang/frontend-craft --skill fec-doc-sync -a cursor -y
Gemini CLI
$ npx skills add bovinphang/frontend-craft --skill fec-doc-sync -a gemini-cli -y
GitHub Copilot
$ npx skills add bovinphang/frontend-craft --skill fec-doc-sync -a github-copilot -y
OpenCode
$ npx skills add bovinphang/frontend-craft --skill fec-doc-sync -a opencode -y
Windsurf
$ npx skills add bovinphang/frontend-craft --skill fec-doc-sync -a windsurf -y
name: fec-doc-sync description: Use when synchronizing frontend project documentation with source-of-truth files such as package.json, lockfiles, config, env examples, routes, API clients or server routes, schemas, components, tests, CI, build/deploy config, ADRs, changelogs, or migration notes. Do not use for general prose polishing only; Chinese triggers include document synchronization, update README, docs sync, environment variable documentation, command list, API Document synchronization.
Follow the [common documentation method](references/common/doc-sync.md) for evidence, multilingual consistency and delivery records.
Inspect package.json, lockfiles, framework/build configuration, env examples, routes, API clients/server routes, types/schemas, components, tests, CI and deployment files.
Check root, package, application, deployment and runtime READMEs, docs, ADRs, changelogs, environment and setup guides. Compare routing/API behavior, client integration, support matrices, plugin entry points, commands, report paths, metadata and example prompts.
Check public facts in every existing language. Record sources, changed/unchanged documents and translation review needs using the common method. Use the project's existing content, type, test and packaging checks.
frontend-craft is a universal frontend plugin that brings the same opinionated engineering standards to all 15 AI coding assistants.
Use when reviewing or improving frontend accessibility, semantic structure, keyboard support, focus management, ARIA labels,…
Use when absorbing ideas, capabilities, workflows, architecture, quality systems, ecosystem extensions, or engineering practices…
Use when designing, implementing, or reviewing frontend-to-backend API integration, typed API clients, REST/tRPC/OpenAPI client…
Use when frontend work needs to communicate data, action, state, permission, validation, or business-rule needs to backend teams…
Use when choosing, implementing, or reviewing browser storage such as localStorage, sessionStorage, IndexedDB, cookies, client…
Use when building or reviewing Canvas 2D, Three.js/WebGL, React Three Fiber, GLSL shaders, ShaderToy-to-WebGL adaptation, 2D/3D…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.