scbe-codebase-orienter
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.
Best use case
scbe-codebase-orienter is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using scbe-codebase-orienter should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/scbe-codebase-orienter/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scbe-codebase-orienter Compares
| Feature / Agent | scbe-codebase-orienter | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# SCBE Codebase Orienter Use this skill when the repo feels too large or too mixed to reason about quickly. ## Orientation Workflow 1. Read `AGENTS.md` and `package.json` first. 2. Read `references/repo-map.md` for the high-level lane breakdown. 3. Read `references/runtime-entrypoints.md` when the task involves running code, APIs, HYDRA commands, or the webtoon/manhwa lane. 4. Separate active code from support material before making claims. ## Repo Truths - Treat `src/` as the main codebase, but note that it is hybrid: it contains both TypeScript package modules and Python runtime modules. - Treat `package.json` as the clearest statement of the npm-distributed TypeScript surface. - Treat `src/api/main.py` and `api/main.py` as different service lanes, not duplicates with identical purpose. - Treat `scripts/` as the operational control plane. Many real workflows live there before they become package APIs. - Treat `artifacts/`, `dist/`, and most of `training-data/` as outputs, corpora, or generated assets unless the user explicitly wants those lanes. - Treat docs as guidance, not proof. When behavior matters, verify against code in `src/`, `api/`, and `scripts/`. ## Output Pattern When explaining the codebase, answer in this order: 1. What the repo is trying to do. 2. Which top-level lanes are active. 3. Which file or directory is the right entrypoint for the user's goal. 4. Which areas are generated, historical, or likely to be noisy. 5. Which command to run next if the user wants to inspect or execute something. ## Avoid These Mistakes - Do not flatten the repo into "just one API". Explain whether the question is about the governance API in `api/` or the newer control-plane work in `src/api/`. - Do not treat all docs as current. Prefer code and tests when there is tension. - Do not send users into `artifacts/` or `training-data/` unless the task is specifically about datasets, webtoon outputs, exports, or generated evidence. - Do not assume every top-level folder is product-critical. Many are experiments, snapshots, or support lanes. ## References - Use `references/repo-map.md` for the core lane map and "where to start" view. - Use `references/runtime-entrypoints.md` for run commands and file-level entrypoints.
Related Skills
scbe-training-pair-authoring
Create prompt and response and metadata training pairs from SCBE documents, repair traces, terminal sessions, and operational workflows using the repository's canonical dataset contract and provenance rules.
scbe-spin-conversation-engine
Generate SFT training data via radial matrix conversation pivots with D&D-style combat research mode. Produces diverse, cost-effective training pairs with Sacred Tongue encoding, golden spiral problem distribution, and harmonic re-attunement.
scbe-research-training-bridge
Stage arXiv evidence and Obsidian markdown into source-grounded Hugging Face training bundles for research, review, and later SFT runs.
scbe-document-management
Consolidate overlapping docs, classify files by authority, and keep SCBE repo documents aligned with runtime truth. Use when the repo has drift between canonical docs, public docs, proposal notes, research branches, and generated evidence.
scbe-colab-bridge
Control Google Colab notebooks from Claude Code via Chrome extension. Execute cells, run terminal commands, read outputs, and manage GPU compute remotely.
scbe-claim-to-code-evidence
Map SCBE Notion technical claims, proof pages, and patent-facing architecture notes to concrete repository evidence such as code paths, tests, demos, and docs. Use when Codex needs to build a due-diligence packet, claim-to-code audit, implementation crosswalk, patent support note, or proof summary from local Notion exports and repo artifacts.
scbe-autonomous-worker-productizer
Turn SCBE automation, autonomous worker, and revenue-system notes into concrete offers, workflow packs, pilot plans, or SaaS-facing product packets. Use when Codex needs to package Notion automation pages into buyer-ready offerings, n8n/Zapier workflow designs, flock-backed worker systems, or implementation roadmaps tied to existing SCBE repo surfaces.
scbe-code-scanning-ops
Operate GitHub code scanning and CodeQL remediation for SCBE repositories. Use when triaging code-scanning alerts, mapping alert classes to fix patterns, validating targeted regressions, or wiring dedicated CodeQL workflows and runbooks into the repo.
scbe-world-anvil-lore-rag-7th-tongue
Build and operate a lore-focused RAG system using World Anvil exports and SCBE docs, with deterministic Claude/Codex cross-talk packets for handoff. Use when users ask to structure lore canon retrieval, sync worldbuilding data, enforce citation-grounded generation, or coordinate a 7th Tongue overseer lane across multiple AI agents.
scbe-webtoon-book-conversion
Convert The Six Tongues Protocol and related manuscript sections into webtoon/manhwa storyboard packets, episode roadmaps, panel expansion plans, and image-generation-ready prompt lanes. Use when extending the series storyboard, adapting book chapters into vertical scroll episodes, or keeping art generation tied to canon instead of drifting into generic fantasy panels.
scbe-voice-render-verification
Govern and verify SCBE voice rendering work that maps Langues weighting into breath, phase, and Layer 14 audio-axis packets. Use when implementing or reviewing `scripts/voice_gen_hf.py`, emitting sidecar voice packets, validating canonical tongue ordering, tuning breath planning or phase timing, or keeping voice docs and code aligned with `docs/LANGUES_WEIGHTING_SYSTEM.md` and `docs/specs/SCBE_VOICE_EMOTIONAL_TIMBRE_SYSTEM.md`.
scbe-universal-synthesis
Orchestrate all installed Codex skills through an auto-updating synthesis matrix with Sacred Tongues routing, emotion/intent metadata, and decodable lexicon packets tied to established SCBE characters. Use when the user asks for cross-skill coordination, auto skill updates, multi-skill routing, or Sacred Tongues intent mapping.