Przejdź do treści
Biblioteka skilli
Produktywność osobista · Planowanie

ideonomy-plain

/ideonomy-plain

Eksploruje pomysły przez wymiary, transformacje i uporządkowane alternatywy, podając pełne wyniki w zwięzłym tekście, do ideacji i dalszej eksploracji.

Repozytorium
ideonomy-skill ↗
Licencja
MIT
Ostatnia zmiana repozytorium
19.09.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
106
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 19.09.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Eksploruje pomysły przez wymiary, transformacje i uporządkowane alternatywy, podając pełne wyniki w zwięzłym tekście, do ideacji i dalszej eksploracji.

Oryginalny opis (EN)

Explore ideas through dimensions, transformations, and structured alternatives. Show complete scoped results in concise, readable text; use for ideation and continued exploration, not execution of a chosen plan.

Jak działa

  1. Scope and route
  2. Explore
  3. Complete, readable output
  4. References and runtime
  5. Rendering
Sekcje z nagłówków SKILL.md, w oryginale · 44 linii, 904 słów
Podgląd SKILL.md
---
name: ideonomy-plain
description: Explore ideas through dimensions, transformations, and structured alternatives. Show complete scoped results in concise, readable text; use for ideation and continued exploration, not execution of a chosen plan.
---

# Ideonomy: plain

An organon is a structured instrument for exploring ideas: alternatives, relationships, gaps, and next inquiries.

## Scope and route

- Preserve the user's goal, explicit non-negotiable constraints, requested methods, counts, axes, and output limits. On follow-ups, develop the existing organon and retain candidate IDs.
- Match breadth to intent: **quick** means a few distinct mechanisms; **broad** covers materially different regions; **deep** examines dependencies, counterexamples, and revisions; **exhaustive** requires a bounded universe and enumeration. A short prompt does not imply shallow coverage. Without a cue, choose a useful range of distinct mechanisms, not a token minimum.
- State scope and why it fits in one sentence. For finite spaces, show input sets, total combinations, and explored count; disclose sampling rules and omitted regions. Do not shrink scope merely to claim completeness. If breadth and length conflict, shorten each entry first; disclose any remaining tradeoff. Distinguish candidates by mechanism, not names or metaphors; group close variants without losing their differences. Keep explicit enumerations to the requested space; do not append extra cells or candidates.
- Honor deliberate routes. Otherwise run `bash /absolute/path/to/this-skill/bin/pick` relative to this loaded file and read its returned bodies. Do not reread them or load the whole catalog. If execution is unavailable, disclose manual selection from [the catalog](methods/README.md). For missing names, consult its aliases. Replace an unsuitable draw deliberately with a brief reason, without repeated redraws.

## Explore

Apply the chosen operators to concrete properties and meaningful axis values. Preserve ordered distinctions such as A-of-B versus B-of-A. Include an unfamiliar relevant direction; mark any adaptation of a dimension prompt. Record the changed property, input pair, or preserved relationship beside each result. Selected methods must visibly shape the exploration; replace an unsuitable form rather than use its name as decoration.

Distinguish facts, examples, hypotheses, and coinages when ambiguous. Inspect existing code, documents, or products before claiming a capability is missing; attach the inspected scope and evidence. A failed keyword search is not proof of absence. For analogies, identify correspondences and where they break. Empty cells can be unknown, unexamined, incompatible, or investigable; they do not prove novelty.

Creativity is a primary objective. Treat available materials, equipment, and familiar methods as starting points unless the user makes them non-negotiable. Explore bold departures and unfamiliar combinations; briefly name added requirements or assumptions instead of discarding an idea for needing more resources. When a hard boundary matters, label a boundary-changing thought experiment separately rather than present it as compliant. Preserve artistic or conceptual value independently of immediate feasibility. An exploration supplies groundwork for a plan; it need not already be one.

## Complete, readable output

Deliver the exploration in the **final answer**, not solely in tools, commentary, or an attachment. Compress wording, not coverage. Default shape, adaptable to the subject:

