Merge branch 'main' of ssh://192.168.3.17:2222/ishenwei/nexus
This commit is contained in:
182
Hermes/xingzhi/major-incident-infographic-prompts-2026-04-20.md
Normal file
182
Hermes/xingzhi/major-incident-infographic-prompts-2026-04-20.md
Normal file
@@ -0,0 +1,182 @@
|
||||
# Major Incident Definition - Infographic Prompts
|
||||
# Generated: 2026-04-20
|
||||
# Layout: Venn Diagram
|
||||
# Style: Cyberpunk Neon
|
||||
# Aspect: 16:9
|
||||
# Language: English
|
||||
|
||||
---
|
||||
|
||||
## Part 1: System Prompt (Image Specifications + Core Principles)
|
||||
|
||||
Create a professional infographic following these specifications:
|
||||
|
||||
**Image Specifications**
|
||||
|
||||
- **Type**: Infographic
|
||||
- **Layout**: Venn Diagram (venn-diagram)
|
||||
- **Style**: Cyberpunk Neon
|
||||
- **Aspect Ratio**: 16:9
|
||||
- **Language**: English
|
||||
|
||||
**Core Principles**
|
||||
|
||||
- Follow the layout structure precisely for information architecture
|
||||
- Apply style aesthetics consistently throughout
|
||||
- If content involves sensitive or copyrighted figures, create stylistically similar alternatives
|
||||
- Keep information concise, highlight keywords and core concepts
|
||||
- Use ample whitespace for visual clarity
|
||||
- Maintain clear visual hierarchy
|
||||
|
||||
**Text Requirements**
|
||||
|
||||
- All text must match the specified style treatment
|
||||
- Main titles should be prominent and readable
|
||||
- Key concepts should be visually emphasized
|
||||
- Labels should be clear and appropriately sized
|
||||
- Use English for all text content
|
||||
|
||||
---
|
||||
|
||||
## Part 2: Style Lock Prompt (Layout Guidelines + Style Guidelines)
|
||||
|
||||
### Layout Guidelines (Venn Diagram)
|
||||
|
||||
**Structure**: Three overlapping circles forming a central intersection area
|
||||
|
||||
**Visual Elements**:
|
||||
|
||||
- Three large overlapping circles representing different categories of Major Incident
|
||||
- Central intersection zone highlighting the combined criteria
|
||||
- Each circle contains key concepts specific to its category
|
||||
- Outer labels for each circle region
|
||||
- Connection lines from concepts to their respective regions
|
||||
- Minimal text, emphasize visual grouping
|
||||
|
||||
**Composition**:
|
||||
|
||||
- Canvas divided into three equal sections for each circle
|
||||
- 30-40% overlap area in center for intersection
|
||||
- Ample negative space between elements
|
||||
- Clear visual boundaries between overlapping regions
|
||||
|
||||
### Style Guidelines (Cyberpunk Neon)
|
||||
|
||||
**Color Palette**:
|
||||
|
||||
- Primary: Neon pink (#FF00FF), cyan (#00FFFF), electric blue
|
||||
- Background: Deep black (#0A0A0A), dark purple gradients
|
||||
- Accents: Neon glow effects, chrome reflections
|
||||
|
||||
**Visual Elements**:
|
||||
|
||||
- Glowing neon outlines on all circle boundaries
|
||||
- Dark atmospheric backgrounds with subtle grid patterns
|
||||
- Digital glitch effects on text
|
||||
- Circuit patterns along connection lines
|
||||
- Holographic elements in intersection zone
|
||||
- Rain and reflections on edges
|
||||
|
||||
**Typography**:
|
||||
|
||||
- Glowing neon text (cyan for primary labels, pink for emphasis)
|
||||
- Digital/tech monospace fonts
|
||||
- Subtle flickering effects on key terms
|
||||
- Outlined glow letters for main title
|
||||
- All caps for section headers
|
||||
|
||||
**Effects**:
|
||||
|
||||
- Neon glow (2-3px bloom) around all text and shapes
|
||||
- Gradient fills with 40-60% opacity
|
||||
- Scanline overlay at 10% opacity
|
||||
- Chromatic aberration on text edges
|
||||
|
||||
---
|
||||
|
||||
## Part 3: Content Structure Prompt (Text Requirements + Content)
|
||||
|
||||
### Main Title
|
||||
|
||||
**MAJOR INCIDENT DEFINITION**
|
||||
*Highest Severity Level (S1/P1/Critical)*
|
||||
|
||||
### Three Venn Circles Content
|
||||
|
||||
**Circle 1: Business Impact**
|
||||
|
||||
- Total Service Outage
|
||||
- Critical Feature Failure
|
||||
- Data Corruption/Loss
|
||||
- Security Breach
|
||||
- Regulatory Compliance Risk
|
||||
- High-Impact SLA Breach
|
||||
|
||||
**Circle 2: Incident Response**
|
||||
|
||||
- Immediate Actions (0-15 min)
|
||||
- Automated Monitoring Alerts
|
||||
- Incident Commander Assigned
|
||||
- Major Incident Bridge
|
||||
- Customer Communication
|
||||
- Investigation & Mitigation (15-60 min)
|
||||
- Root Cause Analysis
|
||||
- Rollback/Hotfix
|
||||
- Failover to Backup
|
||||
- Workarounds
|
||||
- Recovery & Post-Mortem (1-24h+)
|
||||
- Full Service Restored
|
||||
- RCA Report Published
|
||||
- Long-Term Fixes
|
||||
|
||||
**Circle 3: Prevention Measures**
|
||||
|
||||
- High Availability Architecture
|
||||
- Chaos Engineering & Load Testing
|
||||
- Real-Time Monitoring & Alerting
|
||||
- Automated Rollbacks
|
||||
- Strict Change Management
|
||||
- Security Hardening & Compliance
|
||||
|
||||
### Central Intersection (All Three Circles)
|
||||
|
||||
The intersection represents the critical overlap showing that Major Incidents require:
|
||||
|
||||
- Cross-team collaboration
|
||||
- Immediate response (15-30 min SLA)
|
||||
- Significant business impact
|
||||
- Coordinated resolution
|
||||
|
||||
### Key Criteria Table (Bottom Section)
|
||||
|
||||
| Criteria | Description |
|
||||
|----------|-------------|
|
||||
| Scope | Multiple tenants/customers, entire platform |
|
||||
| Business Criticality | Severe financial/reputational impact |
|
||||
| Resolution Time | Immediate, 15-30 min acknowledgment |
|
||||
| Workload Impact | Cloud Ops, DevOps, Security, Support |
|
||||
| Regulatory Compliance | Legal/security obligations at risk |
|
||||
|
||||
### Footer Text
|
||||
|
||||
"Requires Swift, Coordinated Response to Minimize Downtime"
|
||||
|
||||
---
|
||||
|
||||
## Visual Composition for 16:9
|
||||
|
||||
- **Top Section** (10%): Title with neon glow effect
|
||||
- **Middle Section** (70%): Three overlapping circles with content
|
||||
- **Bottom Section** (20%): Criteria table in minimalist style
|
||||
|
||||
### Color Assignment per Circle
|
||||
|
||||
- Circle 1 (Business Impact): Cyan (#00FFFF) neon outline
|
||||
- Circle 2 (Incident Response): Neon Pink (#FF00FF) neon outline
|
||||
- Circle 3 (Prevention): Electric Blue (#0080FF) neon outline
|
||||
- Intersection: White glow with purple tint
|
||||
- Background: Deep black (#0A0A0A) with dark purple gradient
|
||||
|
||||
---
|
||||
|
||||
**Note**: Do not generate the actual image. Output only the prompt for image generation.
|
||||
@@ -0,0 +1,256 @@
|
||||
# Wiki Sync 循环流程信息图 - 提示词
|
||||
|
||||
> 日期:2026-04-20
|
||||
> 布局:circular-flow
|
||||
> 风格:chalkboard
|
||||
|
||||
---
|
||||
|
||||
## 一、系统提示词
|
||||
|
||||
```
|
||||
Create a professional infographic following these specifications:
|
||||
|
||||
## Image Specifications
|
||||
|
||||
- **Type**: Infographic
|
||||
- **Layout**: circular-flow
|
||||
- **Style**: chalkboard
|
||||
- **Aspect Ratio**: 16:9 (landscape)
|
||||
- **Language**: 中文 (Simplified Chinese)
|
||||
|
||||
## Core Principles
|
||||
|
||||
- Follow the layout structure precisely for information architecture
|
||||
- Apply style aesthetics consistently throughout
|
||||
- If content involves sensitive or copyrighted figures, create stylistically similar alternatives
|
||||
- Keep information concise, highlight keywords and core concepts
|
||||
- Use ample whitespace for visual clarity
|
||||
- Maintain clear visual hierarchy
|
||||
|
||||
## Text Requirements
|
||||
|
||||
- All text must match the specified style treatment
|
||||
- Main titles should be prominent and readable
|
||||
- Key concepts should be visually emphasized
|
||||
- Labels should be clear and appropriately sized
|
||||
- Use Chinese for all text content
|
||||
|
||||
## Layout Guidelines
|
||||
|
||||
### Circular Flow Layout
|
||||
- 循环流程:展示持续运行的过程
|
||||
- 环形排列:所有节点围绕中心点均布
|
||||
- 方向箭头:显示顺时针或逆时针流动方向
|
||||
- 无明确起点/终点(持续循环)
|
||||
- 中心可放置核心概念或系统名称
|
||||
|
||||
### Wiki Sync 循环结构
|
||||
1. 9个步骤节点均匀分布在圆环上
|
||||
2. 循环箭头连接各步骤
|
||||
3. 中心显示 "Wiki Sync" 系统名称
|
||||
4. 标题位于圆环上方
|
||||
|
||||
## Style Guidelines
|
||||
|
||||
### Chalkboard Style
|
||||
- 背景:黑板黑 (#1A1A1A) 或深绿黑板色 (#1C2B1C)
|
||||
- 纹理:真实黑板质感,伴有划痕、粉尘、橡皮擦痕迹
|
||||
- 线条:手绘粉笔质感,不完美的sketchy线条
|
||||
- 颜色:仅使用粉笔色板
|
||||
- 字体:手绘粉笔字体
|
||||
- 装饰:手绘星星、下划线、箭头、圆圈、问号
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 二、风格锁定提示词
|
||||
|
||||
```
|
||||
## Style Lock — 必须遵守
|
||||
|
||||
本信息图使用 chalkboard(粉笔黑板)风格。
|
||||
|
||||
### 背景
|
||||
- 颜色:#1C2B1C(深绿黑板)或 #1A1A1A(黑板黑)
|
||||
- 纹理:真实黑板纹理,细微划痕、粉尘粒子、橡皮擦痕迹
|
||||
- 木质框边(可选):手绘木纹线条
|
||||
|
||||
### 粉笔线条质量
|
||||
- 所有线条必须是手绘的、不完美的sketchy风格
|
||||
- 轻微抖动和歪斜
|
||||
- 不要干净的矢量线条
|
||||
|
||||
### 颜色色板(严格使用)
|
||||
| 角色 | 颜色 | Hex |
|
||||
|-----|------|-----|
|
||||
| 主文字/轮廓 | 粉笔白 | #F5F5F5 |
|
||||
| 高亮/下划线 | 粉笔黄 | #FFE566 |
|
||||
| 次要高亮 | 粉笔粉 | #FF9999 |
|
||||
| 技术元素/图表 | 粉笔蓝 | #66B3FF |
|
||||
| 成功/自然 | 粉笔绿 | #90EE90 |
|
||||
| 警告/能量 | 粉笔橙 | #FFB366 |
|
||||
| 木框 | 棕色 | #8B6914 |
|
||||
|
||||
### 装饰元素
|
||||
- 5-7角手绘星星(不规则)
|
||||
- 手绘波浪下划线
|
||||
- 手绘箭头(歪斜的笔触 + 箭头)
|
||||
- 角落的粉笔问号、圆圈
|
||||
- 底部散落的粉笔粉末
|
||||
|
||||
### 禁止出现
|
||||
- 渐变
|
||||
- 完美几何形状
|
||||
- 写实元素
|
||||
- 扁平数字图标
|
||||
|
||||
### 布局规则(circular-flow)
|
||||
- 9个节点均布于圆环上
|
||||
- 顺时针方向箭头连接各节点
|
||||
- 中心放置核心概念
|
||||
- 标题在圆环顶部
|
||||
|
||||
## Layout Guidelines - Circular Flow
|
||||
|
||||
### 环形结构
|
||||
- 步骤节点:9个步骤均匀分布在圆周上
|
||||
- 方向:顺时针流动的箭头
|
||||
- 中心:系统名称 "Wiki Sync"
|
||||
- 标题:信息图主标题在顶部
|
||||
|
||||
### 节点内容
|
||||
每个节点包含:
|
||||
- 步骤编号(圆形框)
|
||||
- 步骤名称(粉笔白大字)
|
||||
- 简要描述(1-2行,较小字体)
|
||||
- 对应图标或符号
|
||||
|
||||
### 节点顺序(Wiki Sync 流程)
|
||||
1. Cron 触发
|
||||
2. 加载 skill
|
||||
3. 启动 TMUX
|
||||
4. 启动 Claude Code
|
||||
5. 发送任务指令
|
||||
6. 执行 9 步 ingest
|
||||
7. 解析 SLUG
|
||||
8. 更新 manifest
|
||||
9. Telegram 通知
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 三、具体内容提示词
|
||||
|
||||
```
|
||||
INFOGRAPHIC: Wiki Sync 系统循环流程
|
||||
|
||||
## 主标题
|
||||
- 位置:圆环顶部居中
|
||||
- 内容:"Wiki Sync 自动同步系统"
|
||||
- 字体:大型粉笔白(#F5F5F5)手写体
|
||||
- 装饰:粉笔黄(#FFE566)双下划线(波浪形手绘)
|
||||
- 两侧:粉笔粉(#FF9999)小星星装饰
|
||||
|
||||
## 圆环中心
|
||||
- 圆形区域放置系统图标或 "WS" 字样
|
||||
- 颜色:粉笔蓝(#66B3FF)轮廓
|
||||
- 背景:深绿黑板色 #1C2B1C
|
||||
|
||||
## 循环节点(顺时针排列)
|
||||
|
||||
### 节点 1:Cron 触发
|
||||
- 编号圆圈:粉笔黄
|
||||
- 步骤名:① Cron 触发
|
||||
- 描述:定时器启动,每15分钟
|
||||
- 图标:时钟或定时器手绘
|
||||
|
||||
### 节点 2:加载 Skill
|
||||
- 编号圆圈:粉笔黄
|
||||
- 步骤名:② 加载 Skill
|
||||
- 描述:加载 llm-wiki-sync
|
||||
- 图标:齿轮或技能图标
|
||||
|
||||
### 节点 3:检查待摄
|
||||
- 编号圆圈:粉笔粉
|
||||
- 步骤名:③ 待摄检查
|
||||
- 描述:sync.py --check
|
||||
- 图标:文档或清单
|
||||
|
||||
### 节点 4:启动 TMUX
|
||||
- 编号圆圈:粉笔粉
|
||||
- 步骤名:④ 启动 TMUX
|
||||
- 描述:创建会话
|
||||
- 图标:终端图标
|
||||
|
||||
### 节点 5:Claude Code
|
||||
- 编号圆圈:粉笔蓝
|
||||
- 步骤名:⑤ Claude Code
|
||||
- 描述:bypassPermissions
|
||||
- 图标:AI/机器人
|
||||
|
||||
### 节点 6:执行 Ingest
|
||||
- 编号圆圈:粉笔蓝
|
||||
- 步骤名:执行 Ingest
|
||||
- 描述:9步标准流程
|
||||
- 图标:输入箭头
|
||||
|
||||
### 节点 7:解析 SLUG
|
||||
- 编号圆圈:粉笔绿
|
||||
- 步骤名:⑦ 解析 SLUG
|
||||
- 描述:从输出提取标识符
|
||||
- 图标:标签/条形码
|
||||
|
||||
### 节点 8:更新 Manifest
|
||||
- 编号圆圈:粉笔绿
|
||||
- 步骤名:更新 Manifest
|
||||
- 描述:写入 JSON 状态
|
||||
- 图标:数据保存
|
||||
|
||||
### 节点 9:Telegram 通知
|
||||
- 编号圆圈:粉笔橙
|
||||
- 步骤名: Telegram 通知
|
||||
- 描述:发送同步结果
|
||||
- 图标:消息气泡
|
||||
|
||||
## 循环箭头
|
||||
- 颜色:粉笔蓝(#66B3FF)
|
||||
- 风格:手绘歪斜箭头
|
||||
- 方向:顺时针
|
||||
- 每两个节点之间
|
||||
|
||||
## 底部装饰
|
||||
- 左侧:粉笔粉 "Claude Code Agent"
|
||||
- 右侧:粉笔黄 "持续运行 ∞"
|
||||
- 底部边缘:散落粉笔粉末痕迹
|
||||
- 角落:粉笔问号、圆圈装饰
|
||||
|
||||
## 整体效果
|
||||
- 深绿黑板背景 (#1C2B1C)
|
||||
- 所有文字使用粉笔质感手写体
|
||||
- 节点框使用手绘不规则圆形/圆角矩形
|
||||
- 箭头使用手绘歪斜线条
|
||||
- 保持信息密度,流程清晰
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 四、使用说明
|
||||
|
||||
```
|
||||
使用方法:
|
||||
|
||||
1. 使用支持 circular-flow 布局 + chalkboard 风格的 AI 图像生成工具
|
||||
2. 建议比例:16:9 (landscape)
|
||||
3. 语言:中文(简体)
|
||||
4. 参考本文件的三部分提示词组合使用
|
||||
|
||||
提示词组合优先级:
|
||||
1. 第一部分(系统提示词)- 基础规范
|
||||
2. 第二部分(风格锁定)- 必须遵守的约束
|
||||
3. 具体内容提示词 - 实际图像内容
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
*Generated: 2026-04-20*
|
||||
148
Hermes/xingzhi/wiki-sync-infographic-prompts-2026-04-20.md
Normal file
148
Hermes/xingzhi/wiki-sync-infographic-prompts-2026-04-20.md
Normal file
@@ -0,0 +1,148 @@
|
||||
# Wiki Sync 系统信息图提示词
|
||||
|
||||
> 生成日期:2026-04-20
|
||||
> 用途:为 LLM Wiki 自动化同步系统生成信息图
|
||||
|
||||
---
|
||||
|
||||
## 第一部分:系统提示词(System Prompt)
|
||||
|
||||
```
|
||||
Create a professional infographic following these specifications:
|
||||
|
||||
## Image Specifications
|
||||
- Type: Infographic
|
||||
- Layout: hub-spoke
|
||||
- Style: corporate-memphis
|
||||
- Aspect Ratio: 16:9
|
||||
- Language: 简体中文
|
||||
|
||||
## Core Principles
|
||||
- Follow the hub-spoke layout structure precisely for information architecture
|
||||
- Apply corporate-memphis style aesthetics consistently throughout
|
||||
- If content involves sensitive or copyrighted figures, create stylistically similar alternatives
|
||||
- Keep information concise, highlight keywords and core concepts
|
||||
- Use ample whitespace for visual clarity
|
||||
- Maintain clear visual hierarchy
|
||||
|
||||
## Text Requirements
|
||||
- All text must match the specified style treatment
|
||||
- Main titles should be prominent and readable
|
||||
- Key concepts should be visually emphasized
|
||||
- Labels should be clear and appropriately sized
|
||||
- Use simplified Chinese for all text content
|
||||
|
||||
## Layout Guidelines
|
||||
- Prominent central hub at the center of the canvas
|
||||
- Clear spoke lines radiating outward from center
|
||||
- Nodes at spoke ends with consistent styling
|
||||
- Even distribution of spokes around the hub
|
||||
- Icons representing each spoke item
|
||||
- Brief labels near each node
|
||||
|
||||
## Style Guidelines
|
||||
- Flat vector illustration style
|
||||
- Bright, saturated colors: purple, orange, teal, yellow
|
||||
- White or light pastel background
|
||||
- Disproportionate human figures (optional)
|
||||
- Abstract geometric shapes and floating elements
|
||||
- Solid fills without outlines
|
||||
- Clean sans-serif typography with bold headings
|
||||
- Professional but friendly appearance
|
||||
|
||||
---
|
||||
|
||||
Generate the infographic based on the content below:
|
||||
|
||||
Text labels (in 简体中文):
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 第二部分:风格锁定提示词(Style Lock Prompt)
|
||||
|
||||
```
|
||||
## 布局规范(hub-spoke)
|
||||
- 中心:突出显示核心主题"Wiki Sync 自动化同步系统"
|
||||
- 辐射:6条均匀分布的辐条连接中心与外圈节点
|
||||
- 节点:每个辐条末端放置一个组件节点,使用统一的图标风格
|
||||
- 连接:辐条使用浅灰色线条,带有标签
|
||||
|
||||
## 视觉元素(corporate-memphis)
|
||||
- 背景:纯白色或浅奶油色 (#FFF8F0)
|
||||
- 主色:明快的紫色 (#8B5CF6)、橙色 (#F97316)、青绿色 (#14B8A6)、黄色 (#FBBF24)
|
||||
- 图形:扁平化几何图形填充,无描边
|
||||
- 人物:抽象的不成比例人物剪影
|
||||
- 装饰:漂浮的几何元素(圆形、方形、三角形)
|
||||
- 字体:思源黑体或类似无衬线字体,标题加粗
|
||||
|
||||
## 图标风格
|
||||
- 简化的线框图标
|
||||
- 保持一致的线条粗细(2-3px)
|
||||
- 圆角处理
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 第三部分:具体内容提示词(Content Prompt)
|
||||
|
||||
```
|
||||
INFOGRAPHIC: Wiki Sync 自动化同步系统
|
||||
|
||||
使用 hub-spoke 布局和 corporate-memphis 风格创建信息图。
|
||||
|
||||
## 中心主题(Hub)
|
||||
- 主标题:Wiki Sync 系统
|
||||
- 副标题:LLM Wiki 自动化同步解决方案
|
||||
|
||||
## 六个辐条节点(Spokes)
|
||||
|
||||
### 1. 核心组件(Core)
|
||||
- 图标:齿轮/工具箱
|
||||
- 标签:sync.py CLI
|
||||
- 描述:manifest 管理、文件追踪
|
||||
|
||||
### 2. 工作流(Workflow)
|
||||
- 图标:流程图/箭头
|
||||
- 标签:llm-wiki-sync
|
||||
- 描述:9步标准化执行流程
|
||||
|
||||
### 3. 定时任务(Schedule)
|
||||
- 图标:时钟/日历
|
||||
- 标签:Cron Job
|
||||
- 描述:15分钟自动触发
|
||||
|
||||
### 4. 状态追踪(Tracking)
|
||||
- 图标:清单/勾选
|
||||
- 标签:manifest.json
|
||||
- 描述:181篇文件状态记录
|
||||
|
||||
### 5. 交互模式(Interaction)
|
||||
- 图标:终端/命令行
|
||||
- 标签:TMUX + Claude
|
||||
- 描述:bypassPermissions 启动
|
||||
|
||||
### 6. 交付通知(Delivery)
|
||||
- 图标:消息/ telegram
|
||||
- 标签:Telegram Bot
|
||||
- 描述:5038825565 消息推送
|
||||
|
||||
## 底部补充信息
|
||||
- 当前状态:已摄入 16 篇 / 待摄入 165 篇
|
||||
- 关键规则:顺序执行 + SLUG 解析
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 使用说明
|
||||
|
||||
1. 将 **第一部分** 作为系统提示词设置到图像生成模型会话开始时
|
||||
2. 将 **第二部分** 作为风格参考添加到提示词中
|
||||
3. 将 **第三部分** 作为具体内容提示词发送给图像生成模型
|
||||
4. 生成的图像应呈现:
|
||||
- 白色/浅奶油色背景
|
||||
- 中心为"Wiki Sync 系统"标题
|
||||
- 6个均匀分布的辐条节点
|
||||
- 明快的紫、橙、青、黄配色
|
||||
- 扁平化几何图标
|
||||
- 思源黑体加粗标题
|
||||
Reference in New Issue
Block a user