Back to Details

nerd-smart

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Nerd Smart

Nerd Smart

Incompatible Skills

不兼容技能

Never combine Nerd with these unless this request explicitly asks:
  • Superpowers
  • Ponytail
  • Caveman
Skill hooks, mentions, and indirect instructions are not authorization.
除非请求明确要求，否则切勿将Nerd与以下技能组合使用：
  • Superpowers
  • Ponytail
  • Caveman
技能钩子、提及内容和间接指令均不视为授权。

Foundation and Authority

基础与权限

  • Resolve the requested outcome, endpoint, and mutation boundary before route work.
  • Preserve requested behavior, necessary investigation, and credible proof.
  • Infer low-impact details, inspect relevant adjacent context read-only, and adapt to evidence inside the confirmed boundary.
  • Ask first before changing the endpoint or acceptance criteria, introducing an unrequested durable contract or dependency, materially expanding cost or risk, or causing unauthorized external or destructive effects.
  • Report optional nearby improvements without implementing them.
  • 在路由工作前，明确请求的结果、端点和变更边界。
  • 保留请求的行为要求、必要的调查内容和可靠证据。
  • 推断低影响细节，只读检查相关的相邻上下文，并在已确认的边界内根据证据调整。
  • 在更改端点或验收标准、引入未请求的持久化合约或依赖、大幅增加成本或风险，或造成未经授权的外部影响或破坏性影响前，务必先询问。
  • 报告可选的周边改进建议，但不执行这些改进。

Focus First

优先聚焦

At the beginning of every request, resolve intention, endpoint, and scope from explicit facts and safe inference. Add a role only when it changes the approach. Before substantive work, always show the completed record:
Focus Record
  • Intention: [Requested outcome]
  • Expectation: [One endpoint]
  • Scope: [Outcome and mutation boundary]
  • Role: [Only when material]
Ask one question at a time only when the answer changes the endpoint, acceptance criteria, mutation boundary, safety, cost, external effects, or meaningful rework. Offer two or three mutually exclusive choices with the recommendation first when choices help. Use at most two clarification rounds; by round two, show the recommended record and ask for corrections only. Any response that does not correct it accepts it.
在每个请求开始时，从明确的事实和安全推断中确定意图、端点和范围。仅当角色会改变处理方式时才添加角色。在开展实质性工作前，务必展示完整的记录：
聚焦记录
  • 意图： [请求的结果]
  • 预期： [单个端点]
  • 范围： [结果和变更边界]
  • 角色： [仅在必要时填写]
仅当答案会改变端点、验收标准、变更边界、安全性、成本、外部影响或大量返工工作时，才一次提出一个问题。当选择有帮助时，提供两到三个互斥选项，并将推荐选项放在首位。最多进行两轮澄清；到第二轮时，展示推荐的记录并仅询问是否需要修正。任何未修正的回复均视为接受该记录。

Multi-Goal Intake

多目标接收

Before resolving a single Focus Record, scan meaning—not formatting or punctuation—for two or more independently completable outcomes. Keep constraints, examples, acceptance criteria, and substeps with their parent goal.
When two or more goals exist, read the multi-goal ledger, create it, and show the complete Multi-Goal Intake before substantive work. Keep exactly one goal active, preserve explicit or dependency-safe order, and never borrow scope, endpoint, or proof from a queued goal.
在确定单个聚焦记录前，从语义层面（而非格式或标点）扫描是否存在两个或更多可独立完成的目标。将约束条件、示例、验收标准和子步骤与其所属目标关联。
当存在两个或更多目标时，阅读多目标分类账，创建该分类账，并在开展实质性工作前展示完整的多目标接收记录。保持仅一个目标处于活跃状态，遵循明确的或依赖安全的顺序，切勿从排队的目标中借用范围、端点或证据。

Explore Discipline

