komi-store
AGENTS.md20k starsChanged 11 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
- Very specific: line 44
Use Komi* components and LocalPersonality tokens, not MaterialTheme or color literals.
- Very specific: line 45
All user-visible text, content descriptions included, comes from Res.string.
- Distinctive: line 46
No KDoc and no comments that restate the code.
- Distinctive: line 47
Don't guess APIs, versions or flags.
≈ “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.
Files
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 rulescore/domain: interfaces, models and pure logic, no framework importscore/data: repositories, Ktor clients, Room, Koin modules, Android and Desktop implementationscore/presentation: thePersonalitydesign system,Komi*components, strings for 14 localesfeature/<name>/{domain,data,presentation}: one folder per feature; some have onlypresentationkonsist-test/: architecture rules;build-logic/convention/: convention plugins; versions ingradle/libs.versions.toml
Build and run
./gradlew :androidApp:assembleDebug # Android APK
./gradlew :composeApp:run # DesktopJDK 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 compileAndroidMainIn 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
FooRootthat collects state and events, calling a statelessFooScreen(state, onAction, modifier). - A ViewModel exposes one
state: StateFlow, takes oneonAction(FooAction)with a sealedFooAction, and sends one-off effects through aChannel. - Errors are typed and become string resources in the UI. Never show
Throwable.message, and never wrap suspend calls inrunCatching. - Use
Komi*components andLocalPersonalitytokens, notMaterialThemeor 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 featuredocs/agents/checks.md: CI checks, baselines, warnings as errors, the stability analyzerdocs/agents/sign-in.md: OAuth handoff, device flow, personal access tokens, theX-GitHub-Tokenheaderdocs/agents/forges.md: Codeberg and Forgejo clients, per-host tokens,RepoIdCodecdocs/agents/releases-and-assets.md: how releases, assets and installed apps are matcheddocs/agents/platform.md: silent installs, local network access, Desktop logs, encrypted storage, Gradle memorydocs/agents/translation.md: translation providersdocs/agents/reviews.md: ratings and reviews, the API contract with the backenddocs/agents/distribution.md: installers, signing, Homebrew and WinGet (maintainers)feature/<name>/CLAUDE.md: notes for one featuredocs/quality/findings.md: the research behind the rules
Trending
Quiet since August.thin dataabout the whole repository
Who's talking about kurikomi-labs/komi-store
- RookieEnough/Orion-Data“App Submission [1 App] - Komi Store”GitHub · Aug 11, 2026
- @troll.maly.io.ap.brid.gy“Eh, s'trop bien 🫴 #KOMIstore :android: 🌐 https://komistore.app/ :github_: …”Bluesky · Jul 9, 2026
- komi-store/komi-store“Homebrew tap is stale after Komi Store 1.9.1 rename”GitHub · Jun 23, 2026
- google.com“Komi Store 1.9.2 (Android 8.0+) - rainxchzed”the web · Jun 27, 2026
- newreleases.io“komi-store/komi-store v1.9.1 on GitHub”the web · Jun 11, 2026
The biggest 5 of 5 mentions linking to the repository that our crawl found. Each line is their own headline.
Other versions2 projects use a version of this.
Word for word · 2
- rainxchzed/Github-Store★ 20k100% same
- OpenHub-Store/GitHub-Store★ 20k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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.
- CLAUDE.mdCLAUDE.md
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.

