← ClaudeAtlas

app-identitylisted

Decide an app's NAME for both stores, and own the project README as the source of truth for the name, subtitle / short description, and detected feature list. Use when the user wants to name or rename an app, asks "what should I call my app", wants to change the name under the icon or in a store listing, or wants the README's feature list written or refreshed ("תן שם לאפליקציה", "עדכן את ה-README"). Run it when the app is feature-complete, and always BEFORE app-store-metadata, play-store-metadata, aso-keywords and appstore-media, which all read the name and feature list from here. It scans the code for features and monetization, proposes ASO-aware candidates, and DISCUSSES them: it never picks a name on its own. Once decided it writes the display name into the Apple build settings and into Android's strings.xml, and owns the README's version label and changelog. It does NOT write the store metadata files or the keyword field — app-store-metadata, play-store-metadata and aso-keywords own those.
yybd/app-factory · ★ 5 · Data & Documents · score 77
Install: claude install-skill yybd/app-factory
# App Name & README (the app's identity, source of truth) > **Conversational language:** talk to the user — questions, summaries, reports — in **the language the user writes in** — unless a `conversational language` is set in the hub `DATA.md` (`$APP_HUB/DATA.md`), which overrides it. This sets the *conversation* language only — content/deliverables follow the app's target locales. An app's name is not one string — it shows up under the icon, in the window title and menu bar, on the App Store listing, and in the subtitle right beneath it. These have different rules (the on-device display name is an Xcode build setting; the App Store name and subtitle are fastlane metadata fields with character limits and ASO weight). When they drift apart, or when nobody wrote down *why* this name was chosen, every later step re-litigates it. Run this when the app is **feature-complete** — at the end of building it, and before the store/listing steps. It decides the name *with the developer*, applies the on-device part, **detects the app's feature list (and any Pro/premium tier) from the finished code**, **tracks the app's version history** (asking each run whether the version changed, and logging what's new when it did), and records all of it in **one source of truth — the project README** — so the listing/media skills lift from there instead of re-interviewing or inventing. In the studio flow that source of truth is `$APP_HUB/<slug>/profile.md`; for a standalone project it is the repo's