Ryan Malloy e21219be8d Initial docs site: Astro/Starlight with caddy-docker-proxy
- Starlight documentation for mcnanovna and mcpositioner
- 19 pages covering tools, prompts, hardware, and tutorials
- Docker deployment with dev/prod modes
- Makefile for docker compose management
- Custom SVG logos and hero illustration
2026-02-04 13:53:21 -07:00

98 lines
2.7 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
title: Prompts
description: Guided workflow prompts for mcpositioner
---
import { Aside } from '@astrojs/starlight/components';
## Available Prompts
| Prompt | Description |
|--------|-------------|
| `home_positioner` | Guided homing with safety checks |
| `configure_positioner` | Motion parameter tuning |
| `measure_pattern_grid` | Cross-server 3D pattern measurement |
## home_positioner
Guides through safe positioner homing with pre-flight checks.
**Parameters:**
| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `axis` | string | `"both"` | Which axis to home |
**What it covers:**
1. Verify positioner is reachable
2. Check for obstructions
3. Confirm cables have slack
4. Run StallGuard homing
5. Verify homed state
## configure_positioner
Helps tune motion parameters for your specific setup.
**Parameters:**
| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `speed` | float | None | Target speed (steps/sec) |
| `accel` | float | None | Target acceleration |
| `microstepping` | int | None | Microstep divisor |
**What it covers:**
- Parameter reference table
- Speed vs. measurement quality tradeoffs
- Microstepping guide
- Test move verification
## measure_pattern_grid
The key cross-server workflow for automated 3D antenna pattern measurement.
<Aside type="note">
This prompt requires both mcpositioner AND mcnanovna MCP servers to be running.
</Aside>
**Parameters:**
| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `antenna_type` | string | `"dipole"` | Label for metadata |
| `band` | string | `"2m"` | Ham band name |
| `theta_step` | float | `5.0` | Polar angle step (°) |
| `phi_step` | float | `10.0` | Azimuth step (°) |
| `points` | int | `51` | VNA frequency points |
| `settle_ms` | int | `200` | Settle time after move |
**What it covers:**
1. **Pre-flight checks** on both servers
2. **Homing** the positioner
3. **VNA calibration** reminder
4. **Grid measurement** procedure:
- Serpentine path optimization
- S21 extraction method
- Progress tracking
5. **Pattern assembly** format
6. **Resolution tradeoffs** table
**Grid examples:**
| Step Size | Grid Points | Est. Time | Use Case |
|-----------|------------|-----------|----------|
| 10° × 20° | 342 | ~9 min | Quick survey |
| 5° × 10° | 1332 | ~33 min | Standard |
| 2° × 5° | 6552 | ~164 min | High-resolution |
## Using Prompts
In Claude Code, invoke prompts by name:
```
User: Run the measure_pattern_grid prompt for my Yagi on 70cm
Claude: [Uses measure_pattern_grid prompt with antenna_type="yagi", band="70cm"]
```
The prompt provides step-by-step guidance, and Claude executes the tools from both mcpositioner and mcnanovna as needed.