# Chrome Extension Studio Plugin

> Codex plugin case study for planning, designing, generating, packaging, QA, and release preparation across Chrome extension product repos.

## Summary
Chrome Extension Studio Plugin is a local developer-platform project for keeping extension plugin logic, reusable templates, and shipped product repositories separate. It defines release profiles for prototype, private beta, public Chrome Web Store, and source-release paths, then generates design briefs, store listing drafts, release plans, product repos, and release-cycle checklists from a single extension contract. The public case study focuses on the reusable release system rather than any one extension product.

## Project Link
https://zack-dev-cm.github.io/projects/chrome-extension-studio-plugin.md

## Key Features
- Separates Codex plugin code, reusable extension templates, and product-specific extension repositories
- Defines publish types for local prototypes, private beta, public Chrome Web Store releases, and source-first releases
- Generates design briefs, store listings, release plans, product repos, and release-cycle outputs from a release profile
- Keeps Chrome extension delivery repeatable without mixing product code and automation scaffolding

## Tech Stack
- Codex Plugin
- Python
- Chrome Extensions
- Manifest V3
- Chrome Web Store
- Release Engineering

## Benchmarks & Analytics
- Publish types: 4 (prototype-local, beta-private, cws-public, source-release)
- Release scripts: 6 (create, design brief, store listing, release plan, release cycle, profile validation)
- Latest local commit: 2026-04-18 (local Mac repo history reviewed before portfolio add)