> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cosmon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Connect Nexus to your tools and run your first command.

## Requirements

See [Supported Software](/getting-started/supported-software) for the full list of supported CAD and simulation platforms. Nexus runs on Windows 10 or Windows 11 (64-bit), and on Linux (x86\_64, glibc 2.28 or newer) — see [Linux system requirements](/getting-started/supported-software#linux-system-requirements).

***

## Connect in three steps

<Note>
  **How long does this take?** About 5 minutes end to end — roughly 2 minutes to
  download and install the Cosmon Connector, then it auto-detects your CAD/CAE
  software the first time you open it. No manual configuration required.
</Note>

<Steps>
  <Step title="Sign in">
    Go to [desktop-app.cosmon.com/login](https://desktop-app.cosmon.com/login) and sign in with your Cosmon account.
  </Step>

  <Step title="Install the Cosmon Connector">
    Download and install the Cosmon Connector on your engineering workstation. This is the bridge between Nexus and your installed CAD/CAE software.

    <Note>The Connector runs locally on your machine. Your files and models never leave your workstation without your explicit action.</Note>
  </Step>

  <Step title="Open your software and connect">
    Launch SolidWorks, Ansys, COMSOL, or Abaqus. The Connector will detect the running application and establish a connection automatically. You'll see a status indicator in the Nexus interface confirming the link.
  </Step>
</Steps>

## Your first prompt

Once connected, try a simple command to confirm everything is working.

**In SolidWorks:**

```text theme={null}
Open a new part and create a 50mm x 50mm x 10mm rectangular block.
```

**In Ansys Mechanical:**

```text theme={null}
What's the current state of the model? List the boundary conditions and any active load steps.
```

Nexus will describe what it's doing and confirm the result.

***

## Prompting Guide

The quality of your results depends on how you prompt. These eight rules will help you get reliable, precise outputs from Nexus every time.

### 1. Lead with outcome

Start with what you're trying to achieve, not the specific operations you think are needed. Nexus can figure out the steps — your job is to define the goal.

<CardGroup cols={2}>
  <Card title="Better" icon="check">
    "Create a support bracket that can withstand a 200N downward load at the free end with a safety factor of 2 or greater."
  </Card>

  <Card title="Worse" icon="xmark">
    "Add a fillet here and make the wall thicker."
  </Card>
</CardGroup>

### 2. Be specific

Include exact values: dimensions, tolerances, material grades, load magnitudes, mesh sizes. Precision in equals precision out.

```text theme={null}
Create a cylindrical boss, diameter 12mm, height 8mm, centred on the top face of the bracket. Add a 1mm chamfer on the top edge.
```

### 3. Give file paths

When referencing parts, assemblies, or simulation files, include the full path. This removes ambiguity and ensures Nexus acts on the right file.

```text theme={null}
Open C:/Projects/Arm_Assembly/arm_v4.SLDASM and suppress the Cover_Plate component.
```

### 4. State what should not change

Tell Nexus which features, constraints, or dimensions are locked. This is especially important when editing existing models.

```text theme={null}
Increase the rib thickness from 3mm to 5mm. Do not change the bolt hole pattern or the outer profile.
```

### 5. Chain steps

For multi-step workflows, list the steps explicitly and in order. Nexus will confirm progress at each stage before moving on.

```text theme={null}
1. Apply Structural Steel to all bodies.
2. Mesh using a 3mm element size with refinement at fillets.
3. Apply a fixed support at the base face.
4. Apply a 500N force in the -Y direction on the top face.
5. Run the static structural analysis.
```

### 6. Attach context

Share relevant background: design specs, applicable standards, prior results, or customer requirements. This helps Nexus make better decisions throughout the task.

```text theme={null}
This bracket must comply with ISO 2768-m tolerancing. The part will be injection-moulded in PA66-GF30. Wall thickness must stay between 2.5mm and 4mm for uniform cooling.
```

### 7. Describe symptoms when debugging

When something isn't working, describe what you observe — not the fix you think is needed. Nexus diagnoses better from symptoms.

<CardGroup cols={2}>
  <Card title="Better" icon="check">
    "The solver is failing at step 3 with: 'Highly distorted elements detected near node 4521.' It's happening at the sharp re-entrant corner on the inner rib."
  </Card>

  <Card title="Worse" icon="xmark">
    "Fix the mesh error."
  </Card>
</CardGroup>

### 8. Iterate

You don't need to get the perfect prompt first time. Start with a clear goal, review the result, then refine. Nexus maintains context across the conversation.

```text theme={null}
That looks good. Now reduce the fillet radius to 2mm, re-run the mesh, and check whether the maximum stress changes significantly.
```