Skip to content

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.

FileKindSize
SKILL.ko.mdmarkdown19.9 KB
SKILL.mdskill md18.4 KB
assets/evals/astro-cases.jsonlother17.1 KB
assets/evals/axum-cases.jsonlother13.7 KB
assets/evals/electron-cases.jsonlother14.6 KB
assets/evals/expo-cases.jsonlother18.3 KB
assets/evals/hono-cases.jsonlother22.2 KB
assets/evals/hyper-architecture-cases.jsonlother26.0 KB
assets/evals/lynx-cases.jsonlother17.9 KB
assets/evals/nextjs-cases.jsonlother21.5 KB
assets/evals/rust-cases.jsonlother17.8 KB
assets/evals/tanstack-start-cases.jsonlother21.0 KB
assets/evals/tauri-cases.jsonlother18.6 KB
assets/evals/vite-cases.jsonlother18.6 KB
assets/templates/setup/repo/editorconfigother357 B
assets/templates/setup/repo/gitattributesother714 B
assets/templates/setup/repo/lefthook.ymlconfig843 B
assets/templates/setup/rust/clippy.tomlconfig110 B
assets/templates/setup/rust/rust-toolchain.tomlconfig86 B
assets/templates/setup/rust/rustfmt.tomlconfig200 B
assets/templates/setup/rust/workspace-lints.tomlconfig809 B
assets/templates/setup/typescript/oxlintrc.jsonconfig929 B
assets/templates/setup/typescript/oxlintrc.react.jsonconfig1.1 KB
assets/templates/setup/typescript/prettierignoreother316 B
assets/templates/setup/typescript/prettierrc.jsonconfig263 B
assets/templates/setup/typescript/tsconfig.base.jsonconfig551 B
references/official/astro/astro-2026-11-07.ko.mdmarkdown18.6 KB
references/official/astro/astro-2026-11-07.mdmarkdown17.0 KB
references/official/axum/axum-docs.ko.mdmarkdown5.7 KB
references/official/axum/axum-docs.mdmarkdown4.8 KB
references/official/axum/ecosystem-docs.ko.mdmarkdown3.8 KB
references/official/axum/ecosystem-docs.mdmarkdown3.5 KB
references/official/axum/sqlx-docs.ko.mdmarkdown5.5 KB
references/official/axum/sqlx-docs.mdmarkdown4.7 KB
references/official/axum/tower-docs.ko.mdmarkdown4.2 KB
references/official/axum/tower-docs.mdmarkdown3.7 KB
references/official/axum/utoipa-docs.ko.mdmarkdown4.1 KB
references/official/axum/utoipa-docs.mdmarkdown3.7 KB
references/official/electron/electron-2026-11-08.ko.mdmarkdown15.7 KB
references/official/electron/electron-2026-11-08.mdmarkdown14.1 KB
references/official/expo/expo-react-native-2026-11-04.ko.mdmarkdown23.0 KB
references/official/expo/expo-react-native-2026-11-04.mdmarkdown21.5 KB
references/official/hono/drizzle-docs.ko.mdmarkdown7.0 KB
references/official/hono/drizzle-docs.mdmarkdown6.6 KB
references/official/hono/hono-docs.ko.mdmarkdown15.8 KB
references/official/hono/hono-docs.mdmarkdown14.8 KB
references/official/lynx/lynx-2026-11-07.ko.mdmarkdown14.3 KB
references/official/lynx/lynx-2026-11-07.mdmarkdown14.0 KB
references/official/nextjs/current-docs-2026-11-04.ko.mdmarkdown13.1 KB
references/official/nextjs/current-docs-2026-11-04.mdmarkdown12.0 KB
references/official/nextjs/drizzle-docs.ko.mdmarkdown6.7 KB
references/official/nextjs/drizzle-docs.mdmarkdown6.3 KB
references/official/nextjs/nextjs-docs.ko.mdmarkdown13.6 KB
references/official/nextjs/nextjs-docs.mdmarkdown13.9 KB
references/official/rust/rust-crates-2026-11-07.ko.mdmarkdown22.6 KB
references/official/rust/rust-crates-2026-11-07.mdmarkdown22.0 KB
references/official/tanstack-start/current-docs-2026-11-04.ko.mdmarkdown16.0 KB
references/official/tanstack-start/current-docs-2026-11-04.mdmarkdown14.7 KB
references/official/tanstack-start/tanstack-router-2026-11-04.ko.mdmarkdown10.5 KB
references/official/tanstack-start/tanstack-router-2026-11-04.mdmarkdown9.6 KB
references/official/tanstack-start/tanstack-start-2026-11-04.ko.mdmarkdown25.8 KB
references/official/tanstack-start/tanstack-start-2026-11-04.mdmarkdown23.9 KB
references/official/tauri/tanstack-vite-react-2026-11-04.ko.mdmarkdown14.1 KB
references/official/tauri/tanstack-vite-react-2026-11-04.mdmarkdown13.1 KB
references/official/tauri/tauri-v2-2026-11-04.ko.mdmarkdown18.5 KB
references/official/tauri/tauri-v2-2026-11-04.mdmarkdown17.6 KB
references/official/tooling/tooling-2026-11-07.ko.mdmarkdown21.0 KB
references/official/tooling/tooling-2026-11-07.mdmarkdown20.5 KB
references/official/vite/current-docs-2026-11-04.ko.mdmarkdown11.2 KB
references/official/vite/current-docs-2026-11-04.mdmarkdown10.3 KB
rules/astro/actions-middleware-env.ko.mdmarkdown14.6 KB
rules/astro/actions-middleware-env.mdmarkdown12.9 KB
rules/astro/content.ko.mdmarkdown8.1 KB
rules/astro/content.mdmarkdown7.3 KB
rules/astro/performance.ko.mdmarkdown11.3 KB
rules/astro/performance.mdmarkdown10.0 KB
rules/astro/project-structure.ko.mdmarkdown11.2 KB
rules/astro/project-structure.mdmarkdown9.6 KB
rules/astro/rendering-and-islands.ko.mdmarkdown10.2 KB
rules/astro/rendering-and-islands.mdmarkdown8.7 KB
rules/astro/testing.ko.mdmarkdown10.4 KB
rules/astro/testing.mdmarkdown9.4 KB
rules/axum/conventions.ko.mdmarkdown5.3 KB
rules/axum/conventions.mdmarkdown4.8 KB
rules/axum/database.ko.mdmarkdown11.9 KB
rules/axum/database.mdmarkdown10.2 KB
rules/axum/errors.ko.mdmarkdown6.5 KB
rules/axum/errors.mdmarkdown6.0 KB
rules/axum/handlers.ko.mdmarkdown5.6 KB
rules/axum/handlers.mdmarkdown5.0 KB
rules/axum/middleware.ko.mdmarkdown5.4 KB
rules/axum/middleware.mdmarkdown4.9 KB
rules/axum/openapi.ko.mdmarkdown9.5 KB
rules/axum/openapi.mdmarkdown8.3 KB
rules/axum/performance.ko.mdmarkdown9.6 KB
rules/axum/performance.mdmarkdown8.6 KB
rules/axum/platform.ko.mdmarkdown6.9 KB
rules/axum/platform.mdmarkdown6.3 KB
rules/axum/project-structure.ko.mdmarkdown10.8 KB
rules/axum/project-structure.mdmarkdown9.9 KB
rules/axum/routes.ko.mdmarkdown7.3 KB
rules/axum/routes.mdmarkdown6.3 KB
rules/axum/testing.ko.mdmarkdown5.2 KB
rules/axum/testing.mdmarkdown4.6 KB
rules/axum/validation.ko.mdmarkdown4.8 KB
rules/axum/validation.mdmarkdown4.4 KB
rules/electron/packaging.ko.mdmarkdown7.9 KB
rules/electron/packaging.mdmarkdown7.0 KB
rules/electron/performance.ko.mdmarkdown5.8 KB
rules/electron/performance.mdmarkdown5.0 KB
rules/electron/processes-and-ipc.ko.mdmarkdown10.6 KB
rules/electron/processes-and-ipc.mdmarkdown9.7 KB
rules/electron/project-structure.ko.mdmarkdown8.8 KB
rules/electron/project-structure.mdmarkdown8.1 KB
rules/electron/renderer.ko.mdmarkdown10.8 KB
rules/electron/renderer.mdmarkdown9.8 KB
rules/electron/security.ko.mdmarkdown10.3 KB
rules/electron/security.mdmarkdown9.2 KB
rules/electron/testing.ko.mdmarkdown5.7 KB
rules/electron/testing.mdmarkdown5.0 KB
rules/expo/data-state-and-boundaries.ko.mdmarkdown4.7 KB
rules/expo/data-state-and-boundaries.mdmarkdown4.3 KB
rules/expo/native-platform-and-security.ko.mdmarkdown8.2 KB
rules/expo/native-platform-and-security.mdmarkdown7.5 KB
rules/expo/performance.ko.mdmarkdown11.2 KB
rules/expo/performance.mdmarkdown10.1 KB
rules/expo/project-structure.ko.mdmarkdown13.4 KB
rules/expo/project-structure.mdmarkdown13.2 KB
rules/expo/routing-and-navigation.ko.mdmarkdown8.6 KB
rules/expo/routing-and-navigation.mdmarkdown8.0 KB
rules/expo/testing-and-validation.ko.mdmarkdown5.1 KB
rules/expo/testing-and-validation.mdmarkdown4.8 KB
rules/hono/conventions.ko.mdmarkdown3.7 KB
rules/hono/conventions.mdmarkdown3.5 KB
rules/hono/database.ko.mdmarkdown11.7 KB
rules/hono/database.mdmarkdown10.8 KB
rules/hono/errors.ko.mdmarkdown3.9 KB
rules/hono/errors.mdmarkdown3.7 KB
rules/hono/handlers.ko.mdmarkdown2.5 KB
rules/hono/handlers.mdmarkdown2.2 KB
rules/hono/middleware.ko.mdmarkdown3.3 KB
rules/hono/middleware.mdmarkdown3.0 KB
rules/hono/openapi.ko.mdmarkdown11.7 KB
rules/hono/openapi.mdmarkdown10.9 KB
rules/hono/performance.ko.mdmarkdown8.9 KB
rules/hono/performance.mdmarkdown8.0 KB
rules/hono/platform.ko.mdmarkdown5.0 KB
rules/hono/platform.mdmarkdown4.7 KB
rules/hono/project-structure.ko.mdmarkdown10.4 KB
rules/hono/project-structure.mdmarkdown9.9 KB
rules/hono/routes.ko.mdmarkdown6.9 KB
rules/hono/routes.mdmarkdown6.6 KB
rules/hono/testing-rpc.ko.mdmarkdown5.6 KB
rules/hono/testing-rpc.mdmarkdown5.2 KB
rules/hono/validation.ko.mdmarkdown3.7 KB
rules/hono/validation.mdmarkdown3.5 KB
rules/lynx/native-and-platform.ko.mdmarkdown11.4 KB
rules/lynx/native-and-platform.mdmarkdown10.7 KB
rules/lynx/performance.ko.mdmarkdown11.6 KB
rules/lynx/performance.mdmarkdown10.6 KB
rules/lynx/project-structure.ko.mdmarkdown10.2 KB
rules/lynx/project-structure.mdmarkdown9.6 KB
rules/lynx/testing.ko.mdmarkdown7.0 KB
rules/lynx/testing.mdmarkdown6.4 KB
rules/lynx/threading.ko.mdmarkdown13.0 KB
rules/lynx/threading.mdmarkdown12.0 KB
rules/lynx/ui-and-data.ko.mdmarkdown11.8 KB
rules/lynx/ui-and-data.mdmarkdown10.8 KB
rules/nextjs/data-fetching.ko.mdmarkdown9.9 KB
rules/nextjs/data-fetching.mdmarkdown9.3 KB
rules/nextjs/db.ko.mdmarkdown8.1 KB
rules/nextjs/db.mdmarkdown7.3 KB
rules/nextjs/execution-model.ko.mdmarkdown5.0 KB
rules/nextjs/execution-model.mdmarkdown4.5 KB
rules/nextjs/hooks.ko.mdmarkdown5.8 KB
rules/nextjs/hooks.mdmarkdown5.3 KB
rules/nextjs/performance.ko.mdmarkdown12.5 KB
rules/nextjs/performance.mdmarkdown11.2 KB
rules/nextjs/platform.ko.mdmarkdown7.7 KB
rules/nextjs/platform.mdmarkdown7.0 KB
rules/nextjs/project-structure.ko.mdmarkdown9.4 KB
rules/nextjs/project-structure.mdmarkdown9.0 KB
rules/nextjs/route-handlers.ko.mdmarkdown4.7 KB
rules/nextjs/route-handlers.mdmarkdown4.3 KB
rules/nextjs/routes.ko.mdmarkdown5.0 KB
rules/nextjs/routes.mdmarkdown4.6 KB
rules/nextjs/server-actions.ko.mdmarkdown7.1 KB
rules/nextjs/server-actions.mdmarkdown6.4 KB
rules/nextjs/services.ko.mdmarkdown5.8 KB
rules/nextjs/services.mdmarkdown5.5 KB
rules/nextjs/validation.ko.mdmarkdown2.2 KB
rules/nextjs/validation.mdmarkdown2.3 KB
rules/rust/cli.ko.mdmarkdown13.6 KB
rules/rust/cli.mdmarkdown12.0 KB
rules/rust/crate-layout.ko.mdmarkdown11.4 KB
rules/rust/crate-layout.mdmarkdown10.1 KB
rules/rust/errors-and-logging.ko.mdmarkdown13.0 KB
rules/rust/errors-and-logging.mdmarkdown11.6 KB
rules/rust/mcp-server.ko.mdmarkdown15.2 KB
rules/rust/mcp-server.mdmarkdown13.8 KB

