fec-typescript-project-standardUse when creating, configuring, reviewing, or debugging TypeScript project standards across frontend apps, libraries, SDKs, CLIs, monorepo packages, tsconfig, strictness, module/moduleResolution, path aliases, project references, declaration files, package exports, public API types, DTOs, advanced g
Install via ClawdBot CLI:
clawdbot install bovinphang/fec-typescript-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://github.com/bovinphang/frontend-craftAudited Nov 19, 2026 · audit v1.0
Generated Nov 18, 2026
A product team notices its Vite build passes in CI while editors and reviewers keep hitting implicit any and null-checking errors in production code. The skill is used to layer base, app, test, and declaration tsconfigs with strict flags, align path aliases across bundler and test runner, and add a standalone typecheck script. It results in a predictable strictness policy that does not get silently relaxed to make builds green.
A design-system team is about to publish a React component library and needs consumers to get parseable type declarations without leaking source-only aliases or test fixtures. The skill guides exports/types/files alignment in package.json, emitDeclarationOnly declaration generation, peer dependency typing, and pre-release pack dry-runs. Public props and DTOs are modeled with explicit API types while internal variables stay inferred.
A monorepo with app, shared, and SDK packages suffers from slow incremental builds and workspace path aliases leaking into published artifacts. The skill is applied to set up project references and composite builds, define inter-package import boundaries, and keep workspace aliases out of release products. Type-level regressions across packages are caught through consumer fixtures and compile-time assertions.
An SDK author receives unknown API payloads and currently widens everything with as-casts, causing downstream runtime failures. The skill drives receiving external data as unknown, narrowing via schema or type guards, and layering DTO, domain model, and public function signatures with discriminated unions where useful. Advanced reference patterns support generics and DTO mapping without compromising type safety.
A Node CLI project mixes ESM and CJS concerns, and its published type entry is ambiguous for consumers. The skill is used to establish Node target versions, moduleResolution, and an explicit ESM/CJS policy, avoiding dual publishing unless clearly needed, and verifying shebang artifacts and process.env typing. Release checks confirm declarations resolve for consumers.
Teams pay for standardized TypeScript project scaffolding, lint rules, tsconfig presets, and CI typecheck templates maintained over time. The skill's convergence and verification procedures become the documented standard deliverable for subscribers.
Maintainers of component libraries and SDKs engage experts for pre-release type audits covering declarations, package exports, and consumer fixtures. Each engagement applies the skill's release and type-boundary procedure to a specific package.
Organizations purchase workshops on tsconfig layering, type modeling, generics, discriminated unions, and release product boundaries. Certification validates that engineers can apply the standard independently across monorepos and libraries.
💬 Integration Tip
Route this skill from project setup or PR review prompts when tsconfig, package exports, or public API types change, and pair it with the relevant framework skill so component architecture decisions stay out of scope. Always add a standalone CI typecheck plus pack dry-run so release products match the declared types.
Scored Nov 19, 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.