Skafold Documentation

Export and Maintenance

Export project context

Understand the full Markdown package, JSON exchange, screenshots, and page or frame-level export options.

Skafold provides different exports for different jobs. Use Markdown for repository and implementation context, JSON for editable 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
  • 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.

Download Skafold JSON

Choose Download Skafold JSON to create a complete editable skafold-context package.

Use this file to:

  • Continue discovery in ChatGPT, 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.

Import JSON and replace

This option validates a complete JSON package, then replaces the current project structure.

Export the current JSON first when you need a recovery point. Ask the AI to preserve IDs for unchanged items and return one complete package, not a patch.

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.
  • Replacing the current editable project: Import JSON and replace.
  • Providing visual orientation: Copy a frame or project screenshot.
  • Working on one isolated page: Copy page context.

Continue with Maintain repository context.