App stores
AuraScore 81/100

App Store Release Compliance and Asset Payload Verification Suite

Generates a TypeScript verification script to mathematically audit binary payload budgets and App Store Connect metadata compliance.

Use this template before submitting application builds to app store review pipelines. It generates an automated CI/CD script that checks binary size thresholds, asset slices, and privacy manifest schemas against strict store limits.

Template

Role: Senior App Store Release Automation Architect

Context

  • Binary Manifest File Path: {{binary_manifest_path}}
  • Store API Credential Environment: {{store_api_credentials}}
  • Max Cellular Download Limit (MB): {{cellular_download_budget_mb}}
  • Target Privacy Manifest Schema: {{privacy_manifest_schema}}
  • Supported Locale Localization List: {{supported_locale_matrix}}
  • Target Distribution Platform: {{platform_target}}

Task

Generate a standalone Node.js / TypeScript automation script that performs mathematical payload budget decomposition on {{binary_manifest_path}}, validates store metadata completeness across {{supported_locale_matrix}}, and verifies {{privacy_manifest_schema}} compliance prior to triggering release pipelines on {{platform_target}}.

Method

  1. Parse {{binary_manifest_path}} to inspect compressed asset slices, dynamic frameworks, and executable binaries.
  2. Calculate uncompressed disk footprint versus over-the-air compressed size against {{cellular_download_budget_mb}}.
  3. Validate the structure of privacy manifest files against the official specification defined in {{privacy_manifest_schema}}.
  4. Audit metadata localized assets to verify 100% string and media coverage across {{supported_locale_matrix}}.
  5. Verify that API authorization tokens derived from {{store_api_credentials}} conform to JWT lifetime and signature rules.
  6. Compute regression deltas comparing current build asset weights against historical baseline budgets.
  7. Format validation results into standard exit codes and structured SARIF/JSON outputs for CI/CD runners.

Constraints

  • MUST write clean, type-safe TypeScript (Node 18+) without any external CLI wrapper dependencies like fastlane.
  • MUST NOT expose raw secrets from {{store_api_credentials}} in generated log outputs or stack traces.
  • Code MUST fail with non-zero exit code if payload exceeds {{cellular_download_budget_mb}} or if manifest validation fails.
  • Size calculations MUST accurately distinguish between binary payload slices (ARM64 vs Universal).

Output format

Production-ready TypeScript script containing:

  • Complete interface definitions for manifests, size metrics, and validation reports
  • Pure mathematical verification functions for byte-to-megabyte budget boundary checks
  • Async runner orchestrating all checks with defensive try/catch blocks
  • JSON report generator and process exit handler

Self-review

  • Confirm that byte-to-megabyte conversion uses binary standard (1024^2) calculations.
  • Verify all required keys in {{privacy_manifest_schema}} are strictly asserted.
  • Ensure zero unhandled promise rejections exist in async validation loops.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-app-stores
complex-reasoning-analysis-math
app-stores
release-engineering
typescript