Handdrawn Route Map Card
Purpose
把城市、美食、旅行、生活清单或工作流，整理成小红书风格手绘收藏地图卡。
This is a lightweight standalone open Skill. It turns a repeated creator task
into a clear Agent workflow with inputs, checks, output shape, and boundaries.
Use This For
- content structure: title, subtitle, nodes, side box, bottom note
- image-generation brief
- quality checklist
- caption pattern when needed
- notes about verification if the map contains real places or current facts
Do Not Use This For
- automatic publishing
- private account login
- private data extraction
- guaranteed traffic, growth, sales, or viral outcomes
- copying another creator's exact wording, identity, images, or claims
- making claims that the user's material does not support
Inputs
- topic or route
- scene type: city food, travel itinerary, hiking, life checklist, or workflow manual
- 5-7 nodes, if known
- style preference
- whether the user wants image generation or just a brief
If the input is incomplete, proceed with a first-pass version and mark
assumptions. Ask only the smallest necessary follow-up when the missing detail
would materially change the result.
Workflow
Read references/workflow-rules.md when the task needs the full rule set.
- Classify the topic into a map card type.
- Build a 5-7 node route or checklist.
- Create side collage subjects, mini box, and bottom note.
- Avoid fake precise navigation, prices, hours, or official claims.
- Return a generation brief and quality checklist.
- If image generation is available, generate and review the file; otherwise return the brief.
Output Contract
## 1. Scope And Assumptions
## 2. Input Reading
## 3. Main Judgment
## 4. Working Table Or Checklist
## 5. Recommended Next Action
## 6. Boundaries
Quality Bar
- Be specific and operational.
- Prefer a small usable output over a broad lecture.
- Explain why each recommendation fits the user's material.
- Mark weak evidence instead of pretending certainty.
- Do not promise results.
- Do not copy another creator's protected expression or personal story.
Tone
Write in the user's language. For Chinese creator tasks, default to clear,
practical Chinese.
Public Boundary
Keep examples generic. Do not include internal thread IDs, private file paths,
unpublished customer material, private account data, or internal product notes.
1---2name: handdrawn-route-map-card-23description: Open Skill for turning a city, food, travel, hiking, life checklist, study plan, creator workflow, AI workflow, or SOP topic into a Xiaohongshu-style hand-drawn route-map card brief. Use when the user asks for handdrawn route map, Xiaohongshu map card, RedNote visual card, travel map brief, 手绘收藏地图, 小红书手绘地图, 手绘路线图, 美食地图. This Skill uses user-provided material and public-safe reasoning only; it does not publish automatically, scrape private data, copy creators, or promise growth.4---56# Handdrawn Route Map Card78## Purpose910把城市、美食、旅行、生活清单或工作流，整理成小红书风格手绘收藏地图卡。1112This is a lightweight standalone open Skill. It turns a repeated creator task13into a clear Agent workflow with inputs, checks, output shape, and boundaries.1415## Use This For1617- content structure: title, subtitle, nodes, side box, bottom note18- image-generation brief19- quality checklist20- caption pattern when needed21- notes about verification if the map contains real places or current facts2223## Do Not Use This For2425- automatic publishing26- private account login27- private data extraction28- guaranteed traffic, growth, sales, or viral outcomes29- copying another creator's exact wording, identity, images, or claims30- making claims that the user's material does not support3132## Inputs3334- topic or route35- scene type: city food, travel itinerary, hiking, life checklist, or workflow manual36- 5-7 nodes, if known37- style preference38- whether the user wants image generation or just a brief3940If the input is incomplete, proceed with a first-pass version and mark41assumptions. Ask only the smallest necessary follow-up when the missing detail42would materially change the result.4344## Workflow4546Read `references/workflow-rules.md` when the task needs the full rule set.4748- Classify the topic into a map card type.49- Build a 5-7 node route or checklist.50- Create side collage subjects, mini box, and bottom note.51- Avoid fake precise navigation, prices, hours, or official claims.52- Return a generation brief and quality checklist.53- If image generation is available, generate and review the file; otherwise return the brief.5455## Output Contract5657```markdown58## 1. Scope And Assumptions5960## 2. Input Reading6162## 3. Main Judgment6364## 4. Working Table Or Checklist6566## 5. Recommended Next Action6768## 6. Boundaries69```7071## Quality Bar7273- Be specific and operational.74- Prefer a small usable output over a broad lecture.75- Explain why each recommendation fits the user's material.76- Mark weak evidence instead of pretending certainty.77- Do not promise results.78- Do not copy another creator's protected expression or personal story.7980## Tone8182Write in the user's language. For Chinese creator tasks, default to clear,83practical Chinese.8485## Public Boundary8687Keep examples generic. Do not include internal thread IDs, private file paths,88unpublished customer material, private account data, or internal product notes.
atian-create