Save up to 90%Learn more
JobsiteOn

JobsiteOn Help Center

Great field operations start with clear guidance

Find complete route-verified guides for authentication, onboarding, owner workflows, settings, integrations, security, and release operations.

AI Agent Help-Center Maintenance Rules

Required AI-agent behavior for keeping help docs accurate.

Platform OperationsLiveOperations
Julian Park

Written by Julian Park

AI and Release Operations Lead

Updated 3/22/2026

Verified Routes

  • AGENTS.md
  • apps/AGENTS.md
  • packages/AGENTS.md
  • scripts/AGENTS.md
  • AGENTS/CONTEXT.md
  • CLAUDE.md
  • AGENTS/ARCHITECTURE.md
  • .claude/commands/web-change.md
  • .claude/skills/next-web-change-workflow/SKILL.md
  • DEPLOYMENT.md
  • apps/landing-web/vercel.json
  • AGENTS/TODO.md
  • AGENTS/DECISIONS.md

What this guide covers

This guide explains how to keep AI-agent policy updates aligned with the help center and release process. It now includes the special-case workflow for isolated landing-web changes and the folder-level AGENTS.md maintenance contract for major apps/, packages/, and scripts/ scopes.

Before you begin

  • Confirm whether the change is truly landing-web-only.
  • If any shared package or non-landing app is touched, stop using the landing-only path and fall back to the broader repo workflow.
  • Keep this article open while you update the policy files so the help center stays in sync.

Workflow overview

  1. Classify the scope.
  2. Update the core policy files.
  3. Sync platform-operations help content and task tracking.
  4. Validate only the smallest correct surface.

Step 1: Classify the scope

Use the landing-web-only path only when the runtime scope is limited to:

  • apps/landing-web/**
  • apps/landing-web/vercel.json
  • landing-web help content under apps/landing-web/data/help-center/**
  • landing-web public assets
  • landing-web-only docs such as docs/landing-web/** or docs/ramp-landing-web/**

Route checklist

  • AGENTS.md
  • AGENTS/CONTEXT.md
  • CLAUDE.md
  • AGENTS/ARCHITECTURE.md
  • .claude/commands/web-change.md
  • .claude/skills/next-web-change-workflow/SKILL.md
  • DEPLOYMENT.md
  • apps/landing-web/vercel.json
  • AGENTS/TODO.md
  • AGENTS/DECISIONS.md

If another app or any shared package is in scope, use the normal affected-workspace and deploy flow instead.

Step 2: Update the core policy files

Update the repo instructions first so future agents see one consistent rule:

  • AGENTS.md
  • folder-level AGENTS.md files in the touched apps/, packages/, and scripts/ path
  • AGENTS/CONTEXT.md
  • CLAUDE.md
  • AGENTS/ARCHITECTURE.md
  • .claude/commands/web-change.md
  • .claude/skills/next-web-change-workflow/SKILL.md

Record the policy decision in AGENTS/DECISIONS.md. Add a completed note in AGENTS/TODO.md when the change materially affects active operating rules. If the policy changes a governed apps/, packages/, or scripts/ path, stage the applicable folder-level AGENTS.md files too.

Step 3: Sync help-center and task tracking

Every AI-agent or release-process policy change must update the platform-operations help articles in the same change set. For this workflow, update the article you are reading and the related changelog/release article together.

If the policy work maps to an existing repo task, update that task file and TODO/PROGRESS.md before implementation begins, then keep them in sync through completion.

Step 4: Validate only the smallest correct surface

For isolated landing-web changes, run only:

  1. pnpm exec prettier -c <changed-files...>
  2. pnpm --filter landing-web build
  3. Route-level smoke or visual checks when public routes changed
  4. A manual check that apps/landing-web/vercel.json still contains:
    • buildCommand: "pnpm --filter landing-web build"
    • ignoreCommand: "npx turbo-ignore --task=build --fallback=HEAD^1 landing-web"

Do not expand to:

  • pnpm exec turbo run lint build --filter="...[origin/main]"
  • pnpm deploy:preflight
  • pnpm deploy:preflight:strict
  • whole-platform regression suites

Validation checklist

  • Policy files were updated together.
  • Applicable folder-level AGENTS.md files were staged for the touched governed paths.
  • Platform-operations help content was updated in the same change set.
  • pnpm --filter landing-web build passed for landing-web-only work.
  • apps/landing-web/vercel.json still points only at the landing-web build.

Troubleshooting

I am not sure whether the change is landing-web-only

If a shared package, another app, or backend contract changed, it is not landing-web-only. Use the broader repo workflow.

The build passed but I still expect broader checks

Do not add platform-wide tests just because the old default said so. The isolated landing-web rule is intentional and should stay narrow unless the change scope expands.

A pre-commit gate says folder-level AGENTS files are missing

Stage the applicable AGENTS.md files from the touched apps/, packages/, or scripts/ path. The gate is intentional and keeps local scope summaries current.

The Vercel config looks wrong

Fix apps/landing-web/vercel.json in the same change set before pushing. Landing-web-only deploys rely on that file staying app-scoped.

FAQ

When do we still run the full platform workflow?

Run the broader flow when the change touches shared packages, another app, API code, or multi-app release work.

Do landing-web-only changes still need help-center updates?

Yes, when the change is an AI-agent, changelog, or release-process policy update.

Do folder-level AGENTS files replace the repo-root instructions?

No. They narrow local context and file ownership, but repo-root AGENTS.md, CLAUDE.md, and AGENTS/DECISIONS.md still win on global policy.

Do we still check Vercel?

Yes. The isolated check is apps/landing-web/vercel.json, not the whole platform alias/preflight stack.

Notes

This article documents the current repo policy for isolated landing-web work.

Related articles