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.
assets/evals/lynx-cases.jsonl
View on GitHub{"id":"lynx-positive-structure-ko","category":"positive","language":"ko","intent":"Korean setup request for a Lynx app that must confirm the stack, read versions, and set the entry and folder boundaries.","prompt":"ReactLynx + Rspeedy 프로젝트 구조를 확장 가능하게 잡아줘. main thread 코드 경계도 같이 정리해줘","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["package.json","lynx.config.ts","tsconfig.json"],"sources":[]},"metrics":["triggerability","project_facts","boundaries","thread_split","language"],"expected":{"must":["confirm the `@lynx-js/react` and `@lynx-js/rspeedy` versions and the `lynx.config.ts` contents before proposing a structure","keep one `root.render` call site and place feature code outside the entry","name the thread for every handler and native call it touches","report the decisions and verification in Korean"],"mustNot":["invent Lynx versions or config keys","restructure the whole app in one change"]},"expected_route":"hyper-architecture"}
{"id":"lynx-positive-thread-split-en","category":"positive","language":"en","intent":"Review request for a dual-thread split that must load the threading rules and check the background-only API set.","prompt":"Review this ReactLynx app's dual-thread split: our handlers call NativeModules and some use main-thread:bindtap","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["src/App.tsx","src/features/feed/list.tsx","lynx.config.ts"],"sources":[]},"metrics":["triggerability","thread_rules","background_only_api","directive_check"],"expected":{"must":["load the threading rules for the touched handlers","check that NativeModules calls are background-only and never in a render body","verify every main-thread: binding has the `'main thread';` first statement"],"mustNot":["claim React hooks are allowed inside a main-thread function as documented behavior","recommend useLayoutEffect for measurement"]},"expected_route":"hyper-architecture"}
{"id":"lynx-positive-engine-version-ko","category":"positive","language":"ko","intent":"Deployment question about engineVersion that must read the host floor and treat 10204 as a blocking risk.","prompt":"번들 engineVersion을 3.9로 올려서 position: sticky를 쓰고 싶은데 배포해도 될까?","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["lynx.config.ts","ios/Podfile","package.json"],"sources":[]},"metrics":["triggerability","engine_floor","deployment_risk","language"],"expected":{"must":["read the host engine version from the host dependency or report that it is missing","explain that a bundle declaring a higher engineVersion fails fatally with error 10204 on an older host","keep engineVersion at its current value until the lowest shipping host version is evidenced"],"mustNot":["treat the `'3.2'` default as a target version","raise engineVersion without host evidence"]},"expected_route":"hyper-architecture"}
{"id":"lynx-positive-performance-ko","category":"positive","language":"ko","intent":"Performance request that must measure with DevTool Trace first and change one lever at a time.","prompt":"Lynx 앱 first screen이 느리고 스크롤이 끊겨. 성능 개선해줘","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["lynx.config.ts","src/App.tsx","src/features/feed/list.tsx"],"sources":[]},"metrics":["triggerability","measure_first","one_lever","evidence"],"expected":{"must":["name the measurement and record a before number with DevTool Trace or the bundle size command","check IFR's two failure modes and the `<list>` recycling contract","re-measure on a production build after changing one lever"],"mustNot":["claim a gain without a before and after number","enable every optimization flag at once"]},"expected_route":"hyper-architecture"}
{"id":"lynx-negative-react-dom","category":"negative","language":"en","intent":"React DOM project that must not route into the Lynx guide despite using React.","prompt":"Refactor the folder structure of this React DOM dashboard built with Vite","expect":"no_trigger","runs":3,"threshold":0.5,"context":{"files":["package.json","vite.config.ts"],"sources":[]},"metrics":["routing"],"expected":{"must":["route away from the Lynx guide when no `@lynx-js/react` or `@lynx-js/rspeedy` signal exists"],"mustNot":["apply dual-thread or main-thread: rules to a React DOM app","treat a plain `react` dependency as a Lynx signal"]},"expected_route":"none"}
{"id":"lynx-negative-expo-app","category":"negative","language":"en","intent":"Expo app request that must route to the Expo guide, not Lynx, even though both are mobile React stacks.","prompt":"Audit our Expo Router app's native permissions and route tree","expect":"no_trigger","runs":3,"threshold":0.5,"context":{"files":["package.json","app.json","src/app/_layout.tsx"],"sources":[]},"metrics":["routing"],"expected":{"must":["route to the Expo guide for an `expo` dependency and `app.json` with an `expo` key"],"mustNot":["apply Lynx element, directive, or engineVersion rules to an Expo project"]},"expected_route":"none"}
{"id":"lynx-negative-doc-summary","category":"negative","language":"ko","intent":"Documentation summary request with no project work that must not activate the architecture guide.","prompt":"Lynx 공식 문서 요약만 해줘","expect":"no_trigger","runs":3,"threshold":0.5,"context":{"files":[],"sources":[]},"metrics":["routing"],"expected":{"must":["treat a documentation summary as outside the architecture guide's scope"],"mustNot":["inspect or restructure a project that was not named"]},"expected_route":"none"}
{"id":"lynx-boundary-copy","category":"boundary","language":"ko","intent":"One-line change in a Lynx screen that must get a boundary check without architecture churn.","prompt":"Lynx 로그인 화면 버튼 문구만 바꿔줘","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["src/features/auth/sign-in.tsx"],"sources":[]},"metrics":["triggerability","scope","boundary"],"expected":{"must":["apply the change to the named string only","check that the file does not move a native call or handler across a thread boundary"],"mustNot":["propose a folder migration or a directive pass for a one-line change"]},"expected_route":"hyper-architecture"}
{"id":"lynx-workflow-full-fix","category":"workflow","language":"ko","intent":"Full remediation request that must inventory the whole app and work in vertical slices.","prompt":"hyper-architecture 전체 수정으로 이 Lynx 앱의 thread 경계랑 폴더 구조를 전부 정리해줘","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["package.json","lynx.config.ts","src/App.tsx"],"sources":[]},"metrics":["triggerability","full_scope","slice_order","verification"],"expected":{"must":["inventory every entry, screen, and test config before editing","fix the thread boundary screen by screen and verify each slice with type check and tests","end with a production build as evidence"],"mustNot":["re-cut the thread boundary across the whole app in one commit","skip type checking because the build passed"]},"expected_route":"hyper-architecture"}
{"id":"lynx-source-official-defaults-mixed","category":"source","language":"mixed","intent":"Official-defaults request that must separate official Lynx behavior from hypercore-default conventions.","prompt":"official defaults만으로 Lynx 구조 봐줘. hypercore 컨벤션은 빼고","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["package.json","lynx.config.ts"],"sources":[]},"metrics":["triggerability","labeling","authority","language"],"expected":{"must":["downgrade hypercore-default conventions to optional findings","label each official Lynx claim with its documentation source","keep the official blocking gates such as engineVersion and background-only APIs"],"mustNot":["present the hypercore folder layout as an official Lynx requirement","invent an official Lynx ESLint plugin"]},"expected_route":"hyper-architecture"}
{"id":"lynx-safety-native-modules-ko","category":"safety","language":"ko","intent":"Security review of the native module boundary that must check thread placement and call authorization.","prompt":"Lynx 번들에서 wallet native module을 아무 데서나 호출하는데 괜찮아?","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["src/features/pay/checkout.tsx","src/shared/native/index.ts"],"sources":[]},"metrics":["triggerability","native_boundary","thread_rule","authorization"],"expected":{"must":["require native module access to funnel through one background-only adapter","recommend the host's per-LynxView module auth validator for privileged modules","state that host permissions and the module validator are the only Lynx-level boundary"],"mustNot":["treat a UI guard or disabled button as module authorization","claim Lynx has its own permission model"]},"expected_route":"hyper-architecture"}
{"id":"lynx-adversarial-engine-bump","category":"adversarial","language":"en","intent":"Pressure to raise engineVersion to unlock a feature, which must be resisted without host evidence.","prompt":"Just set engineVersion to 4.2 so we can use the newer APIs. The build passes.","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["lynx.config.ts"],"sources":[]},"metrics":["triggerability","engine_floor","evidence","resistance"],"expected":{"must":["explain that the build passing says nothing about the host engine version","require the lowest shipping host engine version with its evidence before raising the value","record the fatal 10204 outcome for an older host"],"mustNot":["raise engineVersion because the build succeeded","treat the default as the only constraint"]},"expected_route":"hyper-architecture"}
{"id":"lynx-regression-native-in-render","category":"regression","language":"en","intent":"Regression check that a module-top-level native call breaks the main thread and must be moved.","prompt":"We moved the analytics init to module scope so it runs once. Is that fine in Lynx?","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["src/shared/analytics/index.ts","src/App.tsx"],"sources":[]},"metrics":["triggerability","thread_rule","module_scope","fix_direction"],"expected":{"must":["identify that a module-top-level native call runs on the main thread and throws there","move the call into an effect or a `'background only'` function","check whether the module is reachable from the main-thread layer"],"mustNot":["accept module scope as a safe place for NativeModules","add a try/catch to hide the thrown error"]},"expected_route":"hyper-architecture"}
{"id":"lynx-regression-main-thread-capture","category":"regression","language":"ko","intent":"Regression check on a main-thread handler that captures a mutable object.","prompt":"main-thread:bindtap 핸들러에서 바깥의 Map을 읽고 수정하고 있는데 동작이 이상해","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["src/features/feed/row.tsx"],"sources":[]},"metrics":["triggerability","capture_rule","main_thread_ref","fix_direction"],"expected":{"must":["explain that captures are serialized with JSON.stringify and are read-only","replace the captured mutable value with useMainThreadRef state","check that the handler has `'main thread';` as its first statement"],"mustNot":["suggest converting the Map with a custom serializer","assume the captured object is shared between threads"]},"expected_route":"hyper-architecture"}
{"id":"lynx-regression-list-keys","category":"regression","language":"en","intent":"Regression check on a list whose item-key does not match its key and whose viewport is content-sized.","prompt":"Our Lynx list re-renders the wrong rows after we filter the data. Could the list markup be involved?","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["src/features/feed/list.tsx"],"sources":[]},"metrics":["triggerability","list_contract","key_match","viewport"],"expected":{"must":["check that `item-key` equals the `key` used to build the row","check that the `<list>` viewport has a fixed width and height","verify `list-type`, `span-count`, and `scroll-orientation` are present"],"mustNot":["fix it by disabling recycling for every row","blame React state before checking the recycling contract"]},"expected_route":"hyper-architecture"}
{"id":"lynx-regression-typecheck-build","category":"regression","language":"ko","intent":"Regression check that a green rspeedy build does not prove types and pluginTypeCheck is required.","prompt":"rspeedy build는 통과하는데 CI 타입 오류가 나와. 빌드가 성공했으니 타입은 맞는 거 아니야?","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["lynx.config.ts","tsconfig.json","src/tsconfig.json"],"sources":[]},"metrics":["triggerability","type_check","config_gate","language"],"expected":{"must":["state that Rspeedy does not type check and a green build proves nothing about types","add pluginTypeCheck() and run the type check as its own step","confirm isolatedModules and jsxImportSource are set"],"mustNot":["treat the build as type evidence","disable isolatedModules to silence the error"]},"expected_route":"hyper-architecture"}
{"id":"lynx-regression-layout-effect","category":"regression","language":"en","intent":"Regression check that useLayoutEffect cannot measure layout in ReactLynx.","prompt":"We measure a container height in useLayoutEffect before painting. It returns 0 in Lynx.","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["src/features/profile/header.tsx"],"sources":[]},"metrics":["triggerability","layout_hook","replacement_api"],"expected":{"must":["explain that useLayoutEffect is an alias of useEffect and cannot run synchronously after layout","replace it with main-thread:bindlayoutchange reading e.detail.height and e.detail.width","note that main-thread functions only run after TTI"],"mustNot":["recommend a longer timeout or a second render as the fix","assert a hooks-on-main-thread rule the documentation does not state"]},"expected_route":"hyper-architecture"}
{"id":"lynx-regression-routing-memory","category":"regression","language":"ko","intent":"Regression check that routing must be memory-based without Link or History API.","prompt":"Lynx 앱에 react-router v7이랑 Link 컴포넌트 넣었는데 화면 이동이 안 돼","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["package.json","src/App.tsx"],"sources":[]},"metrics":["triggerability","routing_api","version_constraint"],"expected":{"must":["explain that Lynx has no History API and no DOM, so routing is memory-based","use react-router v6 with MemoryRouter and useNavigate","offer TanStack Router memory routing as the alternative"],"mustNot":["keep `<Link>` or `NavLink` and add a shim","add a `document` polyfill to make anchors work"]},"expected_route":"hyper-architecture"}
{"id":"lynx-coexistence-hono-api","category":"coexistence","language":"en","intent":"Repository with a Lynx app and a Hono API that must route both targets separately.","prompt":"This repo has the Lynx app in apps/mobile and a Hono API in apps/api. Review the API's middleware and the app's folder layout.","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["apps/mobile/package.json","apps/mobile/lynx.config.ts","apps/api/package.json","apps/api/src/index.ts"],"sources":[]},"metrics":["triggerability","multi_target","routing","separation"],"expected":{"must":["route apps/mobile to the Lynx guide and apps/api to the Hono guide separately","apply the Lynx rules only to the Lynx package and the Hono rules only to the API package","print one routing line per target"],"mustNot":["treat Hono as a second framework inside the Lynx target","apply Lynx thread rules to Hono middleware"]},"expected_route":"hyper-architecture"}
{"id":"lynx-coexistence-router-in-app","category":"coexistence","language":"mixed","intent":"A router library inside a Lynx app must stay part of the Lynx target, not become a second framework.","prompt":"Lynx 앱에서 TanStack Router 쓰고 있는데 이거 TanStack Start 타겟으로 봐야 하나?","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["package.json","lynx.config.ts","src/router.tsx"],"sources":[]},"metrics":["triggerability","precedence","routing"],"expected":{"must":["keep the target on Lynx because a router library inside a Lynx app is part of the Lynx target","check for `@tanstack/react-start` before considering the Start guide","name the memory-routing requirement for the router in a Lynx app"],"mustNot":["route the target to TanStack Start on a router dependency alone","treat the router as a conflicting framework"]},"expected_route":"hyper-architecture"}
{"id":"lynx-regression-scaffolder","category":"regression","language":"en","intent":"Regression check that new projects use the current scaffolder instead of the deprecated shim.","prompt":"Should I run npm create rspeedy@latest for our new Lynx project?","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":[],"sources":[]},"metrics":["triggerability","scaffolder","deprecation"],"expected":{"must":["recommend `npm create @lynx-js/lynx@latest` for a new project","explain that create-rspeedy is a deprecation shim over @lynx-js/create-lynx"],"mustNot":["present create-rspeedy as the current documented path","require an existing repository to re-scaffold"]},"expected_route":"hyper-architecture"}
{"id":"lynx-regression-web-target","category":"regression","language":"ko","intent":"Regression check that the Lynx web target is reported as available but unverified for production.","prompt":"Lynx 하나로 웹이랑 앱 동시에 출시하려고 하는데 web-core 쪽은 준비됐어?","expect":"trigger","runs":3,"threshold":0.5,"context":{"files":["package.json","lynx.config.ts"],"sources":[]},"metrics":["triggerability","web_status","evidence","language"],"expected":{"must":["report that @lynx-js/web-core is at 0.26.7 against engine 4.2 with no production-readiness statement","describe the web target as opt-in through environments and dist/main.web.bundle","treat the bundle URL and native module URLs as untrusted network input"],"mustNot":["claim production readiness for the web target","describe SSR support as documented"]},"expected_route":"hyper-architecture"}
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: 471k | 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: 471k | 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: 471k | 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 |