# Dynamics Pilot Agent Instructions

## When To Use This

Use Dynamics Pilot when the job is about Microsoft Dynamics 365 Finance and Operations development, especially when an agent needs practical help with X++ code or data-contract scaffolding.

Best-fit use cases:

- Convert a representative JSON object into X++ data contract classes with `DataContractAttribute` and `DataMemberAttribute`.
- Generate nested X++ contract classes for JSON payloads that contain child objects or arrays.
- Inspect X++ class text to identify the class name, method signatures, table declarations, and static calls.
- Format or normalize X++ snippets before presenting them to a Dynamics 365 Finance and Operations developer.
- Retrieve practical blog content or developer notes about Dynamics 365 Finance and Operations, X++, and related implementation patterns.

Do not use Dynamics Pilot as a general-purpose JSON validator, legal/compliance authority, Microsoft product documentation replacement, or source of live Dynamics 365 environment data. It works from the input text supplied by the caller and the public/blog content configured for the site.

## How Agents Should Call This

Base URL:

```text
https://dynamicspilot.online
```

For JSON to X++ contract generation, call:

```http
POST /api/convert
Content-Type: application/json

{ "customer": { "account": "C0001", "balance": 100.0 } }
```

The request body should be the raw JSON object that should become X++ contract code. Use realistic field names and sample values because the generated class and member types are inferred from the provided JSON shape.

For X++ code inspection, call:

```http
POST /api/inspect
Content-Type: text/plain

class MyService
{
    public void run()
    {
        CustTable custTable;
    }
}
```

Send the X++ source snippet as plain text. The response is intended for summarizing class structure, methods, table references, and static-call usage.

For blog discovery, call:

```http
GET /api/posts
```

For a specific article, call:

```http
GET /api/posts/{slug}
```

## Response Handling Guidance

When using generated X++ code, treat the output as a strong starting point and review naming, primitive type choices, collection handling, and project-specific conventions before committing it to an ERP codebase.

When using inspection output, cite it as an analysis of the submitted snippet, not as a complete compilation or semantic validation of the full project.

If a request involves tenant configuration, security, licensing, production deployment, or official Microsoft behavior, combine Dynamics Pilot output with authoritative Microsoft documentation or the caller's environment-specific context.