agentleFS
SUDARSHANCHAUDHARISUDARSHANCHAUDHARI/DroidForge/skills/package-naming/SKILL.md

package-naming

Skill1 starsChanged 9 days agoMITView on GitHub

Android package naming conventions for DroidForge users — format rules, portfolio consistency, privacy policy URL patterns, and GitHub repo naming. Loaded when creating a new app or setting up package names.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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
  1. Distinctive:

    No spaces, hyphens, or special characters

    line 18
  2. Very specific:

    No underscores — prefer concatenation (e.g.

    line 19
  3. Distinctive:

    Must be globally unique across the Play Store

    line 20
  4. Distinctive:

    Should reflect the app's core purpose, not just a generic word

    line 21
  5. Distinctive:

    Use PascalCase for consistency when the app name is a single word or compound noun.

    line 47
  6. Distinctive:

    Before finalising a package name:

    line 51
  7. Distinctive:

    Search the Play Store for the app name

    line 52
  8. Distinctive:

    Check if the exact package ID is already taken (cannot be reused once published)

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Android Package Naming Convention

Standard format

{config.android.package_prefix}.[appname]

Where {config.android.package_prefix} is set during /droidforge:setup (e.g. com.yourcompany).

Rules for [appname]

  • Lowercase only
  • No spaces, hyphens, or special characters
  • No underscores — prefer concatenation (e.g. taskmanager not task_manager)
  • Must be globally unique across the Play Store
  • Should reflect the app's core purpose, not just a generic word

Derivation from app name

App NameDerived appnameFull package name
TaskMastertaskmaster{config.android.package_prefix}.taskmaster
Weather Nowweathernow{config.android.package_prefix}.weathernow
QR Scanner Proqrscannerpro{config.android.package_prefix}.qrscannerpro
My Budget 2mybudget2{config.android.package_prefix}.mybudget2

Privacy policy URL pattern

{config.github_pages.privacy_policy_pattern} — substitute {appname} with the app name in lowercase with hyphens.

Example for app "TaskMaster": https://[github_username].github.io/taskmaster-privacy-policy/

The privacy policy page must be live before submitting to Play Store.

GitHub repository naming

Two acceptable conventions:

  • PascalCase: TaskMaster (matches the app name exactly)
  • kebab-case: taskmaster-android (descriptive with platform suffix)

Use PascalCase for consistency when the app name is a single word or compound noun.

Play Store uniqueness check

Before finalising a package name:

  1. Search the Play Store for the app name
  2. Check if the exact package ID is already taken (cannot be reused once published)
  3. Once published, the package name is permanent — it can never be changed for an existing app

Namespace vs applicationId

In modern Android projects these should always match:

android {
    namespace = "com.yourcompany.taskmaster"   // used for R class resolution
    defaultConfig {
        applicationId = "com.yourcompany.taskmaster"  // used by Play Store
    }
}

Download now (ZIP)

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.