fec-monorepo-project-standardUse when creating, reviewing, or restructuring frontend monorepos with pnpm workspace, Turborepo, Nx, multi-package dependency boundaries, task orchestration, package naming, or package publishing; Chinese triggers include monorepo, workspace, multi-package.
Install via ClawdBot CLI:
clawdbot install bovinphang/fec-monorepo-project-standardGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://turbo.build/schema.jsonAudited Jun 2, 2026 · audit v1.0
Generated Nov 18, 2026
A frontend platform or infra team is asked to create a new repository that will host multiple web apps (web, admin, docs) plus shared UI, utils, and config packages. They use this skill to scaffold apps/packages/tooling directories, configure pnpm-workspace.yaml and turbo.json, and set workspace:* internal dependencies so builds run in the correct order.
An engineering team inherits a repository with inconsistent package folders, duplicated ESLint/TS configs, and manual dependency versioning. This skill guides the review of directory boundaries, circular dependency checks with pnpm why, and migration of shared configs into packages/config-*, while preserving existing naming and task conventions.
A DevOps or release engineering team wants to reduce CI runtime by caching build/lint/test tasks and running only affected packages on pull requests. The skill helps configure Turborepo/Nx affected commands, cache inputs/outputs, and keeps a full-verification entrypoint on the trunk or release branch.
A design system team maintains a shared UI/component library consumed by multiple apps and published to npm under an @scope. The skill provides guidance on package naming, exports, peer dependencies, version policies, and pre-publish boundary checks to avoid publishing apps as installable packages.
A growing organization with several product squads needs consistent repo conventions so developers can move between projects without relearning structure and commands. This skill provides the canonical directory layout, root task commands, and constraints that new packages and service teams can follow.
Companies monetize indirectly by investing in a platform team that maintains monorepo tooling and standards, reducing build costs and accelerating product delivery across many squads. The value comes from shorter CI times and reuse of shared packages rather than direct software sales.
A subscription SaaS business runs web app, admin console, and docs from one repository with shared UI and config packages. Monorepo standards keep version consistency and allow affected CI runs, improving release velocity for the paid product.
A team publishes an internal or public @scope component library and shared configuration packages from the monorepo. Package naming, workspace:* dependencies, and publish readiness checks support distributing the library to downstream teams or customers.
💬 Integration Tip
Run the skill early during scaffolding or refactor planning so directory, workspace:* , and task-orchestration decisions are applied consistently; pair it with concrete turbo.json/nx.json and CI cache-config review to ensure affected builds never replace full release verification.
Scored Nov 12, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.