[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PXKVMS139JBM4A8VCY2ZR":3,"skill-same:01M75PXKVMS139JBM4A8VCY2ZR":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M75PXKVMS139JBM4A8VCY2ZR","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\".","TehutiRaEl\u002FTHEHIVE","TehutiRaEl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F267495122?v=4","01M75N1QQQHT359S3XMYK7NPCB","01M75N1QRAW5P8P43HEHWMXCTE",0,"MIT","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Fgenerate\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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 | `..\u002Fpw\u002Ftemplates\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 | `..\u002Fpw\u002Ftemplates\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},"main","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1","skills-library\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Fgenerate","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE","https:\u002F\u002Fgithub.com\u002FTehutiRaEl","2026-11-15 04:00:21",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add TehutiRaEl\u002FTHEHIVE --skill generate",{"tool":35,"command":36},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill generate",{"tool":38,"command":39},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill generate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Fgenerate\u002FSKILL.md",true,[43],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"patterns.md","REFERENCE","参考文档",5848,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Fgenerate\u002Fpatterns.md",[50,57,63,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M76XP63XDM4PFPX8MMVYN9JX","preamble-gate","Use BEFORE doing any work in this repo — before the first file edit, commit, push, PR, branch operation, workflow dispatch, scheduled trigger or timer, agent\u002Fsubagent spawn, dependency install, or message sent to an outside service. Forces a plain-language preamble to the founder first: WHAT you are about to do, WHY, HOW, why it is NECESSARY, the PROJECTED IMPROVEMENT, and the COST and RISK — then, for consequential work (governance, security, money, CI\u002Ftriggers, rewriting history, multi-agent fan-out), waits for an explicit go-ahead. Read-only investigation (reading files, grep, git log\u002Fdiff, answering questions) is exempt. Applies to every AI that works in this repo, not just Claude. Founder rule, 2026-11-10, written after an unattended automation ran up cost and froze the hive. Not a substitute for wired-or-not (which governs how completion is CLAIMED); this governs what happens BEFORE work starts.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpreamble-gate\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M75RAYXC1W361YR9NBXD59AM","visionary-recommender","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills\u002Fvisionary-recommender\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75RAQN9Q450RD57J2S6FSR4","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. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75RAG1XMCJMF30HFV5S79AK","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. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"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]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75RA8RK2JVWB8MYGRB65V75","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. Use when the user requests multi-source recency intelligence on a topic (e.g., '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]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75RA08RXYRFSTNC6EEEX4ZD","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. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). 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\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[]]