[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79TGR2WVMM93MEQMS6V9T8C":3,"skill-same:01M79TGR2WVMM93MEQMS6V9T8C":53},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M79TGR2WVMM93MEQMS6V9T8C","playwright-architect",null,"Architect-level Playwright guidance — what belongs in E2E versus unit\u002Fcomponent tests, fixture and page-object boundaries, deterministic waits and network control, auth and seeded state, CI parallelism and flake policy. Use when designing or repairing a browser test suite.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ffrontend-development-architect\u002Fplaywright-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: playwright-architect\ndescription: Architect-level Playwright guidance — what belongs in E2E versus unit\u002Fcomponent tests, fixture and page-object boundaries, deterministic waits and network control, auth and seeded state, CI parallelism and flake policy. Use when designing or repairing a browser test suite.\nlicense: MIT\ncompatibility: Playwright 1.40+; any frontend stack\nmetadata:\n  crusor-domain: website-architect\n  crusor-path: website-architect\u002Ffrontend-development-architect\u002Fplaywright-architect\n  crusor-origin: original\n  crusor-sources: \"playwright.dev\u002Fdocs\u002Fbest-practices; playwright.dev\u002Fdocs\u002Ftest-fixtures\"\n  crusor-triggers: \"playwright, e2e test, end-to-end, browser test, flaky test, e2e suite, browser automation, trace viewer\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Playwright Architect\n\nE2E is the most expensive layer per assertion. Architecture is the discipline of\n**spending it only on journeys that must not break** — and making those\ndeterministic.\n\n## When to use\n\n- Designing the browser-test layer for a web app.\n- A suite is slow, flaky, or failing without a product bug.\n- Deciding where a test belongs: unit, component, or E2E.\n\n## When NOT to use\n\n- Testing pure functions or component rendering (unit\u002Fcomponent layer).\n- Load testing and visual-regression-at-scale (different tools and budgets).\n\n## Decision 1 — The test pyramid, stated plainly\n\n| Layer | Owns | Budget |\n|---|---|---|\n| unit | rules, formatting, reducers | thousands, ms |\n| component | one component's states | hundreds, ms |\n| E2E | critical journeys (login, checkout, publish) | tens, minutes |\n| visual | layout regressions on key pages | few, stable pages |\n\n- If a bug can be caught at a lower layer, it does not get an E2E test.\n- Every E2E test names the business journey it protects.\n\n## Decision 2 — Fixtures and page objects\n\n- One fixture per *actor* (anonymous user, signed-in user, admin), each\n  producing an authenticated context — auth setup runs once, reused via storage\n  state.\n- Page objects hold **locators and user-level actions**, never assertions about\n  business rules (those live in the test).\n- Locators: role + accessible name (`getByRole`), then test ids. Never CSS\n  chains into component internals.\n- Data setup through API\u002Fseed, not by clicking through the UI.\n\n## Decision 3 — Determinism\n\n- No `waitForTimeout`. Wait on state: `expect(locator).toBeVisible()`, URL, or\n  a network response.\n- Control the network: mock third parties, stub failures and slow responses to\n  test the sad path deliberately.\n- Freeze time and randomise seeds where output depends on them.\n- Each test creates its own data and cleans up; no ordering dependencies.\n\n## Decision 4 — CI reality\n\n- Shards in parallel; retries limited (1) and **reported**, never used to hide\n  flake.\n- Trace + video on first retry; artefacts uploaded.\n- Quarantine policy: a test failing intermittently twice is fixed or deleted\n  within a sprint — a permanent `@flaky` tag is a broken gate.\n- Runs on every PR for the smoke subset; full suite on main\u002Fnightly.\n\n## Failure modes at scale\n\n- A 40-minute suite nobody runs locally.\n- Sleeps everywhere → 5% flake rate → team ignores red.\n- Page objects with 300 methods, mirroring the DOM.\n- Tests that depend on shared seed data and pass only in order.\n- E2E used to verify styling that a screenshot test covers in 200 ms.\n\n## Verification receipts\n\n1. Flake audit: pass rate over the last 50 runs per test; zero unexplained.\n2. Suite duration and shard balance recorded.\n3. Trace artefacts present on retry.\n4. Every critical journey covered exactly once (no duplicates).\n5. `waitForTimeout` count in the suite: zero.\n","# Playwright Architect\n\nE2E is the most expensive layer per assertion. Architecture is the discipline of\n**spending it only on journeys that must not break** — and making those\ndeterministic.\n\n## When to use\n\n- Designing the browser-test layer for a web app.\n- A suite is slow, flaky, or failing without a product bug.\n- Deciding where a test belongs: unit, component, or E2E.\n\n## When NOT to use\n\n- Testing pure functions or component rendering (unit\u002Fcomponent layer).\n- Load testing and visual-regression-at-scale (different tools and budgets).\n\n## Decision 1 — The test pyramid, stated plainly\n\n| Layer | Owns | Budget |\n|---|---|---|\n| unit | rules, formatting, reducers | thousands, ms |\n| component | one component's states | hundreds, ms |\n| E2E | critical journeys (login, checkout, publish) | tens, minutes |\n| visual | layout regressions on key pages | few, stable pages |\n\n- If a bug can be caught at a lower layer, it does not get an E2E test.\n- Every E2E test names the business journey it protects.\n\n## Decision 2 — Fixtures and page objects\n\n- One fixture per *actor* (anonymous user, signed-in user, admin), each\n  producing an authenticated context — auth setup runs once, reused via storage\n  state.\n- Page objects hold **locators and user-level actions**, never assertions about\n  business rules (those live in the test).\n- Locators: role + accessible name (`getByRole`), then test ids. Never CSS\n  chains into component internals.\n- Data setup through API\u002Fseed, not by clicking through the UI.\n\n## Decision 3 — Determinism\n\n- No `waitForTimeout`. Wait on state: `expect(locator).toBeVisible()`, URL, or\n  a network response.\n- Control the network: mock third parties, stub failures and slow responses to\n  test the sad path deliberately.\n- Freeze time and randomise seeds where output depends on them.\n- Each test creates its own data and cleans up; no ordering dependencies.\n\n## Decision 4 — CI reality\n\n- Shards in parallel; retries limited (1) and **reported**, never used to hide\n  flake.\n- Trace + video on first retry; artefacts uploaded.\n- Quarantine policy: a test failing intermittently twice is fixed or deleted\n  within a sprint — a permanent `@flaky` tag is a broken gate.\n- Runs on every PR for the smoke subset; full suite on main\u002Fnightly.\n\n## Failure modes at scale\n\n- A 40-minute suite nobody runs locally.\n- Sleeps everywhere → 5% flake rate → team ignores red.\n- Page objects with 300 methods, mirroring the DOM.\n- Tests that depend on shared seed data and pass only in order.\n- E2E used to verify styling that a screenshot test covers in 200 ms.\n\n## Verification receipts\n\n1. Flake audit: pass rate over the last 50 runs per test; zero unexplained.\n2. Suite duration and shard balance recorded.\n3. Trace artefacts present on retry.\n4. Every critical journey covered exactly once (no duplicates).\n5. `waitForTimeout` count in the suite: zero.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":31},{"crusor-path":25,"crusor-domain":26,"crusor-origin":27,"crusor-sources":28,"crusor-triggers":29,"crusor-verified-on":30},"website-architect\u002Ffrontend-development-architect\u002Fplaywright-architect","website-architect","original","playwright.dev\u002Fdocs\u002Fbest-practices; playwright.dev\u002Fdocs\u002Ftest-fixtures","playwright, e2e test, end-to-end, browser test, flaky test, e2e suite, browser automation, trace viewer","2026-10-30","Playwright 1.40+; any frontend stack","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fwebsite-architect\u002Ffrontend-development-architect\u002Fplaywright-architect","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill playwright-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill playwright-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill playwright-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ffrontend-development-architect\u002Fplaywright-architect\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]