Hire an AI WeChat Mini Program developer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A page and navigation plan, with the main package and subpackages
• A plan for login, payment, sharing and messages, step by step
• A size and speed plan with the limits that matter for your app
• Draft code for the parts you ask for, marked as not run
• A checklist to clear before you submit for WeChat review
• Your assumptions and the checks left for you to run

How it does the job well

• Platform limits you recall from the profile or from memory (package size, server address registration, HTTPS, review rules) are starting assumptions. Write "check this in WeChat's current documents" next to each one you rely on. Never present a limit as current fact.
• The profile's success targets (start-up time, package size, first-time review pass rate, retention, crash rate, share conversion) are goals for the role. Do not quote them as results, and do not promise them for this app.
• Payment: your server creates the order and the signed payment values. The Mini Program only calls the payment API with those values. Never put payment keys, signing secrets or server tokens in Mini Program code or in chat.
• Private data (location, profile, phone number) needs the user's consent and a visible reason on the page. Name the Chinese data-protection rules the profile mentions (PIPL) as something the owner must check with a qualified adviser. Do not give legal advice.
• Drafts only. Do not claim code was run, tested, built or approved. Do not claim a review pass.
• Read the existing code, its conventions and its tests before changing anything. Match the project's patterns.
• Make the smallest change that fully solves the request. Keep unrelated refactors out.

Mistakes it avoids

• Web code that needs the DOM or a browser window. Mini Programs have no direct page access.
• Calling servers that are not registered, or over plain HTTP.
• Creating payment signatures in the app instead of on the server.
• Presenting profile targets or remembered limits as measured or current.
• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.

What a good result looks like

An example, not your task: You are starting a Mini Program for a shop, a booking service or a members club and want the page plan first.

• Scope and assumptions. What the app does, the WeChat features it needs and every assumption the plan rests on.
• Pages and navigation. Each page, what it is for, and whether it sits in the main package or a subpackage.
• WeChat features. Login, payment, sharing and message steps, split into what your server does and what the app does.
• Size and speed plan. The risks to start-up time and package size, each with a fix.
• Draft code. Code for the parts you asked for, clearly marked as not run.
• Before you submit. A checklist of server, HTTPS, privacy and permission items to clear before WeChat review.

How the work is checked

• The changed files build, and the relevant tests and linters pass. The commands and results are shown.
• Each change is explained in one line with its reason, and risky areas are named.
• Any check that could not run is reported as NOT_RUN with what it needs.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Kent Beck and Linus Torvalds would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Set the rules first. It lists the limits your app must fit, such as HTTPS, registered server addresses, package size and consent for private data. It marks any it cannot confirm.
• Plan pages and navigation. It lays out app.json, the tab bar, pages and which features go in subpackages so the main package stays small.
• Plan the WeChat features. It maps login, payment, sharing and subscription messages. Your server creates and signs the order. The Mini Program only calls payment.
• Plan speed and size. It names the habits that slow a Mini Program, such as too many setData calls and large images, and what to do about each.
• Draft code and a review checklist. It writes the code you asked for, labelled not run, then lists what to check before you submit.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id engineering-wechat-mini-program-developer only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/engineering-wechat-mini-program-developer/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• What the Mini Program should do and who uses it, in a few lines
• Which WeChat features you need, such as login, payment, sharing, subscription messages or location
• The address and main calls of your own server, if one exists (optional)
• Your project files, such as app.json and the pages folder (optional)
• Your launch date and the phones your users have (optional)

Helpful context (optional)

• A list of your server addresses, so the server items can be checked.
• Screenshots of the pages you plan, so the page plan matches your design.

Tools and access

• Claude, ChatGPT or Gemini with file upload: It can read your app.json and page files and point to the exact lines to change.

Functions and deliverables

• WeChat Mini Program developer: Plan a WeChat Mini Program from your brief, with pages, login, payment, size limits and review checks, plus draft code to test in WeChat DevTools.
  • A page and navigation plan, with the main package and subpackages
  • A plan for login, payment, sharing and messages, step by step
  • A size and speed plan with the limits that matter for your app
  • Draft code for the parts you ask for, marked as not run
  • A checklist to clear before you submit for WeChat review
  • Your assumptions and the checks left for you to run
  Source: Michael Sitarzewski and Agency Agents contributors.
• Stripe payments builder: Describe your billing rules. Get Stripe code drafts for checkout, subscriptions, webhooks and local test steps.
  • Checkout and subscription code
  • A webhook route with a signature check
  • Upgrade and downgrade code with a price preview
  • Customer portal code
  • An eight-step test run using the Stripe CLI
  Source: Alireza Rezvani.
• Program keep-or-cut reviewer: Paste results for each project you run. This program keep-or-cut review marks every one keep, cut or double down, judged on cash and customers.
  • A verdict for each line, either keep, cut or double down
  • Earnings and new cash needed side by side
  • The four tests for each line, and a note on what customers are doing
  • A lesson for every cut line, and a reason short enough to share
• Chrome DevTools page debugger: Share a page and steps to reproduce a bug. Get browser evidence, a proposed fix and checks of the result through Chrome DevTools.
  • A list of console errors and warnings
  • Failed or slow network calls with status and timing
  • Layout and speed findings
  • A pass or fail check that your fix works in the browser
  Source: Addy Osmani.
• AI project context organiser: Share your project and next task. Get a short rules file, a focused file list and a clear handoff for later sessions.
  • A ready rules file for your project
  • A list of which files to load for each task
  • Rules for when to reset or trim the session
  • A checklist for spotting drifting answers
  Source: Addy Osmani.
• Kent Beck: Plan a software change using Kent Beck’s recorded approach. List the cases, take small steps and keep code tidying separate from new behaviour.
  • Your problem worked on the way Kent Beck would: their questions, their method, their push-back
  • The answer or the work, in Kent Beck's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Linus Torvalds: Review a code change using Linus Torvalds’s recorded approach. Ask what works, what breaks for existing users and who owns the fix.
  • Your problem worked on the way Linus Torvalds would: their questions, their method, their push-back
  • The answer or the work, in Linus Torvalds's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• You are starting a Mini Program for a shop, a booking service or a members club and want the page plan first.
• Your app needs WeChat login, WeChat Pay or subscription messages and you want the flow laid out step by step.
• Your main package is close to the size limit and you need to know what to move into subpackages.
• You want a check against what WeChat review looks for before you submit.

Limits to check before starting

• You want a web app or a phone app for iPhone and Android. Use the Frontend developer or the Mobile app builder.
• You want posts, menus and content for a WeChat Official Account. Use the WeChat account content planner.
• You have existing code and want it reviewed line by line. Use the Code Reviewer agent.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack and add it to your AI as a skill. If you cannot, paste SKILL.md and then references/source-agent.md into a new chat. Claude, ChatGPT and Gemini all work.
• Paste your brief. Say what the app does, who uses it and which WeChat features you need. Attach app.json and other project files if you have them.
• Type "Plan this Mini Program and draft the login and payment code." Your AI asks once for anything missing.
• Read the assumptions first. Correct any that are wrong before you trust the plan.
• Test the draft code in WeChat DevTools, then on a real phone. Your AI cannot run it for you.
• Check the size, server and privacy items against WeChat's current documents. Then submit for review yourself.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/engineering-wechat-mini-program-developer for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.