home / skills / tencentcloudbase / cloudbase-mcp / miniprogram-development

miniprogram-development skill

safe

/config/source/skills/miniprogram-development

This skill assists you develop WeChat mini programs with CloudBase, guiding authentication, page generation, and deployment for efficient AI-enabled mini apps.

npx playbooks add skill tencentcloudbase/cloudbase-mcp --skill miniprogram-development

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

Files (2)

SKILL.md

4.8 KB

---
name: miniprogram-development
description: WeChat Mini Program development skill for building, debugging, previewing, testing, publishing, and optimizing mini program projects. This skill should be used when users ask to create, develop, modify, debug, preview, test, deploy, publish, launch, review, or optimize WeChat Mini Programs, mini program pages, components, routing, project structure, project configuration, project.config.json, appid setup, device preview, real-device validation, WeChat Developer Tools workflows, miniprogram-ci preview/upload flows, or mini program release processes. It should also be used when users explicitly mention CloudBase, wx.cloud, Tencent CloudBase, 腾讯云开发, or 云开发 in a mini program project.
alwaysApply: false
---

## When to use this skill

Use this skill for **WeChat Mini Program development** when you need to:

- Build or modify mini program pages and components
- Organize mini program project structure and configuration
- Debug, preview, or publish mini program projects
- Work with WeChat Developer Tools workflows
- Handle mini program runtime behavior, assets, or page config files
- Integrate CloudBase in a mini program project when explicitly needed

**Do NOT use for:**
- Web frontend development (use `web-development`)
- Pure backend service development (use `cloudrun-development` or `cloud-functions` as appropriate)
- UI design-only tasks without mini program development context (use `ui-design`)

---

## How to use this skill (for a coding agent)

1. **Start with the general mini program workflow**
   - Treat WeChat Mini Program development as the default scope
   - Do not assume the project uses CloudBase unless the user or codebase indicates it

2. **Follow mini program project conventions**
   - Keep mini program source under the configured mini program root
   - Ensure page files include the required configuration file such as `index.json`
   - Check `project.config.json` before suggesting preview or IDE workflows

3. **Route by scenario**
   - If the task involves CloudBase, `wx.cloud`, cloud functions, CloudBase database/storage, or CloudBase identity handling, read [CloudBase integration reference](references/cloudbase-integration.md)
   - If the task involves debugging, previewing, publishing, WeChat Developer Tools, or no-DevTools workflows, read [debug and preview reference](references/devtools-debug-preview.md)

4. **Use CloudBase rules only when applicable**
   - CloudBase is an important mini program integration path, but not a universal requirement
   - Only apply CloudBase-specific auth, database, storage, or cloud function constraints when the project is using CloudBase

5. **Recommend the right preview/debug path**
   - Prefer WeChat Developer Tools for simulator, panel-based debugging, preview, and real-device validation
   - If WeChat Developer Tools is unavailable, use `miniprogram-ci` for preview, upload, and npm build workflows where appropriate

---

# WeChat Mini Program Development Rules

## General Project Rules

1. **Project Structure**
   - Mini program code should follow the project root configured in `project.config.json`
   - Keep page-level files complete, including `.json` configuration files
   - Ensure referenced local assets actually exist to avoid compile failures

2. **Configuration Checks**
   - Check `project.config.json` before opening, previewing, or publishing a project
   - Confirm `appid` is available when a real preview, upload, or WeChat Developer Tools workflow is required
   - Confirm `miniprogramRoot` and related path settings are correct

3. **Resource Handling**
   - When generating local asset references such as icons, ensure the files are downloaded into the project
   - Keep file paths stable and consistent with mini program config files

## CloudBase as a Mini Program Sub-Scenario

- If the user explicitly uses CloudBase, `wx.cloud`, Tencent CloudBase, 腾讯云开发, or 云开发, follow the CloudBase integration reference
- In CloudBase mini program projects, use `wx.cloud` APIs and CloudBase environment configuration appropriately
- Do not apply CloudBase-specific rules to non-CloudBase mini program projects

## Debugging, Preview, and Publishing

- If WeChat Developer Tools is available, use it as the primary path for simulator debugging, panel inspection, preview, and device validation
- If WeChat Developer Tools is not available, use `miniprogram-ci` as the fallback path for preview, upload, and npm build-related automation
- For detailed workflows, read [debug and preview reference](references/devtools-debug-preview.md)

## References

- [CloudBase Mini Program Integration](references/cloudbase-integration.md) — use this when the mini program project explicitly integrates CloudBase
- [WeChat DevTools Debug and Preview](references/devtools-debug-preview.md) — use this for debugging, preview, publishing, and no-DevTools fallback workflows

Overview

This skill provides practical rules and conventions for WeChat Mini Program development with CloudBase integration. It focuses on project structure, CloudBase usage, AI model invocation, step count handling, and correct use of WeChat Developer Tools to avoid build and permission issues. Use it to produce reliable, deployable mini program code and deployment guidance.

How this skill works

The skill inspects project layout (miniprogram and cloudfunctions directories), validates required files (project.config.json and page .json configs), and enforces CloudBase conventions such as using the latest base library and environment IDs. It guides resource handling (icon sources and downloads), prescribes secure step-count and identity patterns (CloudID and cloud.getWXContext()), and recommends Developer Tools workflows to preview, debug, and deploy cloud functions with correct permissions.

When to use it

Building WeChat Mini Program pages and components that integrate CloudBase services.
Calling AI models from within a mini program (base library 3.7.1+).
Retrieving WeChat step-count data securely using CloudID.
Preparing a project for preview, debugging, and publishing with WeChat Developer Tools.
Deploying cloud functions and resolving permission / dependency issues after auto-deploy.

Best practices

Keep mini program code in a miniprogram directory and cloud functions in cloudfunctions.
Include page configuration files (e.g., index.json) with any generated pages to avoid compile errors.
Do not generate login pages—use cloud.getWXContext().OPENID in cloud functions for identity.
Prefer Icons8 for small, color-customizable icons and download assets before build.
Use CloudID for step count via wx.getWeRunData() + wx.cloud.CloudID and implement a fallback for failures.
Open projects in WeChat Developer Tools after confirming project.config.json contains an appid.

Example use cases

Generate a new mini program page with corresponding .wxml, .wxss, .js, and .json files and download required icons.
Create a cloud function that reads OPENID via cloud.getWXContext() to scope user data without a login flow.
Integrate an AI model call (wx.cloud.extend.AI) for content generation in a mini program supported by base library 3.7.1+.
Implement secure step-count retrieval: frontend gets cloudID, cloud function decrypts weRunData, with simulated fallback.
Guide user to open the project in WeChat Developer Tools CLI and run dependency install for cloud functions.

FAQ

Should I implement a login page in a CloudBase mini program?

No. CloudBase mini programs are login-free; get user identity in cloud functions via cloud.getWXContext().OPENID.

How should I retrieve WeChat step data securely?

Use wx.getWeRunData() to obtain a cloudID, pass it with wx.cloud.CloudID to a cloud function, and decrypt weRunData there. Provide a fallback for cloudID failures.