rules/nextjs/project-structure.ko.md

View on GitHub
# Project Structure and Shared Code Organization

> 공식 Next.js project structure 규칙과 `src/modules`, `src/services`, `src/db`, `src/server`, `src/integrations`, `src/config` 같은 nested shared folders를 위한 Hypercore local organization guidance.

---

## Top-Level Structure

| Folder | Meaning |
|---|---|
| `app/` 또는 `src/app/` | App Router route tree와 App Router special files |
| `pages/` 또는 `src/pages/` | legacy 또는 Pages-only surface용 Pages Router route tree |
| `public/` | site root에서 제공되는 static assets |
| `src/` | source code와 project configuration을 분리하는 optional application source root |
| `lib/`, `src/lib/`, `services/`, `src/services/`, `src/modules/`, `src/db/`, `src/server/`, `src/integrations/`, `src/config/` | Hypercore local shared code convention이며 Next.js routing convention은 아님 |

`next.config.*`, `package.json`, `tsconfig.json`, lockfiles, `.env*` files는 해당 tool docs가 다르게 말하지 않는 한 project root에 둡니다. `.env*` files가 `src/`에서 load된다고 가정하지 않습니다.

## Routing vs Organization

Next.js routing은 file-system 기반이지만 모든 folder가 같은 의미를 갖지는 않습니다:

