Keep AI Context current

The AI Context URL is stable, but its published snapshot changes only when the team chooses 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
        ↓
AI returns one scoped frame-update
        ↓
Skafold previews and applies supplied frames

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.
• Page placements, order, instance names, or page-specific status.
• Technical Architecture or Design Guidance.

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 generating a Skafold update, use the current locally installed Project Importer rather than old copied instructions.

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 a team update

Before publishing or importing:

1. Wait for the toolbar to show Saved.
2. Confirm another collaborator is not editing a targeted frame.
3. Publish AI Context.
4. Ask the AI for the smallest frame combination that completely represents the requested change.
5. Review removals carefully before applying the file.

If another team member changes a targeted frame after generation, the import is rejected as stale. Publish again and regenerate rather than forcing the older update over newer work.

Related-frame examples

Add a page

Request Structure and Page Hierarchy together. Structure owns page identity and direct hierarchy; Page Hierarchy owns the page’s planning and placements.

Change a reusable Section

Request Sections. Also include Page Hierarchy if placements must be removed, reassigned, renamed, or reordered.

Change a journey

Request User Journeys only unless the primary Structure also changes.

Change implementation architecture

Request Technical Architecture. Include Sections or Page Hierarchy only when their implementation guidance or composition also changes.

Link deletion

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.