Enforce TypeScript best practices with Zod validation, typed tryCatch, and T3 Env.
npx skills add https://github.com/alexejluft/brudi --skill maintaining-quality
Please help me install this Agent Skill. Skill: maintaining-quality Source: https://github.com/alexejluft/brudi/tree/main/skills/maintaining-quality Command: npx skills add https://github.com/alexejluft/brudi --skill maintaining-quality
This Skill addresses common pitfalls in TypeScript development that lead to runtime errors or broken builds, such as unsafe type assertions, poor error handling, insecure environment variable access, and unused imports.
tryCatch utility for predictable error management.eslint-plugin-unused-imports to eliminate unused dependencies.Use the maintaining-quality skill to refactor the provided TypeScript code snippet to include Zod validation for JSON parsing.
High-intent search queries and answers about installing and using this skill.
Type-safe JSON parsing uses Zod schemas to validate external data in TypeScript. This enforces strict typing for parsed JSON and API responses, preventing silent runtime errors and build failures caused by unsafe type assertions in complex projects.
Secure environment variable management uses T3 Env to provide validated, type-safe access in TypeScript projects. This approach prevents broken builds and insecure runtime access by ensuring environment variables are strictly validated before use.
Robust error handling in TypeScript uses a typed tryCatch utility to manage errors predictably. This mechanism replaces unsafe type assertions and helps catch runtime errors gracefully, ensuring complex projects maintain stability during execution.
Automatically removing unused imports uses eslint-plugin-unused-imports to eliminate unused dependencies in TypeScript. This enforces code hygiene and prevents build failures by ensuring the codebase remains clean and maintainable during refactoring.
Yes, Zod and T3 Env work together when refactoring legacy JavaScript to TypeScript. Zod enforces type-safe JSON parsing and API validation, while T3 Env secures environment variables, ensuring external data is validated and errors are caught gracefully.
Unsafe type assertions cause build failures and runtime errors in TypeScript by bypassing strict type checking. Replacing them with Zod schema validation for external data ensures type safety, preventing silent runtime errors common in complex projects.
hivellmAutomates TypeScript project setup with strict mode, Vitest, ESLint, and CI/CD templates.
TabTabGoGenerate, edit, and validate Expo EAS workflow YAML files against schema standards.
carayaEnforce consistent TypeScript formatting with Prettier and ESLint configurations.
BerryKuipersRun TypeScript type checking with tsc --noEmit and report errors by category.