Skip to main content

Best Practice Workflow

tip

Always keep your code source controlled. That will enable you to selectively rollback the changes if you don't like what Priset did.

  1. Select Your Model: Ensure the AI Model/Type Dropdown is set to "Developer" for general tasks.
  2. Start a New Session: If you are starting a new task, click the New Session Button to clear the context. More info about using sessions is given in this article.
  3. Plan: For anything that looks more complex (e.g., full-stack scaffolding, legacy migrations, or intricate multi-file changes), select Architect Mode first to let Priset create possible implementation plans.
  4. Write Your Prompt: Clearly describe the task in the Prompt Input Box. If you used the Architect Mode review the proposed implementation plans.
  5. Execute: Click on the Run Button. If you used the Architect Mode approve and execute one of the proposed implementation plans.
  6. Review: Analyze the code diffs in the appropriate IDE windows to see if you like the changes made. Check the explanations in the Main Conversation Pane. Sometimes Priset will ask for user input as part of the conversation.
  7. Rollback: Undo the changes if you don't like them. You can also undo the changes selectively and keep those that you like.
  8. Test: Test your application to see if the new functionality works as expected.
  9. Fix: If things don't work as expected, use the same session to report the problem, exception, etc., and request Priset to fix them. You can attach screenshots, Word, or PDF documents that provide more details.
  10. Interrogate (Q&A Mode): Once the code is working, switch the Mode of Operation to Q&A Mode. Use this mode to interrogate the codebase against common code-review questions before finalizing. For example, ask Priset: "Are there any security vulnerabilities in the code we just wrote?", "Does this logic meet standard performance benchmarks?", or "Explain the time complexity of this new function."
  11. Check In: After successful testing and a clean Q&A review, check in the changes to your source control repository.
  12. Iterate: Continue the conversation with follow-up prompts until all tasks are complete.
alert

AI is not infallible and it cannot / should not replace humans. If you see that Priset has started doing changes that you haven't anticipated you should hit the Stop button. You can then use the same session to clarify your prompt and provide more details or start all over. Check Using Sessions for more details.

pro tip

Priset will automatically build the solution in order to check for build problems. Nevertheless, even if the solution builds properly it may have runtime errors and bugs. If you see that the runtime errors and bugs are related to the changes just made, use the same session to report them (so Priset would understand the context of the reported issues). Otherwise, when errors and bugs are not deemed related to the changes just made, report them in a new session. Check Using Sessions for more details. You can also use annotated screenshots to tell Priset what to change.