- `app/` 또는 `src/app/`에서 folders는 route groups, private folders, special non-routing conventions가 아닌 한 route segments를 정의합니다.
- `(marketing)` 같은 folder는 route group입니다. URL을 바꾸지 않고 routes와 layouts를 organization합니다.
- `_components`, `_lib`, `_actions`, `_queries` 같은 folder는 private folder입니다. route로 처리되면 안 되는 segment-local implementation details에 private folders를 사용합니다.
- App Router segments 안에 files를 colocate할 수 있지만, private folders는 의도를 더 명확히 하고 future naming conflict를 줄입니다.

Implementation-only folder를 URL segment로 노출하지 않습니다. helper folder가 `app/` 아래에 있다면 그 folder가 route segment 또는 route group이어야 하는 경우가 아닌 한 `_folder` naming을 선호합니다.

## Shared Code Placement

여러 routes에서 공유되는 code는 repo의 기존 convention을 먼저 따르되 runtime/domain boundary가 드러나게 배치합니다. 다음 구조는 Hypercore local convention이며 official Next.js law가 아닙니다:

```text
src/
├── app/
├── components/
├── modules/
│   └── billing/
│       └── invoices/
├── lib/
│   ├── auth/
│   └── cache/
├── services/
│   ├── billing/
│   └── stripe/
├── db/
│   ├── client.server.ts
│   └── schema/
├── server/
├── integrations/
│   └── stripe/
└── config/
```

