bagisto-shop-advance-theme-development

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Shop Advance Theme Development

Shop Advance Theme 开发

Build a distinctive storefront while preserving the installed Bagisto commerce, extension, content, and runtime contracts. Follow official Bagisto conventions, reconcile documentation with the target checkout, and prove behavior before activation.

在保留已安装的Bagisto电商系统、扩展、内容和运行时契约的前提下，构建独特的店面。遵循官方Bagisto规范，协调文档与目标结账流程，并在激活前验证功能行为。

Non-negotiable rules

不可协商规则

Read every applicable repository instruction file before acting.
Treat installed code/configuration as the executable source of truth; use official version-matched Bagisto sources for intent.
Parameterize or discover every theme code, display name, namespace, package path, channel, locale, build path, tool version, and command.
Never edit Bagisto Shop source,
```
vendor/
```
, generated build output, dependencies, lockfiles, or live channel state unless the user and repository policy authorize it.
Prefer a sparse view overlay/package. Create a full fork only after the user accepts its upgrade surface.
Derive the complete asset runtime from the installed Shop package; view fallback does not imply Vite/JavaScript/CSS inheritance.
Preserve layout runtime responsibilities, render events, controller variables, routes, form fields, API shapes, product-type behavior, and enabled extensions.
Make configuration edits merge-only. Never erase sibling themes/providers/autoload mappings or silently change
```
shop-default
```
.
Use dry runs and collision checks. Never force-publish, delete, replace a directory with a symlink, seed destructive data, or overwrite a conflict automatically.
Preserve the exact installed Bagisto license notice for copied/derived sources, choose the theme's own license explicitly before distribution, and verify every bundled asset's redistribution terms.
Treat generated design recommendations as candidates, not authority. Reject any suggestion that weakens commerce clarity, accessibility, performance, licensing, merchant control, installed dependencies, or Bagisto runtime contracts.
Use only this skill's bundled
```
bagisto-ui-ux
```
knowledge and generator for design intelligence. Do not require, discover, import, or call another design skill at runtime.
Treat “dynamic,” “admin-controlled,” and “all functionality works” as evidence claims. Inventory every visible surface and installed/enabled commerce journey; do not infer them from a successful build or homepage screenshot.
Do not add an animation library, UI framework, icon package, remote font, external script, or other dependency merely because a design tool recommends it. Discover the installed capability first and obtain authorization for dependency or network changes.
Build and validate before selecting the theme on any channel. Keep rollback explicit.

执行操作前阅读所有适用的仓库说明文件。
将已安装的代码/配置视为可执行的事实来源；使用官方版本匹配的Bagisto资源来明确意图。
对所有主题代码、显示名称、命名空间、包路径、渠道、区域设置、构建路径、工具版本和命令进行参数化或自动发现。
除非获得用户和仓库政策授权，否则绝不要编辑Bagisto Shop源码、
```
vendor/
```
目录、生成的构建输出、依赖项、锁定文件或实时渠道状态。
优先使用稀疏视图覆盖/包。仅在用户接受其升级影响范围后再创建完整分支。
从已安装的Shop包中获取完整的资产运行时；视图回退并不意味着继承Vite/JavaScript/CSS。
保留布局运行时职责、渲染事件、控制器变量、路由、表单字段、API结构、产品类型行为和已启用的扩展。
仅以合并方式修改配置。绝不要删除同级主题/提供者/自动加载映射，也不要静默修改
```
shop-default
```
。
使用试运行和冲突检查。绝不要强制发布、删除、用符号链接替换目录、植入破坏性数据或自动覆盖冲突内容。
对于复制/衍生的资源，保留已安装Bagisto的确切许可证声明；在分发前明确选择主题自身的许可证，并验证每个捆绑资产的再分发条款。
将生成的设计建议视为候选方案，而非权威标准。拒绝任何削弱电商清晰度、可访问性、性能、许可合规性、商家控制权、已安装依赖项或Bagisto运行时契约的建议。
仅使用本技能捆绑的
```
bagisto-ui-ux
```
知识库和生成器来获取设计智能。运行时无需发现、导入或调用其他设计技能。
将“动态”、“管理员可控”和“所有功能正常”视为需要验证的声明。盘点所有可见界面和已安装/启用的电商流程；不要从构建成功或首页截图推断这些内容。
不要仅因为设计工具推荐就添加动画库、UI框架、图标包、远程字体、外部脚本或其他依赖项。首先确认已安装的功能，然后获取依赖项或网络变更的授权。
在任何渠道选择主题之前，先构建并验证功能。明确保留回滚机制。

Reference files — load only what the current task needs

参考文件——仅加载当前任务所需的文件

File	Load when
workflow.md	The full workflow and the definition of done

REQUIRED SUB-SKILL: Use bagisto-change-verification before calling any change done.

文件	加载时机
workflow.md	完整工作流及完成定义