convez.ai
SkillDesenvolvimento WebIntermediário
enesbytmr

Verificador de Diretrizes App Store & Play

enesbytmr/store-guideline-checker

Audita seu app contra App Store e Google Play antes de submeter

Ver no GitHub
InicialPluginScore · de 0 a 100

Plugin Claude Code que audita apps iOS e Android contra as diretrizes oficiais da Apple App Store e Google Play antes da submissão. Analisa manifests, configurações de build e código-fonte para identificar rejeições potenciais com relatório priorizado por severidade e sugestões de correção.

Instalação

$npx convez-ai enesbytmr/store-guideline-checker

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
2
Forks
0
Acompanhando
0
Saúde
57%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Validar compliance com diretrizes antes de submeter app
  • Identificar permissões, privacy manifests e propósitos de camera/localização faltantes
  • Verificar implementação de Sign in with Apple, IAP e account deletion
  • Detectar problemas de target SDK, ATS e segurança em Android

Veredito

Ferramenta prática e bem-documentada que reduz ciclos de rejeição em submissões de apps. Suporta múltiplos frameworks (native, Flutter, React Native, Expo) e razoa contra regras reais em vez de apenas pattern-matching, adaptando-se a layouts variados de projeto.

README

A tradução para o português deste README ainda está na fila.

📱 App Store & Play Guideline Checker

Catch App Store and Google Play rejections before you submit — right inside Claude Code.

A Claude Code plugin that audits your iOS/Android app against the Apple App Store Review Guidelines and the Google Play Developer Program Policy, then hands you a severity-ranked report with cited rules and concrete fixes.

License: MIT Claude Code Plugin Skill + Agent Frameworks PRs Welcome

⭐ If this saves you a rejection, give it a star — it helps other developers find it.


Why

App review rejections cost days. The same issues come up again and again: a missing NSCameraUsageDescription, a social login with no Sign in with Apple, digital goods sold outside IAP, a targetSdk below Google's floor, a Data Safety form that doesn't match the SDKs you actually shipped.

This plugin reviews your project the way a reviewer would — and tells you what to fix before you hit submit.

Two ways to use it

The plugin ships both a skill and an agent. Same knowledge base, two entry points.

SkillAgent
Invoke/store-guideline-checker:guideline-checker [path] or just ask@agent-store-guideline-checker:guideline-auditor or "use the guideline-auditor agent"
Runs inyour main sessionan isolated subagent context
Best fora quick inline check while you worka focused, self-contained audit you can fire and forget

How it works

No external scanner, no setup, no language runtime. Claude itself reads your project — manifests, build config, source, dependencies — reasons against the guideline catalog, optionally pulls the live rule text from Apple/Google, and writes the report. Because it reasons instead of pattern-matching, it adapts to any project layout.

detect framework → locate config & source → gather evidence
      → confirm live rules (WebFetch, with bundled fallback)
      → evaluate every applicable check → severity-ranked report

Supported frameworks

FrameworkDetected byReads
Native iOS*.xcodeproj, Info.plistpurpose strings, entitlements, ATS, privacy manifest
Native AndroidAndroidManifest.xml, build.gradlepermissions, target SDK, cleartext, components
Flutterpubspec.yamlplugins → permissions, both native layers, Dart source
React Nativepackage.json + ios/ + android/JS deps, both native layers
Expoapp.json / app.config.*infoPlist, android.permissions, plugins

What it checks

Apple — App Store Review

  • Permission purpose strings (5.1.1)
  • Account deletion in-app (5.1.1(v))
  • Sign in with Apple vs social login (4.8)
  • IAP for digital goods (3.1.1)
  • App Tracking Transparency (5.1.2)
  • Privacy manifest / nutrition label (5.1.2)
  • Demo account & completeness (2.1)
  • ATS arbitrary loads (2.5.2)

Google — Play Policy

  • Privacy policy & Data Safety form
  • High-risk permissions (SMS/Call Log/Location)
  • Minimal-permissions / Data Safety match
  • Target API level floor
  • Google Play Billing for digital goods
  • Account & data deletion (in-app + web)
  • Cleartext traffic & exported components
  • Store-listing spam / misleading claims

Full mapping with stable IDs and severities: shared-docs/check-catalog.md.

Install

# In Claude Code
/plugin marketplace add enesbytmr/store-guideline-checker
/plugin install store-guideline-checker@store-guideline-checker

Use

# Skill — point it at a project (or omit for the current directory)
/store-guideline-checker:guideline-checker ./my-app

# Agent — fire a focused audit
@agent-store-guideline-checker:guideline-auditor audit this project for store submission

# Or just ask, in plain language
"Check my app against the App Store and Play guidelines."

Example output

# Compliance Report — MyApp
Framework: flutter    Platforms: ios, android    Rule text: LIVE

## Summary
2 blockers, 1 high, 3 manual — submit-ready? with-fixes

## Blockers
### [APL-USAGE-DESC-MISSING] Missing contacts purpose string
- Rule: App Store Review Guideline 5.1.1
- Where: ios/Runner/Info.plist (Dart call in lib/contacts.dart)
- Why: App calls the contacts API but Info.plist has no NSContactsUsageDescription.
- Fix: Add NSContactsUsageDescription explaining why the app needs contacts.

### [GP-TARGET-API-LEVEL] targetSdk below Play floor
- Rule: Google Play target API level requirement
- Where: android/app/build.gradle
- Why: targetSdk 31 is under the current required level; Play will block publishing.
- Fix: Raise targetSdk to the current required level and re-test.

## Manual verification needed
- [ ] Account deletion reachable in-app (Apple 5.1.1(v) / Play data deletion)
- [ ] Sign in with Apple offered alongside Google Sign-In (Apple 4.8)
- [ ] Data Safety form matches firebase_analytics data collection

What this is not

A pass here is not a guarantee of approval. Reviewers apply human judgment and the guidelines change. Treat this as a strong pre-submission checklist, and always confirm against the live guideline pages. Bundled rule snapshots in shared-docs/ are dated — the plugin fetches live text when it can.

Contributing

Issues and PRs welcome — new checks, framework coverage, rule updates. See CONTRIBUTING.md. The check catalog is designed to be easy to extend: add an entry with a stable ID, a cited rule, and a severity.

License

MIT — free for everyone, commercial use included.

Built for mobile developers who'd rather ship than re-submit. ⭐ Star it · 🐛 Open an issue · 🔀 Send a PR

Ver o original no GitHub

Bom para

Relacionados