User request
    ↓
1. Identify the MCP configuration provided by the user or the specified MCP
    ↓
2. Call get_app_info() to confirm the currently connected MCP application
    ↓
3. Compare: current connection vs. user-specified MCP
    ↓
4. If they do not match → confirm with the user
    ↓
5. Proceed after confirmation

User enters a topic
    ↓
Step 1: Dynamically read the search API configuration (Tavily/Serper) from the HAP "API Service Configuration" table
    ↓
Step 2: Call the search API to retrieve material related to the topic (Tavily API)
    ↓
Step 3: **【MANDATORY】Read the account persona configuration from the HAP "Account Persona" table (must be performed before content generation)**
    - **Local files are prohibited**: using AGENTS.md or any other local file as the account persona source is strictly prohibited
    - **HAP MCP must be called**: MCP must be used to call get_record_list() to read from the HAP "Account Persona" table
    - **Reading flow**:
      1. Confirm the currently connected HAP MCP application through get_app_info()
      2. Dynamically obtain the ID of the "Account Persona" table by matching the alias account_persona or the name 账号人设
      3. Query the account persona for the relevant platform according to platform_type, such as Xiaohongshu
      4. **Read all required fields**:
         - Account positioning (positioning)
         - Target audience (target_audience)
         - Content direction (content_direction)
         - Content style (content_style) **【MUST BE STRICTLY FOLLOWED】**
         - Content principles (content_principles) **【MUST BE STRICTLY OBSERVED】**
         - Image generation prompt (image_generation_prompt)
    - **Validation requirement**: if no account persona configuration is found, throw an exception and do not continue content generation
    ↓
Step 4: Write the content based on the search results and account persona
    - **Strictly follow the account persona**: content must be generated strictly according to content_style and content_principles read from HAP
    - **Local personas are prohibited**: do not reference or use content from the local AGENTS.md file
    - **Combine the search material**: combine the retrieved material with the account persona read from HAP to generate content aligned with the account positioning
    - **Ensure persona alignment**: ensure the content matches the target audience, content direction, and account positioning
    ↓
Step 5: Generate cover titles (5–10 alternatives)
    - Generate titles according to the account persona's content style
    - Ensure they match the account positioning and target audience
    ↓
Step 6: Select topic hashtags (from the HAP Hashtag Library)
    - Select them according to the content topic and the account persona's content direction
    ↓
Step 7: Generate image suggestions
    - Combine the account persona's image generation prompt style
    - Generate image suggestions based on the content topic
    ↓
Step 8: Save to a local file for preview, organized according to the note directory structure
    ↓
Step 9: Confirm the content, titles, and images with the user
    ↓
Step 10: After user confirmation, read the image generation prompt (image style) from the HAP "Account Persona" table
    ↓
Step 11: Dynamically read the image generation configuration from the HAP "API Service Configuration" table
    ↓
Step 12: Combine the image style prompt and image suggestions to generate a complete prompt
    ↓
Step 13: Extract the key and generate images (optional, using the configured API service)
    ↓
Step 14: Confirm with the user whether to publish directly to Xiaohongshu
    ↓
Step 15: Confirm with the user whether to synchronize the content to HAP; upload only after confirmation
    - **Xiaohongshu notes**: upload only image URLs, including the cover image and other images; do not upload the Markdown document
    - **Other platforms**: upload images and documents according to platform requirements
    - **Related topic, if applicable**:
      - If the content was created from a topic in the Topic Idea Library, associate it with the corresponding topic through the related_topic field when creating the content record
      - If the content was not created from a topic, do not create an association
    ↓
Step 16: Publish to the target platform using Playwright MCP, if confirmed by the user

User requests trending content recommendations
    ↓
Step 1: Read the platforms followed by the user from the HAP "Trending Platform Follow List" table (is_followed = 1)
    - Sort by priority
    - Obtain platform codes (platform_code)
    ↓
