rara-skills

Use when designing BDD features, writing Gherkin acceptance criteria, decomposing requirements into testable scenarios, creating GitHub issues with .feature specs, or specifying acceptance criteria for the implementation agent. Keywords: BDD design, Gherkin, acceptance criteria, feature spec, scenario design, requirement decomposition.

Use when implementing a BDD-specced GitHub issue, writing step definitions, delivering code with passing cucumber tests, or picking up an agent-designed feature task. Keywords: BDD implement, step definition, cucumber test, implement issue, feature implementation, agent task.

Use when reviewing .feature files for quality before issue creation, validating Gherkin acceptance criteria against BDD best practices, or checking feature specs during the plan phase. Keywords: BDD review, Gherkin review, feature review, acceptance criteria review, quality gate, plan review.

Use when implementing features, fixing bugs, reviewing code, creating PRs, or performing any code-related development task.

Guido van Rossum 的思维框架与表达方式。基于 PEP 8 / PEP 20 / PEP 572 / PEP 703 等核心文档、 Lex Fridman 两次长谈、2018 年 "Transfer of Power" 邮件、PyCon 历年 keynote、 Microsoft 时期 Faster CPython 公开言论的深度调研，提炼 6 个核心心智模型、 8 条决策启发式与完整表达 DNA。Guido 是 Python 之父（1989 圣诞节起源于 CWI）， 前 BDFL（2018.7 卸任），现 Microsoft Distinguished Engineer，Faster CPython 项目推动者。 用途：作为思维顾问，用 Guido 的视角分析语言设计、API 设计、可读性、向后兼容、 开源治理、Python 生态、渐进式类型、解释器性能、技术决策与社区沟通这类问题。 当用户提到「用 Guido 的视角」「Guido 会怎么看」「BDFL 模式」「guido perspective」时使用。 即使用户只是说「从 Python 之父的角度想想」「如果 Guido 来设计这个 API」「切换到 Guido」也应触发。 也适用于：Python 语言演化、PEP 流程、可读性 vs 灵活性的取舍、print as function 这类 breaking change 的取舍、类型注解设计、GIL 去除的渐进策略、语言 UI 设计哲学这类话题。

2 hooks across 1 event