Skip to main content
Learn how to write effective prompts, use @-mentions for context, and select the right model preset for code generation.

​
What You’ll Learn

  • Compose effective prompts for code generation
  • Use @-mentions to provide context
  • Leverage Desktop-specific features for parallel development
  • Review generated code with Code Review

​
Prompt Composition

​
Effective Prompt Structure

For straightforward code generation:
Create a function that [does X]
Example:
Create a function that validates email addresses using regex

​
Iterative Development

Build features incrementally:
1

Start Simple

Request the basic structure or core functionality first
2

Review and Refine

Review generated code, request specific improvements
3

Add Complexity

Layer in error handling, edge cases, validation
4

Test and Polish

Request tests, documentation, or final polish

​
Using @-Mentions

@-mentions provide context by referencing specific files, folders, or symbols.

​
Syntax

MentionScopeExample
@filenameSingle file@userService.ts
@folder/Directory@src/components/

​
When to Use @-Mentions

Look at @authMiddleware.ts and create a similar middleware for rate limiting

​
Desktop-Specific Code Writing

​
Parallel Feature Development

Build unrelated features simultaneously in separate workspaces:
1

Create First Workspace

Click New Workspace in the Top Bar to create an isolated workspace for your first feature
2

Name the Workspace

Give the workspace a descriptive name (e.g., “feature-auth”)
3

Start a Task

In the input box, describe what you want to build and send your message to start a new task
4

Create Additional Workspaces

Repeat the above steps for each additional feature you want to work on
5

Work in Parallel

Each agent works independently in its own workspace without conflicts
6

Review Changes

When a feature is complete, review changes
7

Rebase to main branch

Click Workspace Actions → Rebase to main branch to apply changes
Example: Build an authentication system in one workspace while another agent builds the dashboard UI in a separate workspace.

​
Plan Mode for Complex Features

For complex code generation:
  1. Press Shift+Tab or Ctrl+. to switch to Plan Mode
  2. Describe the feature you want to build
  3. Review the plan Verdent creates
  4. Refine with follow-up questions
  5. Switch to Agent Mode to execute the plan
Benefit: Review approach before consuming credits on execution.

​
Reviewing Generated Code

After Verdent generates code, use Code Review for quality assurance:
1

View Code Review

After Verdent completes changes, the Code Review panel appears inline within the chat
2

Address Critical Issues

Review Must Fix items first, these are security, performance, or stability issues
3

Consider Suggestions

Review Suggestions for recommended improvements you may want to apply
4

Request Fixes

Ask Verdent to fix any issues by describing what needs to change in the input box
5

View Diff

Click Task Changes in the middle panel to see all file modifications
Code Review analyzes:
CategoryFocus
SecurityVulnerability scanning, injection risks, credential exposure
AccessibilityAccessibility compliance and best practices
PerformanceAlgorithmic complexity, resource usage
Call-chain ImpactDownstream effects on dependent code
Enable Auto Generate Code Review in Settings → Chat to automatically generate reviews after every change.

​
FAQs

  1. Be specific - Include exact requirements
  2. Provide context - Use @-mentions for relevant files
  3. Specify patterns - Reference existing code as examples
  4. Iterate - Build incrementally rather than all at once
Use Plan Mode for:
  • Complex multi-file changes
  • Unfamiliar patterns or codebases
  • When you want to review approach first
Skip Plan Mode for:
  • Simple, straightforward tasks
  • Well-understood changes
  • Quick iterations
Yes. Create separate workspaces for each feature by clicking New Workspace in the Top Bar. Each workspace has its own agent working in isolation.
You don’t need to delete the entire workspace to undo changes. You have several options:
  • Rollback: Hover over any message in the chat and click Rollback to this point to revert to an earlier state.
  • Use Source Control: Open Source Control (Ctrl+Shift+G / Cmd+Shift+G) to view changed files and revert specific changes.
  • Delete workspace: Click Delete Workspace in the Workspace Bar to discard all changes in that workspace. Your base workspace remains unaffected.
Yes. Code reviews consume credits based on the amount of code analyzed. Disable auto-review in Settings → Chat if you want to save credits.
Yes. Ask Verdent to write tests by describing what to test and referencing files with @-mentions (e.g., “Write tests for @userService.ts”).

​
See Also

Code Review

Auto-generated quality assessment

Refactoring

Safe refactoring workflows

Best Practices: Prompts

Prompt engineering tips