tech-react

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Rules

规则

See rules index for detailed patterns.
详见规则索引获取详细模式。

Examples

示例

Positive Trigger

触发场景

User: "Refactor this React component to reduce re-renders and clarify hook usage."
Expected behavior: Use
tech-react
guidance, follow its workflow, and return actionable output.
用户:“重构这个React组件以减少重渲染并明确Hook的使用方式。”
预期行为:遵循
tech-react
指南,按照其工作流程执行,返回可落地的输出结果。

Non-Trigger

非触发场景

User: "Write a Bash script to package release artifacts."
Expected behavior: Do not prioritize
tech-react
; choose a more relevant skill or proceed without it.
用户:“编写一个Bash脚本打包发布制品。”
预期行为:不优先使用
tech-react
;选择更相关的技能或直接处理任务。

Troubleshooting

故障排查

Skill Does Not Trigger

技能未触发

  • Error: The skill is not selected when expected.
  • Cause: Request wording does not clearly match the description trigger conditions.
  • Solution: Rephrase with explicit domain/task keywords from the description and retry.
  • 错误:未按预期选中该技能。
  • 原因:请求表述未明确匹配描述中的触发条件。
  • 解决方案:使用描述中的明确领域/任务关键词重新表述请求后重试。

Guidance Conflicts With Another Skill

指南与其他技能冲突

  • Error: Instructions from multiple skills conflict in one task.
  • Cause: Overlapping scope across loaded skills.
  • Solution: State which skill is authoritative for the current step and apply that workflow first.
  • 错误:同一任务中多个技能的指令存在冲突。
  • 原因:已加载的技能存在范围重叠。
  • 解决方案:指定当前步骤以哪个技能为权威,优先应用该技能的工作流程。

Output Is Too Generic

输出过于笼统

  • Error: Result lacks concrete, actionable detail.
  • Cause: Task input omitted context, constraints, or target format.
  • Solution: Add specific constraints (environment, scope, format, success criteria) and rerun.
  • 错误:结果缺乏具体、可落地的细节。
  • 原因:任务输入遗漏了上下文、约束条件或目标格式。
  • 解决方案:添加具体约束(环境、范围、格式、成功标准)后重新运行。

Workflow

工作流程

  1. Identify whether the request clearly matches
    tech-react
    scope and triggers.
  2. Apply the skill rules and referenced guidance to produce a concrete result.
  3. Validate output quality against constraints; if gaps remain, refine once with explicit assumptions.
  1. 判断请求是否明确匹配
    tech-react
    的范围与触发条件。
  2. 应用技能规则及相关指南生成具体结果。
  3. 根据约束条件验证输出质量;若仍存在不足,基于明确假设优化一次。