chore(linting): refresh configs and sweep auto-fix

Pull in the refreshed linter and tooling configs (editorconfig,
gitignore, gitattributes, prettierignore, prettierrc, markdownlint,
yamllint, env.example, dotnet-tools) and run prettier and markdownlint
in --fix / --write mode across the repo so the existing tree matches
the new rules.

- prettier 2-space indent on yaml/yml and json overrides, asterisk
  strong, underscore emphasis, proseWrap always
- markdownlint MD007 indent aligned to 2 and MD049 to underscore so
  prettier output stays passing
- preflight Block F also ignores CLAUDE.md (gitignored personal file)
- prettierignore extended to keep HellionChat.yaml manifest and the
  NuGet packages.lock.json out of the formatter

No semantic content changed; csharpier, build, full build-suite
(729/729) and the new prettier/markdownlint/yamllint checks all green.
This commit is contained in:
2026-05-17 17:20:55 +02:00
parent 2315f10d91
commit 0220e5d756
53 changed files with 3501 additions and 2630 deletions
+25 -19
View File
@@ -1,13 +1,15 @@
# AI Assistance Disclosure
HellionChat uses AI assistance per the [Dalamud Plugin AI Usage Policy](https://github.com/goatcorp/DalamudPluginsD17/)
at the **Pair** level.
HellionChat uses AI assistance per the
[Dalamud Plugin AI Usage Policy](https://github.com/goatcorp/DalamudPluginsD17/) at the **Pair**
level.
A note up front: HellionChat is currently not submitted to the official Dalamud plugin repository and technically has no
obligation to disclose this. I would rather be upfront about how it is built.
A note up front: HellionChat is currently not submitted to the official Dalamud plugin repository
and technically has no obligation to disclose this. I would rather be upfront about how it is built.
HellionChat is my entry point into game modding and plugin development. I have never written a plugin for a game before.
I work alone, so I get help where I need it. That is not something I want to hide.
HellionChat is my entry point into game modding and plugin development. I have never written a
plugin for a game before. I work alone, so I get help where I need it. That is not something I want
to hide.
## How I Actually Work
@@ -18,12 +20,13 @@ I plan the architecture, decide what gets built, and own every design decision.
- Read the Dalamud log output to verify behaviour
- Run security and privacy audits on anything that touches user data
One of the main reasons I use AI is consistency. I want the HellionChat code to match the style of the upstream Chat 2
codebase and stay readable for anyone who opens the repo, not just for me. Claude helps me catch when I am drifting from
upstream conventions or writing something that only makes sense in my own head.
One of the main reasons I use AI is consistency. I want the HellionChat code to match the style of
the upstream Chat 2 codebase and stay readable for anyone who opens the repo, not just for me.
Claude helps me catch when I am drifting from upstream conventions or writing something that only
makes sense in my own head.
The balance is shifting toward more hand-written work as I get more comfortable with Dalamud and plugin development in
general.
The balance is shifting toward more hand-written work as I get more comfortable with Dalamud and
plugin development in general.
## What AI Is Used For
@@ -34,23 +37,25 @@ general.
## What AI Is Not Used For
- **Visual assets.** Logos, icons, banners, and screenshots are human-drawn or taken from the running game.
- **Visual assets.** Logos, icons, banners, and screenshots are human-drawn or taken from the
running game.
- **German translations.** Written by me as a native speaker.
## What Is Where
Upstream Chat 2 (by Infi & Anna, EUPL-1.2) is the foundation and was not produced with AI assistance.
HellionChat-specific code lives in `HellionChat/Privacy/`, `HellionChat/Export/`,
`HellionChat/Resources/HellionStrings*`, `Ui/SettingsTabs/Privacy.cs`, `Ui/FirstRunWizard.cs`, `Ui/HellionStyle.cs`,
plus the Migrate3 recovery and plugin layout migration in `MessageStore.cs` and `Plugin.cs`. These were developed with
Pair-level assistance as described above.
Upstream Chat 2 (by Infi & Anna, EUPL-1.2) is the foundation and was not produced with AI
assistance. HellionChat-specific code lives in `HellionChat/Privacy/`, `HellionChat/Export/`,
`HellionChat/Resources/HellionStrings*`, `Ui/SettingsTabs/Privacy.cs`, `Ui/FirstRunWizard.cs`,
`Ui/HellionStyle.cs`, plus the Migrate3 recovery and plugin layout migration in `MessageStore.cs`
and `Plugin.cs`. These were developed with Pair-level assistance as described above.
## If AI-Assisted Development Is a Dealbreaker for You
Fair enough. There are solid alternatives:
- [Chat 2](https://github.com/Infiziert90/ChatTwo), the upstream project HellionChat is built on
- [XIV Instant Messenger](https://github.com/NightmareXIV/XIVInstantMessenger), a different approach to FFXIV chat
- [XIV Instant Messenger](https://github.com/NightmareXIV/XIVInstantMessenger), a different approach
to FFXIV chat
Both are good projects. Use what fits you best.
@@ -71,4 +76,5 @@ Both are good projects. Use what fits you best.
## Contact
Questions about this disclosure: <https://gitea.hellion-forge.cloud/JonKazama-Hellion/HellionChat/issues>
Questions about this disclosure:
<https://gitea.hellion-forge.cloud/JonKazama-Hellion/HellionChat/issues>