1. One brief orientation: goal/constraints, selected methods and selection mode, axes/values, and scope. Combine overlapping information.
2. One primary organon: each candidate appears once, with a stable ID, concrete idea, concise transformation, and key implication or uncertainty. Use a compact table or grouped list. For broad explorations, organize by distinct mechanisms; put close variants inside their group instead of a long flat list. Give each mechanism its practical implication, not just a name. Explain shared assumptions once; expand only cases where another detail changes understanding. Keep all declared cells, branches, or entries; mark incompatibilities and duplicate IDs rather than silently dropping them. Include intermediate results needed to understand later transformations, not private reasoning.
3. A short assessment: strongest directions with tradeoffs, a discriminating check or creative probe, and the next unexplored region. Do not restate the inventory or repeat a test and disclaimer under every candidate.

Before delivery, check consistency: do the described actions follow from the mechanism, and are required capabilities or resources explicit? For any proposed routine or prototype, reconcile step durations, totals, dependencies, and observation windows. Repair contradictions or mark what remains unresolved; do not claim a concept is ready to run when it is not. Keep this check unobtrusive and retain imaginative candidates with clear requirements rather than filtering for feasibility alone.

Before delivery, check both **scope adequacy** against the request and **coverage** against the declared space. A complete tiny sample does not fulfill a broad request. Summaries or shortlists replace the organon only when requested; otherwise put them after it. Avoid filler, decorative procedure reports, unexplained jargon, ellipses standing in for enumeration, and collapsed results.

If response limits prevent full inline delivery, preserve the complete Markdown artifact in the task's deliverable directory, link it, and identify exact inline and file-only ranges. For inline-only requests, use labeled parts and name the next range if another turn is necessary. Never call a partial view complete or ask whether the user wants the already-requested full version.

## References and runtime

Read [the worked example](references/worked-example.md) only when useful. Consult [sources](references/sources.md) for lineage, coverage, or catalog extensions: this is a contemporary adaptation of Gunkel, informed by Grace Kind, not a complete canonical system.

Picker flags: `--less`, `--more`, `--print` (names only), `--seed N`, `--cooldown-dir DIR`. Tuple size is not output breadth. Seeds replay selection only with an unchanged catalog and Bash/awk runtime; draws may repeat. Default runs are offline and read-only. Cooldown is opt-in workspace usage history, not quality learning; seeded runs ignore it. Do not modify installed methods during exploration.

## Rendering

