Agent Skills
› NeverSight/learn-skills.dev
› blue-red-team
blue-red-team
GitHub针对SolTechnology.Core设计决策进行蓝红队对抗分析，评估方案可行性与风险。在ADR前使用，确保论点具体且符合Tale Code规范，最终输出争议点及建议。
Trigger Scenarios
决定引入新模块或公共API
选择技术模式（如Result vs异常）
准备编写架构决策记录(ADR)
评估破坏性变更
Install
npx skills add NeverSight/learn-skills.dev --skill blue-red-team -g -y
SKILL.md
Frontmatter
{
"name": "blue-red-team",
"description": "Evaluate a SolTechnology.Core design decision from both supportive (Blue) and skeptical (Red) perspectives. Companion to premortem for ADR-grade choices."
}
Blue / Red Team
Adversarial thinking for design-level decisions in SolTechnology.Core (new module, public API shape, framework choice, breaking change).
Use this skill alongside premortem:
- blue-red-team answers should we do this at all?
- premortem answers if we do this, how does it fail?
When to use
- Before opening an ADR — the Blue/Red output seeds the Decision and Alternatives Considered sections.
- When choosing between two patterns within Tale Code (e.g. Result vs exception, Chain handler vs single handler, Story step vs CQRS handler).
- When introducing a new module to
src/SolTechnology.Core.*.
Critical rules
- No strawmen. Make the strongest honest case for each side.
- Be specific to this repo. Cite modules, files, ADRs, sample apps — not generic industry talking points.
- Tale Code lens. Both sides must address readability and prose-like flow (see docs/ClaudeCodingGuide.md).
Process
1. State the proposal
One sentence. Include the concrete change (file / module / API shape).
2. Blue team — arguments for
Consider:
- Tale Code readability win — does it read more like prose?
- Consistency with existing modules (CQRS, Story, Logging patterns).
- Reduction in NuGet API surface or removal of foot-guns.
- Test simplification, fewer mocks, smaller files (class-size budget).
- Strategic alignment with docs/theDesign.md.
3. Red team — arguments against
Consider:
- Breaking change for public NuGet consumers (semver MAJOR cost).
- Hidden complexity moved, not removed.
- Performance / allocation cost.
- New cross-module coupling (
SolTechnology.Core.Xnow needsY). - Build-side fallout (
TreatWarningsAsErrors, analyzer noise). - Migration cost for sample apps and external consumers.
4. Reconcile
Identify the cruxes — points where Blue and Red disagree on fact, not preference. For each crux, state what evidence would settle it (a benchmark, a prototype, a consumer survey, an ADR).
Output format
Proposal
Blue Team
argument with file / module / ADR reference
Red Team
argument with file / module / ADR reference
Cruxes
disputed fact + evidence that would settle it
Recommendation
Version History
- e0220ca Current 2026-07-05 23:31
