feat: add comprehensive agent rules and workflows for memory curation, communication synchronization, and project documentation management

.opencode/skills/ios-testing-strategy/SKILL.md

@@ -1,34 +0,0 @@
----
-name: ios-testing-strategy
-description: Recommend iOS testing approaches for Swift, SwiftUI, XFlow, Fid4, and REST migration work while respecting existing XCTest/Swift Testing/project constraints.
-compatibility: opencode
----
-
-## When To Use
-
-Use this skill for unit tests, UI tests, integration tests, regression coverage, XFlow flow validation, or REST/GraphQL migration testing questions.
-
-## Workflow
-
-1. Identify the behavior under test.
-2. Classify the test level:
-   - unit
-   - integration
-   - UI / consumer flow
-   - exploratory validation
-3. Check whether the behavior depends on backend configuration, auth state, entry point, feature flags, or Fid4 integration.
-4. Prefer the test framework already used by the project unless the user asks about migration.
-5. If suggesting Swift Testing, confirm Xcode/project support first and do not mix APIs inside the same test.
-
-## Project-Specific Guidance
-
-- XFlow behavior may require exploratory validation beyond unit tests.
-- AO/Discourse issues often need auth-state and entry-point coverage.
-- REST migration tests must distinguish REST path from GraphQL fallback.
-- Consumer-facing changes may require Fid4 validation even when SDK tests pass.
-
-## Output Rules
-
-- Recommend the smallest useful test strategy.
-- Include what cannot be proven by that test layer.
-- Mention manual/exploratory validation when code-level tests are insufficient.

.opencode/skills/ios-testing-strategy/SKILL.md

@@ -0,0 +1 @@
+../../../.agents/rules/ios-testing-strategy.md