Skip to content

Chrome Web Store Deployment

1. Local Extension Test

  1. Open chrome://extensions.
  2. Enable Developer mode.
  3. Click Load unpacked.
  4. Select the repository extension/ folder.
  5. Test on supported sites: ChatGPT, Claude, Gemini, Grok, DeepSeek.

2. First Upload in Chrome Web Store Dashboard

  1. Open Chrome Web Store Developer Dashboard.
  2. Click New item.
  3. Upload a ZIP built from the extension/ folder.
  4. Complete all required listing and privacy fields.

Important: - The first upload creates your CWS_EXTENSION_ID. - Save this ID as GitHub secret CWS_EXTENSION_ID for automated publishing.

3. Store Listing Values You Can Reuse

  • Title: AI Dev Coach
  • Summary: Coach developers to use AI with better reasoning, prompting, and coding habits.
  • Category: Developer Tools
  • Language: English

Suggested long description:

AI Dev Coach helps developers use AI as a force multiplier instead of a shortcut dependency.

It provides:
- Prompt Builder with 6 templates (Debugging, Code Review, System Design, Refactoring, Performance, Learning)
- Required prompt fields (Task, Context, What You Tried) to improve prompt quality
- Prompt quality scoring (0-100) with actionable feedback
- Real-time warning overlays for shortcut/copy-paste behavior
- Local habit tracking for AI requests, manual attempts, and large code pastes

The extension runs locally in your browser and does not send your prompts or code to external analytics services.

4. Required Graphic Assets

Store icon: - 128 x 128 PNG (use extension/assets/icon-128.png)

Recommended promotional assets for better approval/conversion: - Small tile: 440 x 280 - Large tile: 920 x 680 - Marquee promo tile: 1400 x 560 - Screenshots: at least 1280 x 800 (desktop capture preferred)

5. Privacy and Distribution Form Guidance

  • Single purpose: coaching safer AI usage habits for developers.
  • Data usage: local storage only (chrome.storage.local).
  • Remote code: none.
  • Tracking/analytics: none in MVP.
  • Distribution: start with Unlisted for internal testing, then switch to Public when ready.

6. Automated Publish (GitHub Actions)

Release automation is in .github/workflows/release.yml.

On push to main, the workflow: 1. validates extension package structure 2. reads version from extension/manifest.json 3. creates tag v<version> if missing 4. creates GitHub release with autogenerated notes 5. uploads and publishes extension through Chrome Web Store API

Required repository secrets: - CWS_CLIENT_ID - CWS_CLIENT_SECRET - CWS_REFRESH_TOKEN - CWS_PUBLISHER_ID - CWS_EXTENSION_ID

Optional: - CWS_PUBLISH_TARGET (default or trustedTesters)