buildanything 1.7.1 → 2.0.0

package/skills/ios/writing-for-interfaces/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: writing-for-interfaces
+description: Microcopy and tone review for iOS interfaces. Use when reviewing button labels, error messages, onboarding copy, empty states, alerts, permission prompts, and in-app text for clarity, brevity, and consistency with Apple's voice guidelines.
+version: 0.1.0
+status: ready
+---
+
+# Writing for Interfaces
+
+## Purpose
+Reviews and improves microcopy across iOS app screens — button labels, error messages, onboarding text, empty states, alerts, permission dialogs, and navigation titles. Ensures text is clear, concise, actionable, and consistent with Apple's tone guidelines.
+
+## When this fires
+- `/ux-review` iOS branch (Step 4e)
+- Any screen-level copy audit
+- Permission prompt or alert wording review
+
+## Inputs
+- Screen screenshots or SwiftUI view code containing user-facing strings
+- App category and tone keywords from `.build-state.md` (if available)
+
+## Outputs
+- Per-screen findings: issue, severity (P0/P1/P2), current copy, suggested rewrite
+- Tone consistency assessment across reviewed screens
+
+## Principles
+
+### Clarity over cleverness
+- Every label should be instantly understood on first read
+- Avoid jargon, abbreviations, and internal terminology
+- Use familiar words: "Delete" not "Remove from collection"
+
+### Brevity without ambiguity
+- Button labels: 1–3 words (verb or verb + noun)
+- Error messages: one sentence, state what happened and what to do
+- Empty states: one sentence of encouragement + one CTA
+
+### Actionable language
+- Buttons describe what happens: "Save Photo", "Send Message", "Try Again"
+- Avoid vague labels: "OK", "Submit", "Continue" (unless context is unambiguous)
+- Destructive actions name the consequence: "Delete Account", not "Confirm"
+
+### Consistent voice
+- Match the app's established tone (playful, professional, minimal, warm)
+- Keep capitalization consistent (Title Case for buttons, Sentence case for descriptions)
+- Use the same term for the same concept everywhere (don't alternate "photo" and "image")
+
+### Apple conventions
+- Permission prompts: explain the benefit, not the mechanism ("To send you reminders" not "This app needs notification access")
+- Alerts: title states the situation, message gives context, buttons name the actions
+- Navigation titles: short, noun-based ("Settings", "Profile", not "Your Settings Page")
+
+## Review checklist
+
+1. **Buttons** — Are labels verb-first and specific? Are destructive actions clearly named?
+2. **Error messages** — Do they say what went wrong AND what to do next?
+3. **Empty states** — Is there a friendly message + clear CTA to populate the screen?
+4. **Permission prompts** — Do usage descriptions explain the user benefit?
+5. **Alerts** — Does the title summarize the situation? Do button labels name the actions (not "OK"/"Cancel")?
+6. **Navigation titles** — Short, noun-based, consistent across the tab/flow?
+7. **Onboarding** — Is each screen one idea, scannable in 3 seconds?
+8. **Placeholders** — Do text field placeholders show format or example, not just the field name?
+9. **Tone consistency** — Does copy across screens feel like it was written by the same person?
+10. **Localization readiness** — Are strings free of concatenation, hardcoded plurals, and layout-breaking length assumptions?
+
+## Severity guide
+
+| Severity | Criteria | Example |
+|----------|----------|---------|
+| **P0** | Copy is misleading, causes data loss, or blocks the user | Destructive button labeled "OK" with no explanation |
+| **P1** | Copy is confusing, vague, or inconsistent — fix before ship | Error message says "Something went wrong" with no guidance |
+| **P2** | Copy works but could be tighter, friendlier, or more on-brand | Empty state says "No items" instead of something encouraging |
+
+---
+_In-house skill for buildanything iOS mode. See `protocols/ios-context.md` for Senior iOS Engineer persona._

package/skills/web/accessibility/SKILL.md

@@ -0,0 +1,146 @@
+---
+name: accessibility
+description: Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA
+  standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS/Android).
+origin: ECC
+---
+
+# Accessibility (WCAG 2.2)
+
+This skill ensures that digital interfaces are Perceivable, Operable, Understandable, and Robust (POUR) for all users, including those using screen readers, switch controls, or keyboard navigation. It focuses on the technical implementation of WCAG 2.2 success criteria.
+
+## When to Use
+
+- Defining UI component specifications for Web, iOS, or Android.
+- Auditing existing code for accessibility barriers or compliance gaps.
+- Implementing new WCAG 2.2 standards like Target Size (Minimum) and Focus Appearance.
+- Mapping high-level design requirements to technical attributes (ARIA roles, traits, hints).
+
+## Core Concepts
+
+- **POUR Principles**: The foundation of WCAG (Perceivable, Operable, Understandable, Robust).
+- **Semantic Mapping**: Using native elements over generic containers to provide built-in accessibility.
+- **Accessibility Tree**: The representation of the UI that assistive technologies actually "read."
+- **Focus Management**: Controlling the order and visibility of the keyboard/screen reader cursor.
+- **Labeling & Hints**: Providing context through `aria-label`, `accessibilityLabel`, and `contentDescription`.
+
+## How It Works
+
+### Step 1: Identify the Component Role
+
+Determine the functional purpose (e.g., Is this a button, a link, or a tab?). Use the most semantic native element available before resorting to custom roles.
+
+### Step 2: Define Perceivable Attributes
+
+- Ensure text contrast meets **4.5:1** (normal) or **3:1** (large/UI).
+- Add text alternatives for non-text content (images, icons).
+- Implement responsive reflow (up to 400% zoom without loss of function).
+
+### Step 3: Implement Operable Controls
+
+- Ensure a minimum **24x24 CSS pixel** target size (WCAG 2.2 SC 2.5.8).
+- Verify all interactive elements are reachable via keyboard and have a visible focus indicator (SC 2.4.11).
+- Provide single-pointer alternatives for dragging movements.
+
+### Step 4: Ensure Understandable Logic
+
+- Use consistent navigation patterns.
+- Provide descriptive error messages and suggestions for correction (SC 3.3.3).
+- Implement "Redundant Entry" (SC 3.3.7) to prevent asking for the same data twice.
+
+### Step 5: Verify Robust Compatibility
+
+- Use correct `Name, Role, Value` patterns.
+- Implement `aria-live` or live regions for dynamic status updates.
+
+## Accessibility Architecture Diagram
+
+```mermaid
+flowchart TD
+  UI["UI Component"] --> Platform{Platform?}
+  Platform -->|Web| ARIA["WAI-ARIA + HTML5"]
+  Platform -->|iOS| SwiftUI["Accessibility Traits + Labels"]
+  Platform -->|Android| Compose["Semantics + ContentDesc"]
+
+  ARIA --> AT["Assistive Technology (Screen Readers, Switches)"]
+  SwiftUI --> AT
+  Compose --> AT
+```
+
+## Cross-Platform Mapping
+
+| Feature            | Web (HTML/ARIA)          | iOS (SwiftUI)                        | Android (Compose)                                           |
+| :----------------- | :----------------------- | :----------------------------------- | :---------------------------------------------------------- |
+| **Primary Label**  | `aria-label` / `<label>` | `.accessibilityLabel()`              | `contentDescription`                                        |
+| **Secondary Hint** | `aria-describedby`       | `.accessibilityHint()`               | `Modifier.semantics { stateDescription = ... }`             |
+| **Action Role**    | `role="button"`          | `.accessibilityAddTraits(.isButton)` | `Modifier.semantics { role = Role.Button }`                 |
+| **Live Updates**   | `aria-live="polite"`     | `.accessibilityLiveRegion(.polite)`  | `Modifier.semantics { liveRegion = LiveRegionMode.Polite }` |
+
+## Examples
+
+### Web: Accessible Search
+
+```html
+<form role="search">
+  <label for="search-input" class="sr-only">Search products</label>
+  <input type="search" id="search-input" placeholder="Search..." />
+  <button type="submit" aria-label="Submit Search">
+    <svg aria-hidden="true">...</svg>
+  </button>
+</form>
+```
+
+### iOS: Accessible Action Button
+
+```swift
+Button(action: deleteItem) {
+    Image(systemName: "trash")
+}
+.accessibilityLabel("Delete item")
+.accessibilityHint("Permanently removes this item from your list")
+.accessibilityAddTraits(.isButton)
+```
+
+### Android: Accessible Toggle
+
+```kotlin
+Switch(
+    checked = isEnabled,
+    onCheckedChange = { onToggle() },
+    modifier = Modifier.semantics {
+        contentDescription = "Enable notifications"
+    }
+)
+```
+
+## Anti-Patterns to Avoid
+
+- **Div-Buttons**: Using a `<div>` or `<span>` for a click event without adding a role and keyboard support.
+- **Color-Only Meaning**: Indicating an error or status _only_ with a color change (e.g., turning a border red).
+- **Uncontained Modal Focus**: Modals that don't trap focus, allowing keyboard users to navigate background content while the modal is open. Focus must be contained _and_ escapable via the `Escape` key or an explicit close button (WCAG SC 2.1.2).
+- **Redundant Alt Text**: Using "Image of..." or "Picture of..." in alt text (screen readers already announce the role "Image").
+
+## Best Practices Checklist
+
+- [ ] Interactive elements meet the **24x24px** (Web) or **44x44pt** (Native) target size.
+- [ ] Focus indicators are clearly visible and high-contrast.
+- [ ] Modals **contain focus** while open, and release it cleanly on close (`Escape` key or close button).
+- [ ] Dropdowns and menus restore focus to the trigger element on close.
+- [ ] Forms provide text-based error suggestions.
+- [ ] All icon-only buttons have a descriptive text label.
+- [ ] Content reflows properly when text is scaled.
+
+## References
+
+- [WCAG 2.2 Guidelines](https://www.w3.org/TR/WCAG22/)
+- [WAI-ARIA Authoring Practices](https://www.w3.org/TR/wai-aria-practices/)
+- [iOS Accessibility Programming Guide](https://developer.apple.com/documentation/accessibility)
+- [iOS Human Interface Guidelines - Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility)
+- [Android Accessibility Developer Guide](https://developer.android.com/guide/topics/ui/accessibility)
+
+## Related Skills
+
+- `frontend-patterns`
+- `frontend-design`
+- `liquid-glass-design`
+- `swiftui-patterns`