living-codex-browser-builder

Builds AI-native browser stacks with Electron, Playwright, and runtime APIs via lifecycle-driven development.

6|1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/issdandavis/SCBE-AETHERMOORE --skill living-codex-browser-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: living-codex-browser-builder
Source: https://github.com/issdandavis/SCBE-AETHERMOORE/tree/main/external/codex-skills-live/living-codex-browser-builder
Command: npx skills add https://github.com/issdandavis/SCBE-AETHERMOORE --skill living-codex-browser-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute browser development as a lifecycle, not ad hoc patches.

Core Features & Use Cases

  • Lifecycle-driven development loop: Plan, Architect, Evaluate, Implement, Test, Fix, Improve, and Launch to deliver browser features with governance and traceability.
  • Architecture modes and routing: default Infestation mode with Electron shell, FastAPI control plane, Playwright worker, and a dedicated headless research lane; alternative Hive Mind and Chrysalis modes for isolation or web app/browser split.
  • Governance, output contract, and risk controls: explicit output contracts, governance boundaries, and test/verification steps, enabling reproducible releases and auditability.

Quick Start

Describe a new browser feature and run through the development lifecycle to implement and test it.

Frequently Asked Questions about living-codex-browser-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Electron and Playwright browser development as a structured lifecycle instead of ad hoc patches?

Browser development as a structured lifecycle requires enforcing a Plan, Architect, Evaluate, Implement, Test, Fix, Improve, and Launch loop. This approach delivers Electron and Playwright features with governance boundaries, traceability, and reproducible releases.

What is an AI-native browser stack and how does agent routing work within it?

An AI-native browser stack integrates an Electron shell, FastAPI control plane, and Playwright worker. Agent routing directs tasks across these components and a dedicated headless research lane, enabling isolated execution and reliable feature delivery.

How do I set up a headless research lane for browser architecture work?

Setting up a headless research lane involves configuring the default Infestation architecture mode. This mode pairs a Playwright worker with a FastAPI control plane to route research tasks separately from the main Electron UI shell.

Do I need an explicit output contract and governance checks for browser feature releases?

Yes, an explicit output contract and governance checks are required for browser feature releases. These controls enforce test and verification steps, ensuring reproducible builds, auditability, and risk mitigation across the development lifecycle.

What's the best way to isolate browser features during development using alternative architecture modes?

To isolate browser features during development, use the alternative Hive Mind or Chrysalis architecture modes. These modes provide specialized isolation for web app and browser split workflows, contrasting with the default Infestation mode.

Can I use Playwright and Electron together for automated browser testing and UI panels?

Yes, you can use Playwright and Electron together for automated browser testing and UI panels. The architecture routes Playwright workers for testing and runtime API interactions within the Electron shell, ensuring reliability and performance upgrades.