Step 2: Read the Trending News API configuration from the HAP "API Service Configuration" table
    - Function name: Trending News API
    - Service type: Trending News
    - Endpoint URL: https://orz.ai/api/v1/dailynews
    ↓
Step 3: Call the Trending News API to retrieve trending topics for each platform
    - For each followed platform, call: GET https://orz.ai/api/v1/dailynews/?platform={platform_code}
    - Retrieve the headline, URL, score, description, and other information
    - Merge the trending data from all platforms
    ↓
Step 4: Read the account persona configuration from the HAP "Account Persona" table
    - Account positioning (positioning)
    - Target audience (target_audience)
    - Content direction (content_direction)
    - Content style (content_style)
    - Content principles (content_principles)
    ↓
Step 5: Analyze topics based on the trending data and account persona
    - Select trending topics related to the account positioning and content direction
    - Analyze the content potential of each topic, including popularity, relevance, and creatability
    - Generate 5–10 topic suggestions, each containing:
      - Topic title
      - Source platform
      - Topic angle (how to combine it with the account persona)
      - Expected content direction
      - Recommendation reason
      - Relevance score (1–10)
    - **Sort by relevance score and clearly mark the most highly recommended topic**
    ↓
Step 6: Present the topic suggestions in a Markdown table so the user can make a selection
    - **A Markdown table must be used** to provide a more intuitive presentation
    - **Table structure**:
      - Top recommendation table (AI-related or scored 10/10)
      - Other recommendation table (scored 6–9/10)
    - **Table columns**: number, topic title, source platform, topic angle, recommendation reason, relevance score
    - **Clearly mark the top recommendation**, such as ⭐ Top Recommendation
    - Display all topic suggestions
    - The user selects one or more topics
    ↓
Step 6.5: Ask the user whether to add the selected topics to the Topic Idea Library
    - **Ask the user**: Would you like to add these topics to the HAP "Topic Idea Library" table?
    - **How to ask**: after presenting the topic suggestions, ask "Would you like to add these topics to the Topic Idea Library?"
    - If the user confirms, save the selected topics to the HAP "Topic Idea Library" table:
      - topic_title: topic title
      - source_platform: source platform, linked to the Trending Platform Follow List table using the platform record's rowid
      - topic_angle: topic angle
      - recommendation_reason: recommendation reason
      - relevance_score: relevance score
      - source_url: original article URL
      - content_preview: content preview
      - topic_status: topic status, with 待创作 as the default
    - If the user does not want to add them, skip this step
    - **Batch saving**: if the user selects multiple topics, use batch_create_records to save them in bulk
    ↓
Step 7: After the user selects a topic, perform an in-depth search for related material
    - Read the Tavily search API configuration from the HAP "API Service Configuration" table
    - Search for in-depth material based on the topic title and angle
    - Combine it with the original information from the Trending News API
    ↓
Step 8: Generate content based on the trending information and search material
    - Combine the original headline, description, and URL from the trending information
    - Combine the in-depth search material
    - Strictly follow the content style and content principles in the account persona
    - Generate content aligned with the account positioning
    ↓
Step 9: Continue with the standard content generation workflow
    - Generate cover titles (5–10 alternatives)
    - Select topic hashtags from the HAP Hashtag Library
    - Generate image suggestions
    - Save to a local file for preview
    - Confirm the content, titles, and images with the user
    - Generate images after user confirmation
    - Synchronize to HAP after user confirmation:
      - **If the content was created from a topic in the Topic Idea Library**:
        - Associate it with the corresponding topic through the related_topic field when creating the content record
        - Update the topic status to 创作中 or 已创作
        - The related_content field in the Topic Idea Library automatically links to the created content through a bidirectional relation
      - **If the content was not created from a topic**:
        - Do not create an association and leave related_topic empty
    - Publish to the target platform after user confirmation

GET https://orz.ai/api/v1/dailynews/?platform=baidu
GET https://orz.ai/api/v1/dailynews/?platform=weibo
GET https://orz.ai/api/v1/dailynews/?platform=zhihu