root-based project 예시:

```text
app/
components/
lib/
services/
server/
db/
```

이 shared folders는 framework law가 아니라 repo-local convention으로 취급합니다. `src/modules/billing/invoices`, `src/services/billing`, `src/db/schema`, `src/server/auth`, `src/integrations/stripe`, `src/config/env` 같은 preference를 reporting/review할 때 official Next.js docs가 요구하지 않는 한 "Hypercore local convention" 또는 "repo-local convention"이라고 표시합니다. 이 nested shared-folder shape는 official Next.js requirement가 아닙니다.

## Nested Shared Folder Grouping Policy

touched shared code를 추가하거나 재구성할 때 explicit project exception이 없으면 `src/modules/foo.ts`, `src/lib/foo.ts`, `src/services/foo.ts`, `src/db/foo.ts`, `src/server/foo.ts`, `src/integrations/foo.ts`, `src/config/foo.ts`, `lib/foo.ts`, `services/foo.ts` 같은 new direct leaf file을 만들지 않습니다. Ownership, runtime boundaries, provider integrations, domain logic이 드러나는 nested grouping을 선호합니다.

Project가 더 좁은 convention을 기록하지 않는 한 new touched shared code는 `src/modules/<domain>/<feature>/...`, `src/lib/<domain>/...`, `src/services/<domain-or-provider>/...`, `src/db/<area>/...`, `src/server/<area>/...`, `src/integrations/<provider>/...`, `src/config/<area>/...` 같은 ownership path를 사용합니다.

