Triforce Architecture
Create a realistic editorial-style architecture diagram illustration
explaining the "Triforce" cross-modal pipeline of the fumeng skill.
Visual style: Warm editorial schematic in the spirit of a classic
engineering textbook figure crossed with Edward Tufte's visual evidence —
reserved, precise, beautiful by clarity. Feels like a hand-drafted plate
from a technical monograph, NOT an infographic.
Color palette:
- Background: warm cream paper oklch(0.96 0.008 40) with subtle grain
- Primary line ink: deep warm black oklch(0.18 0.02 30)
- Secondary text: muted warm grey oklch(0.50 0.01 30)
- Gold accent for active pathways: warm gold foil oklch(0.72 0.15 75)
- Terracotta accent for labels: oklch(0.58 0.19 28)
Typography:
- Figure caption title: humanist serif display (Tiempos Headline character),
weight 500, 48px, deep warm black: "The Triforce Pipeline"
- Node labels: monospaced letterpress type (IBM Plex Mono character),
14px uppercase tracking 2%, deep warm black
- Descriptive text beside nodes: warm editorial body serif
(PP Editorial Old character), 15px, line-height 1.6
Layout (centered equilateral triangle diagram, deliberately spacious):
- Title "The Triforce Pipeline" top-left, 48px
- Sub-caption just below title: "Three capabilities that only work together"
in 16px italic body serif
- Three nodes arranged in a large equilateral triangle in the center,
about 60% of the canvas height:
* TOP node: a small rendered monitor showing a UI mockup inside,
circular stroke around it, label below in monospaced caps:
"IMAGE-2 · VISUAL ANCHOR". Below, 3 lines of body serif:
"gpt-image-2 4K mockups", "Fixes the design intent", "Accepts $0.02-0.40"
* BOTTOM-LEFT node: a hexagonal schematic plug with six small
dots arrayed around it (representing 6 MCP servers), circular stroke,
label: "MCP · REAL ASSETS". Below: "shadcn / chrome-devtools",
"playwright / logo-search", "context7 / lighthouse"
* BOTTOM-RIGHT node: a classical quill with an ink bottle,
circular stroke, label: "PROMPT · METHODOLOGY". Below:
"9 aesthetic families", "Anti-slop rules (6 banned fonts)",
"Placeholder > Fake philosophy"
- The three nodes are connected by thin warm gold lines with tiny circular
terminals at each end (like a circuit schematic), forming a triangle.
Each edge has a small italic caption in the middle explaining the
directional flow:
* image-2 → MCP edge: "intent fixes target for harvest"
* MCP → prompt edge: "real assets inform tokens"
* prompt → image-2 edge: "methodology shapes the prompt"
- A subtle circular arrow at the CENTER of the triangle, with the label
"cross-modal loop" below it in small terracotta italic.
Bottom-right corner: a small legend:
"— gold line = data flow"
"— thin rule = relationship"
"— solid stroke = active capability"
Background:
- Warm cream paper base
- Faint 8px grid visible beneath (like plotting paper but extremely muted,
3% opacity)
- Slight vignette at edges
Use case: Educational diagram figure in README, 1536x1024, displayed at
reading width on GitHub.
Strict constraints:
- NO Inter, Roboto, Arial, Space Grotesk, Fraunces, system-ui fonts.
- NO purple gradients, NO holographic effects, NO glass morphism.
- NO emoji, NO cartoon characters, NO isometric 3D.
- NO dense infographic data-slop (fake percentages, fake user counts).
- All node icons must be LINE-DRAWING style (hair-line strokes),
not filled illustrations.
- Triangle must be GEOMETRICALLY PRECISE (equilateral), not skewed.
- All text must be EXACTLY as specified — do not hallucinate labels.
- Pixel-perfect 8px grid alignment. Letterpress restraint.when to use it
Community prompt sourced from the open-source GitHub repo qiuxinyuan321/fumeng (MIT). A "Triforce Architecture" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
qiuxinyuan321/fumeng · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions