[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D7ZX0YX74MYG9CYY7JSZ0S":3,"skill-same:01M7D7ZX0YX74MYG9CYY7JSZ0S":51},{"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":29,"updatedAt":30,"install":31,"resources":44},"01M7D7ZX0YX74MYG9CYY7JSZ0S","generate",null,"Generate Playwright tests. Use when user says \"write tests\", \"generate tests\", \"add tests for\", \"test this component\", \"e2e test\", \"create test for\", \"test this page\", or \"test this feature\".","Mabbit143\u002FClaude-SKills","Mabbit143","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192994237?v=4","01M7D6X2W63K4T3N13CSVAKE3V","Mabbit Rountree","01M7D6X2WRPSZF8VMW9MW5ZP1X",0,"MIT","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Fgenerate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"generate\"\ndescription: >-\n  Generate Playwright tests. Use when user says \"write tests\", \"generate tests\",\n  \"add tests for\", \"test this component\", \"e2e test\", \"create test for\",\n  \"test this page\", or \"test this feature\".\n---\n\n# Generate Playwright Tests\n\nGenerate production-ready Playwright tests from a user story, URL, component name, or feature description.\n\n## Input\n\n`$ARGUMENTS` contains what to test. Examples:\n- `\"user can log in with email and password\"`\n- `\"the checkout flow\"`\n- `\"src\u002Fcomponents\u002FUserProfile.tsx\"`\n- `\"the search page with filters\"`\n\n## Steps\n\n### 1. Understand the Target\n\nParse `$ARGUMENTS` to determine:\n- **User story**: Extract the behavior to verify\n- **Component path**: Read the component source code\n- **Page\u002FURL**: Identify the route and its elements\n- **Feature name**: Map to relevant app areas\n\n### 2. Explore the Codebase\n\nUse the `Explore` subagent to gather context:\n\n- Read `playwright.config.ts` for `testDir`, `baseURL`, `projects`\n- Check existing tests in `testDir` for patterns, fixtures, and conventions\n- If a component path is given, read the component to understand its props, states, and interactions\n- Check for existing page objects in `pages\u002F`\n- Check for existing fixtures in `fixtures\u002F`\n- Check for auth setup (`auth.setup.ts` or `storageState` config)\n\n### 3. Select Templates\n\nCheck `templates\u002F` in this plugin for matching patterns:\n\n| If testing... | Load template from |\n|---|---|\n| Login\u002Fauth flow | `templates\u002Fauth\u002Flogin.md` |\n| CRUD operations | `templates\u002Fcrud\u002F` |\n| Checkout\u002Fpayment | `templates\u002Fcheckout\u002F` |\n| Search\u002Ffilter UI | `templates\u002Fsearch\u002F` |\n| Form submission | `templates\u002Fforms\u002F` |\n| Dashboard\u002Fdata | `templates\u002Fdashboard\u002F` |\n| Settings page | `templates\u002Fsettings\u002F` |\n| Onboarding flow | `templates\u002Fonboarding\u002F` |\n| API endpoints | `templates\u002Fapi\u002F` |\n| Accessibility | `templates\u002Faccessibility\u002F` |\n\nAdapt the template to the specific app — replace `{{placeholders}}` with actual selectors, URLs, and data.\n\n### 4. Generate the Test\n\nFollow these rules:\n\n**Structure:**\n```typescript\nimport { test, expect } from '@playwright\u002Ftest';\n\u002F\u002F Import custom fixtures if the project uses them\n\ntest.describe('Feature Name', () => {\n  \u002F\u002F Group related behaviors\n\n  test('should \u003Cexpected behavior>', async ({ page }) => {\n    \u002F\u002F Arrange: navigate, set up state\n    \u002F\u002F Act: perform user action\n    \u002F\u002F Assert: verify outcome\n  });\n});\n```\n\n**Locator priority** (use the first that works):\n1. `getByRole()` — buttons, links, headings, form elements\n2. `getByLabel()` — form fields with labels\n3. `getByText()` — non-interactive text content\n4. `getByPlaceholder()` — inputs with placeholder text\n5. `getByTestId()` — when semantic options aren't available\n\n**Assertions** — always web-first:\n```typescript\n\u002F\u002F GOOD — auto-retries\nawait expect(page.getByRole('heading')).toBeVisible();\nawait expect(page.getByRole('alert')).toHaveText('Success');\n\n\u002F\u002F BAD — no retry\nconst text = await page.textContent('.msg');\nexpect(text).toBe('Success');\n```\n\n**Never use:**\n- `page.waitForTimeout()`\n- `page.$(selector)` or `page.$$(selector)`\n- Bare CSS selectors unless absolutely necessary\n- `page.evaluate()` for things locators can do\n\n**Always include:**\n- Descriptive test names that explain the behavior\n- Error\u002Fedge case tests alongside happy path\n- Proper `await` on every Playwright call\n- `baseURL`-relative navigation (`page.goto('\u002F')` not `page.goto('http:\u002F\u002F...')`)\n\n### 5. Match Project Conventions\n\n- If project uses TypeScript → generate `.spec.ts`\n- If project uses JavaScript → generate `.spec.js` with `require()` imports\n- If project has page objects → use them instead of inline locators\n- If project has custom fixtures → import and use them\n- If project has a test data directory → create test data files there\n\n### 6. Generate Supporting Files (If Needed)\n\n- **Page object**: If the test touches 5+ unique locators on one page, create a page object\n- **Fixture**: If the test needs shared setup (auth, data), create or extend a fixture\n- **Test data**: If the test uses structured data, create a JSON file in `test-data\u002F`\n\n### 7. Verify\n\nRun the generated test:\n\n```bash\nnpx playwright test \u003Cgenerated-file> --reporter=list\n```\n\nIf it fails:\n1. Read the error\n2. Fix the test (not the app)\n3. Run again\n4. If it's an app issue, report it to the user\n\n## Output\n\n- Generated test file(s) with path\n- Any supporting files created (page objects, fixtures, data)\n- Test run result\n- Coverage note: what behaviors are now tested\n","# Generate Playwright Tests\n\nGenerate production-ready Playwright tests from a user story, URL, component name, or feature description.\n\n## Input\n\n`$ARGUMENTS` contains what to test. Examples:\n- `\"user can log in with email and password\"`\n- `\"the checkout flow\"`\n- `\"src\u002Fcomponents\u002FUserProfile.tsx\"`\n- `\"the search page with filters\"`\n\n## Steps\n\n### 1. Understand the Target\n\nParse `$ARGUMENTS` to determine:\n- **User story**: Extract the behavior to verify\n- **Component path**: Read the component source code\n- **Page\u002FURL**: Identify the route and its elements\n- **Feature name**: Map to relevant app areas\n\n### 2. Explore the Codebase\n\nUse the `Explore` subagent to gather context:\n\n- Read `playwright.config.ts` for `testDir`, `baseURL`, `projects`\n- Check existing tests in `testDir` for patterns, fixtures, and conventions\n- If a component path is given, read the component to understand its props, states, and interactions\n- Check for existing page objects in `pages\u002F`\n- Check for existing fixtures in `fixtures\u002F`\n- Check for auth setup (`auth.setup.ts` or `storageState` config)\n\n### 3. Select Templates\n\nCheck `templates\u002F` in this plugin for matching patterns:\n\n| If testing... | Load template from |\n|---|---|\n| Login\u002Fauth flow | `templates\u002Fauth\u002Flogin.md` |\n| CRUD operations | `templates\u002Fcrud\u002F` |\n| Checkout\u002Fpayment | `templates\u002Fcheckout\u002F` |\n| Search\u002Ffilter UI | `templates\u002Fsearch\u002F` |\n| Form submission | `templates\u002Fforms\u002F` |\n| Dashboard\u002Fdata | `templates\u002Fdashboard\u002F` |\n| Settings page | `templates\u002Fsettings\u002F` |\n| Onboarding flow | `templates\u002Fonboarding\u002F` |\n| API endpoints | `templates\u002Fapi\u002F` |\n| Accessibility | `templates\u002Faccessibility\u002F` |\n\nAdapt the template to the specific app — replace `{{placeholders}}` with actual selectors, URLs, and data.\n\n### 4. Generate the Test\n\nFollow these rules:\n\n**Structure:**\n```typescript\nimport { test, expect } from '@playwright\u002Ftest';\n\u002F\u002F Import custom fixtures if the project uses them\n\ntest.describe('Feature Name', () => {\n  \u002F\u002F Group related behaviors\n\n  test('should \u003Cexpected behavior>', async ({ page }) => {\n    \u002F\u002F Arrange: navigate, set up state\n    \u002F\u002F Act: perform user action\n    \u002F\u002F Assert: verify outcome\n  });\n});\n```\n\n**Locator priority** (use the first that works):\n1. `getByRole()` — buttons, links, headings, form elements\n2. `getByLabel()` — form fields with labels\n3. `getByText()` — non-interactive text content\n4. `getByPlaceholder()` — inputs with placeholder text\n5. `getByTestId()` — when semantic options aren't available\n\n**Assertions** — always web-first:\n```typescript\n\u002F\u002F GOOD — auto-retries\nawait expect(page.getByRole('heading')).toBeVisible();\nawait expect(page.getByRole('alert')).toHaveText('Success');\n\n\u002F\u002F BAD — no retry\nconst text = await page.textContent('.msg');\nexpect(text).toBe('Success');\n```\n\n**Never use:**\n- `page.waitForTimeout()`\n- `page.$(selector)` or `page.$$(selector)`\n- Bare CSS selectors unless absolutely necessary\n- `page.evaluate()` for things locators can do\n\n**Always include:**\n- Descriptive test names that explain the behavior\n- Error\u002Fedge case tests alongside happy path\n- Proper `await` on every Playwright call\n- `baseURL`-relative navigation (`page.goto('\u002F')` not `page.goto('http:\u002F\u002F...')`)\n\n### 5. Match Project Conventions\n\n- If project uses TypeScript → generate `.spec.ts`\n- If project uses JavaScript → generate `.spec.js` with `require()` imports\n- If project has page objects → use them instead of inline locators\n- If project has custom fixtures → import and use them\n- If project has a test data directory → create test data files there\n\n### 6. Generate Supporting Files (If Needed)\n\n- **Page object**: If the test touches 5+ unique locators on one page, create a page object\n- **Fixture**: If the test needs shared setup (auth, data), create or extend a fixture\n- **Test data**: If the test uses structured data, create a JSON file in `test-data\u002F`\n\n### 7. Verify\n\nRun the generated test:\n\n```bash\nnpx playwright test \u003Cgenerated-file> --reporter=list\n```\n\nIf it fails:\n1. Read the error\n2. Fix the test (not the app)\n3. Run again\n4. If it's an app issue, report it to the user\n\n## Output\n\n- Generated test file(s) with path\n- Any supporting files created (page objects, fixtures, data)\n- Test run result\n- Coverage note: what behaviors are now tested\n",{"name":5,"description":7},"claude\u002Fregistry-repo-7lRiv","44e1a5b2d387b250bcd0794f7eb5e1228223d1e2","engineering-team\u002Fplaywright-pro\u002Fskills\u002Fgenerate","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills","https:\u002F\u002Fgithub.com\u002FMabbit143","I’m edgy and fun, probably too serious, but I love an adventure.","2026-09-22 07:56:32",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Mabbit143\u002FClaude-SKills --skill generate",{"tool":37,"command":38},"bunx","bunx skills add Mabbit143\u002FClaude-SKills --skill generate",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Mabbit143\u002FClaude-SKills --skill generate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Fgenerate\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"patterns.md","REFERENCE","参考文档",5848,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Fgenerate\u002Fpatterns.md",[52,59,66,73,80,87],{"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},"01M7D99ZA4F916M5CM3K2EQFE8","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\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},"01M7D99ND4B38EG1BYQX722F5D","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\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},"01M7D999VS936SV9TX940A98AQ","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\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},"01M7D98XBECS6368GEJNG8C1Z1","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\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},"01M7D98N2R7CA7RM00PNP4VV6C","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7D98B1SCTS4RAWZFCF9QJ5M","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]