{
  "status": "200",
  "data": [
    {
      "title": "Trending headline",
      "url": "Trending article URL",
      "score": "Popularity score",
      "desc": "Trending description"
    }
  ],
  "msg": "success"
}

undefined

# Validate required fields
if not api_key:
    raise Exception('Tavily API Key is not configured. Enter api_key in the HAP API Service Configuration table')
if not endpoint_url:
    raise Exception('Endpoint URL is not configured. Enter endpoint_url in the HAP API Service Configuration table')

# Call the Tavily API to search
import requests
response = requests.post(
    f"{endpoint_url}/search",
    headers={"Content-Type": "application/json"},
    json={
        "api_key": api_key,
        "query": topic,  # User-provided topic
        "search_depth": "basic",
        "max_results": 5,
        "topic": "general",
        "include_answer": False,
        "include_raw_content": False,
        "include_images": False
    }
)

search_results = response.json().get('results', [])
# Use the search results to generate content

**Tavily API configuration fields (required fields):**
- `function_name`: function name (Text, title field), such as "Tavily Search API"
- `provider`: service provider (Text), such as "Tavily"
- `service_type`: service type (SingleSelect: Search API/Image Generation/Content Generation/Data Analysis/Other)
- `api_key`: **API Key (Text, required)** — Tavily API Key, such as `tvly-dev-xxx...`
  - **When to enter it**: search APIs such as Tavily and Serper require this field
- `endpoint_url`: **Endpoint URL (Text, required)** — API base URL, such as `https://api.tavily.com`
  - **When to enter it**: every API service requires this field to specify its endpoint
- `config_status`: configuration status (SingleSelect: Enabled/Disabled)
- `purpose`: purpose (Text), such as "Used to search for material related to a topic"

**Search flow:**
1. **Read the configuration**: read the Tavily search API configuration from the HAP "API Service Configuration" table
2. **Call the API**: use the configured API Key to call the Tavily API and search for material related to the topic
3. **Process the results**: extract key information from the search results, including titles, content, and URLs
4. **Read the account persona (important: must be done before content generation)**: read the account positioning, content style, content principles, and other settings from the HAP "Account Persona" table
5. **Generate content**: combine the search results with the account persona and strictly follow the persona's `content_style` and `content_principles` to generate high-quality content

**Search parameter notes:**
- `query`: search topic supplied by the user
- `search_depth`: search depth, basic/advanced; basic is recommended
- `max_results`: maximum number of results; 5 is recommended
- `topic`: topic type, such as general, tech, or business
- `include_answer`: whether to include an answer summary; False
- `include_raw_content`: whether to include raw content; False
- `include_images`: whether to include images; False

**Example functional configuration in the HAP table:**
- **Function name**: Tavily Search API (title field)
- **Service provider**: Tavily
- **Service type**: Search API, selected from the dropdown list
- **Purpose**: search for material related to a topic and obtain up-to-date information
- **API Key**: `tvly-dev-xxx...` (**required**, Tavily API Key)
- **Endpoint URL**: `https://api.tavily.com` (**required**, API base URL)
- **Configuration status**: Enabled, selected from the dropdown list

**Example Trending News API configuration in the HAP table:**
- **Function name**: Trending News API (title field)
- **Service provider**: orz.ai
- **Service type**: Trending News, selected from the dropdown list
- **Purpose**: retrieve trending news data for each platform and support daily trending content recommendations
- **Endpoint URL**: `https://orz.ai/api/v1/dailynews` (**required**, API base URL)
- **Configuration status**: Enabled, selected from the dropdown list

**Important notes:**
- `api_key` and `endpoint_url` are required fields for the search API and must be provided
- `api_key` is used for API authentication
- `endpoint_url` specifies the API endpoint, such as `https://api.tavily.com`
- The **Trending News API does not require an `api_key`**; only `endpoint_url` is needed

undefined

undefined

