CTrack V6.0 Manual — Automated Documentation Workflow

Overview

This workflow uses Claude Desktop with two MCP servers to semi-automate the creation of the CTrack V6.0 user manual in Docusaurus format:

• windows-mcp — navigates the CTrack MFC application via the Windows Accessibility tree
• @ai-capabilities-suite/mcp-screenshot — captures targeted window screenshots

Screenshots land directly in C:\CTrack-software\Software\V6.0\Docusaurus\static\img\manual\ and Docusaurus pages reference them as /img/manual/<filename>.png.

Prerequisites

1. Both MCP servers running (green in Claude Desktop settings)
2. CTrack V6.0 application launched and in a known state
3. Target folder exists: static\img\manual\
4. Docusaurus project at C:\CTrack-software\Software\V6.0\Docusaurus\

Prompt Templates

1. Discovery — Inventory all views

Use this first to let Claude map out what's available in CTrack before capturing anything.

Using windows-mcp, find the CTrack window. List all top-level menu items
and any toolbar buttons visible in the main window.
For each menu, expand it and list the submenu entries.
Present the result as a structured outline I can use to plan the manual chapters.
Do NOT take screenshots yet.

2. Single dialog capture + documentation

Use this for one specific view at a time. Most reliable approach.

I need a manual page for the [DIALOG NAME] dialog in CTrack.

Steps:
1. Use windows-mcp to find the CTrack window
2. Navigate to: [Menu > Submenu > Item] to open the dialog
3. Wait 2 seconds for the dialog to fully render
4. Use the screenshot tool to capture ONLY the dialog window
   Save as: C:\CTrack-software\Software\V6.0\Docusaurus\static\img\manual\[filename].png
5. Write a Docusaurus markdown page that:
   - Has a YAML frontmatter with sidebar_position
   - Shows the screenshot: ![Dialog Name](/img/manual/[filename].png)
   - Describes each field/control visible in the dialog
   - Includes any tips or notes about usage
   - Uses CTech manual style (professional, concise)
6. Show me the markdown content (don't save the .md file yet, I'll review first)

Example filled in:

I need a manual page for the Tracker Settings dialog in CTrack.

Steps:
1. Use windows-mcp to find the CTrack window
2. Navigate to: Settings > Tracker > Configuration to open the dialog
3. Wait 2 seconds for the dialog to fully render
4. Use the screenshot tool to capture ONLY the dialog window
   Save as: C:\CTrack-software\Software\V6.0\Docusaurus\static\img\manual\tracker-settings.png
5. Write a Docusaurus markdown page that:
   - Has a YAML frontmatter with sidebar_position
   - Shows the screenshot: ![Tracker Settings](/img/manual/tracker-settings.png)
   - Describes each field/control visible in the dialog
   - Includes any tips or notes about usage
   - Uses CTech manual style (professional, concise)
6. Show me the markdown content (don't save the .md file yet, I'll review first)

3. Batch capture — Multiple views in sequence

Use this when you have a clear list of views to document. Works best for simple dialogs without complex navigation.

I need screenshots of the following CTrack dialogs. For each one:
- Navigate to it using windows-mcp
- Wait 2 seconds after it opens
- Capture the dialog window only
- Save to C:\CTrack-software\Software\V6.0\Docusaurus\static\img\manual\
- Close the dialog before opening the next one

Dialogs to capture:
1. File > New Project           → save as new-project.png
2. File > Open Project          → save as open-project.png  
3. Settings > General           → save as settings-general.png
4. Settings > Tracker           → save as settings-tracker.png
5. Tools > Coordinate System    → save as coordinate-system.png

After all captures are done, list which succeeded and which failed.

4. Tabbed dialog — Capture each tab

MFC tabbed dialogs need special handling: navigate to each tab before capturing.

The [DIALOG NAME] dialog has multiple tabs. For each tab:
1. Open the dialog via [Menu > Item]
2. Click on the tab named [Tab1]
3. Wait 1 second
4. Capture the window → save as [dialog]-[tab1].png
5. Click on the next tab [Tab2]
6. Wait 1 second  
7. Capture → save as [dialog]-[tab2].png
8. Continue for all tabs
9. Close the dialog

Save all screenshots to:
C:\CTrack-software\Software\V6.0\Docusaurus\static\img\manual\

Then write a single Docusaurus page that documents all tabs,
with each tab as a ## heading showing its screenshot and field descriptions.

5. Toolbar documentation

Toolbars are tricky because buttons are small. Consider combining a full toolbar screenshot with individual tooltip descriptions.

I need to document the main toolbar in CTrack.

1. Use windows-mcp to find the CTrack main window
2. Capture the full main window → save as main-window-overview.png
3. Using the accessibility tree, list all toolbar buttons with their:
   - Button name/label
   - Tooltip text (if available)
   - Enabled/disabled state
4. Write a Docusaurus page with:
   - The overview screenshot at the top
   - A table listing each toolbar button, its icon position (left to right),
     name, and description of what it does

Save screenshots to:
C:\CTrack-software\Software\V6.0\Docusaurus\static\img\manual\

6. Context menu capture

MFC context menus lose focus easily. Use this careful approach.

I need to capture the right-click context menu in the [VIEW NAME] view.

IMPORTANT: MFC context menus close when they lose focus. 
Use this sequence carefully:
1. Navigate to the [VIEW NAME] view in CTrack
2. Right-click at the center of the view area
3. IMMEDIATELY capture the full CTrack window (not just the menu)
   → save as [view]-context-menu.png
4. Press Escape to close the menu

Save to: C:\CTrack-software\Software\V6.0\Docusaurus\static\img\manual\

Docusaurus Page Template

Use this as the target format for generated documentation pages:

---
sidebar_position: N
title: "Dialog/Feature Name"
description: "Brief description for SEO"
---

# Dialog/Feature Name

Brief introduction explaining when and why the user would use this feature.

## Opening the Dialog

Navigate to **Menu > Submenu > Item** or use the keyboard shortcut `Ctrl+X`.

## Overview

![Dialog Name](/img/manual/dialog-name.png)

## Fields and Controls

### Field Name
Description of what this field does, valid values, and any defaults.

### Another Field
Description...

## Common Tasks

### Task 1: Doing something specific
1. Step one
2. Step two
3. Step three

:::tip
Helpful tip about this dialog.
:::

:::warning
Important warning about potential issues.
:::

Sidebar Configuration

After generating pages, update sidebars.js to organize them. Suggested structure for CTrack manual:

const sidebars = {
  manual: [
    'intro',
    {
      type: 'category',
      label: 'Getting Started',
      items: ['installation', 'first-project', 'ui-overview'],
    },
    {
      type: 'category',
      label: 'Tracker Setup',
      items: ['tracker-connection', 'tracker-settings', 'coordinate-systems'],
    },
    {
      type: 'category',
      label: 'Measurement',
      items: ['single-point', 'continuous', 'scanning'],
    },
    {
      type: 'category',
      label: 'Analysis',
      items: ['best-fit', 'deviation', 'reports'],
    },
    {
      type: 'category',
      label: 'Settings',
      items: ['general-settings', 'display-options', 'export-formats'],
    },
  ],
};

Troubleshooting

File Naming Convention

Use lowercase kebab-case for all screenshot files:

static/img/manual/
├── main-window-overview.png
├── new-project.png
├── tracker-settings.png
├── tracker-settings-general-tab.png
├── tracker-settings-network-tab.png
├── coordinate-system-dialog.png
├── measurement-toolbar.png
├── best-fit-results.png
└── ...

This keeps Docusaurus image references clean and predictable: