When to use this skill
Use this skill whenever the user wants to:
- Build uni-app mini programs
- Configure mini program settings and capabilities
- Use mini program components and APIs within uni-app
- Understand native mini program limitations and compatibility
How to use this skill
-
Start with the overview:
examples/guide/intro.md
-
Configure mini program settings:
examples/guide/config.md
-
Check component and API references:
examples/components/overview.mdexamples/api/overview.md
Examples and Templates
examples/guide/intro.md- Mini program overviewexamples/guide/config.md- Configuration and capability setupexamples/components/overview.md- Component references and usageexamples/api/overview.md- API references and usage
Best Practices
- Follow mini program platform requirements and audits
- Keep package size small and optimize assets
- Validate API compatibility per platform
- Use conditional compilation for platform-specific code
Resources
Keywords
uniapp, uni-app, mini program, mini program, native support, components, api, platform compatibility
Capability Boundaries
✅ Applicable Scenarios
- When you need to use the technology stack corresponding to this skill
- When the project needs to follow best practices
- When you need to get started quickly or gain an in-depth understanding of core concepts
⚠️ Points to Note
- Complex business logic needs to be adjusted according to specific scenarios
- Performance optimization needs to be evaluated based on the actual data volume
❌ Inapplicable Scenarios
- Irrelevant technology stacks or frameworks
- Special scenarios that require full customization
Common Pitfalls (Gotchas)
- Version Compatibility: Pay attention to the compatibility between the framework version and dependency libraries; APIs may differ across versions
- Configuration File Format: Configuration file format errors are the most common issue; it is recommended to use the editor's syntax checking
- Environment Variables: Ensure that all necessary environment variables are set correctly, and do not hard-code sensitive information
- Dependency Conflicts: Pay attention to dependency conflicts when multiple versions coexist, and use a lock file to pin versions
- Performance Pitfalls: Pay attention to performance optimization in large-data-volume scenarios, and avoid common issues such as N+1 queries
Usage Workflow
Step 1: Environment Preparation
Ensure that the necessary dependencies and tools are installed in the development environment.
Step 2: Configuration Initialization
Perform basic configuration according to project requirements.
Step 3: Using Core Features
Implement the core features according to the example code.
Step 4: Test Verification
Run tests to ensure the functionality works properly.
Step 5: Deployment and Launch
Deploy and monitor after development is completed.