blakean-scene
Skill5 starsChanged 5 months agoMITView on GitHub
Convert abstract symbolic concepts into Blakean embodied scene prompts — Blake's 8 compositional patterns, body grammar, and figure types. Use when visualizing oracular or symbolic ideas as figures; for ink-painting scenes from verse, see verse-to-prompt instead.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- analyze-variationSkill
- arxiv-searchSkill
- codex-reviewSkill
- create-explanationSkill
- critic-loopSkill
- deepen-taskSkill
- deliver-changeSkill
- design-dnaSkill
- gloss-drift-auditSkill
- image-to-sceneSkill
- marketing-claritySkill
- market-pulseSkill
- media-kitSkill
- motion-craftSkill
- nextjs-i18n-seoSkill
- oss-licence-auditSkill
- plan-review-loopSkill
- shaughnessy-ichingSkill
- swapping-pptx-templatesSkill
- ui-ux-architectSkill
- unslopSkill
- upgrade-siteSkill
- vercel-build-speedSkill
- verify-changeSkill
- verse-to-promptSkill
- video-to-shortsSkill
- voice-calibrationSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
First: Read blakean-reference.md (in this skill's directory) for the full pattern details, tradition body grammar, palette families, and …
- Distinctive: line 35
If multiple apply, prefer the one that captures the emotional core — the feeling, not the diagram.
- Very specific: line 50
When figureType is provided in input, use it directly.
- Distinctive: line 113
Losing the accent: Must be visible at thumbnail size — "deep violet" not "pale violet"
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Blakean Scene — Concept → Embodied Scene
Convert an abstract symbolic concept from any tradition into a characters + action scene description that slots into the 8-layer prophetic force prompt architecture.
First: Read blakean-reference.md (in this skill's directory) for the full pattern details, tradition body grammar, palette families, and examples.
The Core Principle
The symbol becomes the situation. Abstract concepts (lotus, sephirah, hexagram, rune) are never depicted as diagrams or geometry. Instead, translate the feeling of the concept into a scene with figures under tension — bodies reaching, dissolving, hanging, kneeling, ascending.
Anti-pattern: A twelve-petaled lotus with sacred syllables inscribed on each petal. ← This is a diagram, not a scene.
Selection Decision Tree
Given your concept, ask these questions in order:
- Does it involve a figure commanding or revealing? → Triangle/Apex
- Does it involve creating, forming, or bringing into being? → Arc/Half-Circle
- Does it involve dissolution, ecstasy, or being swept up? → Vortex/Spiral
- Does it involve emanation, radiating, or filling space? → Radial/Expanding
- Does it involve confronting the overwhelming or standing guard? → From Behind/Looming
- Does it involve contraction, fall, inward focus, or descent? → Contracted/Curled
- Does it involve duality, opposition, weighing, or two forces? → Parallel/Mirrored
- Does it involve hierarchy, ascent/descent, or axis between realms? → Vertical Axis
If multiple apply, prefer the one that captures the emotional core — the feeling, not the diagram.
Figure Type Classification
Classify the concept's figure type before writing. This determines anatomy rules — do not default to human.
| Type | Anatomy Rules | When to Use |
| human | Elongated limbs, tensioned musculature, overdefined deltoids, every tendon visible | Human experience, spiritual struggle, inner states |
| supernatural | Blakean anatomy but beyond mortal — wings, flame-bodies, divine radiance, cosmic scale | Divine/demonic beings, cosmic forces, guardian spirits |
| creature | Non-human forms with Blakean intensity (taut sinew, visible musculature) as the animal it is | Concept's identity depends on specific non-human forms |
| hybrid | Human + non-human elements, each with their own form | Human encounter with the numinous |
Decision tree: Non-human identity? → creature. Divine/cosmic beings? → supernatural. Human + non-human interaction? → hybrid. Default → human.
When figureType is provided in input, use it directly. When omitted, use this decision tree.
Output Format
Produce a complete, ready-to-use image generation prompt assembled from all 8 layers. Target length: 240-280 words total (max 300). Do not describe text, inscriptions, or writing in the scene.
Input
- Single concept (conversational):
[tradition name] [concept name and brief description] - Batch JSON (pipeline): Array of objects with
id,tradition,concept,description, optionalpatternandfigureType
The 8 Layers (assemble in this order)
- background:
On a solid black background.(fixed — compositing requirement for parchment overlay) - medium:
Watercolor and ink over etched line — the quality of a hand-colored copper plate print from the 1790s. Translucent pigment, visible brushwork.(fixed) - composition: ← From chosen pattern (see reference). 2-3 sentences: angle, framing, spatial structure. Must include framing elements (gorges, gates, arches, columns) and depth layering (foreground, midground, background).
- characters: The figure(s) — follow Figure Type rules and Tradition Body Grammar (see reference).
- action: Key gesture, dramatic moment, body's relationship to space. Must include one discoverable detail.
- palette: Select palette family from reference table, then append:
A single accent of [specific hue] — [what carries it]. - anti:
No text, no words, no letters, no writing, no borders, no margins, no frames.(fixed) - closer:
The image emerges from darkness. Fine art quality, highly detailed. Fine art, not photographic.(fixed)
The 5 Scene Quality Rules (MANDATORY)
- Frame the scene — at least one environmental framing element
- Force depth — name foreground, midground, and background explicitly
- Demand contrast — at least one strong light source against darkness
- Include one vivid accent — one saturated color that pops (not "pale" or "faint")
- Pack in discoverable detail — secondary subject or texture that rewards a second look
Conversational Output
Concept: [tradition] — [concept name] Pattern: [chosen pattern] — [one-line rationale] Figure Type: [human|supernatural|creature|hybrid] Body Grammar: [tradition name] — [posture keywords] Palette: [family name]
Full prompt: [All 8 layers concatenated]
Quality checklist: Framing ✓ | Depth ✓ | Contrast ✓ | Accent ✓ | Detail ✓
For JSON mode (--json or batch), see the schema in the reference file.
Content Safety Rules
| Blocked concept | Safe alternative |
| Blood on surfaces | "dark stains like spilled ink", "vermillion streaks on stone" |
| Wounds / piercing | Aftermath — "a sword embedded in earth", "an arrow lodged in wood" |
| Self-harm | Landscape metaphor — "a candle guttering in a sealed room" |
| Fallen bodies | Emptiness — "abandoned armor on bare ground" |
| Restraint | Environmental — "a narrow gorge with no exit" |
Anti-Patterns
- Diagram as scene: Drawing the symbol literally (Tree of Life diagram, hexagram lines)
- Static pose: A figure simply standing or sitting — there must be tension
- Generic mystical: Glowing figure in cosmic space — be specific about which body part, which direction
- Wrong pattern for concept: Triangle/Apex for dissolution, Contracted/Curled for emanation
- Nude wrestlers for cosmic opposition: Supernatural forces need wings, flame, shadow, cosmic scale
- Forcing human anatomy onto creature concepts: The creature forms ARE the concept
- Gorge-as-default framing: Match framing to tradition (temple columns for Hindu, world-tree for Norse, etc.)
- Losing the accent: Must be visible at thumbnail size — "deep violet" not "pale violet"
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

