← ClaudeAtlas

platform-auditlisted

Use when auditing a feature or implementation against platform-specific guidelines such as iOS HIG, Material Design 3, and WCAG. Covers compliance scoring, violation identification, remediation steps, and App Store risk assessment. Do not use for navigation architecture (use navigation-design) or hardware API integration (use device-integration).
dtsong/agentic-council · ★ 0 · API & Backend · score 78
Install: claude install-skill dtsong/agentic-council
# Platform Audit ## Purpose Evaluate a proposed feature or existing implementation against platform-specific guidelines (iOS Human Interface Guidelines, Material Design 3, Web Content Accessibility Guidelines) and produce a compliance report with specific violations and remediation steps. ## Scope Constraints Reads source code, UI mockups, and platform guideline documentation for compliance analysis. Does not modify files or execute code. Does not submit builds or interact with App Store Connect or Google Play Console. ## Inputs - Feature description or UI mockup being evaluated - Target platforms (iOS, Android, Web, or cross-platform) - Existing implementation code (if available) - App Store / Play Store submission history (if relevant) ## Input Sanitization No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets. ## Procedure ### Progress Checklist - [ ] Step 1: Identify target platforms - [ ] Step 2: Audit iOS HIG compliance - [ ] Step 3: Audit Material Design compliance - [ ] Step 4: Audit Web/PWA compliance - [ ] Step 5: Cross-platform consistency check - [ ] Step 6: App Store risk assessment ### Step 1: Identify Target Platforms Determine which platforms the feature targets. For cross-platform projects, note the framework (React Native, Flutter, Capacitor) and assess whether it provides native-feeling UI by default or requires platform-specific overrides. ### Step 2: Audit iOS HIG Compliance If targe