domains / families / software-engineering / browser-extension-launch

browser-extension-launch

combined

面向没有编程经验的用户，把想法做成可试用的浏览器插件，并完成检查、商店材料、审核提交和上线验证；也用于继续已有插件、排错和发布新版。用户说“帮我做个插件”“把插件上架”“继续我的插件”时使用。普通网站开发、仅查询插件知识不触发。 Builds, tests, packages, and prepares Chrome extensions for store launch from a plain-language idea; use for new extensions, fixes, releases, and submission recovery.

When to use

• Use when a user wants to turn a plain-language idea into a browser extension.
• Use when continuing, debugging, packaging, submitting, or releasing an existing extension.
• Do not use for ordinary website development or browser-extension knowledge questions that require no implementation.

When not to use

• 本技能提供交付流程、检查契约和宿主适配规则，不内置可执行脚本、浏览器二进制、商店账号或发布凭据。
• Chrome / Manifest V3 是默认基线；其他浏览器、企业分发策略、商店费用与审核规则必须在执行时依据当前官方资料另行核实。
• 静态检查、文件指纹和自动化报告不能证明真实浏览器操作、商店审核通过或线上可安装；这些状态必须保留各自的直接证据。
• 需要账号登录、付款、身份声明、权限授权或最终提交时，必须由用户本人决定并完成相应操作。

Skill page

Conflict

The two copies are nearly identical, but the davepoon copy contains a concrete, executable local tooling contract (project.py, release_bundle.py, acceptance_gate.py) and a stricter dependency-approval rule that the sickn33 copy omits. The sickn33 copy adds a 'Limitations' section and a more general 'Local Records and Gates' section that the davepoon copy lacks. Because each copy has material steps or constraints the other lacks, crowning one would hide a real alternative.