重要前提
安装AI Skills的关键前提是:必须科学上网,且开启TUN模式,这一点至关重要,直接决定安装能否顺利完成,在此郑重提醒三遍:科学上网,科学上网,科学上网。查看完整安装教程 →
angular-best-practices-rules-reviewer by alfredoperez/angular-best-practices
npx skills add https://github.com/alfredoperez/angular-best-practices --skill angular-best-practices-rules-reviewer审查 Angular 最佳实践规则的准确性、有效性和实用性。
验证每条规则对于 Angular 开发而言是否合法、准确且有价值。不要只检查格式——要验证该规则是否是一个真正的最佳实践。
根据以下标准评估每条规则:
| 标准 | 移除 | 改进 | 保留 |
|---|---|---|---|
| AI 会犯这个错误吗? | AI 已经知道这个 | 取决于上下文 | AI 常犯这个错误 |
| AI 能发现这个吗? | 在 Angular 文档中很容易找到 | 文档存在但很分散 | 文档中没有的部落知识 |
| 指导是否足够具体? | 太模糊("在适当时使用") |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 有一些细节但缺少阈值 |
| 清晰、可衡量的标准 |
| 它能防止真正的错误吗? | 仅是风格偏好 | 小问题 | 防止错误、内存泄漏或性能问题 |
评分:统计"保留"答案的数量 (0-4)
阅读 config/criteria.json 了解确切的格式阈值。
为每条规则生成结构化审查报告:
## 规则审查:[rule-name.md]
### 实用性评估
| 标准 | 评级 | 备注 |
|----------|--------|-------|
| AI 会犯这个错误吗? | 保留/改进/移除 | [解释] |
| AI 能发现这个吗? | 保留/改进/移除 | [解释] |
| 指导是否足够具体? | 保留/改进/移除 | [解释] |
| 它能防止真正的错误吗? | 保留/改进/移除 | [解释] |
**实用性评分:** X/4
### 有效性:有效 | 存疑 | 无效
**证据:** [指向 Angular 文档、博客文章、讨论的链接]
### 准确性:准确 | 过时 | 不正确
**Angular 版本:** 针对 Angular 17+ 测试
**代码问题:** [任何语法错误、已弃用的 API 或问题]
### 格式:通过 | 小问题 | 大问题
**行数:** X/50
**代码块:** X (最多 2 个)
### 裁决:保留 | 改进 | 移除
**建议:** [需要做的具体更改或移除原因]
Review rules/typescript/ts-readonly.md
执行包含研究的完整有效性 + 准确性 + 价值 + 格式检查。
Audit all rules in rules/core/
审查多条规则。阅读 prompts/audit-batch.md 了解批量审计输出模板。
Is rules/angular/signal-computed.md a real best practice?
侧重于有效性和证据的快速检查。
Rewrite rules/core/pattern-facade.md to be more actionable
根据审查结果改进规则。
当审查 SKILL.md 文件(非规则文件)时,请阅读 references/skill-best-practices.md 了解质量标准。评估前言元数据、目录结构、指令语气和负面触发词。
有些规则更适合作为带有行内代码的单句,而不是代码块:
在以下情况转换为纯文本格式:
import type 与 import { type })PascalCase")在以下情况下使用错误和正确的示例:
catchError 的位置)mergeMap 与 switchMap)好的示例:
臃肿的迹象:
移除以下情况的规则:
不好:"在状态复杂时使用" 好:"在组件协调 3 个以上具有相互依赖异步操作的服务时使用"
不好:"不需要时避免使用" 好:"当只有 2 个变体且预期不会增长时避免使用"
在批准规则之前:
每周安装次数
46
代码仓库
GitHub 星标数
19
首次出现
2026年2月16日
安全审计
安装于
codex44
opencode43
github-copilot43
gemini-cli42
amp42
kimi-cli42
Review Angular best practice rules for accuracy, validity, and usefulness.
Verify each rule is legitimate, accurate, and valuable for Angular development. Don't just check formatting—verify the rule is a real best practice.
Evaluate each rule against these criteria:
| Criteria | Remove | Improve | Keep |
|---|---|---|---|
| Would AI make this mistake? | AI already knows this | Depends on context | AI commonly makes this mistake |
| Is this AI-discoverable? | Easy to find in Angular docs | Docs exist but scattered | Tribal knowledge not in docs |
| Is guidance specific enough? | Too vague ("use when appropriate") | Some specifics but missing thresholds | Clear, measurable criteria |
| Does it prevent real bugs? | Style preference only | Minor issues | Prevents bugs, memory leaks, or perf issues |
Score: Count Keep answers (0-4)
Read config/criteria.json for exact format thresholds.
Produce a structured review for each rule:
## Rule Review: [rule-name.md]
### Usefulness Assessment
| Criteria | Rating | Notes |
|----------|--------|-------|
| Would AI make this mistake? | Keep/Improve/Remove | [Explain] |
| Is this AI-discoverable? | Keep/Improve/Remove | [Explain] |
| Is guidance specific enough? | Keep/Improve/Remove | [Explain] |
| Does it prevent real bugs? | Keep/Improve/Remove | [Explain] |
**Usefulness Score:** X/4
### Validity: VALID | QUESTIONABLE | INVALID
**Evidence:** [Links to Angular docs, blog posts, discussions]
### Accuracy: ACCURATE | OUTDATED | INCORRECT
**Angular Version:** Tested against Angular 17+
**Code Issues:** [Any syntax errors, deprecated APIs, or problems]
### Format: PASS | MINOR ISSUES | MAJOR ISSUES
**Lines:** X/50
**Code Blocks:** X (max 2)
### Verdict: KEEP | IMPROVE | REMOVE
**Recommendation:** [Specific changes needed or removal reason]
Review rules/typescript/ts-readonly.md
Perform full validity + accuracy + value + format check with research.
Audit all rules in rules/core/
Review multiple rules. Read prompts/audit-batch.md for the batch audit output template.
Is rules/angular/signal-computed.md a real best practice?
Fast check focusing on validity with evidence.
Rewrite rules/core/pattern-facade.md to be more actionable
Improve rule based on review findings.
When reviewing a SKILL.md file (not a rule file), read references/skill-best-practices.md for quality criteria. Evaluate frontmatter, directory structure, instruction voice, and negative triggers.
Some rules work better as a single sentence with inline code instead of code blocks:
Convert to TEXT-ONLY when:
import type vs import { type })PascalCase for types")Use both incorrect and correct examples when:
catchError placement in RxJS)mergeMap vs switchMap)Good examples:
Signs of bloat:
Remove rules where:
Bad: "Use when you have complex state" Good: "Use when components orchestrate 3+ services with interdependent async operations"
Bad: "Avoid when not needed" Good: "Avoid when you have only 2 variants with no expected growth"
Before approving a rule:
Weekly Installs
46
Repository
GitHub Stars
19
First Seen
Feb 16, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
codex44
opencode43
github-copilot43
gemini-cli42
amp42
kimi-cli42
Skills CLI 使用指南:AI Agent 技能包管理器安装与管理教程
48,700 周安装