LeoYeAI/agent-master-skills / skills/activity-campaign-from-ui
activity-campaign-from-ui
VerifiedTurn campaign UI references into a new H5/Web campaign proposal, page architecture, and HTML/CSS/JavaScript high-fidelity front-end draft. Supports mode-based responses: analysis, proposal, architecture, delivery, and full.
| File | Kind | Size |
|---|---|---|
| CHANGELOG.md | markdown | 6.5 KB |
| CONTRIBUTING.md | markdown | 5.6 KB |
| README.md | markdown | 6.0 KB |
| README.zh-CN.md | markdown | 5.5 KB |
| RELEASE-CHECKLIST.md | markdown | 6.8 KB |
| RELEASE.md | markdown | 2.4 KB |
| SKILL.md | skill md | 17.5 KB |
| _meta.json | config | 481 B |
| agents/openai.yaml | config | 284 B |
| examples/campaign-schema-example.json | config | 1.9 KB |
| examples/full-delivery-example.md | markdown | 13.6 KB |
| examples/input-example.md | markdown | 764 B |
| examples/mode-analysis-example.md | markdown | 1.5 KB |
| examples/mode-architecture-example.md | markdown | 1.6 KB |
| examples/mode-delivery-example.md | markdown | 11.0 KB |
| examples/mode-proposal-example.md | markdown | 2.9 KB |
| examples/output-example.md | markdown | 4.7 KB |
| examples/spring-festival-case.md | markdown | 1019 B |
| references/scope.md | markdown | 1.3 KB |
CONTRIBUTING.md
View on GitHub# Contributing
This repository is for a **single OpenClaw skill with multiple modes**.
Before changing anything, keep the core contract stable:
- One skill, not multiple separate skills in this repo
- Fixed platform: **H5 / Web**
- Fixed stack: **HTML + CSS + JavaScript**
- Supported modes only:
- `analysis`
- `proposal`
- `architecture`
- `delivery`
- `full`
Do not expand this repository back into a multi-framework or generic image-to-code project.
## Contribution goals
Good contributions should improve one or more of these:
- output stability
- mode clarity
- anti-copy protection
- handoff quality
- schema consistency
- example quality
- documentation consistency
## Do not change these without a deliberate versioned decision
Treat these as protected rules:
1. **Fixed stack**
- Do not add Vue, React, Uni-app, or framework-specific guidance.
- Do not add framework-specific examples.
2. **Skill shape**
- Do not split the repo content into multiple default skills.
- Keep the repository centered on one skill with mode-based behavior.
3. **Anti-copy rule**
- Do not weaken the rule that the skill must transform references into a new campaign.
- Do not allow superficial reskinning to pass as valid output.
4. **Mode contract**
- Do not blur the differences between `analysis`, `proposal`, `architecture`, `delivery`, and `full`.
- If mode behavior changes, update all related examples and docs.
## When you must update multiple files together
If you change one of the following, you must update all related files in the same commit.
### A. Skill behavior changes
If you change `SKILL.md`, also review and update:
- `README.md`
- `README.zh-CN.md`
- `references/scope.md`
- relevant files in `examples/`
- `CHANGELOG.md`
### B. Mode changes
If you change any mode definition, also update:
- `README.md`
- `README.zh-CN.md`
- `SKILL.md`
- the matching `examples/mode-*.md`
- `examples/full-delivery-example.md`
- `CHANGELOG.md`
### C. Output structure changes
If you change the output sections, file layout, schema shape, or handoff format, also update:
- `SKILL.md`
- `examples/output-example.md`
- `examples/full-delivery-example.md`
- `examples/campaign-schema-example.json`
- `CHANGELOG.md`
### D. Repository structure changes
If you add, rename, or remove files, also update:
- `README.md`
- `README.zh-CN.md`
- `CHANGELOG.md`
## Required review checklist before merging
Before merging a contribution, verify all of the following.
### 1. Stack discipline
- No mention of unsupported frameworks
- No code output outside HTML/CSS/JS
- No examples suggesting alternate front-end stacks
### 2. Mode discipline
- `analysis` stays analysis-only
- `proposal` stays proposal-first
- `architecture` stays structure-first
- `delivery` stays code-delivery-first
- `full` still covers the complete flow
### 3. Anti-copy discipline
- The skill still requires transformation, not duplication
- New examples do not look like the same page with renamed text
- Examples still show changes in at least two of:
- campaign theme
- reward mechanism
- task structure
- major module sequence or core interaction
### 4. Documentation discipline
- English and Chinese README files still describe the same product
- File lists are still accurate
- Example names in docs still match real files
- Terminology is still consistent across all docs
## Example contribution types
### Good changes
- tighten the mode prompts
- improve anti-copy instructions
- improve schema clarity
- add a better H5/Web example
- make output sections more consistent
- improve English/Chinese wording consistency
### Risky changes
These need extra review:
- adding new modes
- changing default mode behavior
- changing delivery file names
- changing the schema contract
- changing anti-copy rules
- changing the fixed stack
## File naming guidance
Keep naming stable and descriptive.
Preferred pattern for examples:
- `mode-analysis-example.md`
- `mode-proposal-example.md`
- `mode-architecture-example.md`
- `mode-delivery-example.md`
- `full-delivery-example.md`
Avoid vague names like:
- `new-example.md`
- `demo.md`
- `test-output.md`
## Formatting guidance
- Keep `.editorconfig` at the repository root.
- Use `.editorconfig` as the formatting baseline for Markdown and JSON changes.
- Do not introduce a formatter rule that conflicts with the repository `.editorconfig` without a versioned decision.
## Writing guidance
When editing docs:
- keep language direct
- prefer stable wording over clever wording
- avoid overpromising
- avoid implying pixel-perfect visual recovery
- separate observed content from inferred or assumed content when relevant
- keep the skill framed as a handoff-ready planning and delivery tool
## Ownership and licensing
- Keep `LICENSE` present at the repository root.
- Keep `CODEOWNERS` present at the repository root.
- Replace the placeholder owner in `CODEOWNERS` before using this repository in a shared GitHub project.
- If repository ownership changes, update `CODEOWNERS`, `README.md`, and `README.zh-CN.md` together when needed.
## Release discipline
Before publishing a new version:
1. update `CHANGELOG.md`
2. update the `VERSION` file
3. review `RELEASE.md` if the release policy needs adjustment
4. run through `RELEASE-CHECKLIST.md`
5. verify README file lists
6. verify all mode examples still match the current behavior
7. verify no outdated stack wording has slipped back in
## Suggested commit scope
Use small commits when possible:
- docs only
- examples only
- schema only
- mode behavior update
- release prep
This makes it easier to track why a change was made and whether all required files were updated.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |