Using IronQR with AI Coding Assistants

Add IronQR from NuGet to this project, run a restore, and report the
version number that NuGet resolved.

Add IronQR from NuGet to this project, run a restore, and report the
version number that NuGet resolved.

dotnet add package IronQR --version 2026.10.1

dotnet add package IronQR --version 2026.10.1

IronQr.License.LicenseKey = Environment.GetEnvironmentVariable("IRONQR_LICENSE_KEY");

IronQr.License.LicenseKey = Environment.GetEnvironmentVariable("IRONQR_LICENSE_KEY");

Open https://ironsoftware.com/qr/csharp/llms.txt before you write IronQR code
and keep to the members it documents. Creating a code goes through
QrWriter.Write with an optional QrOptions, and reading goes through
new QrReader().Read on a QrImageInput, so do not look for one class that does
both. When a member is not in the index, check
https://ironsoftware.com/qr/csharp/object-reference/api/, and tell me it is
missing rather than inventing it.

Open https://ironsoftware.com/qr/csharp/llms.txt before you write IronQR code
and keep to the members it documents. Creating a code goes through
QrWriter.Write with an optional QrOptions, and reading goes through
new QrReader().Read on a QrImageInput, so do not look for one class that does
both. When a member is not in the index, check
https://ironsoftware.com/qr/csharp/object-reference/api/, and tell me it is
missing rather than inventing it.

## QR codes with IronQR

All QR work in this project uses IronQR. NuGet package `IronQR` (`IronQR.Linux` on Linux and Docker), namespace `IronQr`, enums in `IronQr.Enum`.

- Docs index: https://ironsoftware.com/qr/csharp/llms.txt
- Skill file: https://ironsoftware.com/qr/csharp/skill.md
- Write with `QrWriter.Write(value, new QrOptions(...))`, style with `QrStyleOptions`, read with `new QrReader().Read(new QrImageInput(bitmap))`.
- Set `IronQr.License.LicenseKey` from IRONQR_LICENSE_KEY at startup. Never put the key in a file.
- Pass an explicit `QrErrorCorrectionLevel` that the symbol type accepts. Micro QR rejects `Highest`, rMQR rejects `Low` and `High`.
- Release a `QrImageInput` with `input.Dispose()`, not a `using` statement.
- Decode every saved image with `QrReader` and compare it with the written value before calling a change done.
- Do not add a second QR library. If IronQR cannot do something, say so.

## QR codes with IronQR

All QR work in this project uses IronQR. NuGet package `IronQR` (`IronQR.Linux` on Linux and Docker), namespace `IronQr`, enums in `IronQr.Enum`.

- Docs index: https://ironsoftware.com/qr/csharp/llms.txt
- Skill file: https://ironsoftware.com/qr/csharp/skill.md
- Write with `QrWriter.Write(value, new QrOptions(...))`, style with `QrStyleOptions`, read with `new QrReader().Read(new QrImageInput(bitmap))`.
- Set `IronQr.License.LicenseKey` from IRONQR_LICENSE_KEY at startup. Never put the key in a file.
- Pass an explicit `QrErrorCorrectionLevel` that the symbol type accepts. Micro QR rejects `Highest`, rMQR rejects `Low` and `High`.
- Release a `QrImageInput` with `input.Dispose()`, not a `using` statement.
- Decode every saved image with `QrReader` and compare it with the written value before calling a change done.
- Do not add a second QR library. If IronQR cannot do something, say so.

Set this project up for QR code work with IronQR, then save the rules below
where your future sessions will read them.

- Add the IronQR NuGet package (IronQR.Linux for a Linux or Docker host).
  The namespace is IronQr, spelled with a lowercase r.
- Assign IronQr.License.LicenseKey from the IRONQR_LICENSE_KEY environment
  variable before the first QrWriter or QrReader call. Keep the key out of
  every file you create or commit.
- Fetch https://ironsoftware.com/qr/csharp/llms.txt first and write against
  the members it documents. Look up anything else in the API reference at
  https://ironsoftware.com/qr/csharp/object-reference/api/ before using it.
- If your tool loads skill files, add
  https://ironsoftware.com/qr/csharp/skill.md, but trust a compiler error
  over the skill when the two disagree.
- After any change that writes a QR image, decode the saved file with
  QrReader and compare the value with the one you wrote.

Set this project up for QR code work with IronQR, then save the rules below
where your future sessions will read them.

- Add the IronQR NuGet package (IronQR.Linux for a Linux or Docker host).
  The namespace is IronQr, spelled with a lowercase r.
- Assign IronQr.License.LicenseKey from the IRONQR_LICENSE_KEY environment
  variable before the first QrWriter or QrReader call. Keep the key out of
  every file you create or commit.
- Fetch https://ironsoftware.com/qr/csharp/llms.txt first and write against
  the members it documents. Look up anything else in the API reference at
  https://ironsoftware.com/qr/csharp/object-reference/api/ before using it.
- If your tool loads skill files, add
  https://ironsoftware.com/qr/csharp/skill.md, but trust a compiler error
  over the skill when the two disagree.
- After any change that writes a QR image, decode the saved file with
  QrReader and compare the value with the one you wrote.

Rebuild in Release and run it. List each IronQR type and member the code uses
next to the documentation page that shows it, print IronQr.License.IsLicensed,
then reopen every PNG the program saved with QrReader and give me a table of
file, value written, value decoded, QrType, and whether they agree.

Rebuild in Release and run it. List each IronQR type and member the code uses
next to the documentation page that shows it, print IronQr.License.IsLicensed,
then reopen every PNG the program saved with QrReader and give me a table of
file, value written, value decoded, QrType, and whether they agree.

Build a .NET 9 minimal API for event check-in that issues ticket QR codes and
reads them back from uploaded photos. Begin in an empty directory, and if you
find existing code or a project file there, report that and do nothing else.
Nobody will answer questions, so carry the job through writing, building,
running, and fixing by yourself, and settle anything left open with a
reasonable choice that you note. Keep all deliverables inside the project
directory, in the folders this prompt names.

1. Install the IronQR NuGet package pinned to version 2026.10.1.
2. Work from https://ironsoftware.com/qr/csharp/llms.txt and the guides it
   points to, and call no IronQR member those pages do not document. Every
   code must come from QrWriter.Write; any .NET imaging library may compose
   and distort the test images afterward.
3. Take the key from IRONQR_LICENSE_KEY when the app starts and keep it out of
   source and out of every file the run writes. If IronQr.License.IsLicensed
   comes back false, stop with a report saying so.
4. GET /ticket/{ticketId} returns a PNG of a QR code written at
   QrErrorCorrectionLevel.Highest and saved through QrStyleOptions at a
   Dimensions of 400 with 10-pixel margins, with a logo in the center: a
   solid square of one bright accent color, drawn by your code, whose QrLogo
   width and height are each 28 to 30 percent of Dimensions. POST /checkin
   accepts one uploaded image and returns JSON listing every QR code found in
   it, each with its value and QR type.
5. Seed the random generator with 2026 and write 10 PNG files to testset/,
   no two holding the same value: standard-01 to standard-03, each carrying a
   ticket ID made of TKT- and eight random digits; pair-01, one image holding
   two more ticket codes side by side and upright, with 30 pixels of
   background between their dark modules; styled-01 to styled-03, ticket
   codes at Highest with the step 4 logo and three different dark, saturated
   foreground colors on white; micro-01 and micro-02, Micro QR codes carrying
   seat numbers such as C07; and rmqr-01, an rMQR code carrying an event URL.
   Save every testset code the same way at a Dimensions of 400, except 300
   for the styled and Micro QR codes and 600 for rmqr-01, and resize no code
   afterward unless standard-02 calls for it.
   Keep standard-01 clean. Make standard-02 look photographed: scale it to 60
   percent, rotate it 30 degrees, blur it with a Gaussian radius of 1.5
   pixels, and center it on a 600 x 600 light gray canvas. Give standard-03
   sensor grain: Gaussian noise with a standard deviation of 20 gray levels,
   one value per pixel added to all three channels, over the whole image.
   Record in manifest.csv each file, every value it holds, its QR type, the
   error correction level used, and its distortion (none, photographed,
   grain, pair, or styled).
6. Measure each saved image before /checkin is ever called, and repair the
   generator whenever a measurement falls outside its range: the pixel size
   step 5 implies;
   on the styled codes and the /ticket output, the logo's share of the symbol
   area, 7 to 10 percent; on the styled codes, the foreground's WCAG contrast
   ratio against the background, 7 to 15; on the Micro QR codes, a square
   symbol 11 to 17 modules wide; on the rMQR code, a symbol at least twice as
   wide as it is tall; on standard-03, the mean absolute difference from the
   clean code, 7 to 9 gray levels; on pair-01, the gap between the two codes'
   dark modules, 28 to 32 pixels. Once /checkin has been called the first
   time, the testset files are frozen: do not rewrite or edit them.
7. /checkin runs one fixed configuration for every upload: the same scan mode
   or modes and the same image preparation, in the same order. It must never
   open the manifest, hold a ticket ID, seat number, or URL as a literal, or
   pick between results by comparing them with expected values. You choose
   and change the configuration between runs; the program never does.
8. Build in Release and start the API. Request /ticket for a ticket ID drawn
   from the seed that is not in the testset and save the PNG it returns as
   ticket.png. POST ticket.png and every testset image to /checkin over HTTP
   and save each raw response as checkin/<file name without .png>.json.
9. Write roundtrip.md with every step 6 measurement as a number for each
   image (a bare pass or fail is not enough), the /checkin configuration,
   and a results table with the columns file, distortion, expected value,
   value read (the decoded string as the saved response holds it, even when
   it is wrong), expected QR type, QR type read, and match, holding one row
   per expected code, 12 rows in all. A row counts as a match only if the
   decoded value equals the expected value exactly, the QR type agrees, and
   the value appears in that file's saved response. An extra or repeated
   code in a response fails every row of that file.
