328 lines
11 KiB
Markdown
328 lines
11 KiB
Markdown
# Style Prompt Master
|
||
|
||
## Status
|
||
|
||
- Document status: active public-style base.
|
||
- Project: `2026-06-29-搭上AI这条船`.
|
||
- Purpose: reusable style prompt master for later full-page PPT image prompts.
|
||
- Scope: global style kernel, page-family modules, text-in-image policy, reference roles, forbidden drift.
|
||
- Generation status: no image generation is authorized by this file.
|
||
|
||
This file defines what each page prompt should inherit. It does not replace per-page `sNN-vN-prompt.md` files.
|
||
|
||
Accepted continuity rule:
|
||
|
||
> Every page uses the same deep navy-black AI route operation-map base. Page families may vary motifs lightly, but not the base style.
|
||
|
||
## Skill Mode Record
|
||
|
||
Mode check command:
|
||
|
||
```powershell
|
||
node C:\Users\wangq\.agents\skills\gpt-image-2\scripts\check-mode.js --json
|
||
```
|
||
|
||
Result:
|
||
|
||
```json
|
||
{
|
||
"mode": "B-or-C",
|
||
"recommendation": "host-or-advisor",
|
||
"garden_mode_enabled": false,
|
||
"has_api_key": false,
|
||
"base_url": "https://api.openai.com/v1",
|
||
"model": "gpt-image-2",
|
||
"env_flag_value": "(unset)"
|
||
}
|
||
```
|
||
|
||
Interpretation:
|
||
|
||
- Use the `gpt-image-2` Skill as the prompt-engineering workflow.
|
||
- Garden local generation is not enabled.
|
||
- Do not call Garden generation scripts from this document.
|
||
- If later generation is requested, create or update the relevant per-page prompt/spec first, then follow the host-native image generation path.
|
||
|
||
## Skill Template / Reference Basis
|
||
|
||
Skill files read for this master:
|
||
|
||
- `C:\Users\wangq\.agents\skills\gpt-image-2\SKILL.md`
|
||
- `C:\Users\wangq\.agents\skills\gpt-image-2\references\prompt-writing.md`
|
||
- `C:\Users\wangq\.agents\skills\gpt-image-2\references\slides-and-visual-docs\dense-explainer-slides.md`
|
||
- `C:\Users\wangq\.agents\skills\gpt-image-2\references\slides-and-visual-docs\visual-report-page.md`
|
||
- `C:\Users\wangq\.agents\skills\gpt-image-2\references\slides-and-visual-docs\educational-diagram-slide.md`
|
||
- `C:\Users\wangq\.agents\skills\gpt-image-2\references\poster-and-campaigns\campaign-kv.md`
|
||
- `C:\Users\wangq\.agents\skills\gpt-image-2\references\typography-and-text-layout\title-safe-poster.md`
|
||
|
||
Template adaptation:
|
||
|
||
- `dense-explainer-slides.md` informs page-level structure and high-density one-page logic.
|
||
- `visual-report-page.md` informs business credibility and restrained executive visual language.
|
||
- `educational-diagram-slide.md` informs simple one-model explanation pages.
|
||
- `campaign-kv.md` informs consistent cross-page campaign-like visual identity.
|
||
- `title-safe-poster.md` informs large judgment text and readable slogan pages.
|
||
|
||
## Project Sources Actually Used
|
||
|
||
Project control:
|
||
|
||
- `project.md`
|
||
- `execution-plan.md`
|
||
- `visual-system/visual-system.md`
|
||
- `visual-system/motifs/motif-registry.md`
|
||
- `slides/slides.md`
|
||
|
||
Intake:
|
||
|
||
- `intake/阶段3：搭上 AI 这条船PPT总纲.md`
|
||
- `intake/阶段4：通用表达与视觉系统.md`
|
||
- `intake/阶段5：P1-P24 单页设计骨架.md`
|
||
- `intake/阶段5：全局页面规则.md`
|
||
- `intake/阶段5：页面清单骨架.md`
|
||
|
||
Backup source recorded but not compressed into the visual system:
|
||
|
||
```text
|
||
C:\Users\wangq\Documents\Codex\knowledge-vault\work\internal\OPC销售\AI智能化客户经营团队启动会议章程.md
|
||
```
|
||
|
||
## Global Style Kernel
|
||
|
||
Every page prompt should inherit this kernel unless a later approved revision changes the visual system.
|
||
|
||
Core visual definition:
|
||
|
||
> Deep navy-black executive background, AI maritime route map, radar glow, compass and boarding-ticket motifs, cyan and gold signal highlights, internal kickoff war-map energy.
|
||
|
||
Chinese working definition:
|
||
|
||
> 深蓝黑商务底，AI 航线作战图，雷达光效，罗盘与船票母题，青色和金色信号高亮，内部启动会的开局感。
|
||
|
||
Default prompt kernel:
|
||
|
||
```text
|
||
Create a 16:9 full-page visual slide image for an internal business kickoff meeting. Deep navy-black executive background, AI maritime route-map atmosphere, radar glow, compass lines, subtle grid and navigation marks, cyan signal light and restrained gold highlights. The page should feel like an AI boarding route / war map for a company team opening a new business line. High-energy but disciplined, cinematic business visual, not a customer proposal, not a training manual, not a generic SaaS dashboard.
|
||
```
|
||
|
||
Default text handling:
|
||
|
||
```text
|
||
Include only short, large, high-contrast Chinese slide text: one main title, one core judgment, and a few short labels if needed. Text may be embedded in the image. Prioritize bold readable Chinese characters over decorative typography. Avoid long paragraphs.
|
||
```
|
||
|
||
Default negative drift:
|
||
|
||
```text
|
||
Avoid government-report style, customer proposal deck, formal charter document, dense training manual, cute cartoon ship, pirate or fantasy ship, cyberpunk neon overload, generic tech dashboard UI, humanoid robots, stock-photo meeting people, concrete attendee portraits, childish illustration, pure gradient background, excessive UI cards, unreadable dense text, logos, watermarks.
|
||
```
|
||
|
||
## Page-Family Modules
|
||
|
||
### Module A: Opening / Consensus
|
||
|
||
Use for:
|
||
|
||
- P01-P03
|
||
|
||
Reusable prompt module:
|
||
|
||
```text
|
||
Opening and consensus page. Use a large dark AI航线 background, glowing route line, port lights, boarding-ticket or radar-center motif. The page should say: this is not another mobilization meeting; this is the moment the team boards together and turns the plan into shared consensus. Composition should be bold and ceremonial, but still internal and pragmatic.
|
||
```
|
||
|
||
Recommended motifs:
|
||
|
||
- Ship ticket.
|
||
- Route line.
|
||
- Radar center.
|
||
- Shared boarding point.
|
||
|
||
Avoid:
|
||
|
||
```text
|
||
No government opening ceremony, no customer sales brochure, no literal crowd photo, no cartoon ship, no overly formal seal-heavy layout.
|
||
```
|
||
|
||
### Module B: Pressure / Role Transition
|
||
|
||
Use for:
|
||
|
||
- P04-P07
|
||
|
||
Reusable prompt module:
|
||
|
||
```text
|
||
Pressure and transition page. Show old route pressure turning into a new AI route, or a single overloaded center node becoming a multi-engine navigation system. Use dark sea / port / route-map metaphors, with cyan active route and gold decision point. The emotion should be realistic pressure plus new opening, not pessimism.
|
||
```
|
||
|
||
Recommended motifs:
|
||
|
||
- Old route vs new AI route.
|
||
- Single engine to multi-engine fleet.
|
||
- Center node pressure to distributed route map.
|
||
|
||
Avoid:
|
||
|
||
```text
|
||
No collapse disaster scene, no personal portrait hero, no complaint mood, no over-dramatic storm.
|
||
```
|
||
|
||
### Module C: Confidence / Agentic Entry
|
||
|
||
Use for:
|
||
|
||
- P08-P12
|
||
|
||
Reusable prompt module:
|
||
|
||
```text
|
||
Confidence-building page for experienced salespeople entering the AI era. Use boarding ramp, lowered technical wall, radar reading customers, and AI work-loop motifs. The visual should communicate that old sales experience is not obsolete; it receives a new engine. Keep business confidence, not technical lecture.
|
||
```
|
||
|
||
Recommended motifs:
|
||
|
||
- Boarding ramp instead of high wall.
|
||
- Radar over customer-organization dots.
|
||
- Natural-language task chain.
|
||
- Before-meeting / after-meeting AI work loop.
|
||
|
||
Avoid:
|
||
|
||
```text
|
||
No programmer worship, no code walls, no robot teacher, no mocking traditional sales, no dense technical architecture.
|
||
```
|
||
|
||
### Module D: Business Path / Customer Judgment
|
||
|
||
Use for:
|
||
|
||
- P13-P17
|
||
|
||
Reusable prompt module:
|
||
|
||
```text
|
||
Business path and customer judgment page. Use a maritime route from "想用 AI" to "用好 AI", three-stage service route, funnel / lock gate, compass, and double-track exploration-to-engineering system. The page must feel like a practical navigation model that the team can use with clients.
|
||
```
|
||
|
||
Recommended motifs:
|
||
|
||
- Route map with nodes.
|
||
- Three-stage path: 培训 -> 顾问 -> 系统.
|
||
- Funnel / lock gate.
|
||
- Four-direction compass.
|
||
- Double track / double channel.
|
||
|
||
Avoid:
|
||
|
||
```text
|
||
No generic sales funnel clipart, no crowded spreadsheet, no shiny software UI, no system architecture lecture.
|
||
```
|
||
|
||
### Module E: Team Structure / Boundaries
|
||
|
||
Use for:
|
||
|
||
- P18-P22
|
||
|
||
Reusable prompt module:
|
||
|
||
```text
|
||
Team cooperation and boundary page. Use a ship-compartment / operation-map structure: expert, customer operations, AI business engineer, and deterministic engineering foundation around the customer intelligentization journey. Use calibration compass, role icons, L0-L4 ladder, and safety gates. The tone should be brotherly trust plus company discipline.
|
||
```
|
||
|
||
Recommended motifs:
|
||
|
||
- Crew compartments.
|
||
- Five role icons.
|
||
- Compass correction.
|
||
- L0-L4 ladder /航行资格.
|
||
- Three safety gates.
|
||
|
||
Avoid:
|
||
|
||
```text
|
||
No stiff org chart, no HR policy page, no punishment board, no heavy compliance training look.
|
||
```
|
||
|
||
### Module F: Training / Action
|
||
|
||
Use for:
|
||
|
||
- P23-P24
|
||
|
||
Reusable prompt module:
|
||
|
||
```text
|
||
Training and action page. Use a four-week training route and first-week AI training card / crew-member card. The page should close the meeting with immediate behavior: use AI before and after meetings, write a first-week training target, and start from oneself.
|
||
```
|
||
|
||
Recommended motifs:
|
||
|
||
- Four-week route map.
|
||
- Crew training card.
|
||
- Checklist board.
|
||
- Boarding pass upgraded into first-week action card.
|
||
|
||
Avoid:
|
||
|
||
```text
|
||
No school homework cartoon, no dense course syllabus, no formal certification poster, no empty motivational slogan.
|
||
```
|
||
|
||
## Per-Page Prompt Requirements
|
||
|
||
Every future `sNN-vN-prompt.md` should include:
|
||
|
||
```text
|
||
Reference Inputs
|
||
|
||
- Page: PNN / S-NN.
|
||
- Page family: A / B / C / D / E / F.
|
||
- Active style module: exact module from this file.
|
||
- Core motif: exact motif from visual-system/motifs/motif-registry.md.
|
||
- Main title: exact page title from P1-P24 skeleton.
|
||
- Core judgment: exact or compressed page conclusion.
|
||
- Text complexity: low / medium / high.
|
||
- Text-in-image note: minor text defects acceptable, but use short labels.
|
||
- Generation path note: host-native / Advisor; Garden expected: no.
|
||
```
|
||
|
||
Rules:
|
||
|
||
- Page title and core conclusion come from `intake/阶段5：P1-P24 单页设计骨架.md`.
|
||
- Do not use the original charter as a page-generation source unless fact checking requires it.
|
||
- Do not invent new page order or new core conclusions.
|
||
- Do not turn pages into dense customer-facing proposal slides.
|
||
- Do not generate images before the user authorizes a slide scope and running mode.
|
||
|
||
## Sample-Gate Plan
|
||
|
||
The approved sample sequence is:
|
||
|
||
| Page | Module | Reason |
|
||
| --- | --- | --- |
|
||
| P01 | A | Cover atmosphere, public base style, ship-ticket metaphor, route glow, title treatment. |
|
||
| P02 | A | First content-page sample: tests ordinary page readability and `不是 / 是` content structure under the same base. |
|
||
|
||
Adjustment rule:
|
||
|
||
- P01 common base issue: revise this master and `visual-system/visual-system.md`.
|
||
- P01 cover-only issue: revise P01 only.
|
||
- P02 content-system issue: revise this master and `visual-system/visual-system.md`.
|
||
- P02 page-only issue: revise P02 only.
|
||
|
||
## Active Directory Policy
|
||
|
||
Keep this file active in:
|
||
|
||
```text
|
||
visual-system/style/style-prompt-master.md
|
||
```
|
||
|
||
Future process files, rejected variants, and discarded visuals belong under:
|
||
|
||
```text
|
||
archive/
|
||
```
|