skills/stitch-skills/stitch-skill-creator/SKILL.md
Factory skill for creating new Stitch Scenario Skills with the Design First, Execute Last SOP. Use when you need to add a new domain (e.g. Music Apps, Social Networks, Login Pages) to the Stitch ecosystem. Generates SKILL.md templates, directory structure, and examples via automated script or manual workflow.
npx skillsauth add partme-ai/full-stack-skills stitch-skill-creatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill guides the creation of new Stitch Scenario Skills. A Scenario Skill is a specialized "Prompt Architect" for a specific domain (e.g., stitch-ui-music-designer, stitch-ui-blog-designer).
All Stitch Skills created by this creator MUST adhere to the Stitch Design SOP:
Keep this file concise. Use bundled references when you need full details:
references/workflows.mdreferences/output-patterns.mdUse the bundled script to automatically generate the skill structure, SKILL.md (with Golden Template), and examples/usage.md.
# Usage: ./scripts/init_stitch_skill.py <scenario-name> --path <skills-directory>
./scripts/init_stitch_skill.py music-designer --path skills/
This will automatically:
skills/stitch-ui-music-designer.SKILL.md with the required SOP and Templates.examples/usage.md.Follow: references/workflows.md -> Manual creation.
Identify the domain and name the skill following the strict naming convention: stitch-ui-<scenario>-designer.
stitch-ui-music-designer (MUST start with stitch-ui-)stitch-ui-login-designermkdir -p skills/stitch-ui-<scenario>-designer/examples
SKILL.md (The Golden Template)You MUST use the following template for the new skill. It enforces the required SOP.
---
# <Scenario> Screen Designer
**Constraint**: Only use this skill when the user explicitly mentions "Stitch" or when orchestrating a Stitch design task.
This skill helps you construct high-quality prompts for <Scenario> flows to be used by the Stitch Orchestrator.
## Functionality
It encapsulates best practices for <Scenario> UI design and translates user intent into a structured Stitch prompt.
## Integration with Stitch Designer SOP
This skill is part of the **Stitch UI Orchestration** flow.
1. **Orchestrator**: `stitch-ui-designer` calls this skill when a scenario-specific prompt is needed.
2. **Guidelines**: You MUST apply principles from `stitch-ued-guide` (e.g., visual vocabulary, device constraints).
3. **Output**: You do NOT execute. You return a prompt only.
## Prompt Template
When the user asks for a <Scenario> screen, use this template to construct the prompt:
```text
[Context]
[Device] <Scenario> screen for [App Name]. [Style] aesthetic.
[Layout]
Header: [...]
Body: [...]
Footer: [...]
[Components]
- [...]
- [...]
```
## Output Format (STRICT)
Return exactly one code block and no extra prose:
```text
[Context]
...
[Layout]
...
[Components]
...
```
## Usage in Orchestrator
This skill is designed to be called by `stitch-ui-designer`. It does NOT execute; it returns a prompt only.
examples/usage.mdProvide at least 2 distinct examples of how this skill transforms a vague request into a detailed prompt.
development
Provides per-component and per-API examples with cross-platform compatibility details for uni-app, covering built-in components, uni-ui components, and APIs (network, storage, device, UI, navigation, media). Use when the user needs official uni-app components or APIs, wants per-component examples with doc links, or needs platform compatibility checks.
tools
Creates new uni-app projects via the official CLI or HBuilderX with Vue 2/Vue 3 template selection, manifest.json and pages.json configuration, and directory structure setup. Use when the user wants to scaffold a new uni-app project, initialize project files with a single command, or set up the development environment.
tools
Browses, installs, configures, and manages plugins from the uni-app plugin market (ext.dcloud.net.cn) including component plugins, API plugins, and template plugins with dependency handling. Use when the user needs to find and install uni-app plugins, configure plugin settings, manage plugin dependencies, or integrate third-party components.
tools
Develops native Android and iOS plugins for uni-app including module creation, JavaScript-to-native communication, and plugin packaging for distribution. Use when the user needs to build custom native modules, extend uni-app with native capabilities (camera, Bluetooth, sensors), or create publishable native plugins.