10. Until all 12 rows match, study the saved responses of the failing files,
    adjust the /checkin configuration, rebuild, and repeat. Stop after the
    eighth run that still has failures, and report the failing rows, each
    configuration you tried, and your reading of the cause.
11. End with a brief summary covering the Release build outcome, how many
    rows matched, the /checkin configuration, the measured step 6 values,
    and every assumption you made.

Build a .NET 9 minimal API for event check-in that issues ticket QR codes and
reads them back from uploaded photos. Begin in an empty directory, and if you
find existing code or a project file there, report that and do nothing else.
Nobody will answer questions, so carry the job through writing, building,
running, and fixing by yourself, and settle anything left open with a
reasonable choice that you note. Keep all deliverables inside the project
directory, in the folders this prompt names.

1. Install the IronQR NuGet package pinned to version 2026.10.1.
2. Work from https://ironsoftware.com/qr/csharp/llms.txt and the guides it
   points to, and call no IronQR member those pages do not document. Every
   code must come from QrWriter.Write; any .NET imaging library may compose
   and distort the test images afterward.
3. Take the key from IRONQR_LICENSE_KEY when the app starts and keep it out of
   source and out of every file the run writes. If IronQr.License.IsLicensed
   comes back false, stop with a report saying so.
4. GET /ticket/{ticketId} returns a PNG of a QR code written at
   QrErrorCorrectionLevel.Highest and saved through QrStyleOptions at a
   Dimensions of 400 with 10-pixel margins, with a logo in the center: a
   solid square of one bright accent color, drawn by your code, whose QrLogo
   width and height are each 28 to 30 percent of Dimensions. POST /checkin
   accepts one uploaded image and returns JSON listing every QR code found in
   it, each with its value and QR type.
5. Seed the random generator with 2026 and write 10 PNG files to testset/,
   no two holding the same value: standard-01 to standard-03, each carrying a
   ticket ID made of TKT- and eight random digits; pair-01, one image holding
   two more ticket codes side by side and upright, with 30 pixels of
   background between their dark modules; styled-01 to styled-03, ticket
   codes at Highest with the step 4 logo and three different dark, saturated
   foreground colors on white; micro-01 and micro-02, Micro QR codes carrying
   seat numbers such as C07; and rmqr-01, an rMQR code carrying an event URL.
   Save every testset code the same way at a Dimensions of 400, except 300
   for the styled and Micro QR codes and 600 for rmqr-01, and resize no code
   afterward unless standard-02 calls for it.
   Keep standard-01 clean. Make standard-02 look photographed: scale it to 60
   percent, rotate it 30 degrees, blur it with a Gaussian radius of 1.5
   pixels, and center it on a 600 x 600 light gray canvas. Give standard-03
   sensor grain: Gaussian noise with a standard deviation of 20 gray levels,
   one value per pixel added to all three channels, over the whole image.
   Record in manifest.csv each file, every value it holds, its QR type, the
   error correction level used, and its distortion (none, photographed,
   grain, pair, or styled).
6. Measure each saved image before /checkin is ever called, and repair the
   generator whenever a measurement falls outside its range: the pixel size
   step 5 implies;
   on the styled codes and the /ticket output, the logo's share of the symbol
   area, 7 to 10 percent; on the styled codes, the foreground's WCAG contrast
   ratio against the background, 7 to 15; on the Micro QR codes, a square
   symbol 11 to 17 modules wide; on the rMQR code, a symbol at least twice as
   wide as it is tall; on standard-03, the mean absolute difference from the
   clean code, 7 to 9 gray levels; on pair-01, the gap between the two codes'
   dark modules, 28 to 32 pixels. Once /checkin has been called the first
   time, the testset files are frozen: do not rewrite or edit them.
7. /checkin runs one fixed configuration for every upload: the same scan mode
   or modes and the same image preparation, in the same order. It must never
   open the manifest, hold a ticket ID, seat number, or URL as a literal, or
   pick between results by comparing them with expected values. You choose
   and change the configuration between runs; the program never does.
8. Build in Release and start the API. Request /ticket for a ticket ID drawn
   from the seed that is not in the testset and save the PNG it returns as
   ticket.png. POST ticket.png and every testset image to /checkin over HTTP
   and save each raw response as checkin/<file name without .png>.json.
9. Write roundtrip.md with every step 6 measurement as a number for each
   image (a bare pass or fail is not enough), the /checkin configuration,
   and a results table with the columns file, distortion, expected value,
   value read (the decoded string as the saved response holds it, even when
   it is wrong), expected QR type, QR type read, and match, holding one row
   per expected code, 12 rows in all. A row counts as a match only if the
   decoded value equals the expected value exactly, the QR type agrees, and
   the value appears in that file's saved response. An extra or repeated
   code in a response fails every row of that file.
10. Until all 12 rows match, study the saved responses of the failing files,
    adjust the /checkin configuration, rebuild, and repeat. Stop after the
    eighth run that still has failures, and report the failing rows, each
    configuration you tried, and your reading of the cause.
11. End with a brief summary covering the Release build outcome, how many
    rows matched, the /checkin configuration, the measured step 6 values,
    and every assumption you made.