Skip to content
TheChatArchiveThe Chat Archive
Coherecommand-a-03-2025· CohereHugging Face LMArena Human Preference 140K

I'm interested in terminology, nomenclature, words and names. do not provide me any code…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Geminigemini-2.5-pro’s answer.
  1. User

    I'm interested in terminology, nomenclature, words and names. do not provide me any code unless expressly requested. I am seeking terminology both extant and novel, and primarily engage in divergent thinking patterns of multifarious exploration without judgements. for example, i would like to engage at times with seeking extant nomenclature, and at other times at arriving at aesthetically satisfying neologisms. I value the breadth of approaches, not narrowing down on presupposed "correctness"

    for my first request, i'm interested in a cogent package name for a tool i want to write in go lang. I am a new user to obsidian.md, and am interested in a maximalist approach to the obsidian plugin ecosystem. I consider myself to be the textbook definition of "power user", and Im interested in improving my onboarding process with obsidian. currently, the issue is the limited nature of the community plugins browser. I will be creating a package that interacts with the community-plugins.json to empower me beyond the limitations of the closed source native community plugins browser. I will temporarily be referring to this as "my tool", and remember that ultimately my request is to explore a name for my tool

    as some brief context, here is an example of a motivating limitation. in the obsidian community plugin browser's search, I can only filter search results to include plugins i already have installed. specifically, there is no functionality to exclude already installed plugins from the search results. as the number of my installed plugins increased, every search result has gotten needlessly cluttered.

    I am also seeking to use my tool to better organize the plugins conceptually. I still need to iron out the details of the implementation, but Ideally I would like to identify some "obsidian component" and map community plugins to those components. that way, my tool could hypothetically work with the set of all "metadata components". again, i don't tell you any of this for you to aid in the implementation of doing so. this is context to aid in the process of naming my tool

  2. Cohere Assistant

    Given your maximalist, power-user approach to Obsidian and your desire for a tool that transcends the limitations of the native plugin browser, let's explore nomenclature that captures the essence of your project. We'll aim for names that are both extant (drawing from relevant terminology) and novel (aesthetically satisfying neologisms), aligning with your divergent thinking patterns.

    Extant Terminology-Inspired Names:

    1. Obsidian Nexus

      • Rationale: "Nexus" implies a central hub or connection point, reflecting your tool's role in organizing and managing plugins as a core component of your Obsidian workflow.
    2. Plugin Cartographer

      • Rationale: "Cartographer" evokes mapping and exploration, aligning with your goal of conceptually organizing plugins into "Obsidian components."
    3. Obsidian Forge

      • Rationale: "Forge" suggests shaping and crafting, emphasizing your tool's role in refining and enhancing the plugin ecosystem to suit your needs.
    4. MetaObsidian

      • Rationale: "Meta" highlights the tool's focus on metadata and higher-level organization, while "Obsidian" ties it directly to the platform.
    5. Plugin Pantheon

      • Rationale: "Pantheon" conveys a comprehensive, organized collection of plugins, akin to a hall of gods, reflecting your maximalist approach.

    Novel Neologisms:

    1. Obsidiana

      • Rationale: A blend of "Obsidian" and the suffix "-ana," often used to denote a collection or anthology (e.g., "Americana"). It suggests a curated, comprehensive set of plugins.
    2. Plugithon

      • Rationale: A portmanteau of "plugin" and "marathon," implying an exhaustive, enduring engagement with the plugin ecosystem.
    3. Obsidify

      • Rationale: A playful combination of "Obsidian" and "amplify," suggesting your tool enhances and expands the Obsidian experience.
    4. Plugiscape

      • Rationale: A fusion of "plugin" and "landscape," evoking a broad, organized view of the plugin ecosystem.
    5. Obsidient

      • Rationale: A blend of "Obsidian" and "omnipresent" or "omnipotent," reflecting your tool's all-encompassing role in managing plugins.

    Conceptual Names:

    1. The Obsidian Atlas

      • Rationale: "Atlas" symbolizes a comprehensive guide or map, aligning with your goal of organizing plugins conceptually.
    2. Plugin Alchemy

      • Rationale: "Alchemy" suggests transformation and refinement, reflecting your tool's role in turning raw plugins into a tailored, organized system.
    3. Obsidian Symphony

      • Rationale: "Symphony" implies harmony and coordination, capturing the idea of plugins working together seamlessly under your tool's guidance.
    4. Plugin Cosmos

      • Rationale: "Cosmos" evokes a vast, organized universe, mirroring your maximalist approach to the plugin ecosystem.
    5. Obsidian Prism

      • Rationale: "Prism" suggests breaking down and organizing components (like light into colors), aligning with your goal of mapping plugins to "Obsidian components."

    Final Suggestion:

    If I were to distill these into a single, aesthetically satisfying and conceptually rich name, I'd propose:

    Obsidiana
    It’s concise, directly tied to Obsidian, and carries the connotation of a curated, maximalist collection. It also has a pleasing, almost mystical ring to it, which aligns with the exploratory and creative nature of your project.

    Let me know if you'd like to further refine or explore additional directions!

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.