菜单
Use halo-effect analysis for first impressions and perception spillover. Use when brand polish, visual quality, flagship features, reviews, or spokesperson credibility may shape trust in unrelated product areas; avoid for general trust, social proof, or readability problems.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Analyze a list of open questions and suggest up to three answers for each. Use when the user wants options, recommendations, or help resolving multiple unanswered questions.
Deliver a PRD through orchestrated task decomposition, implementation agents, and independent QA. Use when every acceptance criterion must be verified before completion.
Explain changes made yesterday as a simple list. Use when user asks what changed yesterday, what was implemented yesterday, or needs a non-technical change summary from recent git work.
Pressure-test, reduce, and rewrite prompts for GPT-5.5. Use when the user asks to grill, audit, critique, harden, improve, optimize, simplify, de-noise, or rewrite a prompt, system prompt, developer instruction, agent playbook, or tool-use workflow specifically for GPT-5.5; especially when it may contain no-op instructions, contradictions, vague rules, missing success criteria, missing output rules, missing validation, unsupported claims, or unclear stop rules.
Build shared understanding before action by interviewing the user about ambiguous implementation, product, planning, or design tasks. Use when goal, scope, constraints, risks, success criteria, done state, or next action are unclear; when user wants a thinking partner; or when user needs a handoff-ready task prompt. Do not write PRDs; use to-prd for product requirements.
Detect sloppy-code signals with repo-wide search metrics and sampled evidence. Use when asked to audit codebase quality, "vibe coding", `isRecord`, broad `Record<string, unknown>` guards, fallback usage, excessive null guards, non-null assertions, unsafe type assertions, `node:*` imports in browser/shared code, swallowed errors, TODO debt, or code smell hotspots before refactoring.
| name | halo-effect-psychology |
| description | Use halo-effect analysis for first impressions and perception spillover. Use when brand polish, visual quality, flagship features, reviews, or spokesperson credibility may shape trust in unrelated product areas; avoid for general trust, social proof, or readability problems. |
One strong first impression changes how users judge everything else. Positive halo lifts trust. Negative halo creates horn effect.
## Halo Effect Analysis
Product or feature: [name]
## First Impression Points
- [touchpoint]: [current perception]
## Halo Triggers
- [positive signal]
- [positive signal]
## Horn Risks
- [risk] -> [impact]
## Recommendations
- Quick win: [fix]
- Strategic polish: [investment]
- Risk mitigation: [fix]