القائمة
Behavior-Driven Development with pytest-bdd. ALWAYS invoke when writing Gherkin scenarios, pytest-bdd step definitions, or any BDD acceptance tests. Never write feature files without this skill loaded.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
AWS credential management with awsume. ALWAYS invoke when assuming AWS roles, listing accounts, switching profiles, or running any awsume command. Do not guess flags from memory.
Commit message convention. ALWAYS invoke before creating any git commit or writing a commit message. Never format a commit without this skill loaded.
Domain-Driven Design tactical patterns. ALWAYS invoke when implementing aggregates, entities, value objects, repositories, or domain events in Python. Prevents common DDD mistakes (anemic models, multi-aggregate transactions).
Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use this skill whenever the user asks about a specific library, framework, SDK, CLI tool, or cloud service -- even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Use even when you think you know the answer -- do not rely on training data for API details, signatures, or configuration options as they are frequently outdated. Always verify against current docs. Prefer this over web search for library documentation and API details.
Git branch comparison and diff workflows using worktrees. ALWAYS invoke when comparing branches, diffing synth output, or needing to work with multiple branches simultaneously. Never stash or checkout to compare — use worktrees.
AWS Lambda Powertools Logger gotchas and patterns. ALWAYS invoke when working with Powertools Logger, Lambda logging, or structured logging. Reserved key collisions cause runtime KeyErrors — do not answer from memory.
| name | bdd |
| description | Behavior-Driven Development with pytest-bdd. ALWAYS invoke when writing Gherkin scenarios, pytest-bdd step definitions, or any BDD acceptance tests. Never write feature files without this skill loaded. |
SOP for BDD with pytest-bdd. You MUST invoke before writing any Gherkin feature file or step definitions. BDD is for acceptance and integration tests — you MUST NOT use it for unit tests (use tdd skill instead).
Before writing any Gherkin, align on the scenario with three perspectives.
Constraints:
| Role | Question |
|---|---|
| Business | Why does this behavior matter? |
| Developer | Is this feasible? Any constraints? |
| Tester | What are the edge cases? |
Constraints:
Background: for Given steps repeated across scenarios in the same feature# ✅ Declarative — MUST write like this
Scenario: Premium customer receives discount at checkout
Given "Alice" is logged in as a premium customer
When Alice adds a $100 product to her cart
Then Alice should see a 10% discount applied
# ❌ Imperative — MUST NOT write like this
When I click button with id "submit-btn"
Then I see element with xpath "//div[@class='success']"
Feature: Cost Analysis
Background:
Given the system is online
And I am authenticated as an operator
Scenario: View monthly costs for single account
When I request costs for account "123456789012" in "2026-05"
Then I should see a cost breakdown by service
Constraints:
from pytest_bdd import scenarios, given, when, then, parsersparsers.parse for parametrized step textfrom pytest_bdd import scenarios, given, when, then, parsers
scenarios('../features/checkout.feature')
@given(parsers.parse('"{name}" is logged in as a premium customer'))
def premium_customer(name: str) -> dict:
return {"name": name, "tier": "premium"}
@when(parsers.parse('Alice adds a ${amount:d} product to her cart'))
def add_product(cart: ShoppingCart, amount: int) -> None:
cart.add_item(price=amount)
@then('Alice should see a 10% discount applied')
def verify_discount(cart: ShoppingCart) -> None:
assert cart.discount_rate == 0.10
Constraints:
@slow@api@e2e@smoke @api@api @smoke
Feature: Cost Explorer API
@slow
Scenario: Multi-account cost rollup
...
tdd skill