fec-doc-syncUse 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 polish
Install via ClawdBot CLI:
clawdbot install bovinphang/fec-doc-syncGrade 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 Aug 27, 2026 · audit v1.0
Generated Sep 1, 2026
A web development team uses the skill to automatically synchronize README files and documentation with source-of-truth files like package.json and env examples after each sprint. This ensures that commands, environment variables, and setup instructions stay current without manual review. The skill verifies multi-language docs for consistency, saving time and reducing drift.
A SaaS company uses the skill to sync API route documentation, client code, and server routes, ensuring that public API docs match the actual endpoints. It updates examples and version constraints across all language READMEs, improving developer experience and reducing support tickets. The skill also checks for outdated API references in changelogs and setup guides.
DevOps engineers leverage the skill to synchronize deployment guides, build configurations, and environment variable documentation with actual CI/CD configs. It ensures that deployment steps from READMEs match the current pipeline, avoiding misconfigurations. The skill validates command consistency and flags any discrepancies in multi-language runbooks.
An open-source library maintainer uses the skill to sync component APIs, usage examples, and metadata with the codebase before releases. It scans READMEs for stale commands, update examples, and checks all i18n READMEs for consistency in function names and version constraints. The skill outputs a summary of synced files and risks, easing maintenance.
Consultancies or agencies offer automated documentation sync as a subscription-based service for software teams. They periodically run this skill to keep client documentation aligned with code changes, saving development time. Revenue comes from recurring retainers or per-project fees.
Large tech companies adopt the skill internally to reduce documentation drift across multiple small teams. It is installed in CI pipelines to automatically enforce doc accuracy, reducing manual audits and onboarding friction. Revenue is indirect via improved developer velocity and reduced bug reports.
The skill is packaged as a plugin for platforms like GitHub, GitLab, or VS Code, with basic features free and premium features (e.g., multi-language sync, custom rules) paid. It integrates with existing workflows, attracting developers. Revenue from premium licenses and enterprise tier subscriptions.
💬 Integration Tip
Run as part of the CI pipeline after code merges; use the skill's output in PR reviews to ensure documentation updates are explicit.
Scored Sep 1, 2026
Use when building UI with shadcn/ui components, Tailwind CSS layouts, form patterns with react-hook-form and zod, theming, dark mode, sidebar layouts, mobile navigation, or any shadcn component question.
Tailwind reference tool. Use when working with tailwind in frontend contexts.
A product creation skill based on the "Bee Website Builder" Open API. It is used to create a new product under a specified site language and product group, w...
A product update skill based on the "Bee Website Builder" Open API. It is used to update an existing product under a specified site language and supports upd...
Build WCAG 2.1 AA compliant websites with semantic HTML, proper ARIA, focus management, and screen reader support. Includes color contrast (4.5:1 text), keyboard navigation, form labels, and live regions. Use when implementing accessible interfaces, fixing screen reader issues, keyboard navigation, or troubleshooting "focus outline missing", "aria-label required", "insufficient contrast".
Use when building Vue 3 applications with Composition API, Nuxt 3, or Quasar. Invoke for Pinia, TypeScript, PWA, Capacitor mobile apps, Vite configuration.