# Use Documentation with AI

> Copy WPsigner documentation into ChatGPT, Claude, Cursor, or any AI assistant using per-page Markdown, topic packs, and the full corpus.

edition: both
Edition: Lite + Pro
AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features.
HTML: https://docs.wpsigner.com/support/use-with-ai/
Markdown: https://docs.wpsigner.com/md/support/use-with-ai.md
Source file: support/use-with-ai.md

---

Every WPsigner docs page has a matching **Markdown** twin built for AI assistants. Use it when Ask AI is unavailable, when you work in Cursor/ChatGPT/Claude, or when you want a portable offline reference.

## Fastest path

1. Open any documentation page.
2. Click **Copy for AI** under the title.
3. Paste into your assistant with a prompt like:

```text
You are helping me configure and use WPsigner, a self-hosted electronic-signature plugin for WordPress.
Use ONLY the documentation I paste as your source of truth.
If something is not covered, say so clearly.
Prefer exact admin menu paths, shortcodes, endpoints, and settings names from the docs.
```

You can also click **View Markdown** to open the `.md` file in the browser and copy it manually.

---

## What we publish for AI

| Resource | URL | Best for |
|----------|-----|----------|
| **Per-page Markdown** | `/md/{slug}.md` | One feature or integration |
| **Lite pack** | [`/md/packs/lite.md`](/md/packs/lite.md) | Lite-safe pages only (`edition: both` + Lite hubs) |
| **Topic packs** | [`/md/README.md`](/md/README.md) (packs listed there) | Setup, security, API, integrations, addons |
| **Complete pack** | [`/md/packs/complete.md`](/md/packs/complete.md) | Full docs in one file |
| **Markdown index** | [`/md/README.md`](/md/README.md) | Catalog of every page + pack |
| **LLM sitemap** | [`/llms.txt`](/llms.txt) | Crawlers and agent discovery |
| **Full corpus text** | [`/llms-full.txt`](/llms-full.txt) | Large-context models |

HTML and Markdown are generated from the **same** source files. If a page exists in the docs, it has a Markdown twin. Every `/md/{slug}.md` file starts with `edition: lite`, `edition: pro`, or `edition: both` so assistants do not invent Pro features for Lite users.

---

## Recommended packs

| Pack | Use when |
|------|----------|
| [Lite](/md/packs/lite.md) | WordPress.org / Lite questions — excludes Pro-only pages |
| [Setup](/md/packs/setup.md) | Installing, hosting, first document, system status |
| [Security](/md/packs/security.md) | Roles, OTP/KYC, Digital ID, TSA, audit, storage |
| [Core features](/md/packs/core-features.md) | Documents, campaigns, portal, workflows, fields |
| [API](/md/packs/api.md) | REST endpoints, auth, webhooks, examples |
| [Integrations](/md/packs/integrations.md) | Forms, Fluent Community, CRM, storage, automation |
| [Addons](/md/packs/addons.md) | Document Builder, Smart Forms, MainWP, Uncanny Automator, importers |
| [Customization](/md/packs/customization.md) | Branding, emails, languages |
| [Support](/md/packs/support.md) | Troubleshooting, FAQ, security disclosure |
| [Complete](/md/packs/complete.md) | Everything (large — use only if the model allows) |

> **tip**
Start with the smallest pack that covers your question. Large packs can overflow model context windows and reduce answer quality.

---

## Example URLs

| HTML page | Markdown twin |
|-----------|---------------|
| [/getting-started/installation/](/getting-started/installation/) | [/md/getting-started/installation.md](/md/getting-started/installation.md) |
| [/core-features/team-roles/](/core-features/team-roles/) | [/md/core-features/team-roles.md](/md/core-features/team-roles.md) |
| [/integrations/fluent-community/](/integrations/fluent-community/) | [/md/integrations/fluent-community.md](/md/integrations/fluent-community.md) |
| [/api/documents/](/api/documents/) | [/md/api/documents.md](/md/api/documents.md) |
| [/addons/document-builder/](/addons/document-builder/) | [/md/addons/document-builder.md](/md/addons/document-builder.md) |
| [/addons/uncanny-automator/](/addons/uncanny-automator/) | [/md/addons/uncanny-automator.md](/md/addons/uncanny-automator.md) |
| [/glossary/](/glossary/) | [/md/glossary.md](/md/glossary.md) |
| [/getting-started/lite-vs-pro/](/getting-started/lite-vs-pro/) | [/md/getting-started/lite-vs-pro.md](/md/getting-started/lite-vs-pro.md) |

Machine-readable map: [`/md/manifest.json`](/md/manifest.json)

---

## Prompt recipes

### Configure a feature

```text
I am setting up WPsigner on my WordPress site.
Using only the Markdown below, give me a numbered checklist with exact admin paths and settings.
Ask me for any missing site-specific details (domain, SMTP, plugins already installed).

```

### Debug an error

```text
WPsigner shows this error: 
Using only the documentation below, list the most likely causes and the exact checks to run.
Do not invent menu names or endpoints that are not in the docs.

```

### Build an integration

```text
I need to connect WPsigner to .
Using only the documentation below, outline prerequisites, configuration steps, webhooks/events, and test plan.

```

---

## Completeness guarantees

On every production build we verify:

1. Every docs source file is exported to `/md/` and the Ask AI corpus.
2. The **complete** pack includes every page (no omissions).
3. Named packs only reference slugs that exist.
4. `llms.txt` and `llms-full.txt` are regenerated from the same source set.

If a Markdown twin is missing for a page, treat it as a docs build bug and report it.

---

## Related resources

- [Troubleshooting](/support/troubleshooting/)
- [FAQ](/support/faq/)
- [Glossary](/glossary/)
- [Lite vs Pro](/getting-started/lite-vs-pro/)
- [REST API Overview](/api/)
- Docs LLM index: [docs.wpsigner.com/llms.txt](https://docs.wpsigner.com/llms.txt)
- Product LLM summary + pricing: [wpsigner.com/llms.txt](https://wpsigner.com/llms.txt) · [Pricing](https://wpsigner.com/pricing/?utm_source=docs&utm_medium=ai&utm_campaign=use-with-ai)