157 lines
5.2 KiB
Markdown
157 lines
5.2 KiB
Markdown
# Visual System
|
||
|
||
## Source State
|
||
|
||
This file adapts the accepted visual base from `2026-06-29-搭上AI这条船` to the new prequel deck `2026-07-01-为什么是我们`.
|
||
|
||
Status:
|
||
|
||
- Validation-stage visual system.
|
||
- P01 is the cover sample.
|
||
- P10 is the first content anchor sample.
|
||
|
||
Primary source files:
|
||
|
||
- `../intake/阶段5：P1-P22 单页设计骨架.md`
|
||
- `../intake/阶段3：PPT 总纲 v1.md`
|
||
- `../intake/阶段4：通用表达与视觉系统.md`
|
||
|
||
Style continuity references:
|
||
|
||
- `../../2026-06-29-搭上AI这条船/visual-system/visual-system.md`
|
||
- `../../2026-06-29-搭上AI这条船/visual-system/style/style-prompt-master.md`
|
||
- accepted old images `s01-v1-image.png` and `s10-v1-image.png`
|
||
|
||
Backup fact-check source only:
|
||
|
||
```text
|
||
C:\Users\wangq\Documents\Codex\knowledge-vault\work\internal\OPC销售\为什么是我们.md
|
||
```
|
||
|
||
Do not use the backup source to rewrite the deck structure.
|
||
|
||
## Current Visual Definition
|
||
|
||
> 深蓝黑商务底 + AI 航线作战图 + 深水区剖面 + 雷达 / 罗盘 / 工具箱 / 工厂 / 模具师 / 销售武器库母题 + 青色与金色信号高亮。
|
||
|
||
Working visual sentence:
|
||
|
||
> 这不是一张重新动员大家上船的图，而是一张进入 AI 深水区前的市场判断和销售作战图。
|
||
|
||
Continuity rule:
|
||
|
||
> 保留上一套的深蓝黑 AI 航线底板和青金高亮，但情绪从“兴奋上船”切换为“硬判断、深水区、证据链、销售立场”。
|
||
|
||
## Deck Tone
|
||
|
||
The tone should hold four feelings:
|
||
|
||
1. 清醒：承认平台强，也承认普通 AI 开发公司存在。
|
||
2. 坚定：我们的定位不是平台、不是外包，而是专家能力工程化。
|
||
3. 专业：敢于说简单 AI 客户自己做，复杂专家智能体才是我们的场。
|
||
4. 行动：差异最终要沉淀成销售武器库。
|
||
|
||
Language direction:
|
||
|
||
> 自己人口吻 + 公司化判断 + 战前校准感。
|
||
|
||
Avoid turning it into:
|
||
|
||
- customer-facing proposal;
|
||
- founder biography deck;
|
||
- AI trend lecture;
|
||
- dense internal manual;
|
||
- another copy of the previous kickoff deck.
|
||
|
||
## Format Rules
|
||
|
||
- Output page: 16:9 full-page visual image.
|
||
- Page text may be embedded in the image.
|
||
- Minor small-text defects are acceptable for validation, but the page title and core judgment must be readable.
|
||
- Each page keeps one big judgment, one core visual model, and three to five short support labels.
|
||
- Do not copy long source paragraphs into images.
|
||
- If image text fails but the visual base is strong, later PPT assembly may use text overlays.
|
||
|
||
## Palette
|
||
|
||
Base:
|
||
|
||
- deep navy-black;
|
||
- dark ocean blue;
|
||
- cold slate gray;
|
||
- near-black executive background.
|
||
|
||
Signal:
|
||
|
||
- cyan / blue-green for AI signals, route lines, radar, active judgment paths;
|
||
- restrained gold / warm amber for key commitments, evidence, positioning, and sales confidence;
|
||
- white / pale blue for readable titles.
|
||
|
||
Avoid:
|
||
|
||
- bright cyberpunk neon;
|
||
- government red-gold;
|
||
- cheerful training-course pastel;
|
||
- clean white SaaS proposal style;
|
||
- luxury black-gold with no route-map logic.
|
||
|
||
## Page Families
|
||
|
||
| Family | Pages | Function | Primary Motifs |
|
||
| --- | --- | --- | --- |
|
||
| A Opening / Problem | P01-P03 | Establish why this deck exists and the three sales questions. | deepwater route, radar targets, question gates |
|
||
| B Market Contrast | P04-P07 | Acknowledge platforms and define the first boundary. | toolbox, factory, mold, shallow vs deep water |
|
||
| C Our Positioning | P08-P12 | Define expert agents and our role. | digital employee card, expert capability mold, engineering cutaway |
|
||
| D Customer Choice | P13-P18 | Explain why customers choose us. | decision compass, three-line crossing, iceberg, validation route, calibration loop |
|
||
| E Sober Judgment | P19-P21 | Show the difference is real but must be proved. | evidence chain, lighthouse pillars, maturity dashboard |
|
||
| F Sales Arsenal | P22 | Turn positioning into reusable sales tools. | arsenal wall, navigation map, proof layer, action layer |
|
||
|
||
## Text Rendering Policy
|
||
|
||
- Prefer short Chinese labels of 2-8 characters.
|
||
- Use page title + one core judgment + 3-5 short labels.
|
||
- Avoid long sentence clusters inside diagrams.
|
||
- Do not overfill P10 with every phrase from the source. P10 must focus on:
|
||
- 专家能力;
|
||
- 抽取;
|
||
- 封装;
|
||
- 验证;
|
||
- 校准;
|
||
- 进入真实流程.
|
||
|
||
## Forbidden Drift
|
||
|
||
Avoid:
|
||
|
||
- platform-bashing;
|
||
- developer-company-bashing;
|
||
- claiming we can do all AI;
|
||
- generic humanoid robots;
|
||
- literal cute ships;
|
||
- pirate / fantasy ship;
|
||
- stock meeting photos;
|
||
- customer proposal deck;
|
||
- dense dashboard UI;
|
||
- unrelated futuristic city;
|
||
- large blocks of copied source material.
|
||
|
||
## Validation Questions
|
||
|
||
For P01:
|
||
|
||
1. Does the page feel like the prequel to the previous deck, not a duplicate?
|
||
2. Does “AI 深水区 / 为什么是我们” read before decoration?
|
||
3. Is the cover harder and more sober than the kickoff deck?
|
||
|
||
For P10:
|
||
|
||
1. Does the page make our positioning clear without needing a long explanation?
|
||
2. Can sales take away “专家能力工程化” as the first read?
|
||
3. Does the visual model show extraction, molding, validation, calibration, and workflow entry?
|
||
|
||
## Sample Adjustment Rule
|
||
|
||
- Common base problem: update this file and `visual-system/style/style-prompt-master.md`.
|
||
- Page-specific issue: update only the relevant `slides/sNN/sNN-vN-*` artifacts.
|
||
- Use append-only versions for repairs.
|