undefined

undefined

undefined

# If no default configuration exists, use the first enabled configuration
if not default_config:
    default_config = configs[0]

config = default_config

# Read the appropriate configuration fields based on the service provider
provider = config.get('provider', '').upper()

if 'TUZI' in provider:
    # TUZI API, an OpenAI-compatible interface
    api_key = config.get('api_key')  # Required
    endpoint_url = config.get('endpoint_url', 'https://api.tu-zi.com/v1')  # Required
    # Use the OpenAI SDK to call the API
elif '火山引擎' in provider or '即梦' in config.get('function_name', ''):
    # Volcengine Jimeng API
    access_key_id = config.get('access_key_id')  # Required
    secret_access_key = config.get('secret_access_key')  # Required
    region = config.get('region', 'cn-beijing')
    service = config.get('service', 'cv')
    api_version = config.get('api_version', 'jimeng_t2i_v31')
    sdk_name = config.get('sdk_name', 'volcenginesdkcv20240606')
    # Use the Volcengine SDK to call the API

**Generation flow:**
1. **Confirm the MCP**: confirm the HAP application MCP provided or specified by the user
2. **Read the account persona**: read the account persona configuration for the relevant platform from the HAP "Account Persona" table
3. **Obtain the image style**: extract `image_generation_prompt` from the account persona
4. **Dynamically read the configurations**: query all image generation configurations from the HAP "API Service Configuration" table
5. **Select the configuration**:
   - Prioritize `is_default = 1`
   - If no default configuration exists, use the first enabled configuration
6. **Extract the credentials**: read the appropriate credential fields based on the service provider
   - TUZI API: `api_key`, `endpoint_url`
   - Volcengine Jimeng: `access_key_id`, `secret_access_key`, `region`, `service`, and other fields
7. **Generate the prompt**: combine the account persona's image style prompt with the specific image suggestion to create a complete image generation prompt
   - Format: `{image_generation_prompt}, {specific image content description}`
   - Example: `hand-drawn illustration style, fresh and lively cartoon illustration style, {specific image content}`
8. **Call the API to generate images**:
   - **TUZI API**: use the OpenAI SDK and support multiple models, including gemini-3-pro-image-preview, dall-e-3, and dall-e-2
     - **The `response_format="url"` parameter must be used** to ensure the API returns a URL rather than base64
     - **Request parameters**: `model`, `prompt`, `n=1`, `response_format="url"`, and `size="{width}x{height}"`
   - **Volcengine Jimeng**: use the Volcengine SDK
   - **Parallel generation**: use a thread pool to generate multiple images in parallel, with up to 3 concurrent requests, to significantly improve generation speed
   - **Automatically skip existing files**: check whether the local file already exists and skip generation if it does, saving time and cost
9. **Process the API response**:
   - **Prioritize URLs**: if the API returns an HTTP/HTTPS URL, use it directly
   - **Handle base64 data**: if the API returns base64 data, either as a data URI or a base64 string, automatically decode and save it as an image file
   - **Error handling**: if the API returns invalid data, log the error and continue generating the other images
10. **Save the images**:
    - **Save the image URLs**: save the URLs to `配图/image_urls.json`; do not save base64 data
    - **Automatically download the images**: download the image files from the URLs to `配图/{image_name}.png` for convenient local viewing and display
    - **Image file naming**: names such as `封面图.png`, `对比图.png`, `流程图.png`, and `应用场景图.png`
    - **Download failure handling**: if a download fails, retain the URL and log a warning without interrupting the remaining workflow
11. **Upload to HAP**:
    - **Xiaohongshu notes**: upload only the image URLs, including the cover image and other images, to the HAP attachment fields; do not upload the Markdown document
    - **Other platforms**: upload images and documents according to platform requirements
    - **Use URLs when uploading**: upload image URLs to HAP; base64 data is not required

