Temporary inboxes for agent signup QA — create disposable addresses, wait for verification email, extract OTP or magic links. Use when automating signup, login, or email verification without parsing HTML manually.
A coordinator for Codex Project Autopilot, a workflow that guides a project from an idea through planning, implementation, and handoff. It manages specialized roles and their required project files.
A backend implementation role for Codex Project Autopilot, a workflow that coordinates project work. It builds the server-side logic and connects it to integrations according to an approved plan.
A data-model planning role for Codex Project Autopilot, a workflow that coordinates project work. It designs how an application should store and protect its data when a data layer is needed.
A design-planning role for Codex Project Autopilot, a workflow that coordinates project work. It defines the visual direction and interaction approach for a selected project phase.
A frontend implementation guide for an active Codex Project Autopilot project. It directs the agent to build and check user interfaces according to an approved plan and design.
A discovery interviewer for Codex Project Autopilot, a workflow for turning an idea into a planned project. It asks short questions so a beginner's needs are clear before architecture or coding begins.
A project-specific quality check for Codex Project Autopilot, a workflow that coordinates development work. It reviews the project before handoff and records what was and was not tested.
Personal-data-protection compliance reference for engineers building applications subject to Singapore PDPA, Indonesia UU PDP 27/2022, Thailand PDPA B.E. 2562 (2019), Malaysia PDPA 2010 (with the 2024 Amendments), or Philippines DPA (RA 10173). Use when reviewing or modifying code that touches personal data …
Before running tests for a new package, make sure the test environment is already set up. If the package does not have tests yet, follow creating-julia-test-env first. Tests that use using Test must have Test available from the package or test project.
Use when planning or building the whole Bethesda modpack incrementally — batch strategy, rollback point, naming convention, separator discipline, attribution, and declaring 风格 before adding mods. Triggers - "build a modpack", "plan the pack", "batch strategy", "rollback point", "naming convention", "declare 风格"…
Use when a BGS modded game has CTD, crash log, FPS drop, stuttering, freeze, performance, won't start, 崩溃, 掉帧, 卡顿 symptoms and the user needs a symptom-first diagnostic ladder. NOT for proactive post-install testing; use testing-bgs-modpack.
Use when deciding whether a mod belongs in a modpack — judging mod quality, fit, risk, and pack-value BEFORE download/install. Triggers - "should I add this mod", "is this mod good", "评估这个mod", "这个mod值得装吗", "is this mod worth it", "this mod looks too good to be true", "compare these mods", "does this mod fit my pack".…
Use when deciding how to correctly download/install a Bethesda mod per the author's instructions — triggers "how do I install", "FOMOD choices", "which file to download", "author说明", "install instructions", "which variant", "按作者说明安装", "这个mod怎么装". NOT for deciding whether to include the mod (use evaluating-bgs-mods)…
Use after first-run for ongoing modpack maintenance: update/install KB packs, author or register custom/mod KB packs, maintain localization glossary KBs for translator use, prune KB cache, health-check the environment, version-pin KB/tooling, or handle recurring BGS modding environment care.