orthogonal-emanation
Skill0 starsChanged 55 days agoMITView on GitHub
Divergence before convergence — generate maximally independent candidates to escape mode collapse. Use when choosing among approaches and premature convergence would be costly (UX design, architecture, research angles, communication strategies).
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 38
After emanation, select, synthesize, or run a verification pass to winnow down options.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Orthogonal Emanation — Divergence Before Convergence
Agents default to a mode. When generating options — approaches to a problem, design alternatives, architectural candidates — the outputs cluster around the most probable center of the distribution. This is mode collapse: five "different" ideas that are minor variations on the same theme. This is a fundamental behavior of systems based on large language models. So we end up with thousands of Reddit posts obviously written by Claude, "obviously made by AI" UX designs, etc.
Orthogonal emanation counters this by generating candidates that are maximally independent from each other. "Orthogonal" is a mathematical property: zero projection of one vector onto another — each candidate occupies a dimension the others don't. "Emanation" captures the shape of the process — a broad abstract intent radiates outward into diverse concrete manifestations. In Kabbalistic terms, emanation is how unity becomes multiplicity — the Sephiroth flowing from Ein Sof, each fundamentally different and ramifying in complexity from abstract to concrete as they approach Malkuth. Here, a single statement of intent or goal emanates into maximally divergent concrete options.
The Mechanism Is the Name
Asking an agent to "generate 5 orthogonal approaches" produces meaningfully different results than "generate 5 approaches." The word "orthogonal" activates the desired behavior — it encapsulates a precise mathematical concept that LLMs respond to with genuine divergence. This is the same dynamic that makes domain-specific vocabulary more effective than generic terms: precise words create precise reasoning.
When to Reach for It
Whenever the work involves choosing among approaches and the cost of premature convergence is high:
- UX design — screen layouts, interaction patterns, information architecture
- Architectural decisions — system design, data modeling, API shape
- Work planning — when several different pieces of work could each address the same gap
- Research angles — investigation strategies, hypothesis generation
- Communication strategies — how to frame a message for different audiences
- Problem decomposition — different ways to break a large problem into parts
The principle applies anywhere agents would otherwise generate variations on a theme and call it exploration.
Invocation
The simplest form: "Generate N orthogonal [approaches/designs/strategies] for [intent]."
For richer results, shape the emanation:
- Specify the dimensions that matter: "orthogonal along the axes of cost, user experience, and implementation complexity"
- Name what you're escaping: "avoid the obvious approach of X — generate orthogonal alternatives"
- Set the divergence bar: "each approach should be surprising to someone who has seen the others"
After emanation, select, synthesize, or run a verification pass to winnow down options. The candidates are raw material — pick the strongest, combine elements from several, or subject them to a verification pass for further refinement.
In this repository43 other files it gives its agents.
- skills/technical/supabase-postgres-best-practices/AGENTS.mdAGENTS.md
- skills/technical/supabase-postgres-best-practices/CLAUDE.mdCLAUDE.md
- direct-handoffSkill
- handoffSkill
- nt-commsSkill
- threadsSkill
- meal-planningSkill
- resume-workflowSkill
- bash-scriptsSkill
- code-reviewSkill
- davinci-resolveSkill
- disk-cleanupSkill
- fastmcp-pythonSkill
- go-cliSkill
- markdown-to-pdfSkill
- pr-createSkill
- qa-planSkill
- rcaSkill
- react-native-best-practicesSkill
- ruby-railsSkill
- skill-creatorSkill
- spec-checkSkill
- supabase-migrationsSkill
- supabase-postgres-best-practicesSkill
- supabase-sqlSkill
- testingSkill
- ui-state-managementSkill
- waydroid-adbSkill
- calcinatioSkill
- citationsSkill
- exploreSkill
- manual-qaSkill
- nvim-copilotSkill
- orchestrateSkill
- product-intent-signal-extractionSkill
- project-management-signal-extractionSkill
- request-researchSkill
- researchSkill
- skill-discoverySkill
- slack-thread-triageSkill
- specSkill
- tmux-sidecarSkill
- youtube-transcribeSkill
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.

