living-codex-browser-builder

星标1

分支0

更新时间2026年4月2日 23:21

Build and evolve an AI-native browser stack (Living Codex Browser / AetherBrowse) using existing SCBE infrastructure. Use when implementing browser architecture, headless research lanes, UI panels, agent routing, or browser reliability/performance upgrades across Electron, Playwright, and runtime APIs.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

issdandavis

issdandavis/scbe-aethermoore-demo

打开 GitHub 仓库查看创作者相关仓库

下载

Living Codex Browser Builder

Overview

Execute browser development as a lifecycle, not ad hoc patches. Prefer upgrading existing AetherBrowse systems over rebuilding from scratch.

Default Architecture

Use Infestation mode by default:

Keep Electron shell as primary product container.
Keep FastAPI runtime as control plane.
Keep Playwright worker as browser execution engine.
Add headless research as a dedicated lane, not mixed with user-facing coding panels.

Only switch to alternate architecture if there is a hard blocker:

Hive Mind mode (extension-first): use when shell work is minimal.
Chrysalis mode (web app + browser split): use when strict isolation is required.

Development Flow

Use this exact loop for every browser feature:

Plan

Define feature goal, constraints, affected modules, and acceptance tests.

Architect

Choose integration points across:
- aetherbrowse/electron/*
- aetherbrowse/runtime/*
- aetherbrowse/worker/*
- src/api/* when API surface changes are needed.

Evaluate

Verify design for:
- governance boundaries
- headless vs visible path separation
- performance and failure blast radius.

Implement

Ship smallest useful slice.
Keep patches scoped and reversible.

Test

Run module compile/lint/unit/smoke checks.
Run one real navigation task.

Patch only verified failure points.

Test

Re-run failed checks and smoke path.

Improve

Optimize routing, reliability, or UX after stability.

Test

Confirm no regressions after improvements.

Fix or Launch

If risk remains: fix and loop.
If green: launch.

Launch

Publish release notes with changed files and verification results.

Browser Lane Rules

Use dual browser engines intentionally:

playwriter: preferred for signed-in existing-tab flows.
playwright: preferred for isolated automation and deterministic headless runs.

Always route tasks first:

python scripts/system/browser_chain_dispatcher.py --domain <domain> --task <task> --engine playwriter|playwright

Definition of Done

Feature works end-to-end in one real browser path.
Logs are written to artifact lanes.
Tests/smokes pass.
No unrelated files are touched.
Final output includes what changed, how verified, and next launch action.

Output Contract

Return:

files_changed
verification_run
known_risks
launch_state (hold or go)

同仓库更多 Skills

同仓库

aether-phone-lane-ops

issdandavis/scbe-aethermoore-demo

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.

2026-04-021

aetherbrowser-arxiv-nav

issdandavis/scbe-aethermoore-demo

Navigate arXiv papers and topic searches through AetherBrowser for research extraction workflows. Use when collecting abstracts, paper metadata, and evidence snapshots from arxiv.org.

2026-04-021

aetherbrowser-github-nav

issdandavis/scbe-aethermoore-demo

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.

2026-04-021

aetherbrowser-huggingface-nav

issdandavis/scbe-aethermoore-demo

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.

2026-04-021

aetherbrowser-notion-nav

issdandavis/scbe-aethermoore-demo

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.

2026-04-021

aetherbrowser-operator

issdandavis/scbe-aethermoore-demo

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.

2026-04-021

name	living-codex-browser-builder
description	Build and evolve an AI-native browser stack (Living Codex Browser / AetherBrowse) using existing SCBE infrastructure. Use when implementing browser architecture, headless research lanes, UI panels, agent routing, or browser reliability/performance upgrades across Electron, Playwright, and runtime APIs.

Living Codex Browser Builder

Overview

Execute browser development as a lifecycle, not ad hoc patches. Prefer upgrading existing AetherBrowse systems over rebuilding from scratch.

Default Architecture

Use Infestation mode by default:

Keep Electron shell as primary product container.
Keep FastAPI runtime as control plane.
Keep Playwright worker as browser execution engine.
Add headless research as a dedicated lane, not mixed with user-facing coding panels.

Only switch to alternate architecture if there is a hard blocker:

Hive Mind mode (extension-first): use when shell work is minimal.
Chrysalis mode (web app + browser split): use when strict isolation is required.

Development Flow

Use this exact loop for every browser feature:

Plan

Define feature goal, constraints, affected modules, and acceptance tests.

Architect

Choose integration points across:
- aetherbrowse/electron/*
- aetherbrowse/runtime/*
- aetherbrowse/worker/*
- src/api/* when API surface changes are needed.

Evaluate

Verify design for:
- governance boundaries
- headless vs visible path separation
- performance and failure blast radius.

Implement

Ship smallest useful slice.
Keep patches scoped and reversible.

Test

Run module compile/lint/unit/smoke checks.
Run one real navigation task.

Patch only verified failure points.

Test

Re-run failed checks and smoke path.

Improve

Optimize routing, reliability, or UX after stability.

Test

Confirm no regressions after improvements.

Fix or Launch

If risk remains: fix and loop.
If green: launch.

Launch

Publish release notes with changed files and verification results.

Browser Lane Rules

Use dual browser engines intentionally:

playwriter: preferred for signed-in existing-tab flows.
playwright: preferred for isolated automation and deterministic headless runs.

Always route tasks first:

python scripts/system/browser_chain_dispatcher.py --domain <domain> --task <task> --engine playwriter|playwright

Definition of Done

Feature works end-to-end in one real browser path.
Logs are written to artifact lanes.
Tests/smokes pass.
No unrelated files are touched.
Final output includes what changed, how verified, and next launch action.

Output Contract

Return:

files_changed
verification_run
known_risks
launch_state (hold or go)