refactor(skills): make evolution themes and image counts dynamic and user-provided
This commit is contained in:
parent
bc552a7b36
commit
c6b1a034d8
@ -34,15 +34,7 @@ description: "生成 IT 基础设施系列连续风格 PNG 图片。适用于一
|
||||
- `prompts/image-prompts.md`
|
||||
- 每张图的主题、标题、副标题、结构块、关键词、生成提示词。
|
||||
|
||||
安全演进主题的固定 7 图序列为:
|
||||
|
||||
1. 单机权限
|
||||
2. 网络边界
|
||||
3. Web安全
|
||||
4. 云身份
|
||||
5. Zero Trust
|
||||
6. AI Agent 身份
|
||||
7. AI模型与知识保护
|
||||
主题或章节序列由用户动态输入指定。不要强加固定的章节数或主题(如固定的 7 阶段安全演进),应完全根据用户的实际需求或上下文输入进行推演和拆分。
|
||||
|
||||
## XWorkmate/OpenClaw 交付目录
|
||||
|
||||
@ -88,8 +80,7 @@ scope”,不要声称已经完成文件交付。
|
||||
|
||||
## 多图输出规则
|
||||
|
||||
- `count=N` 表示输出 `N` 个独立文件:`001-*.png`、`002-*.png` ... `N-*.png`。
|
||||
- 用户要求上述安全演进主线时,默认 `count=7`,每个阶段一张独立 PNG。
|
||||
- `count=N` 表示输出 `N` 个独立文件:`001-*.png`、`002-*.png` ... `N-*.png`。如果用户提供了明确的演进主线,则应按各个阶段分别输出。
|
||||
- 严禁把多个章节合成到一张 1024x1536 画布里。
|
||||
- 严禁输出 collage、contact sheet、grid、storyboard sheet、overview board、multi-panel batch preview。
|
||||
- 每张 PNG 内部可以有多个信息卡片,但只能围绕一个主题/章节。
|
||||
|
||||
@ -23,15 +23,7 @@ Final deliverables must stay inside the current XWorkmate/OpenClaw task artifact
|
||||
- `exports/final.pdf`
|
||||
- `DELIVERY.md`
|
||||
|
||||
For the security evolution scenario, preserve this seven-chapter sequence exactly:
|
||||
|
||||
1. 单机权限
|
||||
2. 网络边界
|
||||
3. Web安全
|
||||
4. 云身份
|
||||
5. Zero Trust
|
||||
6. AI Agent 身份
|
||||
7. AI模型与知识保护
|
||||
If the user specifies a particular content sequence or evolutionary path, ensure the exact sequence is preserved. Do not hardcode a fixed number of chapters unless requested.
|
||||
|
||||
## Phase 1: Plan
|
||||
|
||||
@ -69,7 +61,6 @@ the required image artifacts are missing.
|
||||
Required checks before continuing:
|
||||
|
||||
- PNG count equals chapter count.
|
||||
- For the security evolution scenario, PNG count must be exactly 7.
|
||||
- Every `assets/images/*.png` is a real non-empty PNG.
|
||||
- Every chapter image is a generated or user-provided bitmap image, not a text
|
||||
placeholder, blank rectangle, SVG prompt card, or decorative filler.
|
||||
|
||||
@ -1,13 +1,11 @@
|
||||
---
|
||||
name: security-evolution-social-copy-pack
|
||||
description: "围绕单机权限到 AI 模型与知识保护的安全演进主线,输出公众号、小红书、X、头条号等 Markdown 软文矩阵。"
|
||||
name: evolutionary-social-copy-pack
|
||||
description: "根据用户指定的任意演进主线,输出公众号、小红书、X、头条号等 Markdown 软文矩阵。"
|
||||
---
|
||||
|
||||
# Security Evolution Social Copy Pack Workflow
|
||||
|
||||
Use this workflow for content-pack requests around:
|
||||
|
||||
`从单机权限 → 网络边界 → Web安全 → 云身份 → Zero Trust → AI Agent 身份 → AI模型与知识保护`
|
||||
Use this workflow for content-pack requests around user-provided evolutionary paths or thematic series.
|
||||
|
||||
## Output Contract
|
||||
|
||||
@ -24,8 +22,8 @@ Do not combine the five outputs into one Markdown file. Each platform gets one s
|
||||
|
||||
## Writing Rules
|
||||
|
||||
- Keep the same core thesis across all files: security boundaries keep moving closer to identity, agents, models, and knowledge.
|
||||
- Weave in soft keywords naturally: `Zero Trust`, `AI Agent 身份`, `模型保护`, `知识资产保护`, `云身份`, `Web安全`.
|
||||
- Keep the same core thesis across all files based on the user-provided theme or sequence.
|
||||
- Weave in relevant soft keywords naturally depending on the theme context.
|
||||
- For Xiaohongshu, start with a strong hook and include 3-5 topic tags.
|
||||
- For X, write in English and keep every post under 144 characters.
|
||||
- Avoid fake citations and avoid claiming current news unless sources were collected in the same run.
|
||||
Loading…
Reference in New Issue
Block a user