hashgraph-online/awesome-codex-plugins / plugins/alpoxdev/hypercore/skills/hyper-architecture
hyper-architecture
Verified[Hyper] Use this skill when the user asks for architecture, project setup, or performance work - building, auditing, restructuring, or reviewing project structure, routes, data or server boundaries, the lint/format/type tooling baseline (oxlint, Prettier, tsconfig, rustfmt, clippy), or build and runtime performance - in a Next.js App Router, TanStack Start, Vite with TanStack Router, Astro, Expo, Lynx (ReactLynx), Hono, Axum, Tauri v2, Electron, or Rust CLI, WASM, or MCP server project. It detects the stack from manifests and config files, routes each touched package of a monorepo separately, and applies the matching bundled stack guide, the shared setup baseline, and that stack's performance rules. Do not use it for stacks outside those eleven or for work that crosses no architecture, setup, or performance boundary, such as copy edits, a plain dependency bump, or one build failure.
rules/expo/native-platform-and-security.md
View on GitHub# Native Platform and Security
Read when touching app config, permissions, storage, secrets, native code, dependencies with native effects, or platform files. This file owns those gates, the native toolchain baseline, and the project-mode test.
## Project mode
Identify whether native projects are generated by CNG/prebuild, intentionally committed and maintained, or absent. Config plugins/app config are the source of truth only where project ownership says so.
Bare `expo prebuild` clears and regenerates `ios/` and `android/` by default since SDK 57, so a bare run on committed native directories destroys manual changes. Treat `prebuild` itself as the gated command, require `--no-clean` plus a diff review for committed native projects, and treat `prebuild --clean` as the same destructive operation it always was rather than as the only dangerous form.
## Native toolchain baseline
For the SDK 58 generation:
- iOS deployment target 16.4 or newer, Xcode 26.4 or newer, Node.js 22.13 or newer on the 22 line and 24.3 or newer on the 24 line.
- Android 7 or newer, `compileSdk` 37, `targetSdk` 36, minimum Kotlin 2.0, and AGP 9 support with AGP 9 opt-outs (`android.builtInKotlin=false`, `android.newDsl=false`) in `gradle.properties`.
- R8 minify is on by default in release builds through `android.enableMinifyInReleaseBuilds=true`; a reflection-heavy library needs keep rules/expo or an explicit opt-out through `expo-build-properties`.
- CocoaPods remains the default and supported iOS dependency path. Swift Package Manager (`npx react-native spm`) is experimental, additive, and not for production, so do not adopt it silently in an architecture change.
- `expo-modules-core` ships precompiled Android libraries; `android.buildExpoModulesCoreFromSource` is an explicit opt-out, not a default.
A project whose committed `ios/` customizes `AppDelegate.swift` needs a review before an SDK 58 upgrade. iOS 27 requires the UIScene life cycle, and prebuild now generates **SceneDelegate.swift** plus a `UIApplicationSceneManifest` entry while `UIWindow` moves out of `didFinishLaunchingWithOptions`. Expo forwards URL, user-activity, Handoff, life-cycle, and quick-action events to `ExpoAppDelegate` overrides and subscribers, but hand-edited app delegate code must follow the scene-lifecycle migration guide.
## App configuration
Keep `app.config.ts`, `app.json`, `eas.json`, Metro, and TypeScript config at the app root unless existing workspace rules/expo differ. Inspect resolved public config with `npx expo config`; do not print secret evaluation paths. Config-plugin or permission changes generally require a new native build, not only a JavaScript reload/update.
Resolved config now depends on the invoking command: Expo CLI sets `NODE_ENV` from the command and replaces any value you pass, so only the development or production `.env` files load and names such as `.env.staging` and `.env.test` are ignored. Record which command produced an inspected value.
| Mode | Files, first one wins |
|---|---|
| Development | `.env.development.local`, `.env.local`, `.env.development`, `.env` |
| Production | `.env.production.local`, `.env.local`, `.env.production`, `.env` |
Metro config may be `metro.config.js`, `.ts`, or `.mts`; YAML configs and `.es6` extensions are removed in this generation and are broken rather than discouraged.
## Permissions
Treat permissions as two-part contracts: build-time native declaration/purpose text and runtime request/denial handling. Request at the point of user intent, explain purpose, support denied/blocked states, and test fresh-install flows. Minimize Android permissions and iOS usage descriptions.
Expo Go is not evidence that standalone permission configuration is correct: Expo Go skips the native permission declaration step for its own included modules, requires a signed-in Expo account in both the CLI and the app, and only one SDK version ships from the stores. Name the SDK version Expo Go targets before citing a run as evidence.
## Storage and secrets
Use `expo-secure-store` or an evidenced equivalent for small sensitive values through an adapter. Four concrete constraints belong in that adapter's contract:
- iOS Keychain data can survive an uninstall and reinstall under the same bundle ID, so presence of a value does not prove a prior install of the current app instance.
- The underlying platform may reject large payloads; some iOS releases refused values above roughly 2048 bytes, so store a token or a reference rather than a large blob.
- `requireAuthentication` is unavailable in Expo Go when biometrics exist because the face-ID usage description is missing, and protected values become unreadable after biometric settings change.
- Android offers `requireConfirmation`, and the `configureAndroidBackup` plugin option must be disabled when the project maintains its own Auto Backup rules/expo that already exclude `SecureStore`.
Use non-secure storage only for non-sensitive data and define serialization/version migration. Never place secrets in `EXPO_PUBLIC_*`, `extra`, source, logs, analytics, or error reports.
## Platform seams
Prefer shared behavior with explicit adapters. Use `.ios.ts(x)` / `.android.ts(x)` when implementation truly differs; use `Platform.select` for small presentational differences, not large hidden business branches. Keep native-module calls behind typed modules so tests and unsupported platforms have explicit behavior.
## Dependencies and native effects
Use the installed Expo SDK compatibility path and inspect package support for the applicable React Native architecture. From SDK 55 every Expo SDK package shares the SDK major, so a major bump on an Expo package during an SDK upgrade is expected. Package installs, pod/Gradle changes, `prebuild`, EAS credentials/build/update/submit, signing, push credentials, and store actions are gated side effects. When required capability or authorization is unavailable, provide the exact blocked check/change without claiming it ran.
A native dependency that cannot run on the New Architecture has no fallback: there is no opt-out on SDK 55 through 58. Replace or patch it, or report the incompatibility as a blocker with `npx expo-doctor` output and its React Native Directory status.
## EAS and delivery
- `eas update` requires `--environment` since SDK 55. A CI job missing the flag fails rather than defaulting, so the environment mapping belongs in the architecture decision for the app's channels.
- Fingerprint defaults to the `balanced` preset in SDK 58. It ignores common changes such as `version` in app config and hashes native modules by package and version, so the runtime-version policy that decides "OTA or rebuild" must be stated explicitly rather than inherited from the old fingerprint behavior.
- Expo Observe records startup and navigation performance, JavaScript errors, and native crashes. Treat it as one implementation of the observability port in `shared/observability`, not as a dependency scattered through features.
## Sources
> Claims checked 2026-11-04. These statements restate the package's official snapshot, `references/official/expo/expo-react-native-2026-11-04.md`, which cites https://expo.dev/changelog/sdk-58, https://expo.dev/changelog/sdk-57, https://expo.dev/changelog/sdk-55, https://docs.expo.dev/guides/new-architecture/, https://docs.expo.dev/guides/environment-variables/, https://docs.expo.dev/guides/permissions/, https://docs.expo.dev/versions/v58.0.0/sdk/securestore/, https://docs.expo.dev/versions/v58.0.0/sdk/fingerprint/, https://reactnative.dev/blog/2026/08/11/react-native-0.87, and https://expo.fyi/ios-scene-lifecycle.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |