[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C3DQTQP4G00PJBFVHTDNGR":3,"skill-same:01M6C3DQTQP4G00PJBFVHTDNGR":80},{"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":24,"linkOnly":25,"markdownContent":26,"markdownBody":27,"frontMatter":28,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":6,"updatedAt":36,"install":37,"resources":49},"01M6C3DQTQP4G00PJBFVHTDNGR","to-spec",null,"Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.","thegiantbeast\u002Fdotfiles","thegiantbeast","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F31733?v=4","01M6C3CJSWCN22VMJ7DZ7KJX02","Ricardo Ferreira","01M6C3CJY6G03VP48FRFK8HEGE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpocock-picks\u002Fskills\u002Fengineering\u002Fto-spec\u002FSKILL.md",[],[19,20,21,22,23],"spec","to spec","publish","just","interview","2026-11-10 10:12:30",false,"---\nname: to-spec\ndescription: Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.\ndisable-model-invocation: true\n---\n\nThis skill takes the current conversation context and codebase understanding and produces a spec (you may know this document as a PRD). Do NOT interview the user — just synthesize what you already know.\n\nThe issue tracker and triage label vocabulary should have been provided to you — run `\u002Fsetup-matt-pocock-skills` if not.\n\n## Process\n\n1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.\n\n2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.\n\nCheck with the user that these seams match their expectations.\n\n3. Write the spec using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.\n\n\u003Cspec-template>\n\n## Problem Statement\n\nThe problem that the user is facing, from the user's perspective.\n\n## Solution\n\nThe solution to the problem, from the user's perspective.\n\n## User Stories\n\nA LONG, numbered list of user stories. Each user story should be in the format of:\n\n1. As an \u003Cactor>, I want a \u003Cfeature>, so that \u003Cbenefit>\n\n\u003Cuser-story-example>\n1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending\n\u003C\u002Fuser-story-example>\n\nThis list of user stories should be extremely extensive and cover all aspects of the feature.\n\n## Implementation Decisions\n\nA list of implementation decisions that were made. This can include:\n\n- The modules that will be built\u002Fmodified\n- The interfaces of those modules that will be modified\n- Technical clarifications from the developer\n- Architectural decisions\n- Schema changes\n- API contracts\n- Specific interactions\n\nDo NOT include specific file paths or code snippets. They may end up being outdated very quickly.\n\nException: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.\n\n## Testing Decisions\n\nA list of testing decisions that were made. Include:\n\n- A description of what makes a good test (only test external behavior, not implementation details)\n- Which modules will be tested\n- Prior art for the tests (i.e. similar types of tests in the codebase)\n\n## Out of Scope\n\nA description of the things that are out of scope for this spec.\n\n## Further Notes\n\nAny further notes about the feature.\n\n\u003C\u002Fspec-template>\n","This skill takes the current conversation context and codebase understanding and produces a spec (you may know this document as a PRD). Do NOT interview the user — just synthesize what you already know.\n\nThe issue tracker and triage label vocabulary should have been provided to you — run `\u002Fsetup-matt-pocock-skills` if not.\n\n## Process\n\n1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.\n\n2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.\n\nCheck with the user that these seams match their expectations.\n\n3. Write the spec using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.\n\n\u003Cspec-template>\n\n## Problem Statement\n\nThe problem that the user is facing, from the user's perspective.\n\n## Solution\n\nThe solution to the problem, from the user's perspective.\n\n## User Stories\n\nA LONG, numbered list of user stories. Each user story should be in the format of:\n\n1. As an \u003Cactor>, I want a \u003Cfeature>, so that \u003Cbenefit>\n\n\u003Cuser-story-example>\n1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending\n\u003C\u002Fuser-story-example>\n\nThis list of user stories should be extremely extensive and cover all aspects of the feature.\n\n## Implementation Decisions\n\nA list of implementation decisions that were made. This can include:\n\n- The modules that will be built\u002Fmodified\n- The interfaces of those modules that will be modified\n- Technical clarifications from the developer\n- Architectural decisions\n- Schema changes\n- API contracts\n- Specific interactions\n\nDo NOT include specific file paths or code snippets. They may end up being outdated very quickly.\n\nException: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.\n\n## Testing Decisions\n\nA list of testing decisions that were made. Include:\n\n- A description of what makes a good test (only test external behavior, not implementation details)\n- Which modules will be tested\n- Prior art for the tests (i.e. similar types of tests in the codebase)\n\n## Out of Scope\n\nA description of the things that are out of scope for this spec.\n\n## Further Notes\n\nAny further notes about the feature.\n\n\u003C\u002Fspec-template>\n",{"name":5,"description":7,"disable-model-invocation":29},true,"main","215248b05d6d96e163fec33f3c171019a95abd72",".claude\u002Fskills\u002Fpocock-picks\u002Fskills\u002Fengineering\u002Fto-spec","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fthegiantbeast","https:\u002F\u002Fthegiantbeast.tech","2026-11-11 21:04:22",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":29},[39,42,45],{"tool":40,"command":41},"npx","npx skills add thegiantbeast\u002Fdotfiles --skill to-spec",{"tool":43,"command":44},"bunx","bunx skills add thegiantbeast\u002Fdotfiles --skill to-spec",{"tool":46,"command":47},"pnpm","pnpm dlx skills add thegiantbeast\u002Fdotfiles --skill to-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpocock-picks\u002Fskills\u002Fengineering\u002Fto-spec\u002FSKILL.md",[50,56,62,68,72,76],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002FREADME.md","ASSET","资产文件",413,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsecurity\u002Faccess-control-auditor\u002Fskills\u002Fauditing-access-control\u002Fassets\u002FREADME.md",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002FREADME.md","REFERENCE","参考文档",522,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsecurity\u002Faccess-control-auditor\u002Fskills\u002Fauditing-access-control\u002Freferences\u002FREADME.md",{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"scripts\u002Faccess_control_audit.py","SCRIPT","脚本",4984,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsecurity\u002Faccess-control-auditor\u002Fskills\u002Fauditing-access-control\u002Fscripts\u002Faccess_control_audit.py",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"scripts\u002Fpolicy_parser.py",2931,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsecurity\u002Faccess-control-auditor\u002Fskills\u002Fauditing-access-control\u002Fscripts\u002Fpolicy_parser.py",{"path":73,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002FREADME.md",584,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsecurity\u002Faccess-control-auditor\u002Fskills\u002Fauditing-access-control\u002Fscripts\u002FREADME.md",{"path":77,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":78,"sourceHtmlUrl":79},"scripts\u002Freport_generator.py",3011,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsecurity\u002Faccess-control-auditor\u002Fskills\u002Fauditing-access-control\u002Fscripts\u002Freport_generator.py",[81,114,131,140,149,163],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":97,"publishedAt":24},"01M6CA623HKJ9PE7HJC00DXM04","web-quality-audit","Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to \"audit my site\", \"review web quality\", \"run lighthouse audit\", \"check page quality\", or \"optimize my website\".","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-quality-picks\u002Fskills\u002Fweb-quality-audit\u002FSKILL.md",[87,92],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113],"quality","web quality audit","audit","web","run","use","check","page","site","Lighthouse","seo","website","best practices","accessibility","performance","review",{"skillNo":115,"name":108,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":121,"publishedAt":24},"01M6CA5Z9ZK57YANF0QTVXNNKJ","Optimize for search engine visibility and ranking. Use when asked to \"improve SEO\", \"optimize for search\", \"fix meta tags\", \"add structured data\", \"sitemap optimization\", or \"search engine optimization\".","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-quality-picks\u002Fskills\u002Fseo\u002FSKILL.md",[119,120],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},[108,122,123,124,125,101,126,127,103,128,98,129,130],"Meta","data","Optimization","search","structured data","Meta Tags","fix","engine","improve",{"skillNo":132,"name":112,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":24},"01M6CA5W80QAXDSZC196SY8DZC","Optimize web performance for faster loading and better user experience. Use when asked to \"speed up my site\", \"optimize performance\", \"reduce load time\", \"fix slow loading\", \"improve page speed\", or \"performance audit\".","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-quality-picks\u002Fskills\u002Fperformance\u002FSKILL.md",[],[112,137,106,103,128,138,98,105,101,100,139,130],"up","user","web performance",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":24},"01M6CA5SHNJN3B562C279YE2BV","core-web-vitals","Optimize Core Web Vitals (LCP, INP, CLS) for better page experience and search ranking. Use when asked to \"improve Core Web Vitals\", \"fix LCP\", \"reduce CLS\", \"optimize INP\", \"page experience optimization\", or \"fix layout shifts\".","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-quality-picks\u002Fskills\u002Fcore-web-vitals\u002FSKILL.md",[],[101,147,148,124,103,128,98,105,130,125],"core","core web vitals",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":24},"01M6CA5PSD25C6WSNBEHKHR8QK","best-practices","Apply modern web development best practices for security, compatibility, and code quality. Use when asked to \"apply best practices\", \"security audit\", \"modernize code\", \"code quality review\", or \"check for vulnerabilities\".","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-quality-picks\u002Fskills\u002Fbest-practices\u002FSKILL.md",[],[110,156,101,157,158,113,159,103,104,98,160,161,100,162],"code quality","vulnerabilities","security","development","web development","security audit","code",{"skillNo":164,"name":111,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":24},"01M6CA5KGMHWYVB4M5TJK13ZM5","Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to \"improve accessibility\", \"a11y audit\", \"WCAG compliance\", \"screen reader support\", \"keyboard navigation\", or \"make accessible\".","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-quality-picks\u002Fskills\u002Faccessibility\u002FSKILL.md",[],[111,169,170,103,171,98,130,172,173,100,174,175,101,176],"reader","navigation","a11y audit","WCAG","compliance","web accessibility","guidelines","support"]