다음 경우 nested grouping을 선호합니다:

- new touched shared code가 otherwise `src/modules`, `src/lib`, `src/services`, `src/db`, `src/server`, `src/integrations`, `src/config`, `lib`, `services` 바로 아래 direct file로 놓일 때
- folder에 서로 다른 responsibility의 file이 3개 이상 있을 때
- domain, provider, layer, external integration별 자연스러운 분리가 있을 때
- server-only modules, DAL code, schemas, DTOs, cache tags, permissions가 섞여 있을 때
- routes를 가로질러 action/query/helper pattern이 반복될 때
- unrelated helpers가 나란히 있어 imports가 모호할 때

예시 nested shared shape:

```text
src/
├── modules/
│   └── billing/
│       └── invoices/
│           ├── invoices.actions.ts
│           ├── invoices.queries.ts
│           ├── invoices.server.ts
│           └── invoices.schemas.ts
├── lib/
│   ├── auth/
│   │   ├── session.ts
│   │   ├── permissions.ts
│   │   └── dto.ts
│   └── cache/
│       ├── tags.ts
│       └── revalidate.ts
├── services/
│   ├── billing/
│   │   ├── actions.ts
│   │   ├── queries.ts
│   │   └── schema.ts
│   └── stripe/
│       └── client.server.ts
├── db/
│   ├── client.server.ts
│   ├── schema/
│   │   └── users.ts
│   └── repositories/
│       └── users.server.ts
├── integrations/
│   └── stripe/
│       └── client.server.ts
└── config/
    └── env.ts
```

