playbooks

home / skills / masayan1126 / masayan-uni-code-plugins / develop

develop skill

/plugins/chrome-ext-toolkit/skills/develop

This skill guides end-to-end Chrome extension development and store readiness, from concept and requirements to assets and application submission.

npx playbooks add skill masayan1126/masayan-uni-code-plugins --skill develop

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
726 B
---
name: chrome-ext-develop
description: Chrome拡張機能の開発からChrome Web Store申請準備までをサポート。「拡張機能を開発」「Chrome拡張作成」などで使用。
---

# Chrome Extension Development Skill

Chrome拡張機能の開発から、Chrome Web Storeへの申請準備までを一貫してサポートするスキルです。

## 対応タスク

- 新規Chrome拡張機能の開発
- 競合調査と要件定義
- ストア申請用アセット（説明文、画像仕様）の作成

## 関連ファイル

- [WORKFLOW.md](./WORKFLOW.md) - 開発ワークフロー
- [TEMPLATES.md](./TEMPLATES.md) - テンプレート集
- [REFERENCE.md](./REFERENCE.md) - 技術リファレンス

Overview

This skill helps you build Chrome extensions from initial concept through Chrome Web Store submission preparation. It streamlines development tasks, creates store-ready assets, and provides workflow and template guidance. Use it to accelerate prototyping, ensure compliance with store requirements, and produce polished listings. It is focused on practical, end-to-end support for extension projects.

How this skill works

The skill inspects project goals, existing code, and target platform constraints to generate a development plan and concrete artifacts. It provides templates for manifest files, background/content scripts, and UI assets, plus example code snippets and packaging steps. For store submission, it validates required metadata, crafts optimized descriptions, and outputs correctly sized images and permission explanations. It also maps a clear workflow for building, testing, and publishing releases.

When to use it

  • Starting a new Chrome extension project and needing a clear plan and templates
  • Converting an idea or web feature into an extension prototype quickly
  • Preparing or validating Chrome Web Store listing assets and descriptions
  • Reviewing permissions, security, and manifest v3 migration concerns
  • Creating a release workflow and packaging strategy for distribution

Best practices

  • Define core user value and minimal viable features before coding
  • Use manifest v3 patterns and limit requested permissions to least privilege
  • Separate content scripts, background service workers, and UI to simplify testing
  • Provide clear privacy and permissions explanations in the store listing
  • Automate packaging and versioning in your CI pipeline before publishing

Example use cases

  • Generate a manifest v3 template and starter background worker for a new extension
  • Produce store-ready description, short summary, and localized strings for listing
  • Create image assets at required sizes and an assets checklist for submission
  • Audit requested permissions and suggest narrower alternatives to pass review
  • Outline a workflow for testing, building, and publishing updates via CI

FAQ

Will this skill create code for manifest v3?

Yes. It provides manifest v3 templates and example service worker, content script, and UI code snippets tailored to your feature set.

Can it prepare assets for the Chrome Web Store?

Yes. It generates optimized descriptions, required image sizes, and metadata formatted for the store submission form.