Miniapp Official Scaffold Alignment
Validate or design a WeChat Mini Program scaffold, repository layout, or TypeScript setup against official platform rules. Use when Codex needs to review `project.config.json`, `app.json`, `miniprogramRoot`, page or component file sets, or the initial repo skeleton before feature work begins.
Install
$ agentstack add skill-sun-sunshine06-miniprogram-skills-miniapp-official-scaffold-alignment ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Miniapp Official Scaffold Alignment
Overview
Use this skill when scaffold correctness is the blocker. Validate the repository shape before changing pages, components, or build settings.
Quick Start
- Read
references/official-scaffold-baseline.md. - Identify the repository root and the miniapp code root.
- Check
project.config.json,app.json, page paths, component file sets, and TypeScript assumptions. - Report what is already valid, what is incomplete or risky, and the smallest next scaffold decision.
Core Rules
- Use only official WeChat documentation for normative claims.
- Prefer the smallest runnable scaffold that matches the project shape.
- Distinguish repository root from miniapp code root.
- If the repo authors in TypeScript, make the compiler-plugin path explicit.
- Require matching path-and-name file quartets for pages and components.
- Write "not yet specified" instead of inventing missing spec details.
Review Checklist
- Does
project.config.jsonpoint at the intended miniapp code root? - Does
app.json.pagesmatch real page folders? - Does every page have matching logic, structure, style, and config files?
- Do custom components declare
component: trueand have matching file sets? - Is TypeScript support explicit rather than implied?
- Does the repo layout leave room for sibling folders such as
docs/, backend code, or tooling?
Output Format
When answering, keep the result short and action-oriented:
- officially valid parts
- missing or risky parts
- recommended scaffold decision
- first edit to make
Resources
references/official-scaffold-baseline.md: official rule summary and practical implicationsreferences/example-prompts.md: reusable trigger examples and evaluation notes
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Sun-sunshine06
- Source: Sun-sunshine06/miniprogram-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.