**Image format requirements for Xiaohongshu:**
- **Dimensions**: 768x1024, the vertical 3:4 Xiaohongshu format
- **Style**: hand-drawn illustration in a fresh and lively cartoon style
- **Content requirements**: image content must be strongly related to the body content and communicate its core meaning, such as a process, introduction, or comparison

**Image types (must follow the account persona):**
- **Cover image**: combine the account persona's image style prompt, specific content description, and **cover title text**
  - The cover image must contain the cover title, using a bold decorative font with strokes and gradient effects
  - The title must be prominent, occupy an important position on the cover, and comply with Xiaohongshu cover design standards
- **Comparison image**: combine the account persona's image style prompt with a comparison description strongly related to the content
- **Flowchart**: combine the account persona's image style prompt with a process description strongly related to the content
- **Use-case image**: combine the account persona's image style prompt with a use-case description strongly related to the content

**Hand-drawn illustration characteristics (reference):**
- **Overall style**: a fresh and lively cartoon illustration style full of positive energy and vitality
- **Lines**: thick black outlines, a hand-drawn texture, and smooth, natural strokes
- **Colors**: bright, saturated colors such as orange, yellow, blue, green, and red, with harmonious warm-tone combinations
- **Rendering**: primarily flat design, enhanced with simple gradients and highlights to add depth
- **Typography**: bold decorative fonts with strokes and gradient effects
- **Atmosphere**: positive, energetic, technology-oriented, warm, and cute
- **Design philosophy**: concise and lively, with strong visual impact and suitability for digital media distribution

**Important**:
- Image suggestions must be generated by combining the account persona's `image_generation_prompt`
- Image content must be strongly related to the body content and communicate its core meaning, such as a process, introduction, or comparison
- The cover image must contain the cover title text
- Image formats must comply with platform requirements, such as 768x1024 and 3:4 for Xiaohongshu

**Image prompt generation rules:**
1. Read `image_generation_prompt` from the HAP "Account Persona" table
2. Combine the style prompt with the specific image content description
3. **Format**: `{image_generation_prompt}, {specific image content description that is strongly related to the content}`
4. **Special cover image requirements**: the cover image must contain the cover title text
   - Format: `{image_generation_prompt}, cover image content: {specific content description}, title text: "{cover title}", using a bold decorative font with strokes and gradient effects`
5. **Example (cover image)**:
   - Account persona style: `Create a hand-drawn illustration with the following characteristics: overall style: a fresh and lively cartoon illustration style full of positive energy and vitality...`
   - Specific image content: `Show the core concept of what agentic is, with a cute brain icon in the center and multiple small robots or execution arrows around it to represent autonomous planning and execution capabilities`
   - Cover title: `Understand agentic AI in 3 minutes!`
   - Final prompt: `{image_generation_prompt}, cover image content: Show the core concept of what agentic is, with a cute brain icon in the center and multiple small robots or execution arrows around it to represent autonomous planning and execution capabilities. A prominent decorative title reading "Understand agentic AI in 3 minutes!" appears at the top, using a bold decorative font with strokes and gradient effects to enhance visual impact. The title must be prominent, occupy an important position on the cover, and comply with Xiaohongshu cover design standards.`
6. **Example (comparison image)**:
   - Account persona style: `Create a hand-drawn illustration with the following characteristics...`
   - Specific image content: `Use a left-right split-screen comparison. The left side shows traditional AI as a simple question-answering machine that can only respond passively, with question marks. The right side shows agentic AI as an intelligent assistant autonomously planning tasks and executing actions, with execution arrows and task cards. Connect the two sides with a thick arrow to represent the transition from passive response to proactive execution. The overall image should be clear and easy to understand, with a distinct color contrast.`
   - Final prompt: `{image_generation_prompt}, {specific image content description}`

