Skip to content
skivaDocumentation
Using Skiva

Describe. Review. Refine.

Turn natural language into proposed canvas edits while keeping the final decision yours.

Write a useful prompt

Name the components and explain their relationships. For edits, describe one clear outcome and include anything that should stay in place.

Move email delivery to a background worker. Add a queue between the Orders API and the email worker, and keep the existing database connections.

Review before applying

AI output arrives as a proposal. Check the additions, removals, and connections before accepting. Reject a suggestion if it misses your intent, then try a more specific prompt. AI can make mistakes; verify the architecture against your actual system.

Proposals use a diagram version

A proposal is tied to the diagram version it was generated from. If another edit changes that version, request a new proposal so you can review it against the latest canvas. Refreshing the page can restore a pending proposal.

Credit usage

Review the estimate shown before sending a command. Credits depend on model usage, so prompts can cost different amounts. See credits and billing for details. External MCP agents use their own model provider.