[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H73C829VWMFBQS6PRFY3AE":3,"skill-same:01M6H73C829VWMFBQS6PRFY3AE":63},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M6H73C829VWMFBQS6PRFY3AE","jasmine-expert",null,"Use when implementing jasmine 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\u002Fjasmine-expert\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"expert","jasmine expert","testing","codex","Production","quality","use","patterns","with","kit","implementing","2026-11-10 10:12:30",false,"---\nname: jasmine-expert\ndescription: Use when implementing jasmine functionality with production-grade patterns and safeguards.\nmetadata:\n  hermes:\n    tags: [codex-agent, testing-quality]\n    source: codex-field-kit\u002Ftesting-quality\n---\n\n# Jasmine Expert\n\n## Focus Areas\n\n- Understanding Jasmine test suite and spec structure\n- Writing descriptive test cases and using matchers effectively\n- Asynchronous testing with done(), async\u002Fawait, and promises\n- Utilizing spies for mocking and tracking function calls\n- Best practices for organizing test files and suites\n- Sequential and parallel test execution configurations\n- Test-driven development (TDD) methodologies with Jasmine\n- Handling setup and teardown using beforeAll\u002FafterAll and beforeEach\u002FafterEach\n- Ensuring comprehensive test coverage with effective use of tools\n- Integration with continuous integration pipelines\n\n## Approach\n\n- Define clear and concise test suites with meaningful descriptions\n- Break down large test files into smaller, modular test files\n- Write tests that are independent and easy to understand\n- Use custom matchers to express expectations more clearly\n- Apply the Arrange-Act-Assert (AAA) pattern consistently in tests\n- Focus more on edge cases and boundary conditions\n- Ensure tests are deterministic and produce the same result every time\n- Use Spies to replace complex dependencies and isolate the unit under test\n- Keep test feedback fast to ensure quick iteration cycles\n- Regularly refactor tests for clarity and maintainability\n\n## Quality Checklist\n\n- Verify all test cases are passing consistently without flakiness\n- Ensure test descriptions clearly communicate intent\n- Verify use of appropriate Jasmine matchers for different scenarios\n- Confirm asynchronous code is properly handled in tests with done() or async\u002Fawait\n- Review spy usage to ensure accurate and minimal implementation\n- Validate test setup and teardown correctly reset state before each test\n- Run tests in random order to detect implicit dependencies\n- Check for redundant or duplicate tests and eliminate them\n- Perform code coverage analysis to identify untested code paths\n- Ensure tests are well-documented and easy to read\n\n## Output\n\n- Comprehensive and organized test suite using Jasmine framework\n- Test cases covering edge cases and all potential failure points\n- Clean and deterministic tests with accurate setup and teardown\n- High test coverage with minimal false negatives or positives\n- Well-documented tests with clear naming conventions and structure\n- Configurable test environment suited for both development and CI pipelines\n- Efficient test execution with both sequential and parallel options\n- Jasmine spy reports and mock functionality for dependency isolation\n- Automated test results integrated with continuous integration systems\n- Continuous improvement and refactoring of test code based on feedback\n\n","# Jasmine Expert\n\n## Focus Areas\n\n- Understanding Jasmine test suite and spec structure\n- Writing descriptive test cases and using matchers effectively\n- Asynchronous testing with done(), async\u002Fawait, and promises\n- Utilizing spies for mocking and tracking function calls\n- Best practices for organizing test files and suites\n- Sequential and parallel test execution configurations\n- Test-driven development (TDD) methodologies with Jasmine\n- Handling setup and teardown using beforeAll\u002FafterAll and beforeEach\u002FafterEach\n- Ensuring comprehensive test coverage with effective use of tools\n- Integration with continuous integration pipelines\n\n## Approach\n\n- Define clear and concise test suites with meaningful descriptions\n- Break down large test files into smaller, modular test files\n- Write tests that are independent and easy to understand\n- Use custom matchers to express expectations more clearly\n- Apply the Arrange-Act-Assert (AAA) pattern consistently in tests\n- Focus more on edge cases and boundary conditions\n- Ensure tests are deterministic and produce the same result every time\n- Use Spies to replace complex dependencies and isolate the unit under test\n- Keep test feedback fast to ensure quick iteration cycles\n- Regularly refactor tests for clarity and maintainability\n\n## Quality Checklist\n\n- Verify all test cases are passing consistently without flakiness\n- Ensure test descriptions clearly communicate intent\n- Verify use of appropriate Jasmine matchers for different scenarios\n- Confirm asynchronous code is properly handled in tests with done() or async\u002Fawait\n- Review spy usage to ensure accurate and minimal implementation\n- Validate test setup and teardown correctly reset state before each test\n- Run tests in random order to detect implicit dependencies\n- Check for redundant or duplicate tests and eliminate them\n- Perform code coverage analysis to identify untested code paths\n- Ensure tests are well-documented and easy to read\n\n## Output\n\n- Comprehensive and organized test suite using Jasmine framework\n- Test cases covering edge cases and all potential failure points\n- Clean and deterministic tests with accurate setup and teardown\n- High test coverage with minimal false negatives or positives\n- Well-documented tests with clear naming conventions and structure\n- Configurable test environment suited for both development and CI pipelines\n- Efficient test execution with both sequential and parallel options\n- Jasmine spy reports and mock functionality for dependency isolation\n- Automated test results integrated with continuous integration systems\n- Continuous improvement and refactoring of test code based on feedback\n\n",{"name":5,"metadata":35,"description":7},{"hermes":36},{"tags":37,"source":40},[38,39],"codex-agent","testing-quality","codex-field-kit\u002Ftesting-quality","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-agents\u002Fjasmine-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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill jasmine-expert",{"tool":55,"command":56},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill jasmine-expert",{"tool":58,"command":59},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill jasmine-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Fjasmine-expert\u002FSKILL.md",true,[],[64,96,115,125,150,177],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":75,"publishedAt":30},"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",[70],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95],"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":30},"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",[],[103,104,105,106,107,108,109,110,111,112,113,114],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","for","multi","implementation",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":30},"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",[],[122,103,123,108,124],"super swarm spark","spark","commands",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":30},"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",[],[132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,22,149],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":159,"publishedAt":30},"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",[156],{"categoryNo":157,"categoryName":158,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000023","Skill与智能体开发",[160,161,162,90,163,164,165,166,112,167,168,169,170,171,172,25,173,174,175,176],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","user","repo","format","repository",{"skillNo":178,"name":105,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":30},"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",[],[105,183,112,184,27,185,83,110,124,186,187,25,188,189,190,191,192,147,81,193],"outline","atomic","sprints","draft","me","write","phased implementation","plan","help","planning","design"]