PRODUCT GUIDE / PRODUKTLEITFADEN

Prompt Engine

Prompt Engine turns a broad idea into a reviewed architecture and sequential work packages. Clarify the important decisions, approve the blueprint and keep the master plan, shared rules and package checklists in portable project files. It connects planning to the Vigthoria applications that carry out the work.

Your first workflow

  1. 01

    Describe the idea and clarify its missing decisions.

  2. 02

    Review and approve the architecture.

  3. 03

    Work through one checked package at a time.

  4. 04

    Save progress and hand the plan to your repository or next application.

Available working areas

01

Intent and gap analysis

Answer five focused questions with clickable suggestions and editable details before implementation begins.

02

Architecture and master plan

Review the goal, milestones, assumptions, expected files and shared project rules before approving the plan.

03

One package at a time

Load bounded context for the current task. Inspect the actual deliverables and checks, then record the checkpoint before continuing.

04

Direct application handoffs

Review the active brief in ViAgen7 or Visual Editor. Prepare app-specific scene, content and music work without reassembling the shared project intent.

05

Save the plan beside the source

Choose an authorized Community repository. Portable files under .vigthoria/plans/ survive the repository browser, ZIP and CLI transfer.

06

Continue locally

Use CLI 2.1.2 or later, open the project in Vigthoria Code and synchronize the cloud checkpoint before the next package.

Check the actual result

PROJECT_PLAN.md, AGENT_RULES.md, numbered package files, plan.json and a portable workloop runner.

Review the output against your task before sharing, publishing or relying on it. Retain the project files or records needed to continue.

Access and product scope

Use your Vigthoria account. Repository writes require permission in the selected project. Execution and media production use the selected app and its account access.

Planning prepares the task; it does not prove that the implementation passed. Existing saved repository content is not silently replaced by a changed snapshot.

If the next step does not work

I reach sign-in or access is denied.

Sign in with the intended Vigthoria account and reopen this product. Check the selected project, owner or team role and the current product entitlement in User Hub.

The task is queued or a required feature is unavailable.

Inspect the actual job and service state. Check whether the chosen route needs a provider connection, device support, signing setup or an enabled account feature. Keep a saved copy before retrying a completed action.

I need product support.

Include the product, action, time, visible error and relevant job or project identifier. Use a minimal example and keep passwords, secret keys and confidential source material out of the public form.

Continue with related tools