agentleFS
rainxchzedrainxchzed/Github-Store/AGENTS.md

Github-Store

AGENTS.md20k starsChanged 10 days agoApache-2.0View on GitHub

Open-source app store for apps released on GitHub, Codeberg and other Forgejo forges. Kotlin Multiplatform and Compose Multiplatform: one codebase for Android (min API 26) and Desktop (Windows, macOS, Linux). Package zed.rainxch.githubstore. JDK 21+ and the Android SDK. Sign-in uses GITHUBCLIENTID from local.properties when set. CI runs these on every pull request. Existing findings live in committed baselines, so only new ones fail. In Claude Code, /verify runs the same steps. CI also lints agent docs with agnix. Details and…

We split this AGENTS.md into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use Komi* components and LocalPersonality tokens, not MaterialTheme or color literals.

    line 44
  2. Very specific:

    All user-visible text, content descriptions included, comes from Res.string.

    line 45
  3. Distinctive:

    No KDoc and no comments that restate the code.

    line 46
  4. Distinctive:

    Don't guess APIs, versions or flags.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Komi Store

Open-source app store for apps released on GitHub, Codeberg and other Forgejo forges. Kotlin Multiplatform and Compose Multiplatform: one codebase for Android (min API 26) and Desktop (Windows, macOS, Linux). Package zed.rainxch.githubstore.

Map

  • composeApp/: shared app code and the Desktop entry point: navigation (GithubStoreGraph, AppNavigation), DI wiring (ViewModelsModule, initKoin)
  • androidApp/: the Android application: MainActivity, GithubStoreApp, manifest, resources, R8 rules
  • core/domain: interfaces, models and pure logic, no framework imports
  • core/data: repositories, Ktor clients, Room, Koin modules, Android and Desktop implementations
  • core/presentation: the Personality design system, Komi* components, strings for 14 locales
  • feature/<name>/{domain,data,presentation}: one folder per feature; some have only presentation
  • konsist-test/: architecture rules; build-logic/convention/: convention plugins; versions in gradle/libs.versions.toml

Build and run

./gradlew :androidApp:assembleDebug     # Android APK
./gradlew :composeApp:run               # Desktop

JDK 21+ and the Android SDK. Sign-in uses GITHUB_CLIENT_ID from local.properties when set.

Before you push

CI runs these on every pull request. Existing findings live in committed baselines, so only new ones fail.

./gradlew spotlessApply                  # formats the files you changed
./gradlew compileKotlinJvm compileAndroidMain :androidApp:compileDebugKotlin jvmTest detekt :konsist-test:test
./gradlew lintDebug lintAndroidMain
./gradlew stabilityCheck                 # its own invocation, after compileKotlinJvm compileAndroidMain

In Claude Code, /verify runs the same steps. CI also lints agent docs with agnix. Details and baseline rules: docs/agents/checks.md.

Rules the tools don't check

The full rule set, with examples, is docs/code-style.md. These apply to almost every change:

  • A screen is a FooRoot that collects state and events, calling a stateless FooScreen(state, onAction, modifier).
  • A ViewModel exposes one state: StateFlow, takes one onAction(FooAction) with a sealed FooAction, and sends one-off effects through a Channel.
  • Errors are typed and become string resources in the UI. Never show Throwable.message, and never wrap suspend calls in runCatching.
  • Use Komi* components and LocalPersonality tokens, not MaterialTheme or color literals.
  • All user-visible text, content descriptions included, comes from Res.string.
  • No KDoc and no comments that restate the code; comment only non-obvious invariants and workarounds. No em-dashes.
  • Don't guess APIs, versions or flags. Read the code or the docs first.

Read when relevant

  • docs/agents/architecture.md: layers, navigation, DI, core repositories, adding a feature
  • docs/agents/checks.md: CI checks, baselines, warnings as errors, the stability analyzer
  • docs/agents/sign-in.md: OAuth handoff, device flow, personal access tokens, the X-GitHub-Token header
  • docs/agents/forges.md: Codeberg and Forgejo clients, per-host tokens, RepoIdCodec
  • docs/agents/releases-and-assets.md: how releases, assets and installed apps are matched
  • docs/agents/platform.md: silent installs, local network access, Desktop logs, encrypted storage, Gradle memory
  • docs/agents/translation.md: translation providers
  • docs/agents/reviews.md: ratings and reviews, the API contract with the backend
  • docs/agents/distribution.md: installers, signing, Homebrew and WinGet (maintainers)
  • feature/<name>/CLAUDE.md: notes for one feature
  • docs/quality/findings.md: the research behind the rules

Download now (ZIP)

Trending

Quiet since May.thin dataabout the whole repository

Dec 2025: 2 mentionsJan 2026: 3 mentionsFeb 2026: 1 mentionMar 2026: 1 mentionApr 2026: 1 mentionMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the rainxchzed/Github-Store repository that our weekly crawl found: only 10 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Who's talking about rainxchzed/Github-Store

The biggest 5 of 10 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 10

Talked about on GitHub, Hacker News and Bluesky (10 times).

On GitHub · 6

1 more on GitHub
  • Jan 16, 2026github.com — liuleon0/vvo0 reactions
  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repositoryOne other file it gives its agents.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.