メニュー
Explain the SCBE-AETHERMOORE repo, separate live code from generated or archival material, and route work to the correct entrypoints. Use when Codex needs a fast codebase walkthrough, startup map, module ownership summary, or guidance on whether a feature lives in `src/`, `api/`, `scripts/`, `artifacts/`, or docs.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Boot, recover, tune, and verify the SCBE Android emulator phone lane for AetherCode and Polly Pad. Use when Codex needs to operate the `SCBE_Pixel_6_API35` emulator, repair stale lock state, resize the phone surface, or prove the current lane state from local artifacts.
Navigate arXiv papers and topic searches through AetherBrowser for research extraction workflows. Use when collecting abstracts, paper metadata, and evidence snapshots from arxiv.org.
Navigate GitHub repositories, pull requests, issues, and settings through AetherBrowser tentacle routing. Use when tasks require browser-based GitHub movement, page evidence capture, or coordinated lane assignment with playwriter or playwright.
Navigate Hugging Face models, datasets, and spaces through AetherBrowser for research, validation, and publishing workflows. Use when inspecting repo cards, files, docs, and leaderboard surfaces in browser mode.
Navigate Notion workspace pages in AetherBrowser for knowledge retrieval and workspace coordination tasks. Use when locating pages, databases, or section paths in browser mode before API operations.
Operate AetherBrowser as the primary online task surface across search, GitHub, Codespaces, research, Notion, Hugging Face, Shopify, and general web work. Use when Codex should drive a real browser session first, coordinate with built-in search or fetch tools second, capture page-state proof, and keep online work inside the SCBE browser lane instead of defaulting to generic web automation.
| name | scbe-codebase-orienter |
| description | Explain the SCBE-AETHERMOORE repo, separate live code from generated or archival material, and route work to the correct entrypoints. Use when Codex needs a fast codebase walkthrough, startup map, module ownership summary, or guidance on whether a feature lives in `src/`, `api/`, `scripts/`, `artifacts/`, or docs. |
Use this skill when the repo feels too large or too mixed to reason about quickly.
AGENTS.md and package.json first.references/repo-map.md for the high-level lane breakdown.references/runtime-entrypoints.md when the task involves running code, APIs, HYDRA commands, or the webtoon/manhwa lane.src/ as the main codebase, but note that it is hybrid: it contains both TypeScript package modules and Python runtime modules.package.json as the clearest statement of the npm-distributed TypeScript surface.src/api/main.py and api/main.py as different service lanes, not duplicates with identical purpose.scripts/ as the operational control plane. Many real workflows live there before they become package APIs.artifacts/, dist/, and most of training-data/ as outputs, corpora, or generated assets unless the user explicitly wants those lanes.src/, api/, and scripts/.When explaining the codebase, answer in this order:
api/ or the newer control-plane work in src/api/.artifacts/ or training-data/ unless the task is specifically about datasets, webtoon outputs, exports, or generated evidence.references/repo-map.md for the core lane map and "where to start" view.references/runtime-entrypoints.md for run commands and file-level entrypoints.