Individual skill

mini-program-architecture-skill

Translate a confirmed mini-program product specification or bounded feature into an implementable architecture covering modules, pages, components, services, canonical state sources, data models, interfaces, permissions, failures, caching, concurrency, idempotency, migration, rollback, external dependencies, and architecture decision records. Use when users ask how to structure a mini program, design data or APIs, divide frontend and cloud responsibilities, evolve an existing system safely, or prepare implementation after product semantics are stable. Preserves product meaning, current repository constraints, user-owned changes, and verifiable acceptance behavior rather than redesigning the product for technical convenience.

skills/mini-program-architecture-skill/SKILL.md

Read pinned source

Source commit 2b7f9cb24f142125189b8757fcea489546d76ba7

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
95
Repository last updated
Nov 3, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# /mini-program-architecture-skill — 小程序工程架构

把已经确认的产品语义映射为可实现、可验证、可迁移和可回滚的工程方案。架构服务于产品约束,不改变产品语义来迁就技术方案。

## 进入条件与边界

- 需要一份稳定的产品规格、明确功能边界,或现有项目的只读事实图。
- 已有项目先读取规则、当前源码与配置、Git 状态和必须保护的用户改动;优先延续已经有效的工程模式。
- 若目标用户、主流程或关键数据规则仍有实质冲突,退回产品决策点,不用架构选择掩盖歧义。
- 不直接实现代码,不决定未确认的按钮、奖励、付费、权限理由或业务状态。

## 架构流程

1. 列出输入事实、产品不变量、质量目标、约束、未知项和不在本轮范围内的内容。