Reusable Skill Files
This page explains how to add the creating-generators skill to your project and ensures you are using the latest version.
As of 2026-03-25, this page no longer embeds the full SKILL.md and reference.md code blocks. Instead, it points to the Single Source of Truth to avoid drift between the documentation and actual skill files.
Single Source of Truth
Please always refer to these two files:
generator-sdk/generator-sdk-mcp/skills/creating-generators/SKILL.mdgenerator-sdk/generator-sdk-mcp/skills/creating-generators/reference.md
If you are reading this documentation within the current repository, you can also refer directly to:
.cursor/skills/creating-generators/SKILL.md.cursor/skills/creating-generators/reference.md
They should remain synchronized.
Target Directory Structure
.cursor/
skills/
creating-generators/
SKILL.md
reference.mdHow to Copy
Method 1: Copy from Current Repository
If you are working in this repository, copy these two files to your target project:
.cursor/skills/creating-generators/SKILL.md
.cursor/skills/creating-generators/reference.mdMethod 2: Copy from generator-sdk-mcp Package
If you are using the published @atomm-developer/generator-sdk-mcp package, copy from the following directory within the package:
skills/
creating-generators/
SKILL.md
reference.mdMethod 3: Let AI Help You Install or Sync
You can directly tell the AI:
Please help me install the creating-generators skill to the current project and ensure that SKILL.md and reference.md are the latest versions.3 Key Constraints to Verify After Copying
If you are not copying directly from the single source of truth but pasting manually from other pages or chat history, ensure at least these three types of constraints are present.
1. Task Type Distinction
Refactoring existing generators must distinguish between:
- Compatibility Refactoring
- Standardization Refactoring
If the skill only mentions "refactoring existing generators" without splitting these two types, you are using an outdated version.
2. Standardization Completion Gates
The skill must explicitly define:
- Which conditions must be met before claiming "Standardization Refactoring Complete."
- Which cases should only be described as "phased delivery" or "compatibility refactoring complete."
Specifically, these thresholds should be clearly stated:
generator-sdkplatform capabilities integrated.- Full runtime contract exposed.
- Both
fullandembedentry points functional. window.__GENERATOR_RUNTIME__exposed.getPanelSchema()+PanelFilterconsumable by the host.- Unified template protocol used for template scenarios.
3. Mandatory Closing Template
The final response must explicitly include:
- Task Type
- Current Phase
- Completed Items
- Unfinished Items
- Is Standardization Complete?
- Blocking Points or Risks
- Compatibility and Migration Notes
Without this template, the AI might easily describe "partial completion" as "completed according to skill."
Recommended Initial Prompts
New Generator
Help me make a new photo frame generator.Compatibility Refactoring
This is an existing generator source at @index.html.
Please perform compatibility refactoring in the @refactor directory:
1. All functionality, interaction, style, and export behavior must remain unchanged.
2. Integrate generator-sdk.
3. Allow phased delivery, but do not misreport as standardization complete.Standardization Refactoring
This is an existing generator source at @index.html.
Please perform standardization refactoring in the @refactor directory, not just minimal compatibility changes:
1. All functionality, interaction, style, and export behavior must remain unchanged.
2. Integrate generator-sdk.
3. Complete the full Generator Runtime Contract.
4. Provide full / embed dual entry points.
5. Support PanelSchema + PanelFilter.
6. Use the unified template protocol if template scenarios are involved.
7. Do not claim standardization completion until the standard generator refactor is finished.Self-Checklist After Copying
You can ask the AI or check yourself:
Please check if the creating-generators skill in the current project meets:
1. Distinguishes between compatibility and standardization refactoring.
2. Includes standardization completion gates.
3. Includes a mandatory closing template.
4. Refactoring branch asks for task type before asking for code location.
5. reference.md is consistent with SKILL.md.