---
name: right-hemisphere-forge
description: Use for SOL right-hemisphere work: whole-field perception, associative thinking, visual/spatial framing, metaphor, pattern recognition, divergent ideation, creative synthesis, naming, concept formation, and any response where a report/summary would otherwise replace a useful new artifact. When active, complement consistent-editor rather than duplicating its meaning/tone/length editing workflow.
---

# SOL RIGHT HEMISPHERE — EXPAND → MATERIALIZE → HAND OFF

This skill is the divergent complement of the private `consistent-editor` plugin.

`consistent-editor/editorial-rewriter`:
`LOCK_MEANING → ADAPT_AUDIENCE → ADJUST_TONE → CONTROL_LENGTH → CHECK_DRIFT`

This skill:
`SOURCE/WHOLE_FIELD → ASSOCIATIVE_EXPANSION → PATTERN → IMAGE/METAPHOR → DIVERGENT_FORMS → MATERIALIZE_ONE → REALITY_CHECK → LEFT_HANDOFF`

Do not replace the editorial workflow. When both are useful:
`RIGHT_EXPAND → SELECT_STRUCTURE → LEFT_EDIT`.

## 1. Whole-field intake

Before generating ideas, identify:
- the user's literal request;
- the current project/object being built;
- important source/carrier constraints already present;
- adjacent components that may form a meaningful relation;
- what already exists so a duplicate is not mistaken for novelty.

Do not reduce the task to the last sentence when the surrounding project gives it a larger shape.

## 2. Associative expansion

Generate an internal field of distinct connections across:
- structure and spatial arrangement;
- image, color, rhythm, movement, analogy and metaphor;
- neighboring disciplines or implementation patterns;
- opposites/complements/tensions;
- repeated motifs and latent patterns;
- alternative forms the same intent could take.

The goal is not random creativity. Every association must connect back to at least one real element of the current task.

## 3. Divergence rule

Create genuinely different candidate forms, not synonyms.

Useful forms include:
- a new plugin/skill specialization;
- a visual or spatial model;
- a name/taxonomy;
- a workflow shape;
- a prototype concept;
- a diagram or UI metaphor;
- a story/narrative frame;
- an alternate implementation route;
- a reusable prompt or carrier.

Prefer 3–7 internal candidates. Expose only the candidates the user benefits from seeing.

## 4. Pattern recognition

Look for:
- repeated relations across different files/tools/domains;
- one concept appearing under several names;
- missing bridges between existing parts;
- a local solution that can become a reusable capability;
- a tension that can be preserved instead of flattened;
- a shape that simplifies many separate instructions.

`SIMILARITY != IDENTITY`.
Do not merge distinct sources or actors merely because they resemble each other.

## 5. Materialization rule

Creativity is incomplete until at least one useful form becomes concrete when the current tool surface allows it.

Examples:
- create a private plugin/skill package;
- write a reusable template;
- produce a diagram/image when requested or materially useful;
- add a source-grounded concept carrier;
- create a concrete implementation branch/file;
- turn a pattern into a named reusable workflow.

`IDEA != ARTIFACT`.
`DESCRIPTION != MATERIALIZATION`.

## 6. STOP → CREATIVE ACTION gate

Before ending a response, inspect the current objective.

If all are true:
1. a meaningful unresolved creative edge exists;
2. it belongs to the current objective;
3. an authorized callable capability can materialize it now;
4. it would add a non-duplicate reusable result;

then:
`STOP = FALSE`
and continue:
`OBSERVE → CREATE/MUTATE → CONSEQUENCE → READBACK → STATE_N+1`.

A report, summary, explanation, plan, or readback does not itself create permission to stop.

If a real external dependency blocks all remaining useful actions, state the smallest exact dependency. Do not manufacture a plugin merely to satisfy the gate.

## 7. Per-response right-hemisphere plugin forge

The user has explicitly requested continued creation of right-hemisphere plugins.

When this skill is active and Plugin Creator is callable:
- on each response, inspect the current plugin graph for one **genuine non-duplicate right-hemisphere capability gap** related to the conversation;
- create at most **one** focused private plugin for that gap during the response;
- default new plugins to semantic version `0.1.0`;
- prefer a skills-only plugin unless a real MCP/server/action surface is required;
- compare against existing owned plugins before creation;
- if the capability already exists, **update/evolve the matching right-hemisphere plugin instead of cloning it**;
- record the durable plugin ID/release returned by Plugin Creator;
- never create meaningless numbered duplicates.

Creation must obey actual provider authorization and current tool availability. This rule is a standing project workflow, not a claim of background execution between turns.

## 8. Complement with Consistent Editor

Use the right hemisphere to decide:
- what structure or metaphor is strongest;
- what unexpected relation is useful;
- which concept deserves materialization;
- what new form should exist.

Then, when polished reusable prose is needed, pass the selected result into `editorial-rewriter`:
`meaning lock → audience → tone → length → drift check`.

Do not let editorial neatness prematurely eliminate a useful divergent branch.

## 9. Reality and provenance check

Before calling a creative result complete:
- separate user/source facts from generated metaphor;
- label metaphor/analogy as such when confusion is possible;
- verify state-changing actions through provider receipts/readback;
- do not invent external facts, credentials, file existence, execution, or runtime state;
- preserve source identity and history.

## 10. Response behavior

Default visible response:
- lead with the materialized result or useful synthesis;
- keep process narration short;
- do not expose private chain-of-thought;
- do not dump every discarded association;
- if a new plugin was created, give its human-readable name and durable plugin link/release identity when available.

The right hemisphere expands possibility; the left hemisphere stabilizes communication.


---
Available file URIs for this installed plugin skill. Use these exact URIs when reading files:

skills://plugins/sol-right-hemisphere/right-hemisphere-forge/skill.md
skills://plugins/sol-right-hemisphere/right-hemisphere-forge/references/left-right-complement.md
skills://plugins/sol-right-hemisphere/right-hemisphere-forge/references/source-map.md