Use readable Markdown lists or tables; fenced ASCII only when alignment helps. Keep meaning clear on narrow screens; avoid Unicode box drawing.
Pliki w paczce (106)
  • SKILL.md 7 KB
  • bin/pick 5 KB
  • examples/walkthrough.md 2 KB
  • examples/historical-recipes/atlas-of-perspectives.md 2 KB
  • examples/historical-recipes/cross-domain-lift.md 2 KB
  • examples/historical-recipes/dimensional-exhaustion.md 2 KB
  • examples/historical-recipes/negate-and-lift.md 2 KB
  • examples/historical-recipes/negation-cascade.md 1 KB
  • examples/historical-recipes/organon-sandwich.md 2 KB
  • examples/historical-recipes/property-explosion.md 2 KB
  • examples/historical-recipes/tree-walk.md 2 KB
  • methods/README.md 7 KB
  • methods/dimension-prompts/age.md 1 KB
  • methods/dimension-prompts/animacy.md 1 KB
  • methods/dimension-prompts/autonomy.md 1 KB
  • methods/dimension-prompts/cardinality.md 1 KB
  • methods/dimension-prompts/complexity.md 1 KB
  • methods/dimension-prompts/connectivity.md 1 KB
  • methods/dimension-prompts/cyclicity.md 1 KB
  • methods/dimension-prompts/decomposability.md 1 KB
  • methods/dimension-prompts/direction.md 1 KB
  • methods/dimension-prompts/discovery-vs-invention.md 1 KB
  • methods/dimension-prompts/distribution.md 1 KB
  • methods/dimension-prompts/hierarchicalness.md 1 KB
  • methods/dimension-prompts/homogeneity.md 1 KB
  • methods/dimension-prompts/intentionality.md 1 KB
  • methods/dimension-prompts/longevity.md 1 KB
  • methods/dimension-prompts/materiality.md 1 KB
  • methods/dimension-prompts/modularity.md 1 KB
  • methods/dimension-prompts/naturalness.md 1 KB
  • methods/dimension-prompts/polarity.md 1 KB
  • methods/dimension-prompts/predictability.md 1 KB
  • methods/dimension-prompts/purpose.md 1 KB
  • methods/dimension-prompts/rate.md 1 KB
  • methods/dimension-prompts/reversibility.md 1 KB
  • methods/dimension-prompts/scope.md 1 KB
  • methods/dimension-prompts/side-effect.md 1 KB
  • methods/dimension-prompts/size.md 1 KB
  • methods/dimension-prompts/source.md 1 KB
  • methods/dimension-prompts/symmetry.md 1 KB
  • methods/dimension-prompts/visibility.md 1 KB
  • methods/operators/abstraction-lift.md 1 KB
  • methods/operators/clarify-categorize.md 1 KB
  • methods/operators/combination.md 1 KB
  • methods/operators/compare-analogize.md 1 KB
  • methods/operators/construct-hypotheses.md 1 KB
  • methods/operators/critique.md 1 KB
  • methods/operators/cross-domain-reinstantiation.md 1 KB
  • methods/operators/decompose.md 1 KB
  • methods/operators/dimension-identification.md 1 KB
  • methods/operators/evaluate.md 1 KB
  • methods/operators/exemplify.md 1 KB
  • methods/operators/experiment-test.md 1 KB
  • methods/operators/explain.md 1 KB
  • methods/operators/explore.md 1 KB
  • methods/operators/extrapolate.md 1 KB
  • methods/operators/generalize.md 1 KB
  • methods/operators/history.md 1 KB
  • methods/operators/improve.md 1 KB
  • methods/operators/interaction.md 1 KB
  • methods/operators/intersection.md 1 KB
  • methods/operators/law-finding.md 1 KB
  • methods/operators/measure.md 1 KB
  • methods/operators/model-simulate.md 1 KB
  • methods/operators/negation.md 1 KB
  • methods/operators/organon-construction.md 1 KB
  • methods/operators/permutation.md 1 KB
  • methods/operators/predict.md 1 KB
  • methods/operators/recursive-reapplication.md 1 KB
  • methods/operators/research-plan.md 1 KB
  • methods/operators/reuse.md 1 KB
  • methods/operators/situate.md 1 KB
  • methods/operators/specialization.md 1 KB
  • methods/operators/substitution.md 1 KB
  • methods/operators/summarize.md 1 KB
  • methods/operators/transform.md 1 KB
  • methods/operators/tree-finding.md 1 KB
  • methods/organons/atlas.md 2 KB
  • methods/organons/chain.md 1 KB
  • methods/organons/chart.md 2 KB
  • methods/organons/circuit.md 1 KB
  • methods/organons/cycle.md 1 KB
  • methods/organons/dictionary.md 2 KB
  • methods/organons/fractal.md 1 KB
  • methods/organons/graph.md 2 KB
  • methods/organons/lattice.md 2 KB
  • methods/organons/list.md 1 KB
  • methods/organons/map.md 2 KB
  • methods/organons/matrix.md 2 KB
  • methods/organons/notation.md 2 KB
  • methods/organons/periodic-grid.md 1 KB
  • methods/organons/procedure.md 2 KB
  • methods/organons/questionnaire.md 1 KB
  • methods/organons/ring.md 1 KB
  • methods/organons/scale.md 2 KB
  • methods/organons/scenario.md 1 KB
  • methods/organons/set.md 1 KB
  • methods/organons/simulation.md 1 KB
  • methods/organons/spectrum.md 2 KB
  • methods/organons/state-machine.md 2 KB
  • methods/organons/timeline.md 2 KB
  • methods/organons/tree.md 2 KB
  • references/operator-examples.md 6 KB
  • references/organon-forms.md 4 KB
  • references/sources.md 6 KB
  • references/worked-example.md 4 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · latentwill/ideonomy-skill100MIT
vosslab/vosslab-skills100MIT

Migawka bazy z 13.11.2026 · wersja paczki 755aff8acc84 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100ideonomy-rich
    Eksploruje pomysły przez wymiary i transformacje przedstawione jako informacyjne diagramy monospace, do wizualnej ideacji w kanałach o stałej szerokości.
  • 100ideonomy-rich
    Rozwija pomysł losowymi metodami ideonomii z ekspresyjną grafiką monospace: ramki Unicode, banery figlet i gradienty gęstości w kanałach, które to obsługują.
  • 100brainstorming
    Prowadzi uporządkowane sesje burzy mózgów z wykorzystaniem sprawdzonych technik kreatywnych, by generować pomysły, szukać rozwiązań i przełamywać blokady twórcze.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.