Maintain repository context

The exported Skafold Context Package should evolve with the project. Skafold remains the visual editing surface; the Markdown files remain the repository-facing context.

Initial repository setup

1. Download the full Project Context ZIP.
2. Extract it.
3. Add Skafold Context Package/ to the repository.
4. Commit the folder.
5. Give your coding tool the kickoff prompt shown by Skafold.

The tool should start with Overview and Documentation Guidance.md, then read the frame files relevant to the task.

Update one frame

When one planning area changes:

1. Make the change in Skafold.
2. Use that frame's Download frame Markdown action.
3. Replace the matching file in Skafold Context Package/.
4. Review the Git diff.
5. Commit the context update with or before the related implementation.
6. Give the coding tool Skafold's frame update prompt.

File mapping:

• Project Brief → Project Overview.md
• Structure → Structure.md
• User Journeys → User Journeys.md
• Page Hierarchy → Page Layouts.md
• Technical Architecture → Technical Architecture.md
• Design Guidance → Design Guidance.md

You can use Copy frame context instead and paste over the existing file contents.

Update several frames

Replace every affected Markdown file, then use the multi-file update prompt provided by Skafold. Ask the coding tool to inspect the Git diff and identify implementation consequences.

Do not regenerate unrelated files simply to change timestamps or formatting. Smaller diffs make planning changes easier to review.

Typical maintenance loop

Stakeholder or implementation feedback
        ↓
Update the plan in Skafold
        ↓
Export the changed frame Markdown
        ↓
Replace the repository file
        ↓
Review and commit the diff
        ↓
AI or team updates implementation

Examples

A page gains a new section

Add and configure the section in Page Hierarchy, then replace Page Layouts.md.

The route hierarchy changes

Update Structure. If the affected pages also need section changes, replace both Structure.md and Page Layouts.md.

A provider or data model changes

Update Technical Architecture and replace Technical Architecture.md. Update affected section build guidance too when page implementation changes.

Visual direction changes

Update Design Guidance and replace Design Guidance.md. If page composition changes, update Page Hierarchy as well.

A conversion flow changes

Update the relevant User Journey. Update Structure only when the primary page hierarchy changed.

Keep Skafold and the repository aligned

Avoid editing exported Markdown as the only source of a lasting planning change. Make the durable change in Skafold, then export it. Otherwise the next frame export may overwrite repository-only edits.

Repository annotations that do not belong in Skafold can live in separate engineering documentation.

Use JSON for structural AI revisions

If an AI is going to modify the editable plan itself:

1. Download Skafold JSON.
2. Give it to the AI with the requested changes.
3. Import the complete revised JSON over the existing project.
4. Review the canvas.
5. Export the affected Markdown files to the repository.

This closes the loop between discovery, visual planning, repository context, and implementation.