[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7BNVGKXFKKZYR1FKDJXQV":3,"skill-same:01M6H7BNVGKXFKKZYR1FKDJXQV":67},{"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":23,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6H7BNVGKXFKKZYR1FKDJXQV","playwright-expert",null,"Use when implementing playwright functionality with production-grade patterns and safeguards.","0xharryriddle\u002Fcodex-field-kit","0xharryriddle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F100945007?v=4","01M6H686JV0QKZYP2RWG6B2B8T","harryriddle","01M6H686PVZ8JGKWEG7B3GM5PD",3,"MIT","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Fplaywright-expert\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34],"playwright","expert","playwright expert","codex","Production","use","general","patterns","with","kit","implementing","2026-11-10 10:12:30",false,"---\nname: playwright-expert\ndescription: Use when implementing playwright functionality with production-grade patterns and safeguards.\nmetadata:\n  hermes:\n    tags: [codex-agent, general]\n    source: codex-field-kit\u002Fgeneral\n---\n\n# Playwright Expert\n\n## Focus Areas\n\n- Mastery of Playwright's API for end-to-end testing\n- Cross-browser testing capabilities with Playwright\n- Efficient test suite setup and configuration\n- Handling dynamic content and complex page interactions\n- Playwright Test runner usage and customization\n- Network interception and request monitoring\n- Test data management and seeding\n- Debugging and logging strategies for Playwright tests\n- Performance testing with Playwright\n- Integration with CI\u002FCD pipelines for automated testing\n\n## Approach\n\n- Write readable and maintainable Playwright test scripts\n- Use fixtures and test hooks effectively\n- Implement robust selectors and element interactions\n- Leverage Playwright's context and page lifecycle methods\n- Parallelize tests to reduce execution time\n- Isolate test cases for independent execution\n- Continuously refactor and improve test code quality\n- Utilize Playwright's tracing capabilities for issue diagnostics\n- Regularly update and maintain Playwright dependencies\n- Document test strategies and scenarios comprehensively\n\n## Quality Checklist\n\n- Ensure full test coverage for critical user flows\n- Use page object model for test structure\n- Handle flaky tests through retries and waits\n- Optimize tests for speed and reliability\n- Validate test outputs with assertions\n- Implement error handling and cleanup routines\n- Maintain consistency in test data across environments\n- Review and optimize test execution time\n- Conduct peer reviews of test cases\n- Monitor test runs and maintain test stability\n\n## Output\n\n- Comprehensive Playwright test suite with modular structure\n- Test cases with detailed descriptions and comments\n- Execution reports with clear pass\u002Ffail indications\n- Screenshots and videos of test runs for debugging\n- Automated test setup for local and CI environments\n- Test artifacts stored and accessible for analysis\n- Configuration files for environment-specific settings\n- Detailed documentation of test cases and structure\n- Maintained backlog of test improvements and updates\n\n","# Playwright Expert\n\n## Focus Areas\n\n- Mastery of Playwright's API for end-to-end testing\n- Cross-browser testing capabilities with Playwright\n- Efficient test suite setup and configuration\n- Handling dynamic content and complex page interactions\n- Playwright Test runner usage and customization\n- Network interception and request monitoring\n- Test data management and seeding\n- Debugging and logging strategies for Playwright tests\n- Performance testing with Playwright\n- Integration with CI\u002FCD pipelines for automated testing\n\n## Approach\n\n- Write readable and maintainable Playwright test scripts\n- Use fixtures and test hooks effectively\n- Implement robust selectors and element interactions\n- Leverage Playwright's context and page lifecycle methods\n- Parallelize tests to reduce execution time\n- Isolate test cases for independent execution\n- Continuously refactor and improve test code quality\n- Utilize Playwright's tracing capabilities for issue diagnostics\n- Regularly update and maintain Playwright dependencies\n- Document test strategies and scenarios comprehensively\n\n## Quality Checklist\n\n- Ensure full test coverage for critical user flows\n- Use page object model for test structure\n- Handle flaky tests through retries and waits\n- Optimize tests for speed and reliability\n- Validate test outputs with assertions\n- Implement error handling and cleanup routines\n- Maintain consistency in test data across environments\n- Review and optimize test execution time\n- Conduct peer reviews of test cases\n- Monitor test runs and maintain test stability\n\n## Output\n\n- Comprehensive Playwright test suite with modular structure\n- Test cases with detailed descriptions and comments\n- Execution reports with clear pass\u002Ffail indications\n- Screenshots and videos of test runs for debugging\n- Automated test setup for local and CI environments\n- Test artifacts stored and accessible for analysis\n- Configuration files for environment-specific settings\n- Detailed documentation of test cases and structure\n- Maintained backlog of test improvements and updates\n\n",{"name":5,"metadata":40,"description":7},{"hermes":41},{"tags":42,"source":44},[43,30],"codex-agent","codex-field-kit\u002Fgeneral","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-agents\u002Fplaywright-expert",0,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit","https:\u002F\u002Fgithub.com\u002F0xharryriddle","https:\u002F\u002Fharryriddle.vercel.app","2026-04-11 11:49:51",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill playwright-expert",{"tool":59,"command":60},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill playwright-expert",{"tool":62,"command":63},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill playwright-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Fplaywright-expert\u002FSKILL.md",true,[],[68,98,117,127,152,179],{"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":77,"publishedAt":35},"01M6H7ZKE6MR33HC84QZ1TA6MV","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97],"react best practices","react","vercel react best practices","best practices","vercel","tasks","data fetching","triggers","pages","next","performance optimization","refactoring","Next.js","Optimization","code","guidelines","react components","components","performance","writing",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":35},"01M6H7ZGC2WK8SEKYHWDNTMDA9","swarm-planner","[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fswarm-planner\u002FSKILL.md",[],[105,106,107,108,109,110,111,112,113,114,115,116],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","for","multi","implementation",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":35},"01M6H7ZD93853RZCYQWH1D38TM","super-swarm-spark","Only to be triggered by explicit super-swarm-spark commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fsuper-swarm-spark\u002FSKILL.md",[],[124,105,125,110,126],"super swarm spark","spark","commands",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":35},"01M6H7Z987QBY49JCCPT953EAZ","role-creator","Create and install Codex custom agent roles in ~\u002F.codex\u002Fconfig.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Frole-creator\u002FSKILL.md",[],[134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,27,151],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":161,"publishedAt":35},"01M6H7Z5TRPMDQ7YSZQXPN1G60","read-github","Read and search GitHub repository documentation via gitmcp.io MCP service.\n\n**WHEN TO USE:**\n- User provides a GitHub URL\n- User mentions a specific repo in owner\u002Frepo format\n- User asks \"what does this repo do?\", \"read the docs for X repo\", or similar\n- User wants to search code or docs within a repo","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fread-github\u002FSKILL.md",[158],{"categoryNo":159,"categoryName":160,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[162,163,164,92,165,166,167,168,114,169,170,171,172,173,174,29,175,176,177,178],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","user","repo","format","repository",{"skillNo":180,"name":107,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":35},"01M6H7Z215CTKYJ4Y1X6EQWN6M","Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: \"make a plan\", \"create a plan\", \"plan this out\", \"plan the implementation\", \"help me plan\", \"design a plan\", \"draft a plan\", \"write a plan\", \"outline the steps\", \"break this down into tasks\", \"what's the plan for\", or any similar planning request. Also triggers on explicit \"\u002Fplanner\" or \"\u002Fplan\" commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fplanner\u002FSKILL.md",[],[107,185,114,186,32,187,85,112,126,188,189,29,190,191,192,193,194,149,83,195],"outline","atomic","sprints","draft","me","write","phased implementation","plan","help","planning","design"]