작은 existing folders는 더 단순하면 flat하게 유지할 수 있지만, new touched shared files는 explicit exception이 없으면 여전히 grouped 되어야 합니다. unrelated one-off files만을 위해 deep hierarchy를 만들지 않습니다.

## Boundary Naming Guidance

Runtime과 architectural boundaries가 드러나는 이름을 사용합니다:

| Pattern | Use for |
|---|---|
| `_components/` | `app/` 아래 segment-local UI implementation |
| `_lib/` | `app/` 아래 segment-local helpers |
| `_actions/` | `app/` 아래 segment-local Server Actions |
| `actions.ts` | reusable 또는 domain-specific Server Actions |
| `queries.ts` | server-side read helpers |
| `schema.ts` | validation 또는 data shape definitions |
| `dto.ts` | client-safe view models와 return values |
| `permissions.ts` | authorization checks |
| `cache/tags.ts` | cache tag names와 invalidation helpers |
| `src/modules/<domain>/<feature>/` | domain feature orchestration, reusable actions/queries/schemas/DTOs |
| `src/db/<area>/` | Drizzle schema, client, repositories, migrations, transaction helpers |
| `src/integrations/<provider>/` | external SDK/client adapters와 provider-specific mapping |
| `src/server/<area>/` | request/session/server runtime utilities |
| `src/config/<area>/` | env/runtime config, feature flags, deployment config |

DB clients, DAL modules, secret-bearing SDK wrappers, authorization helpers처럼 client graph에 절대 들어가면 안 되는 modules에는 `import 'server-only'`를 추가합니다.

## Hard Rules

| 확인 | 규칙 |
|---|---|
| `app/` 아래 implementation-only folder가 route segment로 노출됨 | 의도적으로 routable하지 않으면 차단 |
| touched shared root에 `src/modules/foo.ts`, `src/lib/foo.ts`, `src/services/foo.ts`, `src/db/foo.ts`, `src/server/foo.ts`, `src/integrations/foo.ts`, `src/config/foo.ts` 같은 direct leaf file 추가 | 경고. logical nested folder로 이동 |
| touched code에서 flat `lib` layout이 server/client, domain, security boundaries를 숨김 | 경고. nested grouping 권장 |
| shared code placement를 repo-local convention이 아니라 official Next.js law처럼 제시 | 차단 |
| 새 nested folders가 circular imports 또는 불명확한 public entry points를 만듦 | 위험도에 따라 경고/차단 |
| server-only shared code에 명확한 server boundary가 없음 | 경고, client import risk가 있으면 차단 |

## Review Checklist

- Top-level `app`, `pages`, `public`, optional `src` usage가 detected router mode와 일치함.
- `app` segment internals가 route segments가 아닐 때 private folders를 사용함.
- Route groups는 URL 변경이 아니라 organization 또는 layout sharing에 사용됨.
- New touched shared code는 explicit exception이 없으면 `src/modules`, `src/lib`, `src/services`, `src/db`, `src/server`, `src/integrations`, `src/config`, `lib`, `services` 바로 아래 direct leaf files를 피함.
- Shared `src/modules` / `src/lib` / `src/services` / `src/db` / `src/server` / `src/integrations` / `src/config` code는 boundaries를 개선한다면 nested domain, provider, layer grouping을 사용함.
- Nested grouping이 더 명확할 때 flat shared folders를 강요하지 않음.
- Framework-required rules와 repo-local conventions를 별도로 labeling함.
- Server-only shared modules에 `import 'server-only'` 또는 동등하게 명확한 boundary가 있음.

## Sources

> 확인 2026-11-04. `https://nextjs.org/docs/app/getting-started/project-structure`, `https://nextjs.org/docs/app/api-reference/file-conventions`, `https://nextjs.org/docs/app/api-reference/file-conventions/src`를 확인했습니다. 날짜가 붙은 스냅숏은 `references/official/nextjs/current-docs-2026-11-04.md`입니다.
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: 469kUpdated Claude CodeCodexVerifiedInstall
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: 469kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall