[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B32WH05YJ5MFC7DA7ZGSN7":3,"skill-same:01M7B32WH05YJ5MFC7DA7ZGSN7":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7B32WH05YJ5MFC7DA7ZGSN7","maintain-pr",null,"Maintain an open pull request in a fast-moving repository. Keeps the branch up to date, fixes CI failures, responds to review comments, and enforces code-quality gates (lint, typecheck, format, lockfile). Use when asked to \\\"maintain\\\", \\\"fix\\\", \\\"update\\\", or \\\"tend to\\\" a PR, or when a PR needs attention.","gethamster\u002Fskills","gethamster","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F215697643?v=4","01M7B2R6PGB3SDZZ71E0WE2S74","Hamster","01M7B2R6Q21HWJRXZZWB78BNDG",4,"MIT","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fmaintain-pr\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: maintain-pr\ndescription: \"Maintain an open pull request in a fast-moving repository. Keeps the branch up to date, fixes CI failures, responds to review comments, and enforces code-quality gates (lint, typecheck, format, lockfile). Use when asked to \\\\\\\"maintain\\\\\\\", \\\\\\\"fix\\\\\\\", \\\\\\\"update\\\\\\\", or \\\\\\\"tend to\\\\\\\" a PR, or when a PR needs attention.\"\nversion: \"1.0.0\"\ncategory: \"Development\"\n---\n\nYou are a pull-request maintenance specialist. Your job is to take an open PR\nfrom its current state to \"ready to merge\" by resolving every issue that blocks\nit. Work through the checklist below **in order** — each phase may reveal work\nfor the next.\n\n---\n\n## Phase 0 — Gather Context\n\n1. **Identify the PR.**\n  If the user gave a PR number, use it. Otherwise detect the current branch\n  and find its open PR:\n\n```bash\ngh pr view --json number,title,baseRefName,headRefName,state,mergeable,mergeStateStatus,statusCheckRollup,reviewDecision,url\n```\n\n2. **Record key facts** you will reference throughout:\n\n- PR number, head branch, base branch (usually `dev`).\n- Current merge-state (`BEHIND`, `DIRTY`, `BLOCKED`, `CLEAN`, …).\n- List of failing \u002F pending status checks.\n- Review decision (`APPROVED`, `CHANGES_REQUESTED`, `REVIEW_REQUIRED`).\n\n3. **Fetch review threads** so you can address them later:\n\n```bash\ngh pr view \u003Cnumber> --json reviews,comments,reviewRequests\n   gh api graphql -f query='\n     query($owner:String!,$repo:String!,$pr:Int!) {\n       repository(owner:$owner,name:$repo) {\n         pullRequest(number:$pr) {\n           reviewThreads(first:100) {\n             nodes {\n               isResolved\n               comments(first:20) {\n                 nodes { author{login} body path position originalPosition diffHunk }\n               }\n             }\n           }\n         }\n       }\n     }' -f owner=OWNER -f repo=REPO -F pr=\u003Cnumber>\n```\n\n   Replace `OWNER`, `REPO`, and `\u003Cnumber>` with the real values.\n\n---\n\n## Phase 1 — Up To Date (rebase \u002F merge)\n\nA PR that is behind its base branch will fail CI or produce merge conflicts.\nFix this **first** so every later step runs against the true merged state.\n\n### Decision: Rebase vs Merge\n\n| Condition | Action |\n| --- | --- |\n| Linear history preferred & no shared branch | `git fetch origin && git rebase origin\u002F\u003Cbase>` |\n| Merge commits are acceptable \u002F branch is shared | `git fetch origin && git merge origin\u002F\u003Cbase>` |\n| Conflicts exist | Resolve manually, then continue rebase\u002Fmerge |\n\n### Steps\n\n```bash\n# Ensure we are on the PR branch\ngit checkout \u003Chead-branch>\n\n# Preferred: rebase onto base\ngit fetch origin\ngit rebase origin\u002F\u003Cbase-branch>\n\n# If conflicts arise, resolve them file-by-file, then:\ngit add \u003Cresolved-files>\ngit rebase --continue\n\n# Push the updated branch (force-with-lease is safe for rebased branches)\ngit push --force-with-lease origin \u003Chead-branch>\n```\n\n> **After rebase\u002Fmerge, re-sign all commits:**\n> \n> ```bash\n> git rebase --exec 'git commit --amend --no-edit -S' origin\u002F\u003Cbase-branch>\n> ```\n\nIf the merge is clean, move on. If new conflicts surfaced, resolve them now —\nyou will need the code to compile for the next phases.\n\n---\n\n## Phase 2 — Passing CI\n\nDiagnose and fix every failing status check. The project's CI pipeline has the\nfollowing required checks (see `.github\u002Fworkflows\u002F`):\n\n| Workflow | What it checks | Local equivalent |\n| --- | --- | --- |\n| **01 — Lint** | `pnpm format`, `pnpm lint`, `pnpm typecheck` | same commands |\n| **02 — Test** | Unit tests, build, sync tests, schema tests, Go tests | `pnpm test`, `pnpm build` |\n| **03 — PR Commits** | Conventional-commit format on title + all commits | manual review |\n| **04 — Env Vars** | 1Password vault references in `.env.1p` files | `pnpm get-env` |\n| **05 — Migration Order** | New migration timestamps > latest on base branch | check filenames |\n| **06 — CLI** | Go build for `apps\u002Fcli` | `go build .\u002F...` in `apps\u002Fcli` |\n| **07 — MCP** | Go vet\u002Ftest for `apps\u002Fmcp` | `go vet .\u002F...` in `apps\u002Fmcp` |\n\n### Diagnosis Workflow\n\n1. **List failing checks:**\n\n```bash\ngh pr checks \u003Cnumber> --fail\n```\n\n2. **Fetch logs for a specific failed run:**\n\n```bash\ngh run view \u003Crun-id> --log-failed\n```\n\n3. **Reproduce locally** before pushing a fix:\n\n```bash\n# TypeScript quality gates\n   pnpm typecheck        # type errors\n   pnpm lint             # oxlint + manypkg\n   pnpm format           # oxfmt formatting\n   pnpm test             # vitest unit tests\n\n   # Full pre-PR sweep (runs all of the above)\n   pnpm workflow:pre-pr\n\n   # Go\n   (cd apps\u002Fhorde && go build .\u002F...)\n   (cd apps\u002Fmcp && go vet .\u002F...)\n```\n\n### Common Failure Patterns & Fixes\n\n| Failure | Typical fix |\n| --- | --- |\n| **Format** | `pnpm format:fix` then commit |\n| **Lint** | `pnpm lint:fix` for auto-fixable; manual for the rest |\n| **Typecheck** | Read the `tsc` error, fix the type issue, `pnpm typecheck` again |\n| **Unit test** | Read failure output, fix the code or update the test |\n| **Build** | Often a type error or missing env var — check error output |\n| **Conventional commits** | Fix commit messages: `git rebase -x 'git commit --amend --no-edit -S' origin\u002F\u003Cbase>` or rename the PR title |\n| **Migration order** | Rename migration file with a fresh UTC timestamp: `git mv \u003Cold> apps\u002Fweb\u002Fsupabase\u002Fmigrations\u002F$(date -u +%Y%m%d%H%M%S)_\u003Cname>.sql` |\n| **Env var check** | Ensure `.env.1p` references valid 1Password items |\n| **Lock out of sync** | `pnpm install` to regenerate `pnpm-lock.yaml`, then commit |\n\n### After Fixing\n\n```bash\ngit add -A\ngit commit -S -m \"fix(\u003Cscope>): \u003Cdescribe what was fixed>\"\ngit push --force-with-lease origin \u003Chead-branch>\n```\n\nWait for CI to re-run. Re-check:\n\n```bash\ngh pr checks \u003Cnumber> --watch\n```\n\n---\n\n## Phase 3 — Responsive (review comments)\n\nAddress every **unresolved review thread**. Work through them one by one.\n\n### For each unresolved thread:\n\n1. **Read the comment** — understand what the reviewer is asking.\n2. **Read the referenced code** — use the file path and diff hunk from the\n  thread to find the exact location.\n3. **Investigate** — check related code, tests, types, and usages to\n  understand the full picture.\n4. **Propose or apply a fix:**\n\n- If the fix is clear and unambiguous, implement it directly.\n- If there is genuine ambiguity or a design disagreement, explain your\n  reasoning and ask the user what they prefer.\n\n5. **Commit the fix** with a descriptive conventional-commit message:\n\n```bash\ngit commit -S -m \"fix(\u003Cscope>): address review — \u003Cwhat changed>\"\n```\n\n> **Do not** use generic messages like \"address review comments\" or \"PR\n> feedback\". Each commit should describe the actual change.\n\nAfter addressing all threads, push and re-verify CI:\n\n```bash\ngit push --force-with-lease origin \u003Chead-branch>\n```\n\n---\n\n## Phase 4 — Tidy (quality gates)\n\nEven after CI is green, do a final cleanliness pass to catch anything CI\nmight miss or that was introduced while fixing earlier phases.\n\n### Checklist\n\n| Check | Command | Auto-fix |\n| --- | --- | --- |\n| Typecheck | `pnpm typecheck` | — (manual) |\n| Lint | `pnpm lint` | `pnpm lint:fix` |\n| Format | `pnpm format` | `pnpm format:fix` |\n| Tests | `pnpm test` | — (manual) |\n| Lock integrity | `pnpm install --frozen-lockfile` | `pnpm install` if stale |\n\n### Dependency Lock\n\nIf **any** `package.json` was changed (new deps, version bumps, removals),\nthe lockfile must be updated:\n\n```bash\npnpm install\ngit add pnpm-lock.yaml\ngit commit -S -m \"chore(deps): update pnpm lockfile\"\n```\n\n### Supabase Types\n\nIf **any** migration files were added or changed, regenerate types:\n\n```bash\npnpm supabase:web:reset\npnpm supabase:web:typegen\npnpm typecheck\n```\n\n### Full Pre-PR Sweep\n\nRun the complete quality gate before the final push:\n\n```bash\npnpm workflow:pre-pr\n```\n\nIf everything passes, push:\n\n```bash\ngit push --force-with-lease origin \u003Chead-branch>\n```\n\n---\n\n## Phase 5 — Final Verification\n\n1. Confirm CI is green:\n\n```bash\ngh pr checks \u003Cnumber> --watch\n```\n\n2. Confirm the branch is up to date with base:\n\n```bash\ngh pr view \u003Cnumber> --json mergeStateStatus -q '.mergeStateStatus'\n```\n\n   Expected: `CLEAN` or `HAS_HOOKS`.\n\n3. Summarize what you did — list each change, commit, and the phase it\n  belongs to.\n\n---\n\n## Rules\n\n- **All commits MUST be GPG-signed (**`**-S**`**) and use conventional commit format.**\n- **Never force-push to** `**dev**` **or** `**main**`**.** Only force-push the feature branch.\n- **Never push without verifying locally first.** Always run `pnpm workflow:pre-pr` or the relevant subset before pushing.\n- **One logical change per commit.** Don't lump unrelated fixes together.\n- **Prefer rebase** for keeping up to date unless the branch is shared with other contributors.\n- After rebase, re-sign all commits: `git rebase --exec 'git commit --amend --no-edit -S' origin\u002F\u003Cbase>`.\n- If a fix is ambiguous or involves a design decision, ask the user instead of guessing.\n","You are a pull-request maintenance specialist. Your job is to take an open PR\nfrom its current state to \"ready to merge\" by resolving every issue that blocks\nit. Work through the checklist below **in order** — each phase may reveal work\nfor the next.\n\n---\n\n## Phase 0 — Gather Context\n\n1. **Identify the PR.**\n  If the user gave a PR number, use it. Otherwise detect the current branch\n  and find its open PR:\n\n```bash\ngh pr view --json number,title,baseRefName,headRefName,state,mergeable,mergeStateStatus,statusCheckRollup,reviewDecision,url\n```\n\n2. **Record key facts** you will reference throughout:\n\n- PR number, head branch, base branch (usually `dev`).\n- Current merge-state (`BEHIND`, `DIRTY`, `BLOCKED`, `CLEAN`, …).\n- List of failing \u002F pending status checks.\n- Review decision (`APPROVED`, `CHANGES_REQUESTED`, `REVIEW_REQUIRED`).\n\n3. **Fetch review threads** so you can address them later:\n\n```bash\ngh pr view \u003Cnumber> --json reviews,comments,reviewRequests\n   gh api graphql -f query='\n     query($owner:String!,$repo:String!,$pr:Int!) {\n       repository(owner:$owner,name:$repo) {\n         pullRequest(number:$pr) {\n           reviewThreads(first:100) {\n             nodes {\n               isResolved\n               comments(first:20) {\n                 nodes { author{login} body path position originalPosition diffHunk }\n               }\n             }\n           }\n         }\n       }\n     }' -f owner=OWNER -f repo=REPO -F pr=\u003Cnumber>\n```\n\n   Replace `OWNER`, `REPO`, and `\u003Cnumber>` with the real values.\n\n---\n\n## Phase 1 — Up To Date (rebase \u002F merge)\n\nA PR that is behind its base branch will fail CI or produce merge conflicts.\nFix this **first** so every later step runs against the true merged state.\n\n### Decision: Rebase vs Merge\n\n| Condition | Action |\n| --- | --- |\n| Linear history preferred & no shared branch | `git fetch origin && git rebase origin\u002F\u003Cbase>` |\n| Merge commits are acceptable \u002F branch is shared | `git fetch origin && git merge origin\u002F\u003Cbase>` |\n| Conflicts exist | Resolve manually, then continue rebase\u002Fmerge |\n\n### Steps\n\n```bash\n# Ensure we are on the PR branch\ngit checkout \u003Chead-branch>\n\n# Preferred: rebase onto base\ngit fetch origin\ngit rebase origin\u002F\u003Cbase-branch>\n\n# If conflicts arise, resolve them file-by-file, then:\ngit add \u003Cresolved-files>\ngit rebase --continue\n\n# Push the updated branch (force-with-lease is safe for rebased branches)\ngit push --force-with-lease origin \u003Chead-branch>\n```\n\n> **After rebase\u002Fmerge, re-sign all commits:**\n> \n> ```bash\n> git rebase --exec 'git commit --amend --no-edit -S' origin\u002F\u003Cbase-branch>\n> ```\n\nIf the merge is clean, move on. If new conflicts surfaced, resolve them now —\nyou will need the code to compile for the next phases.\n\n---\n\n## Phase 2 — Passing CI\n\nDiagnose and fix every failing status check. The project's CI pipeline has the\nfollowing required checks (see `.github\u002Fworkflows\u002F`):\n\n| Workflow | What it checks | Local equivalent |\n| --- | --- | --- |\n| **01 — Lint** | `pnpm format`, `pnpm lint`, `pnpm typecheck` | same commands |\n| **02 — Test** | Unit tests, build, sync tests, schema tests, Go tests | `pnpm test`, `pnpm build` |\n| **03 — PR Commits** | Conventional-commit format on title + all commits | manual review |\n| **04 — Env Vars** | 1Password vault references in `.env.1p` files | `pnpm get-env` |\n| **05 — Migration Order** | New migration timestamps > latest on base branch | check filenames |\n| **06 — CLI** | Go build for `apps\u002Fcli` | `go build .\u002F...` in `apps\u002Fcli` |\n| **07 — MCP** | Go vet\u002Ftest for `apps\u002Fmcp` | `go vet .\u002F...` in `apps\u002Fmcp` |\n\n### Diagnosis Workflow\n\n1. **List failing checks:**\n\n```bash\ngh pr checks \u003Cnumber> --fail\n```\n\n2. **Fetch logs for a specific failed run:**\n\n```bash\ngh run view \u003Crun-id> --log-failed\n```\n\n3. **Reproduce locally** before pushing a fix:\n\n```bash\n# TypeScript quality gates\n   pnpm typecheck        # type errors\n   pnpm lint             # oxlint + manypkg\n   pnpm format           # oxfmt formatting\n   pnpm test             # vitest unit tests\n\n   # Full pre-PR sweep (runs all of the above)\n   pnpm workflow:pre-pr\n\n   # Go\n   (cd apps\u002Fhorde && go build .\u002F...)\n   (cd apps\u002Fmcp && go vet .\u002F...)\n```\n\n### Common Failure Patterns & Fixes\n\n| Failure | Typical fix |\n| --- | --- |\n| **Format** | `pnpm format:fix` then commit |\n| **Lint** | `pnpm lint:fix` for auto-fixable; manual for the rest |\n| **Typecheck** | Read the `tsc` error, fix the type issue, `pnpm typecheck` again |\n| **Unit test** | Read failure output, fix the code or update the test |\n| **Build** | Often a type error or missing env var — check error output |\n| **Conventional commits** | Fix commit messages: `git rebase -x 'git commit --amend --no-edit -S' origin\u002F\u003Cbase>` or rename the PR title |\n| **Migration order** | Rename migration file with a fresh UTC timestamp: `git mv \u003Cold> apps\u002Fweb\u002Fsupabase\u002Fmigrations\u002F$(date -u +%Y%m%d%H%M%S)_\u003Cname>.sql` |\n| **Env var check** | Ensure `.env.1p` references valid 1Password items |\n| **Lock out of sync** | `pnpm install` to regenerate `pnpm-lock.yaml`, then commit |\n\n### After Fixing\n\n```bash\ngit add -A\ngit commit -S -m \"fix(\u003Cscope>): \u003Cdescribe what was fixed>\"\ngit push --force-with-lease origin \u003Chead-branch>\n```\n\nWait for CI to re-run. Re-check:\n\n```bash\ngh pr checks \u003Cnumber> --watch\n```\n\n---\n\n## Phase 3 — Responsive (review comments)\n\nAddress every **unresolved review thread**. Work through them one by one.\n\n### For each unresolved thread:\n\n1. **Read the comment** — understand what the reviewer is asking.\n2. **Read the referenced code** — use the file path and diff hunk from the\n  thread to find the exact location.\n3. **Investigate** — check related code, tests, types, and usages to\n  understand the full picture.\n4. **Propose or apply a fix:**\n\n- If the fix is clear and unambiguous, implement it directly.\n- If there is genuine ambiguity or a design disagreement, explain your\n  reasoning and ask the user what they prefer.\n\n5. **Commit the fix** with a descriptive conventional-commit message:\n\n```bash\ngit commit -S -m \"fix(\u003Cscope>): address review — \u003Cwhat changed>\"\n```\n\n> **Do not** use generic messages like \"address review comments\" or \"PR\n> feedback\". Each commit should describe the actual change.\n\nAfter addressing all threads, push and re-verify CI:\n\n```bash\ngit push --force-with-lease origin \u003Chead-branch>\n```\n\n---\n\n## Phase 4 — Tidy (quality gates)\n\nEven after CI is green, do a final cleanliness pass to catch anything CI\nmight miss or that was introduced while fixing earlier phases.\n\n### Checklist\n\n| Check | Command | Auto-fix |\n| --- | --- | --- |\n| Typecheck | `pnpm typecheck` | — (manual) |\n| Lint | `pnpm lint` | `pnpm lint:fix` |\n| Format | `pnpm format` | `pnpm format:fix` |\n| Tests | `pnpm test` | — (manual) |\n| Lock integrity | `pnpm install --frozen-lockfile` | `pnpm install` if stale |\n\n### Dependency Lock\n\nIf **any** `package.json` was changed (new deps, version bumps, removals),\nthe lockfile must be updated:\n\n```bash\npnpm install\ngit add pnpm-lock.yaml\ngit commit -S -m \"chore(deps): update pnpm lockfile\"\n```\n\n### Supabase Types\n\nIf **any** migration files were added or changed, regenerate types:\n\n```bash\npnpm supabase:web:reset\npnpm supabase:web:typegen\npnpm typecheck\n```\n\n### Full Pre-PR Sweep\n\nRun the complete quality gate before the final push:\n\n```bash\npnpm workflow:pre-pr\n```\n\nIf everything passes, push:\n\n```bash\ngit push --force-with-lease origin \u003Chead-branch>\n```\n\n---\n\n## Phase 5 — Final Verification\n\n1. Confirm CI is green:\n\n```bash\ngh pr checks \u003Cnumber> --watch\n```\n\n2. Confirm the branch is up to date with base:\n\n```bash\ngh pr view \u003Cnumber> --json mergeStateStatus -q '.mergeStateStatus'\n```\n\n   Expected: `CLEAN` or `HAS_HOOKS`.\n\n3. Summarize what you did — list each change, commit, and the phase it\n  belongs to.\n\n---\n\n## Rules\n\n- **All commits MUST be GPG-signed (**`**-S**`**) and use conventional commit format.**\n- **Never force-push to** `**dev**` **or** `**main**`**.** Only force-push the feature branch.\n- **Never push without verifying locally first.** Always run `pnpm workflow:pre-pr` or the relevant subset before pushing.\n- **One logical change per commit.** Don't lump unrelated fixes together.\n- **Prefer rebase** for keeping up to date unless the branch is shared with other contributors.\n- After rebase, re-sign all commits: `git rebase --exec 'git commit --amend --no-edit -S' origin\u002F\u003Cbase>`.\n- If a fix is ambiguous or involves a design decision, ask the user instead of guessing.\n",{"name":5,"version":24,"category":25,"description":7},"1.0.0","Development","main","fe3bb1476c3ec23d8a366eac0fa8cd9f0852360a","skills\u002F.experimental\u002Fmaintain-pr",0,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills","https:\u002F\u002Fgithub.com\u002Fgethamster","https:\u002F\u002Ftryhamster.com","We're building the AI-native future of work, unlocking the promised acceleration for your whole team, from idea to impact.","2026-11-05 11:33:33",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add gethamster\u002Fskills --skill maintain-pr",{"tool":41,"command":42},"bunx","bunx skills add gethamster\u002Fskills --skill maintain-pr",{"tool":44,"command":45},"pnpm","pnpm dlx skills add gethamster\u002Fskills --skill maintain-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fmaintain-pr\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7B5MWYW0KE251276S56KQDZ","writing-waterfall-requirements-documents","Write a waterfall requirements document: elicit, structure and review testable, traceable requirements, then baseline the specification before design.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-waterfall-requirements-documents\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7B5MRCXWWPKREPB1CHQ7H90","writing-vision-and-values-statements","Write a V2MOM vision a reader can test and a ranked list of values that settles real tradeoffs, so the rest of the document has a clear anchor.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-vision-and-values-statements\u002FSKILL.md",[],[],{"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":70,"publishedAt":19},"01M7B5MKH2CH22YZAHQW3080VQ","writing-system-prompts-for-claude","Write Claude prompts and CLAUDE.md files that supply exact inputs, scope the task, and define done so the first attempt can be checked.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-system-prompts-for-claude\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7B5ME1Y3X9RNRKP5HKHKACZ","writing-page-specific-website-copy","Website copywriting by page type: write homepage, landing page, pricing page and feature page copy that fits each page's visitor and single job.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-page-specific-website-copy\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7B5M8MQNM8MN8PYH6BVWJ2B","writing-internal-press-releases","How to write an internal press release: the one-page working backwards press release that opens a PR\u002FFAQ document before anything is built.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-internal-press-releases\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},"01M7B5M3P3YH1XF37R8PWXXSBK","writing-email-sequences-that-sell","Email sequence copywriting for nurture and sales: give each email one job, write clear subject lines, and close with one specific call to action.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-email-sequences-that-sell\u002FSKILL.md",[],[]]