Archive AI files, rewrite CLAUDE.md and README.md as human-only

Artfight staff confirmed AI-assisted HTML is not permitted under their
rules. Archived original AI-assisted CLAUDE.md, README.md, and all
ai-chats session logs to archive/. New CLAUDE.md explicitly blocks AI
from editing HTML files. New README.md documents the ruling and links
to archive/ for transparency.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-06-14 16:15:42 -05:00
parent 20b609349e
commit a19b369d01
8 changed files with 237 additions and 140 deletions

View File

@@ -21,33 +21,19 @@ My own Artfight character pages. These are personal, but you're welcome to use t
Everything here is **free to use and modify** for your own Artfight pages.
**Credit is required** — please either:
- Link back to this repository, or
- Credit **lavender-daydream** on the page where you use the code
---
## ⚠️ Artfight's AI Policy & This Repo
## 🤖 AI Policy
Artfight does not allow AI-generated content to be submitted as attacks or used in character art. This repo uses AI (Claude) to help **write HTML code** — not to generate any artwork or images.
Artfight does not allow AI tools to be used in content on the platform — including AI-assisted HTML. I confirmed this directly with Artfight staff.
I believe these are different things, but Artfight's rules are broad and Claude is explicitly named. **I have reached out to Artfight staff for clarification** and will update this section once I have an answer.
**All HTML in this repo is written entirely by hand.** No AI was used to generate any code in the templates or character pages.
In the meantime:
- **Do not** use AI to generate any artwork for your Artfight characters or attacks
- This repo is **code only** — all art on your profile is your responsibility to keep within Artfight's rules
- If Artfight rules that AI-assisted HTML also falls under their policy, I will update this repo accordingly
---
## 🤖 AI Transparency
I use AI (Claude Code) as a coding assistant when building some of these files. Because art communities have valid concerns about AI, I believe in being fully transparent:
- Every file has a comment at the top stating whether AI was involved and exactly what it did
- A full log is available in [AI-DISCLOSURE.md](AI-DISCLOSURE.md) — written in plain English, no coding knowledge needed to read it
You can use this information to decide for yourself whether you're comfortable using a particular file.
Early setup work on this repo (git config, documentation) was done with AI assistance before I received this ruling. Those session logs are preserved in [`archive/`](archive/) for full transparency — you can see exactly what was done and when.
---