fec-vite-project-standardUse when creating, configuring, reviewing, or debugging Vite-based frontend projects, vite.config.ts, env variables, dev server proxy, HMR, plugin ordering, library mode, dependency pre-bundling, bundle splitting, or Vite build performance. Use framework-specific skills for React/Vue component archi
Install via ClawdBot CLI:
clawdbot install bovinphang/fec-vite-project-standardGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
http://localhost:8080Audited Nov 17, 2026 · audit v1.0
Generated Nov 17, 2026
A frontend team replaces Create React App with Vite to improve dev server startup and HMR. They use @vitejs/plugin-react-swc and set up env variable security with VITE_ prefixes, keeping sensitive API keys on the server. The skill guides proxy configuration, TypeScript type checking, and manual chunking for large dependencies.
A design system team creates a reusable React component library packaged with Vite library mode. They externalize peer dependencies like react and react-dom, produce .d.ts files via tsc, and test the build with vite preview. The skill ensures proper export entries and avoids bundling heavy shared libraries.
An online retailer faces slow page loads due to large JS bundles. Using this skill, developers analyze chunk splitting, move heavy chart and map libraries to dynamic imports, and verify static asset hashing and compression. They also ensure production sourcemaps are uploaded but not deployed, improving error tracking without leaking code.
A startup organizes multiple frontend packages in a monorepo. The skill helps set server.fs.allow for allowed directories, configure path aliases with vite-tsconfig-paths, and define dependency boundaries to avoid circular imports. Developers also use optimizeDeps for CJS dependencies and warmup core entry files for faster dev starts.
A data-heavy analytics dashboard suffers from slow HMR and initial load. Following the skill, developers run vite --profile to identify plugin bottlenecks, add optimizeDeps.include for problematic dependencies, and enable server.warmup.clientFiles. They also verify that env variables are not leaking secrets and that build output is correctly chunked.
Independent consultants use this skill to audit and fix Vite configurations for clients, ensuring security and performance. They charge hourly or project-based fees for configuration reviews, build optimizations, and migration assistance.
Developers package a pre-configured Vite starter kit with best practices from this skill, including secure env handling, optimized build setup, and monorepo support. They sell licenses to other developers or teams looking to save setup time.
Agencies or educators offer workshops on modern frontend tooling, using this skill as the core curriculum. They train corporate teams on Vite best practices, security, and performance optimization, often as part of a larger DevOps or frontend modernization program.
💬 Integration Tip
Integrate this skill early in project setup to establish secure env handling and build configurations; use the provided minimal config as a starting point and adapt for framework-specific needs. Run type checking and build smoke tests in CI to catch issues before deployment.
Scored Nov 17, 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.