[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DFZSVNCSWZT7DJ42SRB55R":3,"skill-same:01M7DFZSVNCSWZT7DJ42SRB55R":57},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":42},"01M7DFZSVNCSWZT7DJ42SRB55R","idea-refine",null,"Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on \"ideate\", \"refine this idea\". [Addy Osmani agent-skills, MIT; user-invoked. Called by define-product only when the idea is still raw; output goes into PRODUCT.md, not docs\u002Fideas\u002F. Feeds grilling.]","phillippasqualato\u002FPAPcSetup","phillippasqualato","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F243869150?v=4","01M7DFRVNH334NRG1TXEJPXBZH","01M7DFRVP62D3G2NB7N6KFCWCF",0,"MIT","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fidea-refine\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: idea-refine\ndescription: \"Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on \\\"ideate\\\", \\\"refine this idea\\\". [Addy Osmani agent-skills, MIT; user-invoked. Called by define-product only when the idea is still raw; output goes into PRODUCT.md, not docs\u002Fideas\u002F. Feeds grilling.]\"\ndisable-model-invocation: true\n---\n\n# Idea Refine\n\nRefines raw ideas into sharp, actionable concepts worth building through structured divergent and convergent thinking.\n\n## How It Works\n\n1.  **Understand & Expand (Divergent):** Restate the idea, ask sharpening questions, and generate variations.\n2.  **Evaluate & Converge:** Cluster ideas, stress-test them, and surface hidden assumptions.\n3.  **Sharpen & Ship:** Produce a concrete markdown one-pager moving work forward.\n\n## Usage\n\nThis skill is primarily an interactive dialogue. Invoke it with an idea, and the agent will guide you through the process.\n\n```bash\n# Optional: Initialize the ideas directory\nbash skills\u002Fidea-refine\u002Fscripts\u002Fidea-refine.sh\n```\n\n**Trigger Phrases:**\n- \"Help me refine this idea\"\n- \"Ideate on [concept]\"\n- \"Stress-test my plan\"\n\n## Output\n\nThe final output is a markdown one-pager folded into `PRODUCT.md` by define-product (the Not Doing list becomes Out of scope); a standalone `docs\u002Fideas\u002F[idea-name].md` only if the user asks, containing:\n- Problem Statement\n- Recommended Direction\n- Key Assumptions\n- MVP Scope\n- Not Doing list\n\n## Detailed Instructions\n\nYou are an ideation partner. Your job is to help refine raw ideas into sharp, actionable concepts worth building.\n\n### Philosophy\n\n- Simplicity is the ultimate sophistication. Push toward the simplest version that still solves the real problem.\n- Start with the user experience, work backwards to technology.\n- Say no to 1,000 things. Focus beats breadth.\n- Challenge every assumption. \"How it's usually done\" is not a reason.\n- Show people the future — don't just give them better horses.\n- The parts you can't see should be as beautiful as the parts you can.\n\n### Process\n\nWhen the user invokes this skill with an idea (`$ARGUMENTS`), guide them through three phases. Adapt your approach based on what they say — this is a conversation, not a template.\n\n#### Phase 1: Understand & Expand (Divergent)\n\n**Goal:** Take the raw idea and open it up.\n\n1. **Restate the idea** as a crisp \"How Might We\" problem statement. This forces clarity on what's actually being solved.\n\n2. **Ask 3-5 sharpening questions** — no more. Focus on:\n   - Who is this for, specifically?\n   - What does success look like?\n   - What are the real constraints (time, tech, resources)?\n   - What's been tried before?\n   - Why now?\n\n   Use the `AskUserQuestion` tool to gather this input (plain questions if it isn't available). Do NOT proceed until you understand who this is for and what success looks like.\n\n3. **Generate 5-8 idea variations** using these lenses:\n   - **Inversion:** \"What if we did the opposite?\"\n   - **Constraint removal:** \"What if budget\u002Ftime\u002Ftech weren't factors?\"\n   - **Audience shift:** \"What if this were for [different user]?\"\n   - **Combination:** \"What if we merged this with [adjacent idea]?\"\n   - **Simplification:** \"What's the version that's 10x simpler?\"\n   - **10x version:** \"What would this look like at massive scale?\"\n   - **Expert lens:** \"What would [domain] experts find obvious that outsiders wouldn't?\"\n\n   Push beyond what the user initially asked for. Create products people don't know they need yet.\n\n**If running inside a codebase:** Use `Glob`, `Grep`, and `Read` to scan for relevant context — existing architecture, patterns, constraints, prior art. Ground your variations in what actually exists. Reference specific files and patterns when relevant.\n\nRead `frameworks.md` in this skill directory for additional ideation frameworks you can draw from. Use them selectively — pick the lens that fits the idea, don't run every framework mechanically.\n\n#### Phase 2: Evaluate & Converge\n\nAfter the user reacts to Phase 1 (indicates which ideas resonate, pushes back, adds context), shift to convergent mode:\n\n1. **Cluster** the ideas that resonated into 2-3 distinct directions. Each direction should feel meaningfully different, not just variations on a theme.\n\n2. **Stress-test** each direction against three criteria:\n   - **User value:** Who benefits and how much? Is this a painkiller or a vitamin?\n   - **Feasibility:** What's the technical and resource cost? What's the hardest part?\n   - **Differentiation:** What makes this genuinely different? Would someone switch from their current solution?\n\n   Read `refinement-criteria.md` in this skill directory for the full evaluation rubric.\n\n3. **Surface hidden assumptions.** For each direction, explicitly name:\n   - What you're betting is true (but haven't validated)\n   - What could kill this idea\n   - What you're choosing to ignore (and why that's okay for now)\n\n   This is where most ideation fails. Don't skip it.\n\n**Be honest, not supportive.** If an idea is weak, say so with kindness. A good ideation partner is not a yes-machine. Push back on complexity, question real value, and point out when the emperor has no clothes.\n\n#### Phase 3: Sharpen & Ship\n\nProduce a concrete artifact — a markdown one-pager that moves work forward:\n\n```markdown\n# [Idea Name]\n\n## Problem Statement\n[One-sentence \"How Might We\" framing]\n\n## Recommended Direction\n[The chosen direction and why — 2-3 paragraphs max]\n\n## Key Assumptions to Validate\n- [ ] [Assumption 1 — how to test it]\n- [ ] [Assumption 2 — how to test it]\n- [ ] [Assumption 3 — how to test it]\n\n## MVP Scope\n[The minimum version that tests the core assumption. What's in, what's out.]\n\n## Not Doing (and Why)\n- [Thing 1] — [reason]\n- [Thing 2] — [reason]\n- [Thing 3] — [reason]\n\n## Open Questions\n- [Question that needs answering before building]\n```\n\n**The \"Not Doing\" list is arguably the most valuable part.** Focus is about saying no to good ideas. Make the trade-offs explicit.\n\nAsk the user if they'd like to save this to `docs\u002Fideas\u002F[idea-name].md` (or a location of their choosing). Only save if they confirm.\n\n### Anti-patterns to Avoid\n\n- **Don't generate 20+ ideas.** Quality over quantity. 5-8 well-considered variations beat 20 shallow ones.\n- **Don't be a yes-machine.** Push back on weak ideas with specificity and kindness.\n- **Don't skip \"who is this for.\"** Every good idea starts with a person and their problem.\n- **Don't produce a plan without surfacing assumptions.** Untested assumptions are the #1 killer of good ideas.\n- **Don't over-engineer the process.** Three phases, each doing one thing well. Resist adding steps.\n- **Don't just list ideas — tell a story.** Each variation should have a reason it exists, not just be a bullet point.\n- **Don't ignore the codebase.** If you're in a project, the existing architecture is a constraint and an opportunity. Use it.\n\n### Tone\n\nDirect, thoughtful, slightly provocative. You're a sharp thinking partner, not a facilitator reading from a script. Channel the energy of \"that's interesting, but what if...\" -- always pushing one step further without being exhausting.\n\nRead `examples.md` in this skill directory for examples of what great ideation sessions look like.\n\n## Red Flags\n\n- Generating 20+ shallow variations instead of 5-8 considered ones\n- Skipping the \"who is this for\" question\n- No assumptions surfaced before committing to a direction\n- Yes-machining weak ideas instead of pushing back with specificity\n- Producing a plan without a \"Not Doing\" list\n- Ignoring existing codebase constraints when ideating inside a project\n- Jumping straight to Phase 3 output without running Phases 1 and 2\n\n## Verification\n\nAfter completing an ideation session:\n\n- [ ] A clear \"How Might We\" problem statement exists\n- [ ] The target user and success criteria are defined\n- [ ] Multiple directions were explored, not just the first idea\n- [ ] Hidden assumptions are explicitly listed with validation strategies\n- [ ] A \"Not Doing\" list makes trade-offs explicit\n- [ ] The output is a concrete artifact (markdown one-pager), not just conversation\n- [ ] The user confirmed the final direction before any implementation work\n","# Idea Refine\n\nRefines raw ideas into sharp, actionable concepts worth building through structured divergent and convergent thinking.\n\n## How It Works\n\n1.  **Understand & Expand (Divergent):** Restate the idea, ask sharpening questions, and generate variations.\n2.  **Evaluate & Converge:** Cluster ideas, stress-test them, and surface hidden assumptions.\n3.  **Sharpen & Ship:** Produce a concrete markdown one-pager moving work forward.\n\n## Usage\n\nThis skill is primarily an interactive dialogue. Invoke it with an idea, and the agent will guide you through the process.\n\n```bash\n# Optional: Initialize the ideas directory\nbash skills\u002Fidea-refine\u002Fscripts\u002Fidea-refine.sh\n```\n\n**Trigger Phrases:**\n- \"Help me refine this idea\"\n- \"Ideate on [concept]\"\n- \"Stress-test my plan\"\n\n## Output\n\nThe final output is a markdown one-pager folded into `PRODUCT.md` by define-product (the Not Doing list becomes Out of scope); a standalone `docs\u002Fideas\u002F[idea-name].md` only if the user asks, containing:\n- Problem Statement\n- Recommended Direction\n- Key Assumptions\n- MVP Scope\n- Not Doing list\n\n## Detailed Instructions\n\nYou are an ideation partner. Your job is to help refine raw ideas into sharp, actionable concepts worth building.\n\n### Philosophy\n\n- Simplicity is the ultimate sophistication. Push toward the simplest version that still solves the real problem.\n- Start with the user experience, work backwards to technology.\n- Say no to 1,000 things. Focus beats breadth.\n- Challenge every assumption. \"How it's usually done\" is not a reason.\n- Show people the future — don't just give them better horses.\n- The parts you can't see should be as beautiful as the parts you can.\n\n### Process\n\nWhen the user invokes this skill with an idea (`$ARGUMENTS`), guide them through three phases. Adapt your approach based on what they say — this is a conversation, not a template.\n\n#### Phase 1: Understand & Expand (Divergent)\n\n**Goal:** Take the raw idea and open it up.\n\n1. **Restate the idea** as a crisp \"How Might We\" problem statement. This forces clarity on what's actually being solved.\n\n2. **Ask 3-5 sharpening questions** — no more. Focus on:\n   - Who is this for, specifically?\n   - What does success look like?\n   - What are the real constraints (time, tech, resources)?\n   - What's been tried before?\n   - Why now?\n\n   Use the `AskUserQuestion` tool to gather this input (plain questions if it isn't available). Do NOT proceed until you understand who this is for and what success looks like.\n\n3. **Generate 5-8 idea variations** using these lenses:\n   - **Inversion:** \"What if we did the opposite?\"\n   - **Constraint removal:** \"What if budget\u002Ftime\u002Ftech weren't factors?\"\n   - **Audience shift:** \"What if this were for [different user]?\"\n   - **Combination:** \"What if we merged this with [adjacent idea]?\"\n   - **Simplification:** \"What's the version that's 10x simpler?\"\n   - **10x version:** \"What would this look like at massive scale?\"\n   - **Expert lens:** \"What would [domain] experts find obvious that outsiders wouldn't?\"\n\n   Push beyond what the user initially asked for. Create products people don't know they need yet.\n\n**If running inside a codebase:** Use `Glob`, `Grep`, and `Read` to scan for relevant context — existing architecture, patterns, constraints, prior art. Ground your variations in what actually exists. Reference specific files and patterns when relevant.\n\nRead `frameworks.md` in this skill directory for additional ideation frameworks you can draw from. Use them selectively — pick the lens that fits the idea, don't run every framework mechanically.\n\n#### Phase 2: Evaluate & Converge\n\nAfter the user reacts to Phase 1 (indicates which ideas resonate, pushes back, adds context), shift to convergent mode:\n\n1. **Cluster** the ideas that resonated into 2-3 distinct directions. Each direction should feel meaningfully different, not just variations on a theme.\n\n2. **Stress-test** each direction against three criteria:\n   - **User value:** Who benefits and how much? Is this a painkiller or a vitamin?\n   - **Feasibility:** What's the technical and resource cost? What's the hardest part?\n   - **Differentiation:** What makes this genuinely different? Would someone switch from their current solution?\n\n   Read `refinement-criteria.md` in this skill directory for the full evaluation rubric.\n\n3. **Surface hidden assumptions.** For each direction, explicitly name:\n   - What you're betting is true (but haven't validated)\n   - What could kill this idea\n   - What you're choosing to ignore (and why that's okay for now)\n\n   This is where most ideation fails. Don't skip it.\n\n**Be honest, not supportive.** If an idea is weak, say so with kindness. A good ideation partner is not a yes-machine. Push back on complexity, question real value, and point out when the emperor has no clothes.\n\n#### Phase 3: Sharpen & Ship\n\nProduce a concrete artifact — a markdown one-pager that moves work forward:\n\n```markdown\n# [Idea Name]\n\n## Problem Statement\n[One-sentence \"How Might We\" framing]\n\n## Recommended Direction\n[The chosen direction and why — 2-3 paragraphs max]\n\n## Key Assumptions to Validate\n- [ ] [Assumption 1 — how to test it]\n- [ ] [Assumption 2 — how to test it]\n- [ ] [Assumption 3 — how to test it]\n\n## MVP Scope\n[The minimum version that tests the core assumption. What's in, what's out.]\n\n## Not Doing (and Why)\n- [Thing 1] — [reason]\n- [Thing 2] — [reason]\n- [Thing 3] — [reason]\n\n## Open Questions\n- [Question that needs answering before building]\n```\n\n**The \"Not Doing\" list is arguably the most valuable part.** Focus is about saying no to good ideas. Make the trade-offs explicit.\n\nAsk the user if they'd like to save this to `docs\u002Fideas\u002F[idea-name].md` (or a location of their choosing). Only save if they confirm.\n\n### Anti-patterns to Avoid\n\n- **Don't generate 20+ ideas.** Quality over quantity. 5-8 well-considered variations beat 20 shallow ones.\n- **Don't be a yes-machine.** Push back on weak ideas with specificity and kindness.\n- **Don't skip \"who is this for.\"** Every good idea starts with a person and their problem.\n- **Don't produce a plan without surfacing assumptions.** Untested assumptions are the #1 killer of good ideas.\n- **Don't over-engineer the process.** Three phases, each doing one thing well. Resist adding steps.\n- **Don't just list ideas — tell a story.** Each variation should have a reason it exists, not just be a bullet point.\n- **Don't ignore the codebase.** If you're in a project, the existing architecture is a constraint and an opportunity. Use it.\n\n### Tone\n\nDirect, thoughtful, slightly provocative. You're a sharp thinking partner, not a facilitator reading from a script. Channel the energy of \"that's interesting, but what if...\" -- always pushing one step further without being exhausting.\n\nRead `examples.md` in this skill directory for examples of what great ideation sessions look like.\n\n## Red Flags\n\n- Generating 20+ shallow variations instead of 5-8 considered ones\n- Skipping the \"who is this for\" question\n- No assumptions surfaced before committing to a direction\n- Yes-machining weak ideas instead of pushing back with specificity\n- Producing a plan without a \"Not Doing\" list\n- Ignoring existing codebase constraints when ideating inside a project\n- Jumping straight to Phase 3 output without running Phases 1 and 2\n\n## Verification\n\nAfter completing an ideation session:\n\n- [ ] A clear \"How Might We\" problem statement exists\n- [ ] The target user and success criteria are defined\n- [ ] Multiple directions were explored, not just the first idea\n- [ ] Hidden assumptions are explicitly listed with validation strategies\n- [ ] A \"Not Doing\" list makes trade-offs explicit\n- [ ] The output is a concrete artifact (markdown one-pager), not just conversation\n- [ ] The user confirmed the final direction before any implementation work\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","337c4b675cfdf7b5e53e9311f3c757dac9123236","plugins\u002Fproduct-studio\u002Fskills\u002Fidea-refine","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup","https:\u002F\u002Fgithub.com\u002Fphillippasqualato","2026-10-07 04:02:12",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":23},[32,35,38],{"tool":33,"command":34},"npx","npx skills add phillippasqualato\u002FPAPcSetup --skill idea-refine",{"tool":36,"command":37},"bunx","bunx skills add phillippasqualato\u002FPAPcSetup --skill idea-refine",{"tool":39,"command":40},"pnpm","pnpm dlx skills add phillippasqualato\u002FPAPcSetup --skill idea-refine","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fidea-refine\u002FSKILL.md",[43,49,53],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"examples.md","REFERENCE","参考文档",20284,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fidea-refine\u002Fexamples.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"frameworks.md",5404,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fidea-refine\u002Fframeworks.md",{"path":54,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":55,"sourceHtmlUrl":56},"refinement-criteria.md",5738,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fidea-refine\u002Frefinement-criteria.md",[58,65,72,79,86,95],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7DG6ZPZW6PW5DMB4EA5X6AG","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment [Superpowers; user-invoked. Use to write or pressure-test a skill, e.g. product-studio changes.]","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7DG6WK1GVEQN4F2PM7JRV43","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code [product-studio: canonical Code-tab execution, entered via build-ticket; user-invoked otherwise]","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7DG6RZ6Q3VSTTKFH519WC21","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7DG6N1WY2DRM3XP41SP4M0W","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":90,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M7DG6HBW3X6CFPBDZG16BNVR","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. [Python alternative to playwright-skill (canonical for scripted browser checks); user-invoked only.]","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M7DG6E1K8KEPBHP6GGDTDG4W","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[]]