Working With AI

Import an AI-planned project

Create a Skafold project from a validated AI-generated seed, then maintain it through the editor and publish AI Context.

Skafold Project Assistant turns confirmed planning into a skafold-project-seed file. A seed creates a new project; it is not used to update an existing one.

Generate the seed

Use the installed Skafold Project Assistant in an AI tool that supports the plugin or standalone skill and its required tools.

Ask the AI to develop and confirm the plan before creating JSON:

Use Skafold Project Assistant to develop this project plan. Keep assumptions and open questions separate. Do not generate the import file until I confirm the plan is ready.

When ready:

Create one validated Skafold project seed from the confirmed plan.

The skill reads its bundled schemas and guidance before generation.

Create the project

  1. Open the Skafold dashboard.
  2. Choose Import AI Plan.
  3. Select the generated .json file.
  4. Review validation errors and warnings.
  5. Confirm the import.

Skafold creates and saves Documentation, Structure, and Pages before opening your new project. It is ready to edit immediately, without a separate legacy-project conversion.

Review the initial result

An AI-generated seed is a starting plan. Confirm:

  • Page names, paths, and direct parents.
  • Reusable Section definitions, patterns, content fields and groupings.
  • Page-specific placements, order, and instance names.
  • Assumptions and unresolved questions.
  • Technical or design decisions that need stakeholder approval.

Use the checklists in Documentation to review imported delivery, QA, and launch requirements.

Continue with AI Context

After the project exists, stop exchanging whole-project seed files. Create one AI Context link from AI Context → Manage AI Context.

For later changes, ask a computer-use agent to inspect and edit the relevant content in your signed-in project. It should preserve unrelated content and verify that each change saved. Publish AI Context after reviewing saved changes so other AI tools can read the revised plan.

Bulk update files are no longer supported. If the project needs a substantial rebuild, generate a new seed and import it as a separate project with its own history. Leave the original intact.

See Update an existing project with AI.

Shared Sections on import

Project seeds define each reusable Section once in globalSections. Page placements reference definitions with globalSectionId.

  • instanceName provides a page-specific label without renaming the definition.
  • Definition and placement status colours remain independent.
  • Divider rows use kind: "separator"; grouped definitions reference the divider through groupId.
  • Stable IDs connect the initial page, section, and relationship definitions.
  • A section's layout selects its visual pattern; contentSchema supplies its fields. The assistant copies and adapts starter fields from its bundled catalogue. Import does not create missing fields automatically.
  • Sections with the same pattern remain independent unless placements reference the same definition. Editing fields does not alter the pattern preview.

Validation warnings

A warning does not always block import. For example, a page may intentionally begin without placements. Errors must be corrected before import and normally identify an unsupported field, duplicate ID, missing reference, invalid hierarchy, or malformed value.