AI Context and Maintenance

Keep AI Context current

Publish deliberate project snapshots so every trusted AI chat and IDE reads the same current plan.

The AI Context URL is stable, but its published snapshot changes only when the team chooses AI Context → Update AI Context. This creates a deliberate boundary between active editing and AI-ready project context.

Normal maintenance loop

Team edits and saves the project
        ↓
Skafold shows Update AI Context
        ↓
Publish the reviewed semantic plan
        ↓
AI chat or IDE refetches the same URL
        ↓
Agent inspects current content in the signed-in editor
        ↓
Agent makes focused edits and verifies saving

When to publish

Publish after saved changes that should influence planning or implementation, including:

  • Project goals, audiences, constraints, or delivery notes.
  • Pages, paths, or direct parent-child hierarchy.
  • User Journey steps or tracking guidance.
  • Reusable section definitions, groupings, or status in Pages.
  • Page placements, order, instance names, or page-specific status.
  • Technical architecture in Structure or brand guidance in Documentation.

Canvas movement and other presentation-only edits may not create a new semantic revision. Skafold can still mark the active snapshot as checked and current.

Use the URL in an IDE

Give the bearer URL to the IDE agent as project planning context and ask it to fetch the URL before planning relevant implementation work. When editing a Skafold project, use the current locally installed Project Assistant and its computer-use guidance.

The URL is the synchronization point; you do not need to maintain a generated context folder in the repository.

Engineering decisions that do not belong in the Skafold plan can still live in normal repository documentation. If they materially change the agreed project, update Skafold and republish AI Context.

Coordinate edits

Ask an agent to inspect the current target immediately before editing it, respect active collaboration and save conflicts, and wait for Saved before continuing. The agent uses the signed-in account's normal history. After an interruption, check what saved before retrying.

A published snapshot is useful background but never permission to replace newer project content. Existing projects have no bulk AI import route. Substantial rebuilds belong in a separate project created from a validated seed, with their own history.

Delete AI Context only when the bearer URL may be compromised or the team intentionally wants to invalidate it. Deletion cannot be undone and a replacement link uses a new URL. Inform every team member and update every configured tool.