By latentwill
Two complementary idea-expansion skills based on Patrick Gunkel's ideonomy — the science of treating ideas as natural phenomena that can be sliced, negated, recombined, and re-instantiated. ideonomy-plain outputs plain-text-portable artifacts (survives SMS/Telegram/Slack). ideonomy-rich outputs performative ASCII art for monospace terminals.
Use when expanding, varying, inverting, recombining, or systematically exploring an idea — brainstorming alternatives, generating opposites, finding unexpected angles, breaking out of a creative rut, or producing a fresh framework instead of the same generic approach. Renders the expansion as plain-text-portable output that survives any channel (Telegram, SMS, plain Slack, fixed-width-only email). Each invocation produces a different combination of ideational operations so the agent can't fall into a default routine. For monospace-rich rendering with Unicode box-drawing and figlet banners, see the sibling skill `ideonomy-rich`.
Use when expanding an idea AND the output channel can render monospace cleanly — terminals, READMEs, blog posts with monospace code blocks, fixed-width-font emails, ttyrec sessions, the Claude Code transcript itself. Same primitives as `ideonomy-plain`, but renders the artifact as performative ASCII art with Unicode box-drawing, figlet banners, density gradients, and visible ideonomy-machinery layers (tuple legend, dimensions surfaced, operator-named dividers, ideonomy trail). If the channel might mangle Unicode (Telegram, SMS, plain Slack DMs), use `ideonomy-plain` instead.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Ideas are natural phenomena. They have properties. They live along dimensions. They can be sliced, negated, recombined, and re-instantiated like any other natural object. — after Patrick Gunkel, via Grace Kind
A pair of skills that turn any idea into a populated neighborhood of related ideas, by applying combinations of ideonomic operators — negate, substitute, combine, abstract, re-instantiate, find-the-tree — drawn from a randomized tuple at every invocation.
Every call picks a different combination of operators, organons, and dimensional prompts from a catalog of millions of distinct method-tuples. The agent doesn't get to fall back on its default brainstorming moves. That's the whole point.
The two skills share one brain (operators × organons × dimension-prompts × picker × cooldown) and differ only in how they render the artifact:
| Skill | Rendering | Best channel |
|---|---|---|
ideonomy-plain | Plain Markdown lists, fenced-code-block tables, no Unicode box-drawing. | Anywhere — including SMS bridges, Telegram, plain Slack DMs, and any context where Unicode might mangle. |
ideonomy-rich | Performative ASCII art: figlet banners, Unicode box-drawing, density gradients, visible ideonomy-machinery layers (tuple legend, dimensions surfaced, operator-named dividers, ideonomy trail). | Terminals, READMEs, blog posts with monospace code blocks, fixed-width-font emails, ttyrec sessions. |
Default to ideonomy-plain. Use ideonomy-rich when you know the medium can hold the art.
$ ~/.claude/skills/ideonomy-plain/bin/pick # or ideonomy-rich; same picker
=== IDEONOMY METHOD TUPLE (this invocation) ===
OPERATORS:
- abstraction-lift
- cross-domain-reinstantiation
ORGANONS:
- periodic-grid
DIMENSION-PROMPTS:
- longevity
- autonomy
- reversibility
==============================================
[…bodies of each picked method file follow, ready for the agent to apply…]
Then ask your agent to apply the tuple to your idea. What you'll get back: five or ten unfamiliar variants of the idea, organized into the picked organon, with the picked operators visible in how the agent got there. Sometimes the result is brilliant. Sometimes it's nonsense. Both are useful — the nonsense tells you which dimensions of your idea were load-bearing.
Run it ten times on the same idea. The expansions won't repeat.
Each skill folder is fully self-contained — drop either or both into any agent's skills/ directory and they load. No installer, no symlinks, no build step.
git clone [email protected]:latentwill/ideonomy-skill.git
cp -R ideonomy-skill/ideonomy-plain <your-skills-folder>/
cp -R ideonomy-skill/ideonomy-rich <your-skills-folder>/ # optional
Common destinations:
| Agent | Skills folder |
|---|---|
| Claude Code | ~/.claude/skills/ |
| Cowork | ~/Library/Application Support/Claude/local-agent-mode-sessions/skills-plugin/<global-uuid>/<workspace-uuid>/skills/ |
| Anything else with a Claude-style skill loader | wherever it puts SKILL.md-based skills |
The agent picks ideonomy-plain vs ideonomy-rich automatically based on the channel — that's why both skills carry their own description. Default to ideonomy-plain if you only want one.
Pure bash + standard tools (awk, sort, find, curl only for the optional --random-org flag). ideonomy-rich additionally benefits from figlet / boxes / toilet if installed (brew install figlet boxes toilet), but always falls back to the public asciified.thelicato.io API.
Maintainer note: the operator/organon/dimension-prompt catalog and
bin/picklive inideonomy-plain/.ideonomy-rich/carries duplicate copies so it can drop in alone — when you change a method file or the picker, update both folders. (diff -r ideonomy-plain/methods ideonomy-rich/methodsto check.)
ideonomy-skill/
├── ideonomy-plain/ ← portable rendering (default)
│ ├── SKILL.md
│ ├── bin/pick ← the chooser
│ ├── methods/ ← operators, organons, dimension-prompts
│ └── examples/
└── ideonomy-rich/ ← monospace-rich rendering
├── SKILL.md
├── bin/pick ← thin wrapper → ../ideonomy-plain/bin/pick
└── rendering/ ← per-organon ASCII recipes
(chart, tree, list, atlas, scale, cycle, dictionary)
The catalog (single source of truth):
npx claudepluginhub latentwill/ideonomy-skill --plugin ideonomyUI/UX design intelligence. 67 styles, 161 palettes, 57 font pairings, 25 charts, 15 stacks (React, Next.js, Vue, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Nuxt, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
This skill should be used when users need to generate ideas, explore creative solutions, or systematically brainstorm approaches to problems. Use when users request help with ideation, content planning, product features, marketing campaigns, strategic planning, creative writing, or any task requiring structured idea generation. The skill provides 30+ research-validated prompt patterns across 14 categories with exact templates, success metrics, and domain-specific applications.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.