ugc-safety-features

Detects missing report, block, filter, and contact mechanisms in iOS apps with user-generated content.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/tvh25082004/Badminton --skill ugc-safety-features-tvh25082004
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ugc-safety-features
Source: https://github.com/tvh25082004/Badminton/tree/main/.claude/skills/apple-app-review/ugc/ugc-safety-features
Command: npx skills add https://github.com/tvh25082004/Badminton --skill ugc-safety-features-tvh25082004

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Apps with user-generated content are frequently rejected from the App Store under Guideline 1.2 when they lack required safety mechanisms. This Skill audits Swift and Objective-C source code to detect missing report, block, content filtering, EULA, and developer contact features before submission. ## Core Features & Use Cases - Safety Mechanism Detection: Greps the codebase for report content, block user, and content filtering implementations across feed, comment, and profile views. - Compliance Gap Reporting: Produces a prioritized findings list (CRITICAL/HIGH/MEDIUM/LOW) with file paths, line numbers, and actionable TODO items mapped to Guideline 1.2. - EULA and Age Verification Checks: Verifies terms-of-service acceptance in onboarding flows and flags missing age verification for apps with user-to-user interaction. - Use Case: Before submitting a community app with posts and comments, run this audit to confirm a Report button, Block User action, in-app support contact, and EULA acceptance all exist, avoiding a guaranteed 1.2 rejection. ## Quick Start Audit my iOS project for App Store Guideline 1.2 user-generated content safety requirements and list any missing report, block, or contact mechanisms.

Frequently Asked Questions about ugc-safety-features

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my iOS app for App Store Guideline 1.2 compliance?▼

Run this audit on your project root to grep Swift source files for report, block, filter, EULA, and contact patterns. It outputs a prioritized findings list showing which Guideline 1.2 mechanisms are missing and where to add them.

What safety features does Apple require for user-generated content apps?▼

Apple Guideline 1.2 requires four mechanisms: content filtering for objectionable material, a report mechanism for flagging posts and profiles, a block mechanism for abusive users, and published developer contact info accessible within the app.

Does this audit work with React Native or Flutter projects?▼

Yes, the audit supports Swift, Objective-C, React Native, and Flutter projects. It uses file globbing and grep patterns rather than compiler analysis, so it works across these frameworks.

Why was my app rejected under Guideline 1.2 even with a report button?▼

A report button alone is insufficient. Apple also requires a block user mechanism, content filtering, an EULA users accept before posting, and in-app developer contact info. Missing any one of these commonly triggers rejection.

Does the audit modify my source code or make network calls?▼

No, the audit is strictly read-only and makes no network calls. It only uses Glob, Grep, and Read operations to inspect source files and generate a findings report.