anime-extensions
CLAUDE.md546 starsChanged 15 days agoApache-2.0View on GitHub
Everything about this codebase — commands, architecture, conventions, versioning, CI — lives in the import above (which itself pulls in CONTRIBUTING.md). Claude Code expands @-imports, so both are already in context; don't re-read them. What follows is only guidance specific to working here through Claude Code's tooling. build/ and .history/ are gitignored but still on disk, and both shadow real source files — build/spotless-clean/ mirrors every Kotlin file it formats, and .history/ holds ~3.6M of timestamped Markdown copies. The Grep…
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cherrypick-logSkill
- cherry-pickSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Don't reach for the Android Studio workflow CONTRIBUTING.md describes — the Gradle task is the headless equivalent and is what belongs in a …
≈ “Common” is an estimate: at least 1 in 5 of the 28,029 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
@AGENTS.md
Everything about this codebase — commands, architecture, conventions, versioning, CI — lives in the
import above (which itself pulls in CONTRIBUTING.md). Claude Code expands @-imports, so both are
already in context; don't re-read them. What follows is only guidance specific to working here
through Claude Code's tooling.
Searching
build/ and .history/ are gitignored but still on disk, and both shadow real source files —
build/spotless-clean/ mirrors every Kotlin file it formats, and .history/ holds ~3.6M of
timestamped Markdown copies. The Grep tool skips them (ripgrep honors .gitignore); grep -r run
through Bash does not, and will report a stale duplicate alongside every real hit. When searching
via Bash, pass --exclude-dir=build --exclude-dir=.history, or use Grep instead.
Editing and verifying
- Pick one extension or theme and verify it with its own
:module:compileDebugKotlin. Gradle configures ~330 modules, so an unscoped invocation is a multi-minute no-op for a one-file change. - Don't reach for the Android Studio workflow
CONTRIBUTING.mddescribes — the Gradle task is the headless equivalent and is what belongs in a tool call. spotlessApplyrewrites files on disk. Re-read anything you have edited before further edits, or run it last.
Scope discipline
Each extension is an independent published artifact with its own version code, so a change that looks repo-wide is usually a change to one module. Before editing a second module, confirm it is actually in scope — a stray edit there means an unwanted version bump and an unrelated APK rebuild in CI.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

