[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MWM7AMPTQBY2N3XZPB72FT":3,"skill-same:01M6MWM7AMPTQBY2N3XZPB72FT":75},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":48,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6MWM7AMPTQBY2N3XZPB72FT","setup-browser-cookies",null,"Import cookies from your real Chromium browser into the headless browse session.\nOpens an interactive picker UI where you select which cookie domains to import.\nUse before QA testing authenticated pages. Use when asked to \"import cookies\",\n\"login to the site\", or \"authenticate the browser\". (gstack)","forbotsake\u002Fforbotsake","forbotsake","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273708741?v=4","01M6MW9A04DY7WQBA8YF96SVJE","01M6MW9A47HYRVBBQ642740E75",5,"MIT","https:\u002F\u002Fgithub.com\u002Fforbotsake\u002Fforbotsake\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgstack\u002Fsetup-browser-cookies\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"setup","browser","cookies","setup browser cookies","login","testing","qa testing","headless","which","you","domains","import","gstack","session","read","select","Bash","browse","ui","qa","2026-11-10 10:12:30",false,"---\nname: setup-browser-cookies\npreamble-tier: 1\nversion: 1.0.0\ndescription: |\n  Import cookies from your real Chromium browser into the headless browse session.\n  Opens an interactive picker UI where you select which cookie domains to import.\n  Use before QA testing authenticated pages. Use when asked to \"import cookies\",\n  \"login to the site\", or \"authenticate the browser\". (gstack)\nallowed-tools:\n  - Bash\n  - Read\n  - AskUserQuestion\n---\n\u003C!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly -->\n\u003C!-- Regenerate: bun run gen:skill-docs -->\n\n## Preamble (run first)\n\n```bash\n_UPD=$(~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-update-check 2>\u002Fdev\u002Fnull || .claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-update-check 2>\u002Fdev\u002Fnull || true)\n[ -n \"$_UPD\" ] && echo \"$_UPD\" || true\nmkdir -p ~\u002F.gstack\u002Fsessions\ntouch ~\u002F.gstack\u002Fsessions\u002F\"$PPID\"\n_SESSIONS=$(find ~\u002F.gstack\u002Fsessions -mmin -120 -type f 2>\u002Fdev\u002Fnull | wc -l | tr -d ' ')\nfind ~\u002F.gstack\u002Fsessions -mmin +120 -type f -exec rm {} + 2>\u002Fdev\u002Fnull || true\n_PROACTIVE=$(~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config get proactive 2>\u002Fdev\u002Fnull || echo \"true\")\n_PROACTIVE_PROMPTED=$([ -f ~\u002F.gstack\u002F.proactive-prompted ] && echo \"yes\" || echo \"no\")\n_BRANCH=$(git branch --show-current 2>\u002Fdev\u002Fnull || echo \"unknown\")\necho \"BRANCH: $_BRANCH\"\n_SKILL_PREFIX=$(~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config get skill_prefix 2>\u002Fdev\u002Fnull || echo \"false\")\necho \"PROACTIVE: $_PROACTIVE\"\necho \"PROACTIVE_PROMPTED: $_PROACTIVE_PROMPTED\"\necho \"SKILL_PREFIX: $_SKILL_PREFIX\"\nsource \u003C(~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-repo-mode 2>\u002Fdev\u002Fnull) || true\nREPO_MODE=${REPO_MODE:-unknown}\necho \"REPO_MODE: $REPO_MODE\"\n_LAKE_SEEN=$([ -f ~\u002F.gstack\u002F.completeness-intro-seen ] && echo \"yes\" || echo \"no\")\necho \"LAKE_INTRO: $_LAKE_SEEN\"\n_TEL=$(~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config get telemetry 2>\u002Fdev\u002Fnull || true)\n_TEL_PROMPTED=$([ -f ~\u002F.gstack\u002F.telemetry-prompted ] && echo \"yes\" || echo \"no\")\n_TEL_START=$(date +%s)\n_SESSION_ID=\"$$-$(date +%s)\"\necho \"TELEMETRY: ${_TEL:-off}\"\necho \"TEL_PROMPTED: $_TEL_PROMPTED\"\nmkdir -p ~\u002F.gstack\u002Fanalytics\nif [ \"$_TEL\" != \"off\" ]; then\necho '{\"skill\":\"setup-browser-cookies\",\"ts\":\"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'\",\"repo\":\"'$(basename \"$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull)\" 2>\u002Fdev\u002Fnull || echo \"unknown\")'\"}'  >> ~\u002F.gstack\u002Fanalytics\u002Fskill-usage.jsonl 2>\u002Fdev\u002Fnull || true\nfi\n# zsh-compatible: use find instead of glob to avoid NOMATCH error\nfor _PF in $(find ~\u002F.gstack\u002Fanalytics -maxdepth 1 -name '.pending-*' 2>\u002Fdev\u002Fnull); do\n  if [ -f \"$_PF\" ]; then\n    if [ \"$_TEL\" != \"off\" ] && [ -x \"~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-telemetry-log\" ]; then\n      ~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-telemetry-log --event-type skill_run --skill _pending_finalize --outcome unknown --session-id \"$_SESSION_ID\" 2>\u002Fdev\u002Fnull || true\n    fi\n    rm -f \"$_PF\" 2>\u002Fdev\u002Fnull || true\n  fi\n  break\ndone\n# Learnings count\neval \"$(~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-slug 2>\u002Fdev\u002Fnull)\" 2>\u002Fdev\u002Fnull || true\n_LEARN_FILE=\"${GSTACK_HOME:-$HOME\u002F.gstack}\u002Fprojects\u002F${SLUG:-unknown}\u002Flearnings.jsonl\"\nif [ -f \"$_LEARN_FILE\" ]; then\n  _LEARN_COUNT=$(wc -l \u003C \"$_LEARN_FILE\" 2>\u002Fdev\u002Fnull | tr -d ' ')\n  echo \"LEARNINGS: $_LEARN_COUNT entries loaded\"\n  if [ \"$_LEARN_COUNT\" -gt 5 ] 2>\u002Fdev\u002Fnull; then\n    ~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-learnings-search --limit 3 2>\u002Fdev\u002Fnull || true\n  fi\nelse\n  echo \"LEARNINGS: 0\"\nfi\n# Session timeline: record skill start (local-only, never sent anywhere)\n~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-timeline-log '{\"skill\":\"setup-browser-cookies\",\"event\":\"started\",\"branch\":\"'\"$_BRANCH\"'\",\"session\":\"'\"$_SESSION_ID\"'\"}' 2>\u002Fdev\u002Fnull &\n# Check if CLAUDE.md has routing rules\n_HAS_ROUTING=\"no\"\nif [ -f CLAUDE.md ] && grep -q \"## Skill routing\" CLAUDE.md 2>\u002Fdev\u002Fnull; then\n  _HAS_ROUTING=\"yes\"\nfi\n_ROUTING_DECLINED=$(~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config get routing_declined 2>\u002Fdev\u002Fnull || echo \"false\")\necho \"HAS_ROUTING: $_HAS_ROUTING\"\necho \"ROUTING_DECLINED: $_ROUTING_DECLINED\"\n```\n\nIf `PROACTIVE` is `\"false\"`, do not proactively suggest gstack skills AND do not\nauto-invoke skills based on conversation context. Only run skills the user explicitly\ntypes (e.g., \u002Fqa, \u002Fship). If you would have auto-invoked a skill, instead briefly say:\n\"I think \u002Fskillname might help here — want me to run it?\" and wait for confirmation.\nThe user opted out of proactive behavior.\n\nIf `SKILL_PREFIX` is `\"true\"`, the user has namespaced skill names. When suggesting\nor invoking other gstack skills, use the `\u002Fgstack-` prefix (e.g., `\u002Fgstack-qa` instead\nof `\u002Fqa`, `\u002Fgstack-ship` instead of `\u002Fship`). Disk paths are unaffected — always use\n`~\u002F.claude\u002Fskills\u002Fgstack\u002F[skill-name]\u002FSKILL.md` for reading skill files.\n\nIf output shows `UPGRADE_AVAILABLE \u003Cold> \u003Cnew>`: read `~\u002F.claude\u002Fskills\u002Fgstack\u002Fgstack-upgrade\u002FSKILL.md` and follow the \"Inline upgrade flow\" (auto-upgrade if configured, otherwise AskUserQuestion with 4 options, write snooze state if declined). If `JUST_UPGRADED \u003Cfrom> \u003Cto>`: tell user \"Running gstack v{to} (just updated!)\" and continue.\n\nIf `LAKE_INTRO` is `no`: Before continuing, introduce the Completeness Principle.\nTell the user: \"gstack follows the **Boil the Lake** principle — always do the complete\nthing when AI makes the marginal cost near-zero. Read more: https:\u002F\u002Fgarryslist.org\u002Fposts\u002Fboil-the-ocean\"\nThen offer to open the essay in their default browser:\n\n```bash\nopen https:\u002F\u002Fgarryslist.org\u002Fposts\u002Fboil-the-ocean\ntouch ~\u002F.gstack\u002F.completeness-intro-seen\n```\n\nOnly run `open` if the user says yes. Always run `touch` to mark as seen. This only happens once.\n\nIf `TEL_PROMPTED` is `no` AND `LAKE_INTRO` is `yes`: After the lake intro is handled,\nask the user about telemetry. Use AskUserQuestion:\n\n> Help gstack get better! Community mode shares usage data (which skills you use, how long\n> they take, crash info) with a stable device ID so we can track trends and fix bugs faster.\n> No code, file paths, or repo names are ever sent.\n> Change anytime with `gstack-config set telemetry off`.\n\nOptions:\n- A) Help gstack get better! (recommended)\n- B) No thanks\n\nIf A: run `~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config set telemetry community`\n\nIf B: ask a follow-up AskUserQuestion:\n\n> How about anonymous mode? We just learn that *someone* used gstack — no unique ID,\n> no way to connect sessions. Just a counter that helps us know if anyone's out there.\n\nOptions:\n- A) Sure, anonymous is fine\n- B) No thanks, fully off\n\nIf B→A: run `~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config set telemetry anonymous`\nIf B→B: run `~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config set telemetry off`\n\nAlways run:\n```bash\ntouch ~\u002F.gstack\u002F.telemetry-prompted\n```\n\nThis only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely.\n\nIf `PROACTIVE_PROMPTED` is `no` AND `TEL_PROMPTED` is `yes`: After telemetry is handled,\nask the user about proactive behavior. Use AskUserQuestion:\n\n> gstack can proactively figure out when you might need a skill while you work —\n> like suggesting \u002Fqa when you say \"does this work?\" or \u002Finvestigate when you hit\n> a bug. We recommend keeping this on — it speeds up every part of your workflow.\n\nOptions:\n- A) Keep it on (recommended)\n- B) Turn it off — I'll type \u002Fcommands myself\n\nIf A: run `~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config set proactive true`\nIf B: run `~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config set proactive false`\n\nAlways run:\n```bash\ntouch ~\u002F.gstack\u002F.proactive-prompted\n```\n\nThis only happens once. If `PROACTIVE_PROMPTED` is `yes`, skip this entirely.\n\nIf `HAS_ROUTING` is `no` AND `ROUTING_DECLINED` is `false` AND `PROACTIVE_PROMPTED` is `yes`:\nCheck if a CLAUDE.md file exists in the project root. If it does not exist, create it.\n\nUse AskUserQuestion:\n\n> gstack works best when your project's CLAUDE.md includes skill routing rules.\n> This tells Claude to use specialized workflows (like \u002Fship, \u002Finvestigate, \u002Fqa)\n> instead of answering directly. It's a one-time addition, about 15 lines.\n\nOptions:\n- A) Add routing rules to CLAUDE.md (recommended)\n- B) No thanks, I'll invoke skills manually\n\nIf A: Append this section to the end of CLAUDE.md:\n\n```markdown\n\n## Skill routing\n\nWhen the user's request matches an available skill, ALWAYS invoke it using the Skill\ntool as your FIRST action. Do NOT answer directly, do NOT use other tools first.\nThe skill has specialized workflows that produce better results than ad-hoc answers.\n\nKey routing rules:\n- Product ideas, \"is this worth building\", brainstorming → invoke office-hours\n- Bugs, errors, \"why is this broken\", 500 errors → invoke investigate\n- Ship, deploy, push, create PR → invoke ship\n- QA, test the site, find bugs → invoke qa\n- Code review, check my diff → invoke review\n- Update docs after shipping → invoke document-release\n- Weekly retro → invoke retro\n- Design system, brand → invoke design-consultation\n- Visual audit, design polish → invoke design-review\n- Architecture review → invoke plan-eng-review\n- Save progress, checkpoint, resume → invoke checkpoint\n- Code quality, health check → invoke health\n```\n\nThen commit the change: `git add CLAUDE.md && git commit -m \"chore: add gstack skill routing rules to CLAUDE.md\"`\n\nIf B: run `~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config set routing_declined true`\nSay \"No problem. You can add routing rules later by running `gstack-config set routing_declined false` and re-running any skill.\"\n\nThis only happens once per project. If `HAS_ROUTING` is `yes` or `ROUTING_DECLINED` is `true`, skip this entirely.\n\n## Voice\n\n**Tone:** direct, concrete, sharp, never corporate, never academic. Sound like a builder, not a consultant. Name the file, the function, the command. No filler, no throat-clearing.\n\n**Writing rules:** No em dashes (use commas, periods, \"...\"). No AI vocabulary (delve, crucial, robust, comprehensive, nuanced, etc.). Short paragraphs. End with what to do.\n\nThe user always has context you don't. Cross-model agreement is a recommendation, not a decision — the user decides.\n\n## Completion Status Protocol\n\nWhen completing a skill workflow, report status using one of:\n- **DONE** — All steps completed successfully. Evidence provided for each claim.\n- **DONE_WITH_CONCERNS** — Completed, but with issues the user should know about. List each concern.\n- **BLOCKED** — Cannot proceed. State what is blocking and what was tried.\n- **NEEDS_CONTEXT** — Missing information required to continue. State exactly what you need.\n\n### Escalation\n\nIt is always OK to stop and say \"this is too hard for me\" or \"I'm not confident in this result.\"\n\nBad work is worse than no work. You will not be penalized for escalating.\n- If you have attempted a task 3 times without success, STOP and escalate.\n- If you are uncertain about a security-sensitive change, STOP and escalate.\n- If the scope of work exceeds what you can verify, STOP and escalate.\n\nEscalation format:\n```\nSTATUS: BLOCKED | NEEDS_CONTEXT\nREASON: [1-2 sentences]\nATTEMPTED: [what you tried]\nRECOMMENDATION: [what the user should do next]\n```\n\n## Operational Self-Improvement\n\nBefore completing, reflect on this session:\n- Did any commands fail unexpectedly?\n- Did you take a wrong approach and have to backtrack?\n- Did you discover a project-specific quirk (build order, env vars, timing, auth)?\n- Did something take longer than expected because of a missing flag or config?\n\nIf yes, log an operational learning for future sessions:\n\n```bash\n~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-learnings-log '{\"skill\":\"SKILL_NAME\",\"type\":\"operational\",\"key\":\"SHORT_KEY\",\"insight\":\"DESCRIPTION\",\"confidence\":N,\"source\":\"observed\"}'\n```\n\nReplace SKILL_NAME with the current skill name. Only log genuine operational discoveries.\nDon't log obvious things or one-time transient errors (network blips, rate limits).\nA good test: would knowing this save 5+ minutes in a future session? If yes, log it.\n\n## Telemetry (run last)\n\nAfter the skill workflow completes (success, error, or abort), log the telemetry event.\nDetermine the skill name from the `name:` field in this file's YAML frontmatter.\nDetermine the outcome from the workflow result (success if completed normally, error\nif it failed, abort if the user interrupted).\n\n**PLAN MODE EXCEPTION — ALWAYS RUN:** This command writes telemetry to\n`~\u002F.gstack\u002Fanalytics\u002F` (user config directory, not project files). The skill\npreamble already writes to the same directory — this is the same pattern.\nSkipping this command loses session duration and outcome data.\n\nRun this bash:\n\n```bash\n_TEL_END=$(date +%s)\n_TEL_DUR=$(( _TEL_END - _TEL_START ))\nrm -f ~\u002F.gstack\u002Fanalytics\u002F.pending-\"$_SESSION_ID\" 2>\u002Fdev\u002Fnull || true\n# Session timeline: record skill completion (local-only, never sent anywhere)\n~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-timeline-log '{\"skill\":\"SKILL_NAME\",\"event\":\"completed\",\"branch\":\"'$(git branch --show-current 2>\u002Fdev\u002Fnull || echo unknown)'\",\"outcome\":\"OUTCOME\",\"duration_s\":\"'\"$_TEL_DUR\"'\",\"session\":\"'\"$_SESSION_ID\"'\"}' 2>\u002Fdev\u002Fnull || true\n# Local analytics (gated on telemetry setting)\nif [ \"$_TEL\" != \"off\" ]; then\necho '{\"skill\":\"SKILL_NAME\",\"duration_s\":\"'\"$_TEL_DUR\"'\",\"outcome\":\"OUTCOME\",\"browse\":\"USED_BROWSE\",\"session\":\"'\"$_SESSION_ID\"'\",\"ts\":\"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'\"}' >> ~\u002F.gstack\u002Fanalytics\u002Fskill-usage.jsonl 2>\u002Fdev\u002Fnull || true\nfi\n# Remote telemetry (opt-in, requires binary)\nif [ \"$_TEL\" != \"off\" ] && [ -x ~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-telemetry-log ]; then\n  ~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-telemetry-log \\\n    --skill \"SKILL_NAME\" --duration \"$_TEL_DUR\" --outcome \"OUTCOME\" \\\n    --used-browse \"USED_BROWSE\" --session-id \"$_SESSION_ID\" 2>\u002Fdev\u002Fnull &\nfi\n```\n\nReplace `SKILL_NAME` with the actual skill name from frontmatter, `OUTCOME` with\nsuccess\u002Ferror\u002Fabort, and `USED_BROWSE` with true\u002Ffalse based on whether `$B` was used.\nIf you cannot determine the outcome, use \"unknown\". The local JSONL always logs. The\nremote binary only runs if telemetry is not off and the binary exists.\n\n## Plan Mode Safe Operations\n\nWhen in plan mode, these operations are always allowed because they produce\nartifacts that inform the plan, not code changes:\n\n- `$B` commands (browse: screenshots, page inspection, navigation, snapshots)\n- `$D` commands (design: generate mockups, variants, comparison boards, iterate)\n- `codex exec` \u002F `codex review` (outside voice, plan review, adversarial challenge)\n- Writing to `~\u002F.gstack\u002F` (config, analytics, review logs, design artifacts, learnings)\n- Writing to the plan file (already allowed by plan mode)\n- `open` commands for viewing generated artifacts (comparison boards, HTML previews)\n\nThese are read-only in spirit — they inspect the live site, generate visual artifacts,\nor get independent opinions. They do NOT modify project source files.\n\n## Skill Invocation During Plan Mode\n\nIf a user invokes a skill during plan mode, that invoked skill workflow takes\nprecedence over generic plan mode behavior until it finishes or the user explicitly\ncancels that skill.\n\nTreat the loaded skill as executable instructions, not reference material. Follow\nit step by step. Do not summarize, skip, reorder, or shortcut its steps.\n\nIf the skill says to use AskUserQuestion, do that. Those AskUserQuestion calls\nsatisfy plan mode's requirement to end turns with AskUserQuestion.\n\nIf the skill reaches a STOP point, stop immediately at that point, ask the required\nquestion if any, and wait for the user's response. Do not continue the workflow\npast a STOP point, and do not call ExitPlanMode at that point.\n\nIf the skill includes commands marked \"PLAN MODE EXCEPTION — ALWAYS RUN,\" execute\nthem. The skill may edit the plan file, and other writes are allowed only if they\nare already permitted by Plan Mode Safe Operations or explicitly marked as a plan\nmode exception.\n\nOnly call ExitPlanMode after the active skill workflow is complete and there are no\nother invoked skill workflows left to run, or if the user explicitly tells you to\ncancel the skill or leave plan mode.\n\n## Plan Status Footer\n\nWhen you are in plan mode and about to call ExitPlanMode:\n\n1. Check if the plan file already has a `## GSTACK REVIEW REPORT` section.\n2. If it DOES — skip (a review skill already wrote a richer report).\n3. If it does NOT — run this command:\n\n\\`\\`\\`bash\n~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-review-read\n\\`\\`\\`\n\nThen write a `## GSTACK REVIEW REPORT` section to the end of the plan file:\n\n- If the output contains review entries (JSONL lines before `---CONFIG---`): format the\n  standard report table with runs\u002Fstatus\u002Ffindings per skill, same format as the review\n  skills use.\n- If the output is `NO_REVIEWS` or empty: write this placeholder table:\n\n\\`\\`\\`markdown\n## GSTACK REVIEW REPORT\n\n| Review | Trigger | Why | Runs | Status | Findings |\n|--------|---------|-----|------|--------|----------|\n| CEO Review | \\`\u002Fplan-ceo-review\\` | Scope & strategy | 0 | — | — |\n| Codex Review | \\`\u002Fcodex review\\` | Independent 2nd opinion | 0 | — | — |\n| Eng Review | \\`\u002Fplan-eng-review\\` | Architecture & tests (required) | 0 | — | — |\n| Design Review | \\`\u002Fplan-design-review\\` | UI\u002FUX gaps | 0 | — | — |\n| DX Review | \\`\u002Fplan-devex-review\\` | Developer experience gaps | 0 | — | — |\n\n**VERDICT:** NO REVIEWS YET — run \\`\u002Fautoplan\\` for full review pipeline, or individual reviews above.\n\\`\\`\\`\n\n**PLAN MODE EXCEPTION — ALWAYS RUN:** This writes to the plan file, which is the one\nfile you are allowed to edit in plan mode. The plan file review report is part of the\nplan's living status.\n\n# Setup Browser Cookies\n\nImport logged-in sessions from your real Chromium browser into the headless browse session.\n\n## CDP mode check\n\nFirst, check if browse is already connected to the user's real browser:\n```bash\n$B status 2>\u002Fdev\u002Fnull | grep -q \"Mode: cdp\" && echo \"CDP_MODE=true\" || echo \"CDP_MODE=false\"\n```\nIf `CDP_MODE=true`: tell the user \"Not needed — you're connected to your real browser via CDP. Your cookies and sessions are already available.\" and stop. No cookie import needed.\n\n## How it works\n\n1. Find the browse binary\n2. Run `cookie-import-browser` to detect installed browsers and open the picker UI\n3. User selects which cookie domains to import in their browser\n4. Cookies are decrypted and loaded into the Playwright session\n\n## Steps\n\n### 1. Find the browse binary\n\n## SETUP (run this check BEFORE any browse command)\n\n```bash\n_ROOT=$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull)\nB=\"\"\n[ -n \"$_ROOT\" ] && [ -x \"$_ROOT\u002F.claude\u002Fskills\u002Fgstack\u002Fbrowse\u002Fdist\u002Fbrowse\" ] && B=\"$_ROOT\u002F.claude\u002Fskills\u002Fgstack\u002Fbrowse\u002Fdist\u002Fbrowse\"\n[ -z \"$B\" ] && B=~\u002F.claude\u002Fskills\u002Fgstack\u002Fbrowse\u002Fdist\u002Fbrowse\nif [ -x \"$B\" ]; then\n  echo \"READY: $B\"\nelse\n  echo \"NEEDS_SETUP\"\nfi\n```\n\nIf `NEEDS_SETUP`:\n1. Tell the user: \"gstack browse needs a one-time build (~10 seconds). OK to proceed?\" Then STOP and wait.\n2. Run: `cd \u003CSKILL_DIR> && .\u002Fsetup`\n3. If `bun` is not installed:\n   ```bash\n   if ! command -v bun >\u002Fdev\u002Fnull 2>&1; then\n     BUN_VERSION=\"1.3.10\"\n     BUN_INSTALL_SHA=\"bab8acfb046aac8c72407bdcce903957665d655d7acaa3e11c7c4616beae68dd\"\n     tmpfile=$(mktemp)\n     curl -fsSL \"https:\u002F\u002Fbun.sh\u002Finstall\" -o \"$tmpfile\"\n     actual_sha=$(shasum -a 256 \"$tmpfile\" | awk '{print $1}')\n     if [ \"$actual_sha\" != \"$BUN_INSTALL_SHA\" ]; then\n       echo \"ERROR: bun install script checksum mismatch\" >&2\n       echo \"  expected: $BUN_INSTALL_SHA\" >&2\n       echo \"  got:      $actual_sha\" >&2\n       rm \"$tmpfile\"; exit 1\n     fi\n     BUN_VERSION=\"$BUN_VERSION\" bash \"$tmpfile\"\n     rm \"$tmpfile\"\n   fi\n   ```\n\n### 2. Open the cookie picker\n\n```bash\n$B cookie-import-browser\n```\n\nThis auto-detects installed Chromium browsers and opens\nan interactive picker UI in your default browser where you can:\n- Switch between installed browsers\n- Search domains\n- Click \"+\" to import a domain's cookies\n- Click trash to remove imported cookies\n\nTell the user: **\"Cookie picker opened — select the domains you want to import in your browser, then tell me when you're done.\"**\n\n### 3. Direct import (alternative)\n\nIf the user specifies a domain directly (e.g., `\u002Fsetup-browser-cookies github.com`), skip the UI:\n\n```bash\n$B cookie-import-browser comet --domain github.com\n```\n\nReplace `comet` with the appropriate browser if specified.\n\n### 4. Verify\n\nAfter the user confirms they're done:\n\n```bash\n$B cookies\n```\n\nShow the user a summary of imported cookies (domain counts).\n\n## Notes\n\n- On macOS, the first import per browser may trigger a Keychain dialog — click \"Allow\" \u002F \"Always Allow\"\n- On Linux, `v11` cookies may require `secret-tool`\u002Flibsecret access; `v10` cookies use Chromium's standard fallback key\n- Cookie picker is served on the same port as the browse server (no extra process)\n- Only domain names and cookie counts are shown in the UI — no cookie values are exposed\n- The browse session persists cookies between commands, so imported cookies work immediately\n","\u003C!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly -->\n\u003C!-- Regenerate: bun run gen:skill-docs -->\n\n## Preamble (run first)\n\n```bash\n_UPD=$(~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-update-check 2>\u002Fdev\u002Fnull || .claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-update-check 2>\u002Fdev\u002Fnull || true)\n[ -n \"$_UPD\" ] && echo \"$_UPD\" || true\nmkdir -p ~\u002F.gstack\u002Fsessions\ntouch ~\u002F.gstack\u002Fsessions\u002F\"$PPID\"\n_SESSIONS=$(find ~\u002F.gstack\u002Fsessions -mmin -120 -type f 2>\u002Fdev\u002Fnull | wc -l | tr -d ' ')\nfind ~\u002F.gstack\u002Fsessions -mmin +120 -type f -exec rm {} + 2>\u002Fdev\u002Fnull || true\n_PROACTIVE=$(~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config get proactive 2>\u002Fdev\u002Fnull || echo \"true\")\n_PROACTIVE_PROMPTED=$([ -f ~\u002F.gstack\u002F.proactive-prompted ] && echo \"yes\" || echo \"no\")\n_BRANCH=$(git branch --show-current 2>\u002Fdev\u002Fnull || echo \"unknown\")\necho \"BRANCH: $_BRANCH\"\n_SKILL_PREFIX=$(~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config get skill_prefix 2>\u002Fdev\u002Fnull || echo \"false\")\necho \"PROACTIVE: $_PROACTIVE\"\necho \"PROACTIVE_PROMPTED: $_PROACTIVE_PROMPTED\"\necho \"SKILL_PREFIX: $_SKILL_PREFIX\"\nsource \u003C(~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-repo-mode 2>\u002Fdev\u002Fnull) || true\nREPO_MODE=${REPO_MODE:-unknown}\necho \"REPO_MODE: $REPO_MODE\"\n_LAKE_SEEN=$([ -f ~\u002F.gstack\u002F.completeness-intro-seen ] && echo \"yes\" || echo \"no\")\necho \"LAKE_INTRO: $_LAKE_SEEN\"\n_TEL=$(~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config get telemetry 2>\u002Fdev\u002Fnull || true)\n_TEL_PROMPTED=$([ -f ~\u002F.gstack\u002F.telemetry-prompted ] && echo \"yes\" || echo \"no\")\n_TEL_START=$(date +%s)\n_SESSION_ID=\"$$-$(date +%s)\"\necho \"TELEMETRY: ${_TEL:-off}\"\necho \"TEL_PROMPTED: $_TEL_PROMPTED\"\nmkdir -p ~\u002F.gstack\u002Fanalytics\nif [ \"$_TEL\" != \"off\" ]; then\necho '{\"skill\":\"setup-browser-cookies\",\"ts\":\"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'\",\"repo\":\"'$(basename \"$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull)\" 2>\u002Fdev\u002Fnull || echo \"unknown\")'\"}'  >> ~\u002F.gstack\u002Fanalytics\u002Fskill-usage.jsonl 2>\u002Fdev\u002Fnull || true\nfi\n# zsh-compatible: use find instead of glob to avoid NOMATCH error\nfor _PF in $(find ~\u002F.gstack\u002Fanalytics -maxdepth 1 -name '.pending-*' 2>\u002Fdev\u002Fnull); do\n  if [ -f \"$_PF\" ]; then\n    if [ \"$_TEL\" != \"off\" ] && [ -x \"~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-telemetry-log\" ]; then\n      ~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-telemetry-log --event-type skill_run --skill _pending_finalize --outcome unknown --session-id \"$_SESSION_ID\" 2>\u002Fdev\u002Fnull || true\n    fi\n    rm -f \"$_PF\" 2>\u002Fdev\u002Fnull || true\n  fi\n  break\ndone\n# Learnings count\neval \"$(~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-slug 2>\u002Fdev\u002Fnull)\" 2>\u002Fdev\u002Fnull || true\n_LEARN_FILE=\"${GSTACK_HOME:-$HOME\u002F.gstack}\u002Fprojects\u002F${SLUG:-unknown}\u002Flearnings.jsonl\"\nif [ -f \"$_LEARN_FILE\" ]; then\n  _LEARN_COUNT=$(wc -l \u003C \"$_LEARN_FILE\" 2>\u002Fdev\u002Fnull | tr -d ' ')\n  echo \"LEARNINGS: $_LEARN_COUNT entries loaded\"\n  if [ \"$_LEARN_COUNT\" -gt 5 ] 2>\u002Fdev\u002Fnull; then\n    ~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-learnings-search --limit 3 2>\u002Fdev\u002Fnull || true\n  fi\nelse\n  echo \"LEARNINGS: 0\"\nfi\n# Session timeline: record skill start (local-only, never sent anywhere)\n~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-timeline-log '{\"skill\":\"setup-browser-cookies\",\"event\":\"started\",\"branch\":\"'\"$_BRANCH\"'\",\"session\":\"'\"$_SESSION_ID\"'\"}' 2>\u002Fdev\u002Fnull &\n# Check if CLAUDE.md has routing rules\n_HAS_ROUTING=\"no\"\nif [ -f CLAUDE.md ] && grep -q \"## Skill routing\" CLAUDE.md 2>\u002Fdev\u002Fnull; then\n  _HAS_ROUTING=\"yes\"\nfi\n_ROUTING_DECLINED=$(~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config get routing_declined 2>\u002Fdev\u002Fnull || echo \"false\")\necho \"HAS_ROUTING: $_HAS_ROUTING\"\necho \"ROUTING_DECLINED: $_ROUTING_DECLINED\"\n```\n\nIf `PROACTIVE` is `\"false\"`, do not proactively suggest gstack skills AND do not\nauto-invoke skills based on conversation context. Only run skills the user explicitly\ntypes (e.g., \u002Fqa, \u002Fship). If you would have auto-invoked a skill, instead briefly say:\n\"I think \u002Fskillname might help here — want me to run it?\" and wait for confirmation.\nThe user opted out of proactive behavior.\n\nIf `SKILL_PREFIX` is `\"true\"`, the user has namespaced skill names. When suggesting\nor invoking other gstack skills, use the `\u002Fgstack-` prefix (e.g., `\u002Fgstack-qa` instead\nof `\u002Fqa`, `\u002Fgstack-ship` instead of `\u002Fship`). Disk paths are unaffected — always use\n`~\u002F.claude\u002Fskills\u002Fgstack\u002F[skill-name]\u002FSKILL.md` for reading skill files.\n\nIf output shows `UPGRADE_AVAILABLE \u003Cold> \u003Cnew>`: read `~\u002F.claude\u002Fskills\u002Fgstack\u002Fgstack-upgrade\u002FSKILL.md` and follow the \"Inline upgrade flow\" (auto-upgrade if configured, otherwise AskUserQuestion with 4 options, write snooze state if declined). If `JUST_UPGRADED \u003Cfrom> \u003Cto>`: tell user \"Running gstack v{to} (just updated!)\" and continue.\n\nIf `LAKE_INTRO` is `no`: Before continuing, introduce the Completeness Principle.\nTell the user: \"gstack follows the **Boil the Lake** principle — always do the complete\nthing when AI makes the marginal cost near-zero. Read more: https:\u002F\u002Fgarryslist.org\u002Fposts\u002Fboil-the-ocean\"\nThen offer to open the essay in their default browser:\n\n```bash\nopen https:\u002F\u002Fgarryslist.org\u002Fposts\u002Fboil-the-ocean\ntouch ~\u002F.gstack\u002F.completeness-intro-seen\n```\n\nOnly run `open` if the user says yes. Always run `touch` to mark as seen. This only happens once.\n\nIf `TEL_PROMPTED` is `no` AND `LAKE_INTRO` is `yes`: After the lake intro is handled,\nask the user about telemetry. Use AskUserQuestion:\n\n> Help gstack get better! Community mode shares usage data (which skills you use, how long\n> they take, crash info) with a stable device ID so we can track trends and fix bugs faster.\n> No code, file paths, or repo names are ever sent.\n> Change anytime with `gstack-config set telemetry off`.\n\nOptions:\n- A) Help gstack get better! (recommended)\n- B) No thanks\n\nIf A: run `~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config set telemetry community`\n\nIf B: ask a follow-up AskUserQuestion:\n\n> How about anonymous mode? We just learn that *someone* used gstack — no unique ID,\n> no way to connect sessions. Just a counter that helps us know if anyone's out there.\n\nOptions:\n- A) Sure, anonymous is fine\n- B) No thanks, fully off\n\nIf B→A: run `~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config set telemetry anonymous`\nIf B→B: run `~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config set telemetry off`\n\nAlways run:\n```bash\ntouch ~\u002F.gstack\u002F.telemetry-prompted\n```\n\nThis only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely.\n\nIf `PROACTIVE_PROMPTED` is `no` AND `TEL_PROMPTED` is `yes`: After telemetry is handled,\nask the user about proactive behavior. Use AskUserQuestion:\n\n> gstack can proactively figure out when you might need a skill while you work —\n> like suggesting \u002Fqa when you say \"does this work?\" or \u002Finvestigate when you hit\n> a bug. We recommend keeping this on — it speeds up every part of your workflow.\n\nOptions:\n- A) Keep it on (recommended)\n- B) Turn it off — I'll type \u002Fcommands myself\n\nIf A: run `~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config set proactive true`\nIf B: run `~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config set proactive false`\n\nAlways run:\n```bash\ntouch ~\u002F.gstack\u002F.proactive-prompted\n```\n\nThis only happens once. If `PROACTIVE_PROMPTED` is `yes`, skip this entirely.\n\nIf `HAS_ROUTING` is `no` AND `ROUTING_DECLINED` is `false` AND `PROACTIVE_PROMPTED` is `yes`:\nCheck if a CLAUDE.md file exists in the project root. If it does not exist, create it.\n\nUse AskUserQuestion:\n\n> gstack works best when your project's CLAUDE.md includes skill routing rules.\n> This tells Claude to use specialized workflows (like \u002Fship, \u002Finvestigate, \u002Fqa)\n> instead of answering directly. It's a one-time addition, about 15 lines.\n\nOptions:\n- A) Add routing rules to CLAUDE.md (recommended)\n- B) No thanks, I'll invoke skills manually\n\nIf A: Append this section to the end of CLAUDE.md:\n\n```markdown\n\n## Skill routing\n\nWhen the user's request matches an available skill, ALWAYS invoke it using the Skill\ntool as your FIRST action. Do NOT answer directly, do NOT use other tools first.\nThe skill has specialized workflows that produce better results than ad-hoc answers.\n\nKey routing rules:\n- Product ideas, \"is this worth building\", brainstorming → invoke office-hours\n- Bugs, errors, \"why is this broken\", 500 errors → invoke investigate\n- Ship, deploy, push, create PR → invoke ship\n- QA, test the site, find bugs → invoke qa\n- Code review, check my diff → invoke review\n- Update docs after shipping → invoke document-release\n- Weekly retro → invoke retro\n- Design system, brand → invoke design-consultation\n- Visual audit, design polish → invoke design-review\n- Architecture review → invoke plan-eng-review\n- Save progress, checkpoint, resume → invoke checkpoint\n- Code quality, health check → invoke health\n```\n\nThen commit the change: `git add CLAUDE.md && git commit -m \"chore: add gstack skill routing rules to CLAUDE.md\"`\n\nIf B: run `~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-config set routing_declined true`\nSay \"No problem. You can add routing rules later by running `gstack-config set routing_declined false` and re-running any skill.\"\n\nThis only happens once per project. If `HAS_ROUTING` is `yes` or `ROUTING_DECLINED` is `true`, skip this entirely.\n\n## Voice\n\n**Tone:** direct, concrete, sharp, never corporate, never academic. Sound like a builder, not a consultant. Name the file, the function, the command. No filler, no throat-clearing.\n\n**Writing rules:** No em dashes (use commas, periods, \"...\"). No AI vocabulary (delve, crucial, robust, comprehensive, nuanced, etc.). Short paragraphs. End with what to do.\n\nThe user always has context you don't. Cross-model agreement is a recommendation, not a decision — the user decides.\n\n## Completion Status Protocol\n\nWhen completing a skill workflow, report status using one of:\n- **DONE** — All steps completed successfully. Evidence provided for each claim.\n- **DONE_WITH_CONCERNS** — Completed, but with issues the user should know about. List each concern.\n- **BLOCKED** — Cannot proceed. State what is blocking and what was tried.\n- **NEEDS_CONTEXT** — Missing information required to continue. State exactly what you need.\n\n### Escalation\n\nIt is always OK to stop and say \"this is too hard for me\" or \"I'm not confident in this result.\"\n\nBad work is worse than no work. You will not be penalized for escalating.\n- If you have attempted a task 3 times without success, STOP and escalate.\n- If you are uncertain about a security-sensitive change, STOP and escalate.\n- If the scope of work exceeds what you can verify, STOP and escalate.\n\nEscalation format:\n```\nSTATUS: BLOCKED | NEEDS_CONTEXT\nREASON: [1-2 sentences]\nATTEMPTED: [what you tried]\nRECOMMENDATION: [what the user should do next]\n```\n\n## Operational Self-Improvement\n\nBefore completing, reflect on this session:\n- Did any commands fail unexpectedly?\n- Did you take a wrong approach and have to backtrack?\n- Did you discover a project-specific quirk (build order, env vars, timing, auth)?\n- Did something take longer than expected because of a missing flag or config?\n\nIf yes, log an operational learning for future sessions:\n\n```bash\n~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-learnings-log '{\"skill\":\"SKILL_NAME\",\"type\":\"operational\",\"key\":\"SHORT_KEY\",\"insight\":\"DESCRIPTION\",\"confidence\":N,\"source\":\"observed\"}'\n```\n\nReplace SKILL_NAME with the current skill name. Only log genuine operational discoveries.\nDon't log obvious things or one-time transient errors (network blips, rate limits).\nA good test: would knowing this save 5+ minutes in a future session? If yes, log it.\n\n## Telemetry (run last)\n\nAfter the skill workflow completes (success, error, or abort), log the telemetry event.\nDetermine the skill name from the `name:` field in this file's YAML frontmatter.\nDetermine the outcome from the workflow result (success if completed normally, error\nif it failed, abort if the user interrupted).\n\n**PLAN MODE EXCEPTION — ALWAYS RUN:** This command writes telemetry to\n`~\u002F.gstack\u002Fanalytics\u002F` (user config directory, not project files). The skill\npreamble already writes to the same directory — this is the same pattern.\nSkipping this command loses session duration and outcome data.\n\nRun this bash:\n\n```bash\n_TEL_END=$(date +%s)\n_TEL_DUR=$(( _TEL_END - _TEL_START ))\nrm -f ~\u002F.gstack\u002Fanalytics\u002F.pending-\"$_SESSION_ID\" 2>\u002Fdev\u002Fnull || true\n# Session timeline: record skill completion (local-only, never sent anywhere)\n~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-timeline-log '{\"skill\":\"SKILL_NAME\",\"event\":\"completed\",\"branch\":\"'$(git branch --show-current 2>\u002Fdev\u002Fnull || echo unknown)'\",\"outcome\":\"OUTCOME\",\"duration_s\":\"'\"$_TEL_DUR\"'\",\"session\":\"'\"$_SESSION_ID\"'\"}' 2>\u002Fdev\u002Fnull || true\n# Local analytics (gated on telemetry setting)\nif [ \"$_TEL\" != \"off\" ]; then\necho '{\"skill\":\"SKILL_NAME\",\"duration_s\":\"'\"$_TEL_DUR\"'\",\"outcome\":\"OUTCOME\",\"browse\":\"USED_BROWSE\",\"session\":\"'\"$_SESSION_ID\"'\",\"ts\":\"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'\"}' >> ~\u002F.gstack\u002Fanalytics\u002Fskill-usage.jsonl 2>\u002Fdev\u002Fnull || true\nfi\n# Remote telemetry (opt-in, requires binary)\nif [ \"$_TEL\" != \"off\" ] && [ -x ~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-telemetry-log ]; then\n  ~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-telemetry-log \\\n    --skill \"SKILL_NAME\" --duration \"$_TEL_DUR\" --outcome \"OUTCOME\" \\\n    --used-browse \"USED_BROWSE\" --session-id \"$_SESSION_ID\" 2>\u002Fdev\u002Fnull &\nfi\n```\n\nReplace `SKILL_NAME` with the actual skill name from frontmatter, `OUTCOME` with\nsuccess\u002Ferror\u002Fabort, and `USED_BROWSE` with true\u002Ffalse based on whether `$B` was used.\nIf you cannot determine the outcome, use \"unknown\". The local JSONL always logs. The\nremote binary only runs if telemetry is not off and the binary exists.\n\n## Plan Mode Safe Operations\n\nWhen in plan mode, these operations are always allowed because they produce\nartifacts that inform the plan, not code changes:\n\n- `$B` commands (browse: screenshots, page inspection, navigation, snapshots)\n- `$D` commands (design: generate mockups, variants, comparison boards, iterate)\n- `codex exec` \u002F `codex review` (outside voice, plan review, adversarial challenge)\n- Writing to `~\u002F.gstack\u002F` (config, analytics, review logs, design artifacts, learnings)\n- Writing to the plan file (already allowed by plan mode)\n- `open` commands for viewing generated artifacts (comparison boards, HTML previews)\n\nThese are read-only in spirit — they inspect the live site, generate visual artifacts,\nor get independent opinions. They do NOT modify project source files.\n\n## Skill Invocation During Plan Mode\n\nIf a user invokes a skill during plan mode, that invoked skill workflow takes\nprecedence over generic plan mode behavior until it finishes or the user explicitly\ncancels that skill.\n\nTreat the loaded skill as executable instructions, not reference material. Follow\nit step by step. Do not summarize, skip, reorder, or shortcut its steps.\n\nIf the skill says to use AskUserQuestion, do that. Those AskUserQuestion calls\nsatisfy plan mode's requirement to end turns with AskUserQuestion.\n\nIf the skill reaches a STOP point, stop immediately at that point, ask the required\nquestion if any, and wait for the user's response. Do not continue the workflow\npast a STOP point, and do not call ExitPlanMode at that point.\n\nIf the skill includes commands marked \"PLAN MODE EXCEPTION — ALWAYS RUN,\" execute\nthem. The skill may edit the plan file, and other writes are allowed only if they\nare already permitted by Plan Mode Safe Operations or explicitly marked as a plan\nmode exception.\n\nOnly call ExitPlanMode after the active skill workflow is complete and there are no\nother invoked skill workflows left to run, or if the user explicitly tells you to\ncancel the skill or leave plan mode.\n\n## Plan Status Footer\n\nWhen you are in plan mode and about to call ExitPlanMode:\n\n1. Check if the plan file already has a `## GSTACK REVIEW REPORT` section.\n2. If it DOES — skip (a review skill already wrote a richer report).\n3. If it does NOT — run this command:\n\n\\`\\`\\`bash\n~\u002F.claude\u002Fskills\u002Fgstack\u002Fbin\u002Fgstack-review-read\n\\`\\`\\`\n\nThen write a `## GSTACK REVIEW REPORT` section to the end of the plan file:\n\n- If the output contains review entries (JSONL lines before `---CONFIG---`): format the\n  standard report table with runs\u002Fstatus\u002Ffindings per skill, same format as the review\n  skills use.\n- If the output is `NO_REVIEWS` or empty: write this placeholder table:\n\n\\`\\`\\`markdown\n## GSTACK REVIEW REPORT\n\n| Review | Trigger | Why | Runs | Status | Findings |\n|--------|---------|-----|------|--------|----------|\n| CEO Review | \\`\u002Fplan-ceo-review\\` | Scope & strategy | 0 | — | — |\n| Codex Review | \\`\u002Fcodex review\\` | Independent 2nd opinion | 0 | — | — |\n| Eng Review | \\`\u002Fplan-eng-review\\` | Architecture & tests (required) | 0 | — | — |\n| Design Review | \\`\u002Fplan-design-review\\` | UI\u002FUX gaps | 0 | — | — |\n| DX Review | \\`\u002Fplan-devex-review\\` | Developer experience gaps | 0 | — | — |\n\n**VERDICT:** NO REVIEWS YET — run \\`\u002Fautoplan\\` for full review pipeline, or individual reviews above.\n\\`\\`\\`\n\n**PLAN MODE EXCEPTION — ALWAYS RUN:** This writes to the plan file, which is the one\nfile you are allowed to edit in plan mode. The plan file review report is part of the\nplan's living status.\n\n# Setup Browser Cookies\n\nImport logged-in sessions from your real Chromium browser into the headless browse session.\n\n## CDP mode check\n\nFirst, check if browse is already connected to the user's real browser:\n```bash\n$B status 2>\u002Fdev\u002Fnull | grep -q \"Mode: cdp\" && echo \"CDP_MODE=true\" || echo \"CDP_MODE=false\"\n```\nIf `CDP_MODE=true`: tell the user \"Not needed — you're connected to your real browser via CDP. Your cookies and sessions are already available.\" and stop. No cookie import needed.\n\n## How it works\n\n1. Find the browse binary\n2. Run `cookie-import-browser` to detect installed browsers and open the picker UI\n3. User selects which cookie domains to import in their browser\n4. Cookies are decrypted and loaded into the Playwright session\n\n## Steps\n\n### 1. Find the browse binary\n\n## SETUP (run this check BEFORE any browse command)\n\n```bash\n_ROOT=$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull)\nB=\"\"\n[ -n \"$_ROOT\" ] && [ -x \"$_ROOT\u002F.claude\u002Fskills\u002Fgstack\u002Fbrowse\u002Fdist\u002Fbrowse\" ] && B=\"$_ROOT\u002F.claude\u002Fskills\u002Fgstack\u002Fbrowse\u002Fdist\u002Fbrowse\"\n[ -z \"$B\" ] && B=~\u002F.claude\u002Fskills\u002Fgstack\u002Fbrowse\u002Fdist\u002Fbrowse\nif [ -x \"$B\" ]; then\n  echo \"READY: $B\"\nelse\n  echo \"NEEDS_SETUP\"\nfi\n```\n\nIf `NEEDS_SETUP`:\n1. Tell the user: \"gstack browse needs a one-time build (~10 seconds). OK to proceed?\" Then STOP and wait.\n2. Run: `cd \u003CSKILL_DIR> && .\u002Fsetup`\n3. If `bun` is not installed:\n   ```bash\n   if ! command -v bun >\u002Fdev\u002Fnull 2>&1; then\n     BUN_VERSION=\"1.3.10\"\n     BUN_INSTALL_SHA=\"bab8acfb046aac8c72407bdcce903957665d655d7acaa3e11c7c4616beae68dd\"\n     tmpfile=$(mktemp)\n     curl -fsSL \"https:\u002F\u002Fbun.sh\u002Finstall\" -o \"$tmpfile\"\n     actual_sha=$(shasum -a 256 \"$tmpfile\" | awk '{print $1}')\n     if [ \"$actual_sha\" != \"$BUN_INSTALL_SHA\" ]; then\n       echo \"ERROR: bun install script checksum mismatch\" >&2\n       echo \"  expected: $BUN_INSTALL_SHA\" >&2\n       echo \"  got:      $actual_sha\" >&2\n       rm \"$tmpfile\"; exit 1\n     fi\n     BUN_VERSION=\"$BUN_VERSION\" bash \"$tmpfile\"\n     rm \"$tmpfile\"\n   fi\n   ```\n\n### 2. Open the cookie picker\n\n```bash\n$B cookie-import-browser\n```\n\nThis auto-detects installed Chromium browsers and opens\nan interactive picker UI in your default browser where you can:\n- Switch between installed browsers\n- Search domains\n- Click \"+\" to import a domain's cookies\n- Click trash to remove imported cookies\n\nTell the user: **\"Cookie picker opened — select the domains you want to import in your browser, then tell me when you're done.\"**\n\n### 3. Direct import (alternative)\n\nIf the user specifies a domain directly (e.g., `\u002Fsetup-browser-cookies github.com`), skip the UI:\n\n```bash\n$B cookie-import-browser comet --domain github.com\n```\n\nReplace `comet` with the appropriate browser if specified.\n\n### 4. Verify\n\nAfter the user confirms they're done:\n\n```bash\n$B cookies\n```\n\nShow the user a summary of imported cookies (domain counts).\n\n## Notes\n\n- On macOS, the first import per browser may trigger a Keychain dialog — click \"Allow\" \u002F \"Always Allow\"\n- On Linux, `v11` cookies may require `secret-tool`\u002Flibsecret access; `v10` cookies use Chromium's standard fallback key\n- Cookie picker is served on the same port as the browse server (no extra process)\n- Only domain names and cookie counts are shown in the UI — no cookie values are exposed\n- The browse session persists cookies between commands, so imported cookies work immediately\n",{"name":5,"version":43,"description":44,"allowed-tools":45,"preamble-tier":48},"1.0.0","Import cookies from your real Chromium browser into the headless browse session.\nOpens an interactive picker UI where you select which cookie domains to import.\nUse before QA testing authenticated pages. Use when asked to \"import cookies\",\n\"login to the site\", or \"authenticate the browser\". (gstack)\n",[34,46,47],"Read","AskUserQuestion",1,"main","d91f0c567548c80403f85619693a405ed65d2b60",".claude\u002Fskills\u002Fgstack\u002Fsetup-browser-cookies","https:\u002F\u002Fgithub.com\u002Fforbotsake\u002Fforbotsake","https:\u002F\u002Fgithub.com\u002Fforbotsake","2026-08-17 21:39:59",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add forbotsake\u002Fforbotsake --skill setup-browser-cookies",{"tool":61,"command":62},"bunx","bunx skills add forbotsake\u002Fforbotsake --skill setup-browser-cookies",{"tool":64,"command":65},"pnpm","pnpm dlx skills add forbotsake\u002Fforbotsake --skill setup-browser-cookies","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fforbotsake\u002Fforbotsake\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgstack\u002Fsetup-browser-cookies\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"SKILL.md.tmpl","OTHER","其他",2632,"https:\u002F\u002Fgithub.com\u002Fforbotsake\u002Fforbotsake\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgstack\u002Fsetup-browser-cookies\u002FSKILL.md.tmpl",[76,96,122,151,173,207],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":38},"01M6MWS487CZVEME2DWGT48C58","forbotsake-upgrade","Upgrade forbotsake to the latest version. Detects install type (git clone\nvs vendored), runs the upgrade, and shows what's new.\nUse when: \"upgrade forbotsake\", \"update forbotsake\", \"get latest version\",\n\"forbotsake update\".","https:\u002F\u002Fgithub.com\u002Fforbotsake\u002Fforbotsake\u002Fblob\u002Fmain\u002Fforbotsake-upgrade\u002FSKILL.md",[],[83,84,9,85,86,34,32,87,88,89,90,91,92,93,94,95],"upgrade","forbotsake upgrade","update","git","write","install","use","version","git clone","get","type","latest","clone",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":107,"publishedAt":38},"01M6MWRZ7XD9Q73JTRBQ0N8682","forbotsake-spy","Stage 3: RESEARCH (competitors). Analyzes 3-5 competitors to find messaging whitespace\nand positioning gaps. Produces competitor-analysis.md with a messaging matrix showing\nwhat each competitor says, what's missing, and where you can win.\nUse when: \"competitor analysis\", \"competitive research\", \"what are others doing\",\n\"market landscape\", \"who am I competing with\", \"spy on competitors\",\n\"messaging whitespace\", \"differentiation research\".\nProactively invoke when the user mentions competitors or asks how to differentiate.","https:\u002F\u002Fgithub.com\u002Fforbotsake\u002Fforbotsake\u002Fblob\u002Fmain\u002Fforbotsake-spy\u002FSKILL.md",[102],{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[108,9,109,110,111,34,112,32,87,113,89,114,115,116,117,118,119,27,120,121],"forbotsake spy","messaging","analysis","how","competitors","edit","positioning","landscape","missing","how to","differentiation","competitive","websearch","matrix",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":137,"publishedAt":38},"01M6MWRPHXWYB38V08BZM8SSRE","forbotsake-sharpen","Stage 4.5: SHARPEN. Takes a specific outreach target (person or organization) and\nproduces a deep execution plan with contextual research, relationship mapping,\nangle selection, and a multi-touch sequence. Reads your founder profile and strategy\nto leverage warm paths and unfair advantages.\nUse when: \"refine this plan\", \"go deeper on this\", \"sharpen execution\",\n\"how do I approach [person]\", \"outreach to [person]\", \"target [person\u002Forg]\",\n\"approach [person]\", \"engage [org]\".\nProactively invoke when the user mentions approaching a specific person or\norganization as part of their marketing strategy.\nRequires: strategy.md (from \u002Fforbotsake-marketing-start).","https:\u002F\u002Fgithub.com\u002Fforbotsake\u002Fforbotsake\u002Fblob\u002Fmain\u002Fforbotsake-sharpen\u002FSKILL.md",[128,131,132],{"categoryNo":129,"categoryName":130,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[138,139,9,140,111,34,141,32,87,113,142,143,144,145,146,147,148,149,120,150],"sharpen","forbotsake sharpen","start","plan","selection","relationship","organization","refine","deeper","deep","leverage","paths","sequence",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":159,"publishedAt":38},"01M6MWRHXHECX1N4WNHBJJQKER","forbotsake-retro","Stage 9: MEASURE. Reviews what you published, analyzes performance data,\nand produces a retro report with evidence-based recommendations.\nTells you what to double down on, what to drop, and what to try next.\nUse when: \"what worked\", \"marketing retro\", \"measure results\", \"review performance\",\n\"which content performed best\", \"should I keep doing this\".\nProactively invoke one week after \u002Fforbotsake-publish was last run.","https:\u002F\u002Fgithub.com\u002Fforbotsake\u002Fforbotsake\u002Fblob\u002Fmain\u002Fforbotsake-retro\u002FSKILL.md",[157,158],{"categoryNo":129,"categoryName":130,"taxonomyType":105,"taxonomyTypeDesc":106},{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},[160,161,9,162,163,164,165,166,34,167,32,87,113,168,169,170,27,171,26,172],"retro","forbotsake retro","review","performance","run","publish","data","marketing","next","drop","recommendations","reviews","what worked",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":191,"publishedAt":38},"01M6MWRB8GN0AZTEVTQD1GBA8K","forbotsake-publish","Stage 8: SHIP. Two modes: POST (auto-post via Claude for Chrome) or COPY\n(format for copy-paste). Handles X\u002FTwitter threads, LinkedIn posts, blog posts,\nand more. Logs everything for retrospective analysis.\nFor auto-posting, the user needs the Claude for Chrome extension installed.\nWithout it, the skill falls back to COPY mode automatically.\nUse when: \"publish this\", \"format for twitter\", \"post to X\", \"ship this content\",\n\"format for blog\", \"send this email\", \"ready to publish\", \"auto-post\",\n\"post this to X\", \"publish to LinkedIn\".\nProactively invoke when the user has content in content\u002F and says they want to ship it.","https:\u002F\u002Fgithub.com\u002Fforbotsake\u002Fforbotsake\u002Fblob\u002Fmain\u002Fforbotsake-publish\u002FSKILL.md",[179,182,185,188],{"categoryNo":180,"categoryName":181,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":183,"categoryName":184,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":186,"categoryName":187,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":189,"categoryName":190,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000036","内容创作者",[165,192,9,193,194,195,196,197,198,32,87,113,199,200,201,202,203,204,205,206],"forbotsake publish","MCP","image","create","logs","ship","text","context","auto","ready","chrome extension","posts","paste","mode","send",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":215,"publishedAt":38},"01M6MWR5K98QN9BDH4179Y47F0","forbotsake-marketing-start","The starting point for marketing your product. Reads your codebase to understand\nwhat you built, asks 5 hard questions about positioning, audience, and channels,\nthen produces strategy.md with your marketing strategy and first concrete move.\nUse when: \"how should I market this\", \"go-to-market\", \"GTM\", \"positioning\",\n\"I don't know how to sell this\", \"help me market\", \"marketing strategy\".\nProactively invoke when the user asks about marketing, growth, or getting users\nand no strategy.md exists yet.","https:\u002F\u002Fgithub.com\u002Fforbotsake\u002Fforbotsake\u002Fblob\u002Fmain\u002Fforbotsake-marketing-start\u002FSKILL.md",[213,214],{"categoryNo":129,"categoryName":130,"taxonomyType":105,"taxonomyTypeDesc":106},{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},[140,167,216,9,217,218,111,34,32,87,113,219,114,220,117,221,222,27,120,223],"forbotsake marketing start","go","product","me","gtm","go-to-market","move","for"]