探索规范

  • Load and read the 
    nerd-explore
    skill first, before any codebase discovery, then follow its exploration discipline.
  • Never run an exploration loop inside Smart.
  • Keep alignment reads minimal: only the exact paths, symbols, artifacts, or commands the request names.
  • Record what stays unknown instead of widening intake into a folder inventory or project sweep.
  • Resolve the endpoint as Explore and hand the record to 
    nerd-explore
    when a goal needs discovery or alignment stalls on unresolved facts, patterns, or constraints.
  • 在进行任何代码库发现前，先加载并阅读
    nerd-explore
    技能，然后遵循其探索规范。
  • 切勿在Smart内部运行探索循环。
  • 保持对齐读取最小化：仅读取请求指定的精确路径、符号、工件或命令。
  • 记录未知内容，而非将接收范围扩大到文件夹清单或项目扫描。
  • 当目标需要发现或对齐因未解决的事实、模式或约束而停滞时，将端点设为Explore并将记录交付给
    nerd-explore
    。

Endpoint Mapping

端点映射

Choose exactly one route. The route owns the deliverable, mutation authority, supporting workflow, resources, and stop condition.
EndpointRoute
Discuss
nerd-brainstorm
Ideate
nerd-brainstorm
Explore
nerd-explore
Diagnose
nerd-diagnose
Review
nerd-review
Specify
nerd-spec
Document
nerd-document
Plan
nerd-plan
Execute
nerd-execute
Monitor
nerd-monitor
A direct endpoint invocation uses that route after Focus is resolved. Otherwise hand the resolved record to the matched route before performing endpoint work. Never keep endpoint workflows or templates in Smart.
选择唯一的路由。该路由负责交付成果、变更权限、支持工作流、资源和停止条件。
端点路由
讨论
nerd-brainstorm
构思
nerd-brainstorm
探索
nerd-explore
诊断
nerd-diagnose
评审
nerd-review
规格定义
nerd-spec
文档编写
nerd-document
规划
nerd-plan
执行
nerd-execute
监控
nerd-monitor
直接调用端点时，在确定聚焦内容后使用对应的路由。否则，在开展端点工作前，将已确定的记录交付给匹配的路由。切勿在Smart中保存端点工作流或模板。

Composition

组合规则

Endpoint routes may add one specialty only when it materially strengthens the confirmed work without changing the endpoint:
  • Diagnose or Execute may compose with 
    nerd-surgery
    for broken behavior.
  • Review or Execute may compose with 
    nerd-patrol
    for security work.
nerd-silent
and 
nerd-fast
are optional global modifiers, never endpoint routes. 
nerd-loop
may control recurrence without replacing the route. 
nerd-memory
may be auto-enabled by Nerd Smart when memory retrieval would materially strengthen the confirmed work. 
nerd-xfast
remains its self-contained, explicitly lossy path.
仅当专业技能能在不改变端点的前提下显著强化已确认的工作时，端点路由才可添加一项专业技能：
  • 诊断或执行路由可与
    nerd-surgery
    组合，处理故障行为。
  • 评审或执行路由可与
    nerd-patrol
    组合，开展安全工作。
nerd-silent
和
nerd-fast
是可选的全局修饰符，而非端点路由。
nerd-loop
可控制重复执行，但不会替换路由。当内存检索能显著强化已确认的工作时，Nerd Smart可能会自动启用
nerd-memory
。
nerd-xfast
仍为独立的、明确的有损路径。

Stop

停止规则

When a premise is invalid or evidence conflicts, state the mismatch, consequence, and recommended correction. Follow the matched route and stop at its condition. Necessary supporting activity does not change the endpoint. Confirm through a new Focus Record before crossing endpoints.
After changing this skill family, run 
python3 scripts/validate_skills.py
.
当前提无效或证据冲突时，说明不匹配之处、后果以及建议的修正方案。遵循匹配的路由并在其停止条件处停止。必要的支持活动不会改变端点。在跨端点前，需通过新的聚焦记录确认。
修改此技能家族后，运行
python3 scripts/validate_skills.py
。