[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DFTS9C84WBCG2XSEXTW572":3,"skill-same:01M7DFTS9C84WBCG2XSEXTW572":53},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7DFTS9C84WBCG2XSEXTW572","build-handoff",null,"Turn approved product, tech, toolchain and design definitions into a build-ready repository and a handoff for the coding agent, by orchestrating Matt Pocock's setup, to-spec and to-tickets skills - writes AGENTS.md (alongside Next.js's managed block) and CLAUDE.md, publishes a spec and tracer-bullet tickets on GitHub Issues, adds the human-only setup checklist, lands the docs on main, and gives the paste-ready Code-tab prompt with the Code-tab plugin and MCP setup. Handoff phase called by start-project or askmatt, or when the user explicitly asks for tickets or a Code-tab prompt.","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\u002Fbuild-handoff\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: build-handoff\ndescription: Turn approved product, tech, toolchain and design definitions into a build-ready repository and a handoff for the coding agent, by orchestrating Matt Pocock's setup, to-spec and to-tickets skills - writes AGENTS.md (alongside Next.js's managed block) and CLAUDE.md, publishes a spec and tracer-bullet tickets on GitHub Issues, adds the human-only setup checklist, lands the docs on main, and gives the paste-ready Code-tab prompt with the Code-tab plugin and MCP setup. Handoff phase called by start-project or askmatt, or when the user explicitly asks for tickets or a Code-tab prompt.\n---\n\n# Build Handoff\n\nPlanning happens in Cowork; building in the Code tab, which doesn't see this conversation. The repo must carry everything. Danish to the user, English in files. Invoke skills with the Skill tool (user-only and refused → read `..\u002F\u003Cname>\u002FSKILL.md` and follow it).\n\n## Order of play\n\n1. **Instruction files first.**\n   - `AGENTS.md` is the one project instruction file (Claude Code, Codex and Cursor all read it). Write our `product-studio:managed` block from `references\u002Fagents-md-template.md`. If Next.js's `\u003C!-- BEGIN:nextjs-agent-rules -->` block already exists, keep it untouched above ours; if it doesn't exist yet, don't fake its markers: the walking-skeleton ticket adds it. Update our block in place on later runs; never touch the user's own sections.\n   - `CLAUDE.md` contains `@AGENTS.md` (Next.js convention). If a `CLAUDE.md` with other content exists, move project rules into `AGENTS.md` and leave `CLAUDE.md` importing it (tell the user in one line).\n2. **Configure the repo once.** If `docs\u002Fagents\u002Fissue-tracker.md` is missing, run `product-studio:setup-matt-pocock-skills` with answers pre-filled for a one-word \"ja\": edit `AGENTS.md` (the file carrying the rules; `CLAUDE.md` only imports it); tracker = GitHub Issues whenever the project will live on GitHub, even if this session can't reach GitHub yet; default triage labels; single-context. Setup owns the `## Agent skills` block; it goes inside our managed block. Create the labels now if this session has GitHub reach, otherwise add `gh label create … --force` lines to the Code tab's step 0.\n3. **Toolchain outputs in place.** Confirm `docs\u002Ftoolchain.md`, `.mcp.json`, `.claude\u002Fsettings.json` from define-toolchain exist and match; if the toolchain phase is still running in the background, wait for it here.\n4. **Spec and tickets.**\n   - **Multi-session build** (normal for a new project): run `product-studio:to-spec`. You pick the test seams yourself (the user can't judge them) and state them in one line; the spec is always saved to `docs\u002Fspecs\u002FYYYY-MM-DD-\u003Cfeature>.md`. Show a ≤10-bullet summary and wait for \"godkendt\" **before** it's published. Then `product-studio:to-tickets`: tracer-bullet vertical slices with blocking edges, quizzed in plain Danish before publishing. Always include:\n     - **00 Setup** (human-only steps, step 5), labelled `ready-for-human`, blocking everything. No Docker required: database tests run in the `db-tests` CI job. Optional: a Docker-compatible runtime on the Mac (Docker Desktop or OrbStack; a 16 GB Mac recommended) for faster local runs in the Code tab. Supabase branching is optional (paid plan, about $0.013\u002Fhour per branch, outside the Spend Cap) and never replaces the CI test job.\n     - **01 Walking skeleton**: scaffold with `create-next-app` **in a temporary folder** (it refuses a non-empty directory and writes its own AGENTS.md\u002FCLAUDE.md), then merge it into the repo: keep Next's AGENTS.md block, keep our managed block after it, keep `CLAUDE.md` = `@AGENTS.md`, keep every doc. Then `supabase init` (commit `supabase\u002Fconfig.toml`; `supabase start` in the `db-tests` job needs it), `supabase\u002Ftests\u002F00000-supabase_test_helpers.sql` copied from harden's assets, Supabase clients, auth, one real screen on a Vercel preview, CI green. Also: `CONSTRAINTS.md` written with `product-studio:constraint-driven-development` using our stack defaults as recommended answers (you fill them; the user decides only product, feel and money), plus `scripts\u002Ffloor-guard.mjs` adapted from its `references\u002Ffloor-guard.md`; and a base `ci.yml` (lint, typecheck, test, build, `semgrep scan --config p\u002Fdefault --error --metrics=off` in the `semgrep\u002Fsemgrep` container (skipped for dependabot), floor-guard with `fetch-depth: 0`, a `db-tests` job (triggered on `pull_request` and on `push` to `feat\u002F**`; setup-cli → `supabase start -x studio,imgproxy,vector,logflare,mailpit` → `supabase test db`), Playwright report uploaded on failure) with `dependabot.yml`.\n     - **02 Capture the design system**: run impeccable `document` in scan mode now that code exists, turning the seed `DESIGN.md` into real tokens + Components + `.impeccable\u002Fdesign.json`, and wire the tokens into Tailwind\u002Fshadcn CSS variables per `docs\u002Fdesign\u002Fcomponent-states.md`.\n   - **Small change** (from askmatt): one ticket, labelled `size:bounded` when it's an existing flow, one seam and no schema\u002FRLS\u002Fauth change (build-ticket then skips the plan document), with acceptance criteria, including visual acceptance (\"cards match DESIGN.md hover state\"), the impeccable command to apply if the route came from a design critique, and, for data changes, \"supabase-security-reviewer finds no blocker\". Show before publishing.\n   - **Publishing.** With GitHub reach: publish now (issues with native blocking links; label `ready-for-agent`, except 00). Without: write the tickets as files in `docs\u002Fspecs\u002F\u003Cfeature>\u002Ftickets\u002FNN-\u003Cslug>.md` (Matt's local-ticket template) and let the Code tab publish them in its step 0.\n5. **Human-only steps** (ticket 00): a numbered checklist with direct links and exact clicks: create the Supabase project in the chosen EU region; install the Vercel↔Supabase integration; import the GitHub repo in Vercel; enable Supabase's GitHub integration\u002Fbranching if chosen; create a fine-grained GitHub token for this repo if the GitHub MCP is used; add the connectors from define-toolchain. Offer `product-studio:wizard` only if the user will run a script in their own terminal. When Vercel is linked, record the production URL and project name in `docs\u002Ftech.md`.\n6. **Commit, and get the docs onto `main`.** Before the first commit, make sure `.gitignore` contains `.worktrees\u002F`, `.superpowers\u002F`, `.claude\u002Fworktrees\u002F`, `.claude\u002Fsettings.local.json` and `.env*` (except `.env.example`), so the first build worktree never has to commit a `.gitignore` fix on `main`. Commit in the connected folder (no login needed). With GitHub reach, push: a new repo's first commit goes straight to `main`; on an existing repo use branch `docs\u002F\u003Ctopic>`, a PR, and merge after \"godkendt\". Without GitHub reach, the push is the Code tab's step 0. The build agent branches from `main`, so docs land before any ticket starts. Append to `docs\u002Flog.md`.\n7. **The Code-tab prompt.** One fenced block from `references\u002Fcode-tab-prompt.md`, including step 0 when this session couldn't do the remote parts. Below it, the one-time Code-tab setup from `docs\u002Ftoolchain.md`:\n   - Preferred: install **product-studio** in the Code tab too (the same plugin; see the README's \"Code tab\" section), so `build-ticket`, the Superpowers execution skills, `next-dev-loop` and the review agents exist there. Then don't also install `mattpocock-skills`, the `superpowers` plugin itself (its SessionStart hook forces its methodology on every session), Addy's `agent-skills`, or the vendor plugins whose skills we already bundle (duplicates compete); take their MCPs from the repo's `.mcp.json` instead.\n   - Optional, design-heavy builds: `\u002Fimpeccable hooks on` in the Code tab (writes to the git-ignored `.claude\u002Fsettings.local.json`; suggest `hook.quiet: true`). Ask yes\u002Fno; default no.\n   - If product-studio can't be installed there: `\u002Fplugin install mattpocock-skills@claude-plugins-official` and the vendor plugins the toolchain chose (e.g. `vercel`, `supabase`, `typescript-lsp`), and copy our three agents into the repo's `.claude\u002Fagents\u002F`.\n   - Either way: `security-guidance` (always-on security checks), and \"approve the project MCP servers when the Code tab asks\".\n8. **Close the loop.** The Code tab opens a PR per ticket; Vercel posts a preview URL; `\u002Fharden` gives the independent verdict (in the Code tab, or from Cowork with `\u002Fharden`); only SHIP merges. Offer to add harden's CI gate as a required check once the first PR exists.\n\n## Done when\n\nEverything is committed in the connected folder and either pushed to `main` or queued as the Code tab's step 0; the spec and tickets exist (GitHub or `docs\u002Fspecs\u002F\u003Cfeature>\u002Ftickets\u002F`); the user has the prompt and the setup lines.\n","# Build Handoff\n\nPlanning happens in Cowork; building in the Code tab, which doesn't see this conversation. The repo must carry everything. Danish to the user, English in files. Invoke skills with the Skill tool (user-only and refused → read `..\u002F\u003Cname>\u002FSKILL.md` and follow it).\n\n## Order of play\n\n1. **Instruction files first.**\n   - `AGENTS.md` is the one project instruction file (Claude Code, Codex and Cursor all read it). Write our `product-studio:managed` block from `references\u002Fagents-md-template.md`. If Next.js's `\u003C!-- BEGIN:nextjs-agent-rules -->` block already exists, keep it untouched above ours; if it doesn't exist yet, don't fake its markers: the walking-skeleton ticket adds it. Update our block in place on later runs; never touch the user's own sections.\n   - `CLAUDE.md` contains `@AGENTS.md` (Next.js convention). If a `CLAUDE.md` with other content exists, move project rules into `AGENTS.md` and leave `CLAUDE.md` importing it (tell the user in one line).\n2. **Configure the repo once.** If `docs\u002Fagents\u002Fissue-tracker.md` is missing, run `product-studio:setup-matt-pocock-skills` with answers pre-filled for a one-word \"ja\": edit `AGENTS.md` (the file carrying the rules; `CLAUDE.md` only imports it); tracker = GitHub Issues whenever the project will live on GitHub, even if this session can't reach GitHub yet; default triage labels; single-context. Setup owns the `## Agent skills` block; it goes inside our managed block. Create the labels now if this session has GitHub reach, otherwise add `gh label create … --force` lines to the Code tab's step 0.\n3. **Toolchain outputs in place.** Confirm `docs\u002Ftoolchain.md`, `.mcp.json`, `.claude\u002Fsettings.json` from define-toolchain exist and match; if the toolchain phase is still running in the background, wait for it here.\n4. **Spec and tickets.**\n   - **Multi-session build** (normal for a new project): run `product-studio:to-spec`. You pick the test seams yourself (the user can't judge them) and state them in one line; the spec is always saved to `docs\u002Fspecs\u002FYYYY-MM-DD-\u003Cfeature>.md`. Show a ≤10-bullet summary and wait for \"godkendt\" **before** it's published. Then `product-studio:to-tickets`: tracer-bullet vertical slices with blocking edges, quizzed in plain Danish before publishing. Always include:\n     - **00 Setup** (human-only steps, step 5), labelled `ready-for-human`, blocking everything. No Docker required: database tests run in the `db-tests` CI job. Optional: a Docker-compatible runtime on the Mac (Docker Desktop or OrbStack; a 16 GB Mac recommended) for faster local runs in the Code tab. Supabase branching is optional (paid plan, about $0.013\u002Fhour per branch, outside the Spend Cap) and never replaces the CI test job.\n     - **01 Walking skeleton**: scaffold with `create-next-app` **in a temporary folder** (it refuses a non-empty directory and writes its own AGENTS.md\u002FCLAUDE.md), then merge it into the repo: keep Next's AGENTS.md block, keep our managed block after it, keep `CLAUDE.md` = `@AGENTS.md`, keep every doc. Then `supabase init` (commit `supabase\u002Fconfig.toml`; `supabase start` in the `db-tests` job needs it), `supabase\u002Ftests\u002F00000-supabase_test_helpers.sql` copied from harden's assets, Supabase clients, auth, one real screen on a Vercel preview, CI green. Also: `CONSTRAINTS.md` written with `product-studio:constraint-driven-development` using our stack defaults as recommended answers (you fill them; the user decides only product, feel and money), plus `scripts\u002Ffloor-guard.mjs` adapted from its `references\u002Ffloor-guard.md`; and a base `ci.yml` (lint, typecheck, test, build, `semgrep scan --config p\u002Fdefault --error --metrics=off` in the `semgrep\u002Fsemgrep` container (skipped for dependabot), floor-guard with `fetch-depth: 0`, a `db-tests` job (triggered on `pull_request` and on `push` to `feat\u002F**`; setup-cli → `supabase start -x studio,imgproxy,vector,logflare,mailpit` → `supabase test db`), Playwright report uploaded on failure) with `dependabot.yml`.\n     - **02 Capture the design system**: run impeccable `document` in scan mode now that code exists, turning the seed `DESIGN.md` into real tokens + Components + `.impeccable\u002Fdesign.json`, and wire the tokens into Tailwind\u002Fshadcn CSS variables per `docs\u002Fdesign\u002Fcomponent-states.md`.\n   - **Small change** (from askmatt): one ticket, labelled `size:bounded` when it's an existing flow, one seam and no schema\u002FRLS\u002Fauth change (build-ticket then skips the plan document), with acceptance criteria, including visual acceptance (\"cards match DESIGN.md hover state\"), the impeccable command to apply if the route came from a design critique, and, for data changes, \"supabase-security-reviewer finds no blocker\". Show before publishing.\n   - **Publishing.** With GitHub reach: publish now (issues with native blocking links; label `ready-for-agent`, except 00). Without: write the tickets as files in `docs\u002Fspecs\u002F\u003Cfeature>\u002Ftickets\u002FNN-\u003Cslug>.md` (Matt's local-ticket template) and let the Code tab publish them in its step 0.\n5. **Human-only steps** (ticket 00): a numbered checklist with direct links and exact clicks: create the Supabase project in the chosen EU region; install the Vercel↔Supabase integration; import the GitHub repo in Vercel; enable Supabase's GitHub integration\u002Fbranching if chosen; create a fine-grained GitHub token for this repo if the GitHub MCP is used; add the connectors from define-toolchain. Offer `product-studio:wizard` only if the user will run a script in their own terminal. When Vercel is linked, record the production URL and project name in `docs\u002Ftech.md`.\n6. **Commit, and get the docs onto `main`.** Before the first commit, make sure `.gitignore` contains `.worktrees\u002F`, `.superpowers\u002F`, `.claude\u002Fworktrees\u002F`, `.claude\u002Fsettings.local.json` and `.env*` (except `.env.example`), so the first build worktree never has to commit a `.gitignore` fix on `main`. Commit in the connected folder (no login needed). With GitHub reach, push: a new repo's first commit goes straight to `main`; on an existing repo use branch `docs\u002F\u003Ctopic>`, a PR, and merge after \"godkendt\". Without GitHub reach, the push is the Code tab's step 0. The build agent branches from `main`, so docs land before any ticket starts. Append to `docs\u002Flog.md`.\n7. **The Code-tab prompt.** One fenced block from `references\u002Fcode-tab-prompt.md`, including step 0 when this session couldn't do the remote parts. Below it, the one-time Code-tab setup from `docs\u002Ftoolchain.md`:\n   - Preferred: install **product-studio** in the Code tab too (the same plugin; see the README's \"Code tab\" section), so `build-ticket`, the Superpowers execution skills, `next-dev-loop` and the review agents exist there. Then don't also install `mattpocock-skills`, the `superpowers` plugin itself (its SessionStart hook forces its methodology on every session), Addy's `agent-skills`, or the vendor plugins whose skills we already bundle (duplicates compete); take their MCPs from the repo's `.mcp.json` instead.\n   - Optional, design-heavy builds: `\u002Fimpeccable hooks on` in the Code tab (writes to the git-ignored `.claude\u002Fsettings.local.json`; suggest `hook.quiet: true`). Ask yes\u002Fno; default no.\n   - If product-studio can't be installed there: `\u002Fplugin install mattpocock-skills@claude-plugins-official` and the vendor plugins the toolchain chose (e.g. `vercel`, `supabase`, `typescript-lsp`), and copy our three agents into the repo's `.claude\u002Fagents\u002F`.\n   - Either way: `security-guidance` (always-on security checks), and \"approve the project MCP servers when the Code tab asks\".\n8. **Close the loop.** The Code tab opens a PR per ticket; Vercel posts a preview URL; `\u002Fharden` gives the independent verdict (in the Code tab, or from Cowork with `\u002Fharden`); only SHIP merges. Offer to add harden's CI gate as a required check once the first PR exists.\n\n## Done when\n\nEverything is committed in the connected folder and either pushed to `main` or queued as the Code tab's step 0; the spec and tickets exist (GitHub or `docs\u002Fspecs\u002F\u003Cfeature>\u002Ftickets\u002F`); the user has the prompt and the setup lines.\n",{"name":5,"description":7},"main","337c4b675cfdf7b5e53e9311f3c757dac9123236","plugins\u002Fproduct-studio\u002Fskills\u002Fbuild-handoff","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup","https:\u002F\u002Fgithub.com\u002Fphillippasqualato","2026-10-07 04:02:12",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add phillippasqualato\u002FPAPcSetup --skill build-handoff",{"tool":35,"command":36},"bunx","bunx skills add phillippasqualato\u002FPAPcSetup --skill build-handoff",{"tool":38,"command":39},"pnpm","pnpm dlx skills add phillippasqualato\u002FPAPcSetup --skill build-handoff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fbuild-handoff\u002FSKILL.md",true,[43,49],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"references\u002Fagents-md-template.md","REFERENCE","参考文档",8627,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fbuild-handoff\u002Freferences\u002Fagents-md-template.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fcode-tab-prompt.md",2227,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fbuild-handoff\u002Freferences\u002Fcode-tab-prompt.md",[54,61,68,75,82,91],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":86,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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",[],[]]