[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M730XY2E4PPKSC3HBX701GV3":3,"skill-same:01M730XY2E4PPKSC3HBX701GV3":59},{"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":38,"commitSha":39,"skillDirectory":40,"forksCount":14,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M730XY2E4PPKSC3HBX701GV3","software-development-writing-plans",null,"Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.","JOHNadonis\u002Fclaude-code-skills","JOHNadonis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F31716775?v=4","01M72YRBKCVM4ZYJFF7Z71KVQQ","Hongcai Wang","01M72YRBMFSBZNVRJ4D48MWMZ3",0,"MIT","https:\u002F\u002Fgithub.com\u002FJOHNadonis\u002Fclaude-code-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development-writing-plans\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: software-development-writing-plans\ndescription: Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.\nversion: 1.1.0\nauthor: Hermes Agent (adapted from obra\u002Fsuperpowers)\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [planning, design, implementation, workflow, documentation]\n    related_skills: [subagent-driven-development, test-driven-development, requesting-code-review]\n---\n\n# Writing Implementation Plans\n\n## Overview\n\nWrite comprehensive implementation plans assuming the implementer has zero context for the codebase and questionable taste. Document everything they need: which files to touch, complete code, testing commands, docs to check, how to verify. Give them bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.\n\nAssume the implementer is a skilled developer but knows almost nothing about the toolset or problem domain. Assume they don't know good test design very well.\n\n**Core principle:** A good plan makes implementation obvious. If someone has to guess, the plan is incomplete.\n\n## When to Use\n\n**Always use before:**\n- Implementing multi-step features\n- Breaking down complex requirements\n- Delegating to subagents via subagent-driven-development\n\n**Don't skip when:**\n- Feature seems simple (assumptions cause bugs)\n- You plan to implement it yourself (future you needs guidance)\n- Working alone (documentation matters)\n\n## Bite-Sized Task Granularity\n\n**Each task = 2-5 minutes of focused work.**\n\nEvery step is one action:\n- \"Write the failing test\" — step\n- \"Run it to make sure it fails\" — step\n- \"Implement the minimal code to make the test pass\" — step\n- \"Run the tests and make sure they pass\" — step\n- \"Commit\" — step\n\n**Too big:**\n```markdown\n### Task 1: Build authentication system\n[50 lines of code across 5 files]\n```\n\n**Right size:**\n```markdown\n### Task 1: Create User model with email field\n[10 lines, 1 file]\n\n### Task 2: Add password hash field to User\n[8 lines, 1 file]\n\n### Task 3: Create password hashing utility\n[15 lines, 1 file]\n```\n\n## Plan Document Structure\n\n### Header (Required)\n\nEvery plan MUST start with:\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For Hermes:** Use subagent-driven-development skill to implement this plan task-by-task.\n\n**Goal:** [One sentence describing what this builds]\n\n**Architecture:** [2-3 sentences about approach]\n\n**Tech Stack:** [Key technologies\u002Flibraries]\n\n---\n```\n\n### Task Structure\n\nEach task follows this format:\n\n````markdown\n### Task N: [Descriptive Name]\n\n**Objective:** What this task accomplishes (one sentence)\n\n**Files:**\n- Create: `exact\u002Fpath\u002Fto\u002Fnew_file.py`\n- Modify: `exact\u002Fpath\u002Fto\u002Fexisting.py:45-67` (line numbers if known)\n- Test: `tests\u002Fpath\u002Fto\u002Ftest_file.py`\n\n**Step 1: Write failing test**\n\n```python\ndef test_specific_behavior():\n    result = function(input)\n    assert result == expected\n```\n\n**Step 2: Run test to verify failure**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_specific_behavior -v`\nExpected: FAIL — \"function not defined\"\n\n**Step 3: Write minimal implementation**\n\n```python\ndef function(input):\n    return expected\n```\n\n**Step 4: Run test to verify pass**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_specific_behavior -v`\nExpected: PASS\n\n**Step 5: Commit**\n\n```bash\ngit add tests\u002Fpath\u002Ftest.py src\u002Fpath\u002Ffile.py\ngit commit -m \"feat: add specific feature\"\n```\n````\n\n## Writing Process\n\n### Step 1: Understand Requirements\n\nRead and understand:\n- Feature requirements\n- Design documents or user description\n- Acceptance criteria\n- Constraints\n\n### Step 2: Explore the Codebase\n\nUse Hermes tools to understand the project:\n\n```python\n# Understand project structure\nsearch_files(\"*.py\", target=\"files\", path=\"src\u002F\")\n\n# Look at similar features\nsearch_files(\"similar_pattern\", path=\"src\u002F\", file_glob=\"*.py\")\n\n# Check existing tests\nsearch_files(\"*.py\", target=\"files\", path=\"tests\u002F\")\n\n# Read key files\nread_file(\"src\u002Fapp.py\")\n```\n\n### Step 3: Design Approach\n\nDecide:\n- Architecture pattern\n- File organization\n- Dependencies needed\n- Testing strategy\n\n### Step 4: Write Tasks\n\nCreate tasks in order:\n1. Setup\u002Finfrastructure\n2. Core functionality (TDD for each)\n3. Edge cases\n4. Integration\n5. Cleanup\u002Fdocumentation\n\n### Step 5: Add Complete Details\n\nFor each task, include:\n- **Exact file paths** (not \"the config file\" but `src\u002Fconfig\u002Fsettings.py`)\n- **Complete code examples** (not \"add validation\" but the actual code)\n- **Exact commands** with expected output\n- **Verification steps** that prove the task works\n\n### Step 6: Review the Plan\n\nCheck:\n- [ ] Tasks are sequential and logical\n- [ ] Each task is bite-sized (2-5 min)\n- [ ] File paths are exact\n- [ ] Code examples are complete (copy-pasteable)\n- [ ] Commands are exact with expected output\n- [ ] No missing context\n- [ ] DRY, YAGNI, TDD principles applied\n\n### Step 7: Save the Plan\n\n```bash\nmkdir -p docs\u002Fplans\n# Save plan to docs\u002Fplans\u002FYYYY-MM-DD-feature-name.md\ngit add docs\u002Fplans\u002F\ngit commit -m \"docs: add implementation plan for [feature]\"\n```\n\n## Principles\n\n### DRY (Don't Repeat Yourself)\n\n**Bad:** Copy-paste validation in 3 places\n**Good:** Extract validation function, use everywhere\n\n### YAGNI (You Aren't Gonna Need It)\n\n**Bad:** Add \"flexibility\" for future requirements\n**Good:** Implement only what's needed now\n\n```python\n# Bad — YAGNI violation\nclass User:\n    def __init__(self, name, email):\n        self.name = name\n        self.email = email\n        self.preferences = {}  # Not needed yet!\n        self.metadata = {}     # Not needed yet!\n\n# Good — YAGNI\nclass User:\n    def __init__(self, name, email):\n        self.name = name\n        self.email = email\n```\n\n### TDD (Test-Driven Development)\n\nEvery task that produces code should include the full TDD cycle:\n1. Write failing test\n2. Run to verify failure\n3. Write minimal code\n4. Run to verify pass\n\nSee `test-driven-development` skill for details.\n\n### Frequent Commits\n\nCommit after every task:\n```bash\ngit add [files]\ngit commit -m \"type: description\"\n```\n\n## Common Mistakes\n\n### Vague Tasks\n\n**Bad:** \"Add authentication\"\n**Good:** \"Create User model with email and password_hash fields\"\n\n### Incomplete Code\n\n**Bad:** \"Step 1: Add validation function\"\n**Good:** \"Step 1: Add validation function\" followed by the complete function code\n\n### Missing Verification\n\n**Bad:** \"Step 3: Test it works\"\n**Good:** \"Step 3: Run `pytest tests\u002Ftest_auth.py -v`, expected: 3 passed\"\n\n### Missing File Paths\n\n**Bad:** \"Create the model file\"\n**Good:** \"Create: `src\u002Fmodels\u002Fuser.py`\"\n\n## Execution Handoff\n\nAfter saving the plan, offer the execution approach:\n\n**\"Plan complete and saved. Ready to execute using subagent-driven-development — I'll dispatch a fresh subagent per task with two-stage review (spec compliance then code quality). Shall I proceed?\"**\n\nWhen executing, use the `subagent-driven-development` skill:\n- Fresh `delegate_task` per task with full context\n- Spec compliance review after each task\n- Code quality review after spec passes\n- Proceed only when both reviews approve\n\n## Remember\n\n```\nBite-sized tasks (2-5 min each)\nExact file paths\nComplete code (copy-pasteable)\nExact commands with expected output\nVerification steps\nDRY, YAGNI, TDD\nFrequent commits\n```\n\n**A good plan makes implementation obvious.**\n","# Writing Implementation Plans\n\n## Overview\n\nWrite comprehensive implementation plans assuming the implementer has zero context for the codebase and questionable taste. Document everything they need: which files to touch, complete code, testing commands, docs to check, how to verify. Give them bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.\n\nAssume the implementer is a skilled developer but knows almost nothing about the toolset or problem domain. Assume they don't know good test design very well.\n\n**Core principle:** A good plan makes implementation obvious. If someone has to guess, the plan is incomplete.\n\n## When to Use\n\n**Always use before:**\n- Implementing multi-step features\n- Breaking down complex requirements\n- Delegating to subagents via subagent-driven-development\n\n**Don't skip when:**\n- Feature seems simple (assumptions cause bugs)\n- You plan to implement it yourself (future you needs guidance)\n- Working alone (documentation matters)\n\n## Bite-Sized Task Granularity\n\n**Each task = 2-5 minutes of focused work.**\n\nEvery step is one action:\n- \"Write the failing test\" — step\n- \"Run it to make sure it fails\" — step\n- \"Implement the minimal code to make the test pass\" — step\n- \"Run the tests and make sure they pass\" — step\n- \"Commit\" — step\n\n**Too big:**\n```markdown\n### Task 1: Build authentication system\n[50 lines of code across 5 files]\n```\n\n**Right size:**\n```markdown\n### Task 1: Create User model with email field\n[10 lines, 1 file]\n\n### Task 2: Add password hash field to User\n[8 lines, 1 file]\n\n### Task 3: Create password hashing utility\n[15 lines, 1 file]\n```\n\n## Plan Document Structure\n\n### Header (Required)\n\nEvery plan MUST start with:\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For Hermes:** Use subagent-driven-development skill to implement this plan task-by-task.\n\n**Goal:** [One sentence describing what this builds]\n\n**Architecture:** [2-3 sentences about approach]\n\n**Tech Stack:** [Key technologies\u002Flibraries]\n\n---\n```\n\n### Task Structure\n\nEach task follows this format:\n\n````markdown\n### Task N: [Descriptive Name]\n\n**Objective:** What this task accomplishes (one sentence)\n\n**Files:**\n- Create: `exact\u002Fpath\u002Fto\u002Fnew_file.py`\n- Modify: `exact\u002Fpath\u002Fto\u002Fexisting.py:45-67` (line numbers if known)\n- Test: `tests\u002Fpath\u002Fto\u002Ftest_file.py`\n\n**Step 1: Write failing test**\n\n```python\ndef test_specific_behavior():\n    result = function(input)\n    assert result == expected\n```\n\n**Step 2: Run test to verify failure**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_specific_behavior -v`\nExpected: FAIL — \"function not defined\"\n\n**Step 3: Write minimal implementation**\n\n```python\ndef function(input):\n    return expected\n```\n\n**Step 4: Run test to verify pass**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_specific_behavior -v`\nExpected: PASS\n\n**Step 5: Commit**\n\n```bash\ngit add tests\u002Fpath\u002Ftest.py src\u002Fpath\u002Ffile.py\ngit commit -m \"feat: add specific feature\"\n```\n````\n\n## Writing Process\n\n### Step 1: Understand Requirements\n\nRead and understand:\n- Feature requirements\n- Design documents or user description\n- Acceptance criteria\n- Constraints\n\n### Step 2: Explore the Codebase\n\nUse Hermes tools to understand the project:\n\n```python\n# Understand project structure\nsearch_files(\"*.py\", target=\"files\", path=\"src\u002F\")\n\n# Look at similar features\nsearch_files(\"similar_pattern\", path=\"src\u002F\", file_glob=\"*.py\")\n\n# Check existing tests\nsearch_files(\"*.py\", target=\"files\", path=\"tests\u002F\")\n\n# Read key files\nread_file(\"src\u002Fapp.py\")\n```\n\n### Step 3: Design Approach\n\nDecide:\n- Architecture pattern\n- File organization\n- Dependencies needed\n- Testing strategy\n\n### Step 4: Write Tasks\n\nCreate tasks in order:\n1. Setup\u002Finfrastructure\n2. Core functionality (TDD for each)\n3. Edge cases\n4. Integration\n5. Cleanup\u002Fdocumentation\n\n### Step 5: Add Complete Details\n\nFor each task, include:\n- **Exact file paths** (not \"the config file\" but `src\u002Fconfig\u002Fsettings.py`)\n- **Complete code examples** (not \"add validation\" but the actual code)\n- **Exact commands** with expected output\n- **Verification steps** that prove the task works\n\n### Step 6: Review the Plan\n\nCheck:\n- [ ] Tasks are sequential and logical\n- [ ] Each task is bite-sized (2-5 min)\n- [ ] File paths are exact\n- [ ] Code examples are complete (copy-pasteable)\n- [ ] Commands are exact with expected output\n- [ ] No missing context\n- [ ] DRY, YAGNI, TDD principles applied\n\n### Step 7: Save the Plan\n\n```bash\nmkdir -p docs\u002Fplans\n# Save plan to docs\u002Fplans\u002FYYYY-MM-DD-feature-name.md\ngit add docs\u002Fplans\u002F\ngit commit -m \"docs: add implementation plan for [feature]\"\n```\n\n## Principles\n\n### DRY (Don't Repeat Yourself)\n\n**Bad:** Copy-paste validation in 3 places\n**Good:** Extract validation function, use everywhere\n\n### YAGNI (You Aren't Gonna Need It)\n\n**Bad:** Add \"flexibility\" for future requirements\n**Good:** Implement only what's needed now\n\n```python\n# Bad — YAGNI violation\nclass User:\n    def __init__(self, name, email):\n        self.name = name\n        self.email = email\n        self.preferences = {}  # Not needed yet!\n        self.metadata = {}     # Not needed yet!\n\n# Good — YAGNI\nclass User:\n    def __init__(self, name, email):\n        self.name = name\n        self.email = email\n```\n\n### TDD (Test-Driven Development)\n\nEvery task that produces code should include the full TDD cycle:\n1. Write failing test\n2. Run to verify failure\n3. Write minimal code\n4. Run to verify pass\n\nSee `test-driven-development` skill for details.\n\n### Frequent Commits\n\nCommit after every task:\n```bash\ngit add [files]\ngit commit -m \"type: description\"\n```\n\n## Common Mistakes\n\n### Vague Tasks\n\n**Bad:** \"Add authentication\"\n**Good:** \"Create User model with email and password_hash fields\"\n\n### Incomplete Code\n\n**Bad:** \"Step 1: Add validation function\"\n**Good:** \"Step 1: Add validation function\" followed by the complete function code\n\n### Missing Verification\n\n**Bad:** \"Step 3: Test it works\"\n**Good:** \"Step 3: Run `pytest tests\u002Ftest_auth.py -v`, expected: 3 passed\"\n\n### Missing File Paths\n\n**Bad:** \"Create the model file\"\n**Good:** \"Create: `src\u002Fmodels\u002Fuser.py`\"\n\n## Execution Handoff\n\nAfter saving the plan, offer the execution approach:\n\n**\"Plan complete and saved. Ready to execute using subagent-driven-development — I'll dispatch a fresh subagent per task with two-stage review (spec compliance then code quality). Shall I proceed?\"**\n\nWhen executing, use the `subagent-driven-development` skill:\n- Fresh `delegate_task` per task with full context\n- Spec compliance review after each task\n- Code quality review after spec passes\n- Proceed only when both reviews approve\n\n## Remember\n\n```\nBite-sized tasks (2-5 min each)\nExact file paths\nComplete code (copy-pasteable)\nExact commands with expected output\nVerification steps\nDRY, YAGNI, TDD\nFrequent commits\n```\n\n**A good plan makes implementation obvious.**\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"description":7},"Hermes Agent (adapted from obra\u002Fsuperpowers)","1.1.0",{"hermes":27},{"tags":28,"related_skills":34},[29,30,31,32,33],"planning","design","implementation","workflow","documentation",[35,36,37],"subagent-driven-development","test-driven-development","requesting-code-review","main","4ac29a24db9fc8bba16c61b1cdaa3f5058934247","skills\u002Fsoftware-development-writing-plans","https:\u002F\u002Fgithub.com\u002FJOHNadonis\u002Fclaude-code-skills","https:\u002F\u002Fgithub.com\u002FJOHNadonis","Java\u002FGo\u002FC++，student majoring in computer.","2026-10-26 22:44:45",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add JOHNadonis\u002Fclaude-code-skills --skill software-development-writing-plans",{"tool":51,"command":52},"bunx","bunx skills add JOHNadonis\u002Fclaude-code-skills --skill software-development-writing-plans",{"tool":54,"command":55},"pnpm","pnpm dlx skills add JOHNadonis\u002Fclaude-code-skills --skill software-development-writing-plans","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJOHNadonis\u002Fclaude-code-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development-writing-plans\u002FSKILL.md",true,[],[60,68,76,85,92,100],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":64,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7317QQ43D8KSNYCMQ9YSVV4","youtube-clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FJOHNadonis\u002Fclaude-code-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FJOHNadonis\u002Fclaude-code-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"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":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7316R2JBWWT24DEVFGVZ1WW","yao-meta-skill","Create, refactor, evaluate, and package agent skills from workflows, prompts, transcripts, docs, or notes. Use when asked to create a skill, turn a repeated process into a reusable skill, improve an existing skill, add evals, or package a skill for team reuse.","https:\u002F\u002Fgithub.com\u002FJOHNadonis\u002Fclaude-code-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyao-meta-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FJOHNadonis\u002Fclaude-code-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyao-meta-skill\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7314XDMF1VN8H6GE0RXWX3V","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FJOHNadonis\u002Fclaude-code-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FJOHNadonis\u002Fclaude-code-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M73142X503419G1YEBQZVRWJ","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\u002FJOHNadonis\u002Fclaude-code-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7313E33KEXPQSJ6JBSW7CT5","ui-test","AI-powered adversarial UI testing via the browse CLI. Analyzes git diffs to test only what changed, or explores the full app to find bugs. Tests functional correctness, accessibility, responsive layout, and UX heuristics. Use when the user asks to test UI changes, QA a pull request, audit accessibility, or run exploratory testing. Supports local browser (localhost) and remote Browserbase (deployed sites).","https:\u002F\u002Fgithub.com\u002FJOHNadonis\u002Fclaude-code-skills\u002Fblob\u002Fmain\u002Fskills\u002Fui-test\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FJOHNadonis\u002Fclaude-code-skills\u002Fblob\u002Fmain\u002Fskills\u002Fui-test\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M73123QNJHSG1XT7XJPQD0HK","technical-seo-checker","Use when the user asks to \"technical SEO audit\", \"check page speed\", \"crawl issues\", \"Core Web Vitals\", \"site indexing problems\", \"my site is slow\", \"Google cannot crawl my site\", \"mobile issues\", or \"indexing problems\". Performs technical SEO audits covering site speed, crawlability, indexability, mobile-friendliness, security, and structured data. Identifies technical issues preventing optimal search performance. For content and heading element issues, see on-page-seo-auditor. For link architecture, see internal-linking-optimizer.","https:\u002F\u002Fgithub.com\u002FJOHNadonis\u002Fclaude-code-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-seo-checker\u002FSKILL.md",[],[]]