Skip to content

Node Reference

In conventional prompt engineering, adjusting tone and behavior often relies on natural-language modifier phrasing (“act as an expert,” “think step by step”). Such phrasing tends to be ambiguous and often introduces meta-instruction noise alongside the task itself.

MTP replaces much of that control with non-verbal metadata: coordinates and axis labels compiled into tiered constraints. This page separates the core semantics of each Side A / Side B node from the prompt-output tendencies produced by the current MTP Skill.

Core semantics describe the direction represented by a node across applications. Prompt-output tendencies describe how that direction is currently translated into LLM behavior.


Each color axis in MTP has two nodes: Side A and Side B (each referred to as <node>). Intensity (<intensity>) can be specified in the range 0 to 100.

Side A is the positive-side node and can be specified by node name, such as power:70 (<node>:<intensity>). Side B is the inverse-side node and can be specified by node name, such as void:70.

When using a color name instead of a node name, positive values activate Side A and negative values activate Side B. For example, red:70 activates Power, while red:-70 activates Void. The same polarity rule applies to node names: power:-70 also activates the Red axis through Void.

Color / AxisNodeUsage exampleCore semanticsPrompt-output tendencies
Yellowopenopen:100 / yellow:100 / D:4Opening, possibility, expansionDivergent ideation, option generation, leaving room for choice
Redpowerpower:100 / red:100 / J:4Force, assertion, driveFirm claims, decisions, persuasive conclusions
Magentareturnreturn:100 / magenta:100 / P:4Return, reversal, recurrence, reframingCritique, counter-reading, reframing a premise
Greengrowgrow:100 / green:100 / D:10Development, layering, wideningExpanded explanations, elaboration, branching ideas
Transparenthelixhelix:100 / transparent:100Integration, unfolding structure, interrelationTraceable reasoning, linked steps, visible structure
Whitefocusfocus:100 / white:100 / P:10Precision, clarity, definitionSpecification checks, evidence, narrowed scope
Cyanenterenter:100 / cyan:100 / D:16Threshold, entry, framingIntroductions, onboarding, explicit scope and prerequisites
Blueflowflow:100 / blue:100 / J:16Continuity, connection, rhythmSmooth prose, transitions, readable progression
Purplecloseclose:100 / purple:100 / P:16Closure, completion, sealingSummaries, conclusions, next actions
Color / AxisNodeUsage exampleCore semanticsPrompt-output tendencies
Dark Yellowstillstill:100 / yellow:-100 / A:1Restraint, preservation, suspensionFormatting, proofreading, minimal change, suppressing new suggestions
Dark Redvoidvoid:100 / red:-100 / J:1Absence, subtraction, hollowing, silenceShortening, removing noise, dry or minimal responses
Dark Magentasurgesurge:100 / magenta:-100 / S:1Release, excess, eruption, overflowHigh-energy writing, dense accumulation, forceful expression
Dark Greenwitherwither:100 / green:-100 / A:10Attenuation, pruning, declineKey-point summaries, concise explanations, reduced branching
Translucent (Transparent)collapsecollapse:100 / transparent:-100Compression, convergence, loss of structureDirect answers, simplified summaries, flattened organization
Dark Grey (White)hazehaze:100 / white:-100 / S:10Ambiguity, diffusion, obscured definitionPoetic language, atmosphere, softened distinctions
Dark Cyandriftdrift:100 / cyan:-100 / A:19Deviation, wandering, loosened directionFree association, tangents, lateral development
Dark Blueabyssabyss:100 / blue:-100 / J:19Depth, descent, weightDeep reflection, criticism, dense analysis
Dark Purplefadefade:100 / purple:-100 / S:19Attenuation, dissolution, afterimageOpen-ended prose, tapering conclusions, lingering resonance

Side B color names are not the opposite color (White does not flip to Black); they restate the axis color to match each node’s meaning. Haze is White growing hazy toward grey, shown as “Dark Grey (White),” and Collapse is Transparent breaking down, shown as “Translucent (Transparent).”


This section briefly organizes how each axis relates within the taxonomy.

  • Vertical (Red ↔ Blue): The axis where directions that stress assertion and structure face directions that preserve receptivity and continuity.
  • Horizontal (Green ↔ White): The axis where outward expansion while holding outline faces narrowing the subject for rigorous scrutiny.
  • Corners (Yellow, Magenta, Cyan, Purple): Transitional gradient regions that connect adjacent nodes of the cross.
  • Center (Transparent): A neutral node placed between opposing directions.

MTP coordinate system and node layout diagram showing the unified Side A/B color and node map, plus coordinate pairs such as D:4 and A:19.

The axis layout can be read both as a 3x3 Side A / Side B map and as coordinate positions on the 19x19 grid.


As an output tendency, Side A often appears as a force that moves the response forward. In an introduction, for example, it may invite the reader in, add reasons, structure the material, sharpen focus, or carry the text toward a conclusion.

Side B is not simply a weaker Side A. As the inverted pole of the same axis, it often shifts output away from construction toward reduction, away from clarity toward ambiguity, away from expansion toward descent, and away from closure toward afterimage. Side B is not the “bad” or “low” side; it functions as the shadow or reverse face of the axis.


Under the Chebyshev-based radial rule, coordinates on the outer perimeter frame flip to Side B for that zone. In constraint design, Side B is expressed as an inverted pole of the same axis: a paired opposite in a yin-yang sense (for example, Power → Void, Focus → Haze, Grow → Wither).

Side B suits cases that call for a stronger extreme along that axis or more compressed surface wording, with the same model-to-model variability as Side A.


MTP can also specify multiple nodes at the same time to blend output tendencies. Instead of switching output with a single node, it can layer several axes like a gradient, such as combining assertion (power:20) with precision (focus:30), or development (grow:20) with readability (flow:50).

The idea is to reduce the burden of operation by combining MTP nodes intuitively, while still changing the model’s output tendency in a controlled way.

When several MTP tokens are present, each token is still resolved under the same Space / Intensity rules; the compiler emits one constraint block per token in parse order (the order they appear in the payload).

That order is not a third parameter space or a dedicated “motion” layer. The sequence may be read as a semantic trajectory on the grid, but that is an optional design reading only.

Named sliders (power:100, flow:70) are an easy starting point when meaning should stay readable; grid coordinates suit cases where the visible message should remain short.

Named presets expand to fixed coordinate sequences defined in skills/mtp/references/presets.yaml; they can be applied to reproducible multi-step blends.