1. Search for material through the Tavily API → obtain the latest information
2. Generate content → save it to a local file for preview, using the note directory structure: 内容/{platform}/{note_title}/{note_title}.md
3. Confirm the content, titles, and images with the user
4. After user confirmation, generate images → save them in the note's image directory: 内容/{platform}/{note_title}/配图/
5. Confirm whether to publish and synchronize
6. After user confirmation, synchronize to HAP:
   - **Xiaohongshu notes**: upload only the image URLs, including the cover image and other images; do not upload the Markdown document
   - **Other platforms**: upload images and documents according to platform requirements
7. After user confirmation, publish → use Playwright to publish to the target platform
8. After successful publication → update the publishing status and note URL

Directory structure notes:
- 内容/: root directory
- 内容/{platform}/: platform directory, including 小红书/抖音/微信公众号/视频号
- 内容/{platform}/{note_title}/: note directory, using the cover title as the directory name
- 内容/{platform}/{note_title}/{note_title}.md: Markdown document, stored locally only and not synchronized to HAP for Xiaohongshu
- 内容/{platform}/{note_title}/配图/: image directory

Important notes:
- **Markdown documents for Xiaohongshu notes are not synchronized to HAP**; only image URLs are synchronized
- Markdown documents are stored locally only for previewing and editing
- After image generation:
  1. Save the image URLs to 配图/image_urls.json
  2. **Download the images locally**: save the image files to 配图/{image_name}.png, such as 封面图.png or 对比图.png, for convenient local viewing and display
  3. Upload the URLs to HAP through MCP; use the URLs rather than base64 data when uploading

// 1. Navigate to the publishing page
await page.goto('https://creator.xiaohongshu.com/publish/publish?type=image_text');

// 2. Upload the images
const fileInput = await page.locator('input[type="file"]').first();
await fileInput.setInputFiles(imageFiles);

// 3. Enter the title
await page.getByRole('textbox', { name: '填写标题会有更多赞哦～' }).fill(title);

// 4. Enter the body, including hashtags
await page.getByRole('textbox').nth(1).fill(content + '\n\n' + tags);

// 5. Click Publish
await page.getByRole('button', { name: '发布' }).click();

// 6. Wait for successful publication and obtain the note URL
// 7. Update the HAP record: publishing status, publishing time, and note URL

User: Generate a Xiaohongshu note about "An introduction to Skills" and publish it

Execution flow:
1. **Confirm the MCP**: confirm the currently connected HAP application MCP through the user-provided or user-specified configuration
2. **Read the search configuration**: read the Tavily search API configuration from the HAP "API Service Configuration" table
3. **Search for material**: call the Tavily API to retrieve the 5 latest results related to the topic
4. **【MANDATORY】Read the account persona** before generating content: read the account persona configuration from the HAP "Account Persona" table
   - **Local files are prohibited**: never use AGENTS.md or any other local file
   - **HAP MCP must be called**: use MCP to call get_record_list() to read from the HAP "Account Persona" table
   - **Read all required fields**:
     - **Account positioning** (positioning): understand the account's core positioning
     - **Target audience** (target_audience): understand the audience for whom the content is intended
     - **Content direction** (content_direction): understand the account's main content areas
     - **Content style** (content_style): understand the style to use; it must be strictly followed
     - **Content principles** (content_principles): understand the principles and considerations for content creation; they must be strictly observed
     - **Image generation prompt** (image_generation_prompt): understand the image style requirements
   - **Validation requirement**: if no account persona configuration is found, throw an exception and do not continue content generation
5. **Write the content**: write the content based on the search results and the account persona read from HAP
   - **Strictly follow the account persona**: write strictly according to content_style and content_principles read from HAP
   - **Local personas are prohibited**: do not reference or use content from the local AGENTS.md file
   - **Combine the search material**: combine the retrieved material with the account persona read from HAP to generate content aligned with the positioning
   - **Suit the target audience**: ensure the content is suitable for the target audience
6. **Generate cover titles**: generate 5–10 cover titles according to the account persona's content style
   - The title style must comply with the account persona's content style
   - Titles must match the account positioning and target audience
7. **Select hashtags**: select 5–8 hashtags from the HAP Hashtag Library through dynamic queries
   - Select them according to the content topic and the account persona's content direction
8. **Generate image suggestions**: combine the account persona's image generation prompt style with the content topic to generate image suggestions
9. **Save the preview**: save it to a local file using the note directory structure: 内容/小红书/{note_title}/{note_title}.md
10. **Confirm with the user**: confirm the content, titles, and images
11. **Generate images after user confirmation**: read the image generation prompt from the HAP "Account Persona" table, read the image generation configuration from the HAP "API Service Configuration" table, and generate the images
12. **Confirm publication**: ask whether to publish directly to Xiaohongshu
13. **Confirm synchronization**: ask whether to synchronize the content to HAP, and upload only after confirmation
14. **Synchronize to HAP after user confirmation**: synchronize it to the HAP "Content Management" table with platform_type = 小红书
    - **Upload only images**: upload the cover image and other image URLs to HAP
    - **Do not upload the Markdown document**: do not synchronize the Xiaohongshu note's Markdown document to HAP
15. **Publish the content after user confirmation**: use Playwright to publish to Xiaohongshu
16. **Update the status**: update the HAP publishing status and content URL

User: Generate a week of Xiaohongshu notes, 7 posts in total, with these topics:
1. New Claude Code features
2. Recommended AI tools
3. Large-model application scenarios
...

Execution flow:
1. **Confirm the MCP**: confirm the currently connected HAP application MCP
2. **Batch generation**: repeat the preceding workflow for each topic
3. **Dynamically read the configuration**: read the image generation configuration from the HAP "API Service Configuration" table whenever images are generated
4. **Save in bulk**: generate the content in bulk and save it to the HAP "Content Management" table with platform_type = 小红书

User: Publish this note to both Xiaohongshu and WeChat Official Account

Execution flow:
1. **Confirm the MCP**: confirm the currently connected HAP application MCP
2. **Read the content**: read the content from the HAP "Content Management" table with platform_type = 小红书
3. **Dynamically obtain the worksheet**: dynamically obtain the ID and field structure of the "Content Management" table
4. **Adapt the format**: adapt the content to the format requirements of each platform:
   - Xiaohongshu: 300–400 Chinese characters and 5–8 hashtags
   - WeChat Official Account: 2,000–5,000 Chinese characters in HTML format
5. **Publish the content**: publish it separately to both platforms
6. **Update HAP**: create a new record in the HAP "Content Management" table with platform_type = 微信公众号, or update the existing record's publishing status

social-media-operation/
├── AGENTS.md                    # Account persona configuration (optional local reference file)
├── 笔记生成工作流.md            # Workflow documentation
├── 内容/                        # Content root directory
│   └── 小红书/                  # Platform categories: 小红书/抖音/微信公众号/视频号
│       └── {note_title}/        # One directory per note, using the cover title as the directory name
│           ├── {note_title}.md    # Markdown document, named after the note title
│           └── 配图/            # Image directory
│               ├── 封面图.png
│               ├── 架构图.png
│               └── 应用场景图.png
├── 话题库/                      # Hashtag library (optional local reference file)
│   └── {type}.md
└── README.md                    # Project documentation

Directory structure notes:
- 内容/: root directory containing content for all platforms
- 小红书/: platform directory containing all note titles for that platform
- {note_title}/: note directory using the note title as the directory name for greater clarity
- {note_title}.md: Markdown document named after the note title
- 配图/: image directory containing all images for the note

Example:
内容/
  └── 小红书/
      └── 什么是 MCP？/           # Note title used as the directory name
          ├── MCP科普介绍.md      # Markdown document
          └── 配图/
              ├── 封面图.png
              ├── 架构图.png
              └── 应用场景图.png

Notes:
- Account persona and Hashtag Library data are stored uniformly in HAP
- Local files are provided only as references; actual usage reads from HAP tables
- Content is organized by note directory, with each note containing an md document and images
- Directory names use note titles for greater clarity