Skafold Documentation

Export and Maintenance

Skafold Context Exporter

Export the Markdown handoff package used by IDEs, plus JSON exchange files, screenshots, and focused context.

The Skafold Context Exporter turns a project already planned in Skafold into the Markdown handoff package added to an IDE or repository for implementation. This is the direction Skafold project → IDE implementation.

It is separate from Skafold Project Importer, which turns a user's AI conversation and project thinking into JSON that creates or updates a project inside Skafold. Use Markdown for repository and implementation context, JSON for editable Skafold project exchange, and screenshots for visual reference.

Download Project Context

Choose Export Context → Download Project Context to download a ZIP containing:

  • Overview and Documentation Guidance.md
  • Project Overview.md
  • Structure.md
  • User Journeys.md
  • Sections.md
  • Page Layouts.md
  • Technical Architecture.md
  • Design Guidance.md

The ZIP contains a Skafold Context Package folder. Add that complete folder to the repository or project workspace.

After download, Skafold provides a kickoff prompt. Give it to your coding tool so the tool reads the package before planning or implementation.

Page Layouts in the package

Sections.md contains the stable reusable definitions, including shared structures, notes, composition tags, build guidance, library workflow status, and usage counts.

Page Layouts.md is generated from Page Hierarchy and includes:

  • Ordered sections for each page.
  • Selected abstract section patterns.
  • Shared section markers.
  • Workflow status color and its suggested meaning.
  • Notes, composition tags, and build guidance.

Use this file as the authoritative page composition handoff. Structure.md describes route hierarchy and paths; Page Layouts.md describes what each page contains.

Download Skafold JSON

Choose Import/Export JSON → Download Skafold JSON to create a complete editable skafold-context package.

Use this file to:

  • Continue discovery with Skafold Project Importer in ChatGPT or Codex, or with its standalone skill in Claude or Gemini.
  • Ask an AI to add or revise pages, journeys, architecture, or design guidance.
  • Move a project between compatible Skafold workflows.
  • Keep a recovery snapshot before replacing a project.

JSON is not the repository handoff format. It is the round-trip exchange format for the editable project model.

The JSON package includes Page Hierarchy data:

  • globalSections
  • pages[].sections[].globalSectionId
  • pages[].sections[].layout
  • pages[].sections[].tags
  • pages[].sections[].buildGuidance
  • pages[].sections[].statusColor
  • globalSections[].statusColor for the reusable definition's independent library workflow state

Page instance statusColor and globalSections[].statusColor are independent. Explicit statuses use blue, purple, amber, red, or green; omit the field for no status or not started. Legacy gray values import as no explicit status and are not exported. Do not combine statusColor with legacy completed in the same imported section.

Legacy completed: true values remain import-compatible and map to green.

Preserve these fields when an AI revises the file.

Import/Export JSON

This workflow helps you revise the current project with AI. It lets you download the current Skafold JSON, copy an AI revision prompt, upload the revised complete package, preview project-level changes, then apply the update.

Ask the AI to preserve IDs for unchanged items and return one complete package, not a patch. Skafold records a rollback point when the update is applied.

When a revised package is applied to the existing project, Skafold tries to reuse matching nodes, connector paths, page placements, and Page Hierarchy card positions. This works best when the AI preserves IDs for unchanged pages, sections, journeys, architecture items, and shared sections.

Copy project screenshot

This copies or downloads a visual image of the full project structure. Use it as supporting reference alongside Markdown, not as the only implementation context.

Frame exports

Each frame header supports:

  • Copy frame context: places the frame's Markdown on the clipboard.
  • Download frame Markdown: downloads the correctly named Markdown file.
  • Copy frame screenshot: captures that frame as a visual reference.

Frame files map directly to files in the full context package. This makes incremental updates possible without regenerating and replacing the entire folder.

Page context

Page nodes include Copy page context. The copied Markdown combines:

  • Page context
  • Page section outline
  • Goal and CTA where available
  • Requirements and constraints
  • SEO and interaction notes
  • Direct child pages and connected services or data

Use this for a focused implementation task involving one page. Keep the full context package available when the page depends on broader architecture or design decisions.

Readiness and export

Skafold allows a draft export once the project has:

  • A substantive brief
  • At least one meaningful page
  • At least one page with sections

A strong handoff has sections for every meaningful page. Optional design, journey, and architecture context should be included whenever it materially affects implementation.

Which export should I use?

  • Starting implementation: Download Project Context.
  • Updating one planning area in a repository: Download or copy that frame Markdown.
  • Giving an AI the editable Skafold project: Download Skafold JSON.
  • Applying an AI revision to the current editable project: Import/Export JSON.
  • Providing visual orientation: Copy a frame or project screenshot.
  • Working on one isolated page: Copy page context.

Continue with Maintain repository context.