[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7516F8N9CS5AP3BT958B62P":3,"skill-same:01M7516F8N9CS5AP3BT958B62P":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7516F8N9CS5AP3BT958B62P","gherkin-authoring",null,"Authors `.feature` files that stay business-readable, translate cleanly from PRD acceptance criteria, and reuse a shared step-definition library. Use when writing or editing scenarios — the SSOT enforcement rules live in `.agents\u002Frules\u002Fgherkin-standards.md`; this skill shows authors how to apply them.","chrisbarrantes\u002Fmandrel","chrisbarrantes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4534419?v=4","01M7511VXT2H7WE09JE4ZMBESG","Chris Barrantes","01M7511VYGPFHQCE9HNVKES0QN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstack\u002Fqa\u002Fgherkin-authoring\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: gherkin-authoring\ndescription:\n  Authors `.feature` files that stay business-readable, translate cleanly from\n  PRD acceptance criteria, and reuse a shared step-definition library. Use\n  when writing or editing scenarios — the SSOT enforcement rules live in\n  `.agents\u002Frules\u002Fgherkin-standards.md`; this skill shows authors how to apply\n  them.\n---\n\n# Skill: gherkin-authoring\n\n## Policy Capsule\n\n- Write `Given` clauses as stative preconditions, `When` as a single business action, and `Then` as a user-visible outcome.\n- Allow exactly one `When` per scenario; if you need two, split into two scenarios.\n- Never assert on HTTP status codes, SQL state, DOM selectors, URLs, or JSON payloads inside `.feature` prose — push those to contract tests.\n- Tag every Scenario or Outline with exactly one canonical `@domain-*` tag and the appropriate risk\u002Fplatform tags from the gherkin-standards taxonomy.\n- Use `Background` only when every scenario in the file genuinely shares the precondition with no per-scenario variation.\n- Reuse existing step definitions: grep the steps tree for the verb stem before authoring a new step.\n- Author one scenario per PRD acceptance criterion; for bounded matrices, use a Scenario Outline with ≤12 Examples rows.\n- Use third-person present-tense, role-qualified actors (`the billing-admin`), never first person.\n\nGuidance for authoring `.feature` files that stay business-readable, translate\ncleanly from PRD acceptance criteria, and reuse a shared step-definition\nlibrary. The enforcement rules — tag taxonomy, forbidden patterns, Outline\nconventions, selector discipline, step reuse — live in\n[`.agents\u002Frules\u002Fgherkin-standards.md`](..\u002F..\u002F..\u002F..\u002Frules\u002Fgherkin-standards.md),\nwhich is the SSOT. This skill shows authors **how** to apply those rules; read\nthe rule file for the **what**. Runtime wiring for Playwright consumers is\ncovered by [`playwright-bdd`](..\u002Fplaywright-bdd\u002FSKILL.md); test-layer scope is\ncovered by\n[`testing-standards.md`](..\u002F..\u002F..\u002F..\u002Frules\u002Ftesting-standards.md).\n\n## 1. Canonical Given \u002F When \u002F Then Phrasing\n\n`.feature` prose is written for a product-minded reader, not a test harness.\nEach clause has exactly one job:\n\n- **Given** — a precondition that is *already true* when the scenario starts.\n  Stative, past or present tense. No actions.\n  - Good: `Given a signed-in account-owner with an unpaid invoice`.\n  - Bad: `Given the user clicks the login button` (that's a When).\n- **When** — the single business action under test. One verb, one actor, one\n  event. Splitting a When into multiple clauses is almost always wrong — move\n  the extra clauses into Given.\n  - Good: `When they issue the invoice`.\n  - Bad: `When they log in and issue the invoice and download the PDF`.\n- **Then** — an observable, user-visible outcome. Assert what the *user* sees\n  or what the *business* records, not what the system emits internally.\n  - Good: `Then the invoice appears in the issued invoices list`.\n  - Bad: `Then a 201 is returned` (forbidden; see\n    [gherkin-standards § Forbidden Patterns](..\u002F..\u002F..\u002F..\u002Frules\u002Fgherkin-standards.md#forbidden-patterns)).\n- **And \u002F But** — continuation clauses. They inherit the mood of the most\n  recent Given\u002FWhen\u002FThen. Never start a scenario with And\u002FBut.\n\nVoice and tense:\n\n- Third-person, present tense. `the user`, `an admin`, `a billing-admin`\n  (role-qualified nouns, not \"I\" or \"we\").\n- One clause, one fact. Comma-chained facts hide compound assertions.\n- Numbers and identifiers go in `Examples` tables or fixtures, not inline\n  prose. Prose should read the same whether the underlying fixture has 1 or\n  10,000 rows.\n\n## 2. Translating PRD Acceptance Criteria to Scenarios\n\nPRD ACs are the raw material. The authoring move is **one AC → one scenario**\nunless the AC encodes a matrix (in which case it becomes a Scenario Outline —\nsee §3).\n\nWalkthrough — a PRD AC from a billing feature:\n\n> **AC-3:** When a billing-admin issues an invoice for a customer with a\n> negative balance, the system rejects the issue and shows an error naming the\n> outstanding amount.\n\nTranslation steps:\n\n1. **Identify the domain.** Billing → tag the scenario `@domain-billing`.\n2. **Identify the actor and precondition.** \"billing-admin\", \"customer with a\n   negative balance\" → two Givens.\n3. **Identify the single action.** \"issues an invoice\" → one When.\n4. **Identify the observable outcome.** \"rejects the issue and shows an error\n   naming the outstanding amount\" → two Thens. The first asserts the business\n   outcome (rejection); the second asserts the user-visible detail (error\n   names the amount).\n5. **Pick the risk tag.** If the originating ticket was `risk::high`, add\n   `@risk-high`. Smoke tag only if this is a critical path on every PR.\n\nResulting scenario:\n\n```gherkin\n@domain-billing @risk-high\nScenario: Issuing an invoice is rejected when the customer has a negative balance\n  Given a signed-in billing-admin\n  And a customer with a negative account balance\n  When the billing-admin issues an invoice for that customer\n  Then the issue is rejected\n  And the rejection message names the outstanding amount\n```\n\nHeuristics:\n\n- If a single AC needs more than **one When**, it is really two ACs. Split\n  before you write.\n- If a Then starts with \"and the database has…\" or \"and the API returned…\",\n  you have crossed into step-definition or contract-test territory. Rewrite\n  it as user-visible language or move the assertion to a contract test (see\n  [testing-standards](..\u002F..\u002F..\u002F..\u002Frules\u002Ftesting-standards.md)).\n- If an AC says \"the system logs X\", that's an engineering non-functional\n  requirement — not a BDD scenario. Cover it with a focused unit or\n  integration test, not a `.feature` file.\n- When a PRD AC is phrased negatively (\"non-admins cannot export\"), prefer a\n  Scenario Outline if there are multiple negative roles; write a plain\n  Scenario if there is exactly one.\n\n## 3. Background vs. Given — and Outline vs. Multi-Scenario\n\nTwo authoring decisions that authors routinely get wrong.\n\n### 3.1 Background vs. Given\n\n`Background` runs before **every** scenario in the file. Use it only when:\n\n- Every scenario in the file genuinely shares the precondition, **and**\n- The precondition has no per-scenario variation (no `\u003Cplaceholders>`,\n  no per-scenario data).\n\nPrefer a per-scenario Given when:\n\n- Only some scenarios need the precondition. A Background that applies to\n  four out of five scenarios is a Background for none of them; move it.\n- The precondition varies by role, plan tier, or fixture shape. Variation\n  belongs in a Scenario Outline's Examples, not in Background.\n- Readers cannot understand the scenario without scrolling up to read\n  Background. Background is a shortcut; if it hurts readability, inline it.\n\nRule of thumb: if you find yourself writing *\"except in the admin scenario,\nwhere the Background step is actually…\"*, delete the Background.\n\n### 3.2 Scenario Outline vs. multiple Scenarios\n\nUse `Scenario Outline` when the **same behavior** is exercised across a\n**bounded matrix** (roles, plan tiers, locales). The shape of the scenario —\nGivens, When, Thens — is identical; only the data varies.\n\nUse multiple `Scenario` blocks when:\n\n- The Givens differ structurally (not just in value).\n- The When verb differs.\n- The Then outcomes differ in kind, not just in value. \"Delivered vs.\n  denied\" is one outcome column (see Outline skeleton in\n  [gherkin-standards § Scenario Outline Conventions](..\u002F..\u002F..\u002F..\u002Frules\u002Fgherkin-standards.md#scenario-outline-conventions)).\n  \"Email is sent vs. invoice is issued vs. account is suspended\" are three\n  different scenarios.\n\nScale guardrails (also in gherkin-standards):\n\n- Keep `Examples` tables under ~12 rows. Larger tables hide distinct\n  behaviors behind a shared skeleton.\n- Split `Examples` by tag when rows need different tags (e.g. `@risk-high`\n  on admin rows only).\n\n## 4. Step-Definition Library Structure\n\nAuthoring scenarios and maintaining steps are the same job split across two\nfiles. The library layout below keeps that coupling visible.\n\n### 4.1 Layout\n\n```text\ntests\u002F\n  steps\u002F\n    _common\u002F          # actor, auth, navigation — reused across every domain\n      auth.steps.ts\n      navigation.steps.ts\n    billing\u002F          # one directory per @domain-* tag\n      invoices.steps.ts\n      subscriptions.steps.ts\n    auth\u002F\n      signin.steps.ts\n    _deprecated\u002F      # steps pending migration; see §4.4\n```\n\n- One directory per `@domain-*` tag. `_common\u002F` holds cross-cutting steps\n  (sign-in, navigation, generic waits handled at the fixture layer).\n- Files are named by the noun the steps act on\n  (`invoices.steps.ts`, not `billing-steps-1.ts`). A new noun is a new file.\n- Avoid deep nesting. Two levels (`steps\u002F\u003Cdomain>\u002F\u003Cnoun>.steps.ts`) is the\n  ceiling for most projects.\n\n### 4.2 Naming\n\nStep text follows the scenario text verbatim — if the scenario reads `the\ninvoice appears in the issued invoices list`, the step regex matches exactly\nthat phrase. Divergence between scenario prose and step text is a bug.\n\n- Parameterize only over values that vary across scenarios. A step that\n  accepts `{string}` for a literal that is always the same value is over-\n  parameterized; bake the constant in and rename the step.\n- Role-qualified actors (`{actor}`) read better than generic `{string}`.\n  Define a custom parameter type that resolves `account-owner`, `billing-admin`,\n  `viewer` to fixtures.\n- Keep step implementations ≤20 lines. Longer implementations indicate a\n  missing helper (domain fixture, page object, API client).\n\n### 4.3 Reuse Before Authoring\n\nThe non-negotiable workflow is in\n[gherkin-standards § Step Reuse](..\u002F..\u002F..\u002F..\u002Frules\u002Fgherkin-standards.md#step-reuse--grep-before-you-write):\ngrep the step tree for the verb stem before writing anything new. In practice:\n\n1. Search for the verb: `rg -n \"issues? an invoice\" tests\u002Fsteps`.\n2. If the phrase exists, **change your scenario** to use that phrase. Do not\n   fork a near-duplicate step.\n3. If a near-match exists, extend the existing step (add a parameter, widen\n   the regex) and update every call site in the same PR.\n4. Only when no reasonable match exists, add a new step in the correct\n   domain directory.\n\n### 4.4 Deprecation\n\nWhen a step is superseded:\n\n1. Move the old definition into `steps\u002F_deprecated\u002F` and annotate it with a\n   one-line comment naming the replacement.\n2. Migrate every call site to the replacement in the same PR.\n3. Delete the `_deprecated\u002F` entry when the migration lands.\n\nNever leave two live step definitions that mean the same thing. Parallel\nvocabularies rot the suite faster than any other source of maintenance cost.\n\n## 5. Authoring Checklist\n\nBefore opening a PR that adds or edits a `.feature` file:\n\n- [ ] Every Scenario\u002FOutline carries exactly one `@domain-*` tag.\n- [ ] No forbidden patterns (SQL, status codes, selectors, URLs, payloads,\n      framework names, explicit waits) appear in prose.\n- [ ] Each scenario has exactly one `When`.\n- [ ] `Then` clauses assert user-visible outcomes, not implementation.\n- [ ] `Background` is justified (applies to every scenario in the file).\n- [ ] If a Scenario Outline is used, the matrix is bounded (≤12 rows) and the\n      shape is truly identical across rows.\n- [ ] Every step phrase grep-matches an existing step definition **or** is\n      accompanied by a new step definition in the right domain directory.\n- [ ] Reads standalone — a product reader who has never seen the codebase can\n      understand the intent without opening a step file.\n\n## 6. Cross-References\n\n- SSOT rules: [`.agents\u002Frules\u002Fgherkin-standards.md`](..\u002F..\u002F..\u002F..\u002Frules\u002Fgherkin-standards.md).\n- Runtime wiring: [`playwright-bdd`](..\u002Fplaywright-bdd\u002FSKILL.md).\n- Browser-level conventions: [`playwright`](..\u002Fplaywright\u002FSKILL.md).\n- Test-layer scope: [`testing-standards.md`](..\u002F..\u002F..\u002F..\u002Frules\u002Ftesting-standards.md).\n- Example feature: [`examples\u002Finvoice-issue.feature`](.\u002Fexamples\u002Finvoice-issue.feature).\n","# Skill: gherkin-authoring\n\n## Policy Capsule\n\n- Write `Given` clauses as stative preconditions, `When` as a single business action, and `Then` as a user-visible outcome.\n- Allow exactly one `When` per scenario; if you need two, split into two scenarios.\n- Never assert on HTTP status codes, SQL state, DOM selectors, URLs, or JSON payloads inside `.feature` prose — push those to contract tests.\n- Tag every Scenario or Outline with exactly one canonical `@domain-*` tag and the appropriate risk\u002Fplatform tags from the gherkin-standards taxonomy.\n- Use `Background` only when every scenario in the file genuinely shares the precondition with no per-scenario variation.\n- Reuse existing step definitions: grep the steps tree for the verb stem before authoring a new step.\n- Author one scenario per PRD acceptance criterion; for bounded matrices, use a Scenario Outline with ≤12 Examples rows.\n- Use third-person present-tense, role-qualified actors (`the billing-admin`), never first person.\n\nGuidance for authoring `.feature` files that stay business-readable, translate\ncleanly from PRD acceptance criteria, and reuse a shared step-definition\nlibrary. The enforcement rules — tag taxonomy, forbidden patterns, Outline\nconventions, selector discipline, step reuse — live in\n[`.agents\u002Frules\u002Fgherkin-standards.md`](..\u002F..\u002F..\u002F..\u002Frules\u002Fgherkin-standards.md),\nwhich is the SSOT. This skill shows authors **how** to apply those rules; read\nthe rule file for the **what**. Runtime wiring for Playwright consumers is\ncovered by [`playwright-bdd`](..\u002Fplaywright-bdd\u002FSKILL.md); test-layer scope is\ncovered by\n[`testing-standards.md`](..\u002F..\u002F..\u002F..\u002Frules\u002Ftesting-standards.md).\n\n## 1. Canonical Given \u002F When \u002F Then Phrasing\n\n`.feature` prose is written for a product-minded reader, not a test harness.\nEach clause has exactly one job:\n\n- **Given** — a precondition that is *already true* when the scenario starts.\n  Stative, past or present tense. No actions.\n  - Good: `Given a signed-in account-owner with an unpaid invoice`.\n  - Bad: `Given the user clicks the login button` (that's a When).\n- **When** — the single business action under test. One verb, one actor, one\n  event. Splitting a When into multiple clauses is almost always wrong — move\n  the extra clauses into Given.\n  - Good: `When they issue the invoice`.\n  - Bad: `When they log in and issue the invoice and download the PDF`.\n- **Then** — an observable, user-visible outcome. Assert what the *user* sees\n  or what the *business* records, not what the system emits internally.\n  - Good: `Then the invoice appears in the issued invoices list`.\n  - Bad: `Then a 201 is returned` (forbidden; see\n    [gherkin-standards § Forbidden Patterns](..\u002F..\u002F..\u002F..\u002Frules\u002Fgherkin-standards.md#forbidden-patterns)).\n- **And \u002F But** — continuation clauses. They inherit the mood of the most\n  recent Given\u002FWhen\u002FThen. Never start a scenario with And\u002FBut.\n\nVoice and tense:\n\n- Third-person, present tense. `the user`, `an admin`, `a billing-admin`\n  (role-qualified nouns, not \"I\" or \"we\").\n- One clause, one fact. Comma-chained facts hide compound assertions.\n- Numbers and identifiers go in `Examples` tables or fixtures, not inline\n  prose. Prose should read the same whether the underlying fixture has 1 or\n  10,000 rows.\n\n## 2. Translating PRD Acceptance Criteria to Scenarios\n\nPRD ACs are the raw material. The authoring move is **one AC → one scenario**\nunless the AC encodes a matrix (in which case it becomes a Scenario Outline —\nsee §3).\n\nWalkthrough — a PRD AC from a billing feature:\n\n> **AC-3:** When a billing-admin issues an invoice for a customer with a\n> negative balance, the system rejects the issue and shows an error naming the\n> outstanding amount.\n\nTranslation steps:\n\n1. **Identify the domain.** Billing → tag the scenario `@domain-billing`.\n2. **Identify the actor and precondition.** \"billing-admin\", \"customer with a\n   negative balance\" → two Givens.\n3. **Identify the single action.** \"issues an invoice\" → one When.\n4. **Identify the observable outcome.** \"rejects the issue and shows an error\n   naming the outstanding amount\" → two Thens. The first asserts the business\n   outcome (rejection); the second asserts the user-visible detail (error\n   names the amount).\n5. **Pick the risk tag.** If the originating ticket was `risk::high`, add\n   `@risk-high`. Smoke tag only if this is a critical path on every PR.\n\nResulting scenario:\n\n```gherkin\n@domain-billing @risk-high\nScenario: Issuing an invoice is rejected when the customer has a negative balance\n  Given a signed-in billing-admin\n  And a customer with a negative account balance\n  When the billing-admin issues an invoice for that customer\n  Then the issue is rejected\n  And the rejection message names the outstanding amount\n```\n\nHeuristics:\n\n- If a single AC needs more than **one When**, it is really two ACs. Split\n  before you write.\n- If a Then starts with \"and the database has…\" or \"and the API returned…\",\n  you have crossed into step-definition or contract-test territory. Rewrite\n  it as user-visible language or move the assertion to a contract test (see\n  [testing-standards](..\u002F..\u002F..\u002F..\u002Frules\u002Ftesting-standards.md)).\n- If an AC says \"the system logs X\", that's an engineering non-functional\n  requirement — not a BDD scenario. Cover it with a focused unit or\n  integration test, not a `.feature` file.\n- When a PRD AC is phrased negatively (\"non-admins cannot export\"), prefer a\n  Scenario Outline if there are multiple negative roles; write a plain\n  Scenario if there is exactly one.\n\n## 3. Background vs. Given — and Outline vs. Multi-Scenario\n\nTwo authoring decisions that authors routinely get wrong.\n\n### 3.1 Background vs. Given\n\n`Background` runs before **every** scenario in the file. Use it only when:\n\n- Every scenario in the file genuinely shares the precondition, **and**\n- The precondition has no per-scenario variation (no `\u003Cplaceholders>`,\n  no per-scenario data).\n\nPrefer a per-scenario Given when:\n\n- Only some scenarios need the precondition. A Background that applies to\n  four out of five scenarios is a Background for none of them; move it.\n- The precondition varies by role, plan tier, or fixture shape. Variation\n  belongs in a Scenario Outline's Examples, not in Background.\n- Readers cannot understand the scenario without scrolling up to read\n  Background. Background is a shortcut; if it hurts readability, inline it.\n\nRule of thumb: if you find yourself writing *\"except in the admin scenario,\nwhere the Background step is actually…\"*, delete the Background.\n\n### 3.2 Scenario Outline vs. multiple Scenarios\n\nUse `Scenario Outline` when the **same behavior** is exercised across a\n**bounded matrix** (roles, plan tiers, locales). The shape of the scenario —\nGivens, When, Thens — is identical; only the data varies.\n\nUse multiple `Scenario` blocks when:\n\n- The Givens differ structurally (not just in value).\n- The When verb differs.\n- The Then outcomes differ in kind, not just in value. \"Delivered vs.\n  denied\" is one outcome column (see Outline skeleton in\n  [gherkin-standards § Scenario Outline Conventions](..\u002F..\u002F..\u002F..\u002Frules\u002Fgherkin-standards.md#scenario-outline-conventions)).\n  \"Email is sent vs. invoice is issued vs. account is suspended\" are three\n  different scenarios.\n\nScale guardrails (also in gherkin-standards):\n\n- Keep `Examples` tables under ~12 rows. Larger tables hide distinct\n  behaviors behind a shared skeleton.\n- Split `Examples` by tag when rows need different tags (e.g. `@risk-high`\n  on admin rows only).\n\n## 4. Step-Definition Library Structure\n\nAuthoring scenarios and maintaining steps are the same job split across two\nfiles. The library layout below keeps that coupling visible.\n\n### 4.1 Layout\n\n```text\ntests\u002F\n  steps\u002F\n    _common\u002F          # actor, auth, navigation — reused across every domain\n      auth.steps.ts\n      navigation.steps.ts\n    billing\u002F          # one directory per @domain-* tag\n      invoices.steps.ts\n      subscriptions.steps.ts\n    auth\u002F\n      signin.steps.ts\n    _deprecated\u002F      # steps pending migration; see §4.4\n```\n\n- One directory per `@domain-*` tag. `_common\u002F` holds cross-cutting steps\n  (sign-in, navigation, generic waits handled at the fixture layer).\n- Files are named by the noun the steps act on\n  (`invoices.steps.ts`, not `billing-steps-1.ts`). A new noun is a new file.\n- Avoid deep nesting. Two levels (`steps\u002F\u003Cdomain>\u002F\u003Cnoun>.steps.ts`) is the\n  ceiling for most projects.\n\n### 4.2 Naming\n\nStep text follows the scenario text verbatim — if the scenario reads `the\ninvoice appears in the issued invoices list`, the step regex matches exactly\nthat phrase. Divergence between scenario prose and step text is a bug.\n\n- Parameterize only over values that vary across scenarios. A step that\n  accepts `{string}` for a literal that is always the same value is over-\n  parameterized; bake the constant in and rename the step.\n- Role-qualified actors (`{actor}`) read better than generic `{string}`.\n  Define a custom parameter type that resolves `account-owner`, `billing-admin`,\n  `viewer` to fixtures.\n- Keep step implementations ≤20 lines. Longer implementations indicate a\n  missing helper (domain fixture, page object, API client).\n\n### 4.3 Reuse Before Authoring\n\nThe non-negotiable workflow is in\n[gherkin-standards § Step Reuse](..\u002F..\u002F..\u002F..\u002Frules\u002Fgherkin-standards.md#step-reuse--grep-before-you-write):\ngrep the step tree for the verb stem before writing anything new. In practice:\n\n1. Search for the verb: `rg -n \"issues? an invoice\" tests\u002Fsteps`.\n2. If the phrase exists, **change your scenario** to use that phrase. Do not\n   fork a near-duplicate step.\n3. If a near-match exists, extend the existing step (add a parameter, widen\n   the regex) and update every call site in the same PR.\n4. Only when no reasonable match exists, add a new step in the correct\n   domain directory.\n\n### 4.4 Deprecation\n\nWhen a step is superseded:\n\n1. Move the old definition into `steps\u002F_deprecated\u002F` and annotate it with a\n   one-line comment naming the replacement.\n2. Migrate every call site to the replacement in the same PR.\n3. Delete the `_deprecated\u002F` entry when the migration lands.\n\nNever leave two live step definitions that mean the same thing. Parallel\nvocabularies rot the suite faster than any other source of maintenance cost.\n\n## 5. Authoring Checklist\n\nBefore opening a PR that adds or edits a `.feature` file:\n\n- [ ] Every Scenario\u002FOutline carries exactly one `@domain-*` tag.\n- [ ] No forbidden patterns (SQL, status codes, selectors, URLs, payloads,\n      framework names, explicit waits) appear in prose.\n- [ ] Each scenario has exactly one `When`.\n- [ ] `Then` clauses assert user-visible outcomes, not implementation.\n- [ ] `Background` is justified (applies to every scenario in the file).\n- [ ] If a Scenario Outline is used, the matrix is bounded (≤12 rows) and the\n      shape is truly identical across rows.\n- [ ] Every step phrase grep-matches an existing step definition **or** is\n      accompanied by a new step definition in the right domain directory.\n- [ ] Reads standalone — a product reader who has never seen the codebase can\n      understand the intent without opening a step file.\n\n## 6. Cross-References\n\n- SSOT rules: [`.agents\u002Frules\u002Fgherkin-standards.md`](..\u002F..\u002F..\u002F..\u002Frules\u002Fgherkin-standards.md).\n- Runtime wiring: [`playwright-bdd`](..\u002Fplaywright-bdd\u002FSKILL.md).\n- Browser-level conventions: [`playwright`](..\u002Fplaywright\u002FSKILL.md).\n- Test-layer scope: [`testing-standards.md`](..\u002F..\u002F..\u002F..\u002Frules\u002Ftesting-standards.md).\n- Example feature: [`examples\u002Finvoice-issue.feature`](.\u002Fexamples\u002Finvoice-issue.feature).\n",{"name":5,"description":7},"main","22b1847659cc2a98f4fb8c24858f2199d91fda66",".agents\u002Fskills\u002Fstack\u002Fqa\u002Fgherkin-authoring","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes","2026-05-27 08:16:47",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add chrisbarrantes\u002Fmandrel --skill gherkin-authoring",{"tool":36,"command":37},"bunx","bunx skills add chrisbarrantes\u002Fmandrel --skill gherkin-authoring",{"tool":39,"command":40},"pnpm","pnpm dlx skills add chrisbarrantes\u002Fmandrel --skill gherkin-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstack\u002Fqa\u002Fgherkin-authoring\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"examples\u002Finvoice-issue.feature","OTHER","其他",1554,"https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstack\u002Fqa\u002Fgherkin-authoring\u002Fexamples\u002Finvoice-issue.feature",[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M75171YZD373TXY5ZWJNXGS9","no-capsule-skill","Fixture without a Policy Capsule section.","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002Ftests\u002Forchestration\u002Ffixtures\u002Fskill-capsule\u002Fno-capsule-skill\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7516ZA88ESAAY3JWXBNA56K","backend-security-patterns","Combined backend protocols for authentication (Clerk JWT verification) and PII-safe observability. Use when handling auth on the server, verifying Clerk webhooks via `svix`, scoping metadata via `publicMetadata`\u002F `privateMetadata`, or sanitizing logs to keep emails, tokens, and request bodies out of telemetry.","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstack\u002Fsecurity\u002Fbackend-security-patterns\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7516WFQMKD2NGFMDNFG6C4A","vitest","Writes fast, isolated unit and integration tests with Vitest. Use when each test must run on file-save without shared state — `vi.mock()` for external deps, `vi.spyOn()` for call monitoring, AAA structure, and edge-case coverage for null\u002Fundefined\u002Fboundary inputs.","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstack\u002Fqa\u002Fvitest\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7516T8FX7B0B0D510EE2FAP","playwright","Robust E2E browser testing with Playwright. Use when writing browser-driven tests — leverage auto-waiting (no `waitForTimeout`), prefer user-visible locators (`getByRole`, `getByText`, `getByLabel`) over CSS\u002FXPath, reuse `storageState` for auth, and enable trace-on-first-retry for CI debugging.","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstack\u002Fqa\u002Fplaywright\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7516PHY868BJXHHZJ0FRYSX","playwright-bdd","Wires Gherkin `.feature` files to Playwright via the `playwright-bdd` library. Use when running BDD scenarios on a Playwright runtime — pairs with the `gherkin-authoring` skill (scenario prose) and the `playwright` skill (browser conventions). Drives execution by tag expression with trace-first debugging and Playwright-native sharding.","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstack\u002Fqa\u002Fplaywright-bdd\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7516KEGSBBFJXRZWYBKYM4P","lighthouse-baseline","Codifies the capture-and-check baseline pattern for long-running quality signals (Lighthouse scores, bundle size, p95 latency, runtime memory). Use when wiring a new metric that needs a baseline file, paired :capture \u002F :check npm scripts, a tolerance-bounded gate, and a weekly refresh cadence — the goal is a hard CI signal that ratchets only with intent.","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstack\u002Fqa\u002Flighthouse-baseline\u002FSKILL.md",[],[]]