AGENTS.md

Guidance for coding agents working on the AB Framework web harness role.

Project Overview

The web harness owns the generated public web app: route shell, public UX, centralized API client, production web image shape, and generated <app>-web ownership when assigned by the orchestrator. It must stay separate from admin-only flows and server runtime internals.

Project Map

.claude/web/AGENT.md defines the web role.
.claude/web/README.md documents generated web expectations.
.claude/web/skeleton/ contains starter public web files.
.claude/agents/ab-framework-orchestrator.md coordinates role assignment.
.claude/scripts/verify-framework.mjs verifies generated suites.
docs/source-architecture.md and docs/harness.md explain the framework boundary.

Setup Commands

bashnode .claude/scripts/verify-framework.mjs
node .claude/scripts/lint-claude-harness.mjs
node .claude/scripts/lint-harness-md.mjs

Change Rules For Agents

Keep public web and admin surfaces separate.
Centralize API calls in the generated web API client.
Keep generated route and page files thin.
Use deploy-owned scripts for image build and compose execution.
Do not import shared runtime source from server, admin, or mobile repos.
Keep generated copy and routes product-specific but framework-pattern compliant.
Update verifier checks when skeleton expectations change.

Verification

bashnode .claude/scripts/verify-framework.mjs

Inspect generated <app>-web output after skeleton changes.

Security Notes

Public web code must not include admin credentials, server secrets, private endpoints, or real environment values. Use placeholders in skeletons and docs.

PR Checklist

Public routes remain thin.
API client remains centralized.
Admin-only behavior is not exposed.
Framework verifier passes.

AB Framework Web Harness Agent Guide