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 |
RELEASE.md
View on GitHub# Release Policy
This repository uses a simple versioning strategy so the skill can be maintained as a stable, single-skill project.
## Current version
See the `VERSION` file at the repository root.
## Version format
Use `MAJOR.MINOR.PATCH`.
Examples:
- `0.1.0`
- `0.2.0`
- `0.2.1`
- `1.0.0`
## What each part means
### MAJOR
Increase the major version when the core contract changes in a breaking way.
Examples:
- changing the repository from one skill to multiple default skills
- changing the fixed stack away from HTML + CSS + JavaScript
- renaming or removing existing modes
- changing the delivery file contract in a breaking way
### MINOR
Increase the minor version when the skill gains meaningful capability without breaking its main contract.
Examples:
- adding a new example set
- improving schema coverage
- improving anti-copy rules
- refining mode guidance
- improving delivery structure while keeping the same file contract
### PATCH
Increase the patch version when making small, non-breaking improvements.
Examples:
- wording fixes
- example corrections
- README cleanup
- typo fixes
- clarifying documentation
- packaging cleanup
## Pre-1.0 guidance
This repository is still in an early stage.
Use `0.x.y` while the skill is still being shaped.
Treat minor version bumps in `0.x.y` as meaningful repository milestones.
Recommended interpretation:
- `0.1.x` — first stable repository structure
- `0.2.x` — stronger examples, schema, and release discipline
- `0.3.x` — stronger behavior consistency and validation
- `1.0.0` — ready for long-term stable maintenance
## Release checklist
Before changing the version:
1. update `CHANGELOG.md`
2. update the `VERSION` file
3. verify `README.md` and `README.zh-CN.md`
4. verify all `examples/` still match the current skill behavior
5. verify `SKILL.md` still matches the fixed platform, stack, and mode rules
6. run the repository release checklist if available
## Suggested tag format
Use lightweight repository tags like:
- `v0.1.0`
- `v0.2.0`
- `v0.2.1`
## Suggested release note sections
When writing a release note, keep it short and structured:
- Added
- Changed
- Fixed
- Removed
## Breaking-change warning
If a change touches any of the following, strongly consider a major version decision:
- skill shape
- supported modes
- fixed stack
- delivery file contract
- anti-copy contract
- schema contract
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 |