找出TypeScript中绕过类型检查的any，协助改用unknown、泛型或外部数据验证，并说明各使用位置所需的类型检查与修改。
Use when reviewing TypeScript files for type safety regressions, during code review of functions that handle external data, or when the codebase has ESLint warnings for @typescript-eslint/no-explicit-any.
找出TypeScript代码中的any，协助替换为能发挥类型检查作用的写法。检查范围包括显式类型标注、缺少类型信息或依赖项没有类型信息而产生的隐式any，以及断言为any的写法。对于结构未知的值，建议使用unknown；对于需要保持类型关系的操作，建议使用泛型；对于外部数据，建议通过Zod验证，并说明各使用位置需要进行的类型检查。
适合修复ESLint的@typescript-eslint/no-explicit-any警告，或审查API返回数据的处理方式。也会检查函数返回值将any传播到调用方的位置。还可用于解释unknown与any的区别，以及as Type类型断言在什么情况下合理、什么情况下存在风险。
any，并提出替代方案。”any替换为Zod验证。”适用对象为TypeScript代码。外部数据的验证方案使用Zod。
本介绍由 AI（OpenAI Codex）根据公开的 SKILL.md 撰写。准确的规格请查看下方原文。
AI 仅根据 SKILL.md 的内容，从 4 个方面进行了评估。星标数和热度不计入评估。
总分按每项 A=25 分、B=15 分、C=5 分相加。 由 AI（OpenAI Codex）于 2026年10月23日 评估。仅供参考，安装前请同时查看原文。
安装前可以查看交给 AI 代理的指令内容。
The any type is a local opt-out that becomes a global problem: a function returning any propagates unchecked types to every caller, silently undermining the type system across the entire codebase. Replacing any with unknown forces type narrowing at the point of use, turning latent runtime errors into compile-time failures where they are cheapest to fix.
Scan this TypeScript file for uses of the any type (explicit annotations, implicit any from missing types, and type assertions to any). Report each location and suggest a safer alternative.
Replace the any types in this code with unknown (for values of unknown shape), appropriate generics (for type-consistent operations), or Zod validation (for external data). Show the narrowing or generic constraint needed at each usage site.
Explain why the any type undermines TypeScript's guarantees, how unknown differs from any, and when a type assertion (as Type) is acceptable versus dangerous.
Review all type annotations, function signatures, and external data handling in this file. Flag every explicit or implicit any, any type assertion that lacks a preceding type guard, and any return types inferred as any from untyped dependencies.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/javascript/no-explicit-any
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
中文简介正在准备中。当前显示英语简介。
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
中文简介正在准备中。当前显示英语简介。
为页面和共用组件添加自动无障碍测试，检查现有测试的覆盖缺口，并将检查接入持续集成流程，以发现结构、属性问题及修改引入的新问题。
检查从登录、多因素认证到账户恢复的完整流程，找出禁止粘贴、验证码必须手动输入等使用障碍，并协助改进认证方式。
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
中文简介正在准备中。当前显示英语简介。
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.
中文简介正在准备中。当前显示英语简介。