Automate every Google Play Store publishing task — store listings, ASO, release notes, policy declarations, and screenshot copy — all from Claude Code.
Play Store compliance had no repeatable structure. Each submission was manually reconstructed — listing copy format, release notes character limits, Data Safety section declarations. At fleet scale across 22+ apps, this was producing compliance gaps and inconsistent listing quality.
PlayCraft encodes the full Play Store submission workflow into structured commands. Every listing goes through the same format, the same character limit enforcement, the same ASO scoring pass. The compliance declarations checklist runs before every release. No manual reconstruction, no missed fields.
Step 1 — Add the marketplace
/plugin marketplace add SUDARSHANCHAUDHARI/PlayCraft
Step 2 — Install the plugin
/plugin install playcraft
When you install, Claude Code prompts you for your developer details once (name, company, email, GitHub username, country, default locale). These are stored globally and used automatically in every project.
| Command | Description |
|---|---|
/playcraft:setup |
Show your current config and how to update it |
/playcraft:store-listing |
Generate title, short description, and full description |
/playcraft:release-notes |
Write what’s new copy for an app update |
/playcraft:aso-audit |
Score and fix your ASO with keyword recommendations |
/playcraft:declarations |
Generate all required policy declarations checklist |
/playcraft:screenshots |
Write captions and alt text for Play Store screenshots |
1. Generate your store listing
/playcraft:store-listing
Provide your app name, category, features, and target audience. Output includes title, short description, and full description with live character counts.
2. Audit your ASO
/playcraft:aso-audit
Paste your current listing. Get a score out of 30, keyword recommendations, and offers to rewrite any section that scores below 7.
3. Write release notes
/playcraft:release-notes
Paste your git log or describe your changes. Get polished, user-friendly release notes under 500 characters.
/playcraft:store-listing ──► listing-writer ──► title / short desc / full desc
└──► policy-checker ──► compliance review
/playcraft:aso-audit ─────► aso-agent ────────► keyword report + scored listing
/playcraft:declarations ──► policy-checker ───► declarations checklist
/playcraft:release-notes ─► locale-agent ─────► localized versions (if requested)
PlayCraft/
├── .claude-plugin/
│ ├── plugin.json # Plugin manifest + userConfig
│ └── marketplace.json # Marketplace manifest
├── commands/ # /playcraft:setup|store-listing|release-notes|aso-audit|declarations|screenshots
├── agents/ # aso-agent, listing-writer, policy-checker, locale-agent
├── skills/ # play-policy-2026, closed-testing, financial-declarations,
│ # ai-content-declarations, developer-identity-th
├── hooks/
│ └── pre-release-check.md # Pre-release checklist reminder
├── README.md
├── CHANGELOG.md
├── DOCUMENTATION.md
└── LICENSE
Commands say config is missing — Go to Claude Code Settings → Plugins → PlayCraft → Configure and fill in your developer details.
Character count exceeds limit — The listing-writer agent will catch this. If it doesn’t, ask: “Rewrite the title to be under 30 characters.”
Release notes over 500 characters — Ask: “Trim the release notes to under 500 characters, keep the most user-visible changes.”
Localization not offered — Set your target locales in Settings → Plugins → PlayCraft → Configure → Target Locales (comma-separated, e.g. th-TH, fr-FR).
SUDARSHANCHAUDHARI — github.com/SUDARSHANCHAUDHARI SudarshanTechLabs
For full details — all commands, agents, skills, compliance coverage, and architecture — see DOCUMENTATION.md.
MIT — see LICENSE