Features
Analyze story genre types, extract creative elements, and identify story features and stylistic characteristics.
Use Cases
- Identify the core genre and type positioning of a story, and clarify the market direction.
- Extract the unique creative elements of a story to enhance the appeal of the work.
- Analyze the market positioning and audience groups of a story to guide promotional strategy.
- Provide in-depth reference basis for story adaptation and commercialization.
Core Steps
- Genre Identification: Analyze the main genre types and secondary genre elements of the story.
- Creative Extraction: Identify and extract the core creative elements and innovation points in the story.
- Feature Analysis: Analyze the uniqueness, innovation points, and stylistic characteristics of the story.
- Style Interpretation: Interpret the narrative style and artistic characteristics of the story, and grasp the tone of the work.
- Value Assessment: Comprehensively assess the commercial value and artistic value of the genre.
Input Requirements
- Story Text/Outline/Synopsis: Complete original story text, outline, or synopsis.
- Recommended Text Length: 500 characters or more.
Output Format
【题材类型分析】
- 主导题材：[题材类型]
- 辅助题材：[题材类型1、题材类型2]
- 题材融合度：[高/中/低]
【创意元素提炼】
1. 核心创意：[描述最核心的创意元素]
2. 创新点1：[具体描述]
3. 创新点2：[具体描述]
【故事特色】
- 设定特色：[描述故事的设定特点]
- 叙事特色：[描述叙事手法的特色]
【题材价值】
- 商业价值：[评估商业潜力]
- 艺术价值：[评估艺术特色]
Constraints
- Analysis results must be faithful to the original story text, without subjective speculation.
- Genre classification must be accurate, and creative extraction must be concise.
- Value assessment must be objective, with specific reasons provided.
Examples
Please refer to {baseDir}/references/examples.md for detailed analysis examples.
Detailed Documentation
See the {baseDir}/references/ directory for more documentation:
guide.md- Complete analysis guide and definition explanationsexamples.md- More scenario examples
Version History
| Version | Date | Changes |
|---|---|---|
| 2.1.0 | 2026-01-11 | Optimized the description field to make it more concise and compliant with imperative language conventions; added allowed-tools (Read) and model (opus) fields; optimized the descriptions of features, use cases, core steps, input requirements, and output format to make them more compliant with imperative language conventions; added constraints, examples, and detailed documentation sections. |
| 2.0.0 | 2026-01-11 | Refactored according to official specifications |
| 1.0.0 | 2026-01-10 | Initial version |