[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7516T8FX7B0B0D510EE2FAP":3,"skill-same:01M7516T8FX7B0B0D510EE2FAP":44},{"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},"01M7516T8FX7B0B0D510EE2FAP","playwright",null,"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.","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\u002Fplaywright\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: playwright\ndescription:\n  Robust E2E browser testing with Playwright. Use when writing browser-driven\n  tests — leverage auto-waiting (no `waitForTimeout`), prefer user-visible\n  locators (`getByRole`, `getByText`, `getByLabel`) over CSS\u002FXPath, reuse\n  `storageState` for auth, and enable trace-on-first-retry for CI debugging.\nvendor: playwright\n---\n\n# Skill: Playwright\n\n## Policy Capsule\n\n- Rely on Playwright's auto-waiting; never use `waitForTimeout` or hardcoded sleeps to paper over flakes.\n- Prefer user-visible locators (`getByRole`, `getByText`, `getByLabel`) over CSS selectors or XPath.\n- Reuse `storageState` to seed authenticated scenarios; do not repeat login flows in every test.\n- Use `toHaveScreenshot()` for critical visual surfaces; treat snapshot diffs as intentional reviews, not auto-refreshes.\n- Write tests independent of one another so they run in parallel; clean up shared state in fixtures, not afterwards.\n- Enable `trace: 'on-first-retry'` (or `'retain-on-failure'`) so CI failures are debuggable in the Trace Viewer.\n- Use a unique data set per test run, or tear down state explicitly, to prevent cross-test contamination.\n\nStandard operating procedures for robust, end-to-end (E2E) browser testing.\n\n## 1. Core Principles\n\n- **End-to-End focus:** Test the application as a user would, through the\n  browser.\n- **Auto-waiting:** Leverage Playwright's built-in auto-waiting instead of\n  hardcoded `waitForTimeout` calls.\n- **Resilience:** Write tests that survive minor UI changes (e.g., color tweaks)\n  by using robust selectors.\n\n## 2. Technical Standards\n\n- **Locators:** Use user-visible locators (e.g., `getByRole`, `getByText`,\n  `getByLabel`) over brittle CSS selectors or XPath.\n- **State Management:** Use `storageState` to reuse authentication between\n  tests, avoiding repetitive login flows.\n- **Visual Testing:** Use `toHaveScreenshot()` for critical UI layouts to detect\n  visual regressions.\n\n## 3. Best Practices\n\n- **Parallelism:** Ensure tests are independent so they can run concurrently to\n  reduce CI time.\n- **Tracing:** Enable trace recording on failure to quickly debug CI issues with\n  the Playwright Trace Viewer.\n- **Test Data:** Use a unique data set per test run or clean up state to prevent\n  cross-contamination.\n","# Skill: Playwright\n\n## Policy Capsule\n\n- Rely on Playwright's auto-waiting; never use `waitForTimeout` or hardcoded sleeps to paper over flakes.\n- Prefer user-visible locators (`getByRole`, `getByText`, `getByLabel`) over CSS selectors or XPath.\n- Reuse `storageState` to seed authenticated scenarios; do not repeat login flows in every test.\n- Use `toHaveScreenshot()` for critical visual surfaces; treat snapshot diffs as intentional reviews, not auto-refreshes.\n- Write tests independent of one another so they run in parallel; clean up shared state in fixtures, not afterwards.\n- Enable `trace: 'on-first-retry'` (or `'retain-on-failure'`) so CI failures are debuggable in the Trace Viewer.\n- Use a unique data set per test run, or tear down state explicitly, to prevent cross-test contamination.\n\nStandard operating procedures for robust, end-to-end (E2E) browser testing.\n\n## 1. Core Principles\n\n- **End-to-End focus:** Test the application as a user would, through the\n  browser.\n- **Auto-waiting:** Leverage Playwright's built-in auto-waiting instead of\n  hardcoded `waitForTimeout` calls.\n- **Resilience:** Write tests that survive minor UI changes (e.g., color tweaks)\n  by using robust selectors.\n\n## 2. Technical Standards\n\n- **Locators:** Use user-visible locators (e.g., `getByRole`, `getByText`,\n  `getByLabel`) over brittle CSS selectors or XPath.\n- **State Management:** Use `storageState` to reuse authentication between\n  tests, avoiding repetitive login flows.\n- **Visual Testing:** Use `toHaveScreenshot()` for critical UI layouts to detect\n  visual regressions.\n\n## 3. Best Practices\n\n- **Parallelism:** Ensure tests are independent so they can run concurrently to\n  reduce CI time.\n- **Tracing:** Enable trace recording on failure to quickly debug CI issues with\n  the Playwright Trace Viewer.\n- **Test Data:** Use a unique data set per test run or clean up state to prevent\n  cross-contamination.\n",{"name":5,"vendor":5,"description":7},"main","22b1847659cc2a98f4fb8c24858f2199d91fda66",".agents\u002Fskills\u002Fstack\u002Fqa\u002Fplaywright","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 playwright",{"tool":36,"command":37},"bunx","bunx skills add chrisbarrantes\u002Fmandrel --skill playwright",{"tool":39,"command":40},"pnpm","pnpm dlx skills add chrisbarrantes\u002Fmandrel --skill playwright","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstack\u002Fqa\u002Fplaywright\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"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":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7516F8N9CS5AP3BT958B62P","gherkin-authoring","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.","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstack\u002Fqa\u002Fgherkin-authoring\u002FSKILL.md",[],[]]