What You’ll Learn
- Request new features using natural language prompts
- Generate code across multiple files with proper dependencies
- Work with various programming languages and frameworks
- Scaffold entire project structures
- Iterate on generated code through conversational refinement
Prerequisites
Before writing code with Verdent:- Visual Studio Code with Verdent extension installed
- Active Verdent subscription with available credits
- A project workspace open in VS Code (or empty directory for scaffolding)
Requesting New Features
Verdent understands natural language feature requests without requiring special commands or syntax. Simply describe what you want in the Input Box. Basic Feature Requests: Start with straightforward descriptions of what you need:- Simple Requests
- Complex Requests with Plan Mode
Use concise descriptions for straightforward features:Verdent makes reasonable implementation choices based on your project’s existing code patterns.
Adding Context with @-Mentions
Reference specific files or components when you want targeted feature additions:@ symbol followed by a file path tells Verdent to focus on specific code when implementing your request. This ensures new features integrate seamlessly with existing implementations.
Language and Framework Support
Verdent works with virtually any programming language and understands code semantics, syntax patterns, and common frameworks across all major ecosystems without requiring language-specific plugins.- Exceptional Support
- Strong Support
Languages with outstanding results and deep framework understanding:
- JavaScript & TypeScript - React, Vue, Angular, Node.js, Next.js, modern async/await patterns, component analysis
- Python - Django, Flask, FastAPI, Pandas, NumPy, Jupyter notebooks, backend services, data analysis
- Java/Kotlin - Spring Boot, Hibernate, Maven/Gradle ecosystem, enterprise development
Framework Understanding
Beyond languages, Verdent recognizes framework-specific patterns:| Category | Frameworks & Patterns |
|---|---|
| Frontend | React hooks, Redux, Context API, Vue Composition API, Angular dependency injection, Next.js server components |
| Backend | Express middleware, Django ORM, Spring Boot microservices, FastAPI async endpoints, Rails Active Record |
| Testing | Jest, Pytest, JUnit, Mocha/Chai, Cypress, React Testing Library |
| Database | Prisma, TypeORM, Sequelize, SQLAlchemy, Hibernate, Mongoose |
Verdent adapts to your technology stack rather than requiring specific languages or frameworks. Well-organized codebases with clear separation of concerns produce better results regardless of programming language.
- Providing code examples showing patterns you want to follow
- Including snippets from existing codebase using @-mentions
- Using MCP (Model Context Protocol) servers to inject language-specific context
Multi-File Code Generation
Verdent creates multiple coordinated files in a single request, handling imports, dependencies, and cross-file references automatically. Example:components/UserDashboard/UserDashboard.tsx- Main componentcomponents/UserDashboard/useUserData.ts- Custom hookcomponents/UserDashboard/UserDashboard.module.css- Stylescomponents/UserDashboard/types.ts- TypeScript interfacescomponents/UserDashboard/UserDashboard.test.tsx- Tests
Generating Boilerplate and Scaffolding
Boilerplate Code Generation
Verdent generates boilerplate by understanding your project’s existing patterns and creating new code that follows the same style and structure:Project Scaffolding
Verdent scaffolds entire project structures with complete folder hierarchies, configuration files, dependencies, and initial code:package.json, tsconfig.json, component directories, routing configuration, context providers, test files, and version control setup (.gitignore, initial commit).
Best Practice for Scaffolding:
Use Plan Mode when scaffolding projects. Verdent will:
- Ask clarifying questions about preferences (styling solution, component structure, testing approach)
- Present a detailed plan with the complete file structure and directory layout
- Allow you to review and refine the scaffold before creation
- Generate the project with verification to ensure all files are created correctly
Iterating on Generated Code
Verdent uses a conversational workflow where you refine generated code through natural language follow-up requests in the same chat session. Basic Iteration Flow:- Verdent generates initial code
- You review the output
- You provide feedback or request changes
- Verdent updates the code based on your feedback
- Repeat until satisfied
- Request incremental changes without repeating context
- Test the code and report issues for Verdent to fix
- Ask “why” questions about implementation choices
- Try different approaches by asking for alternatives
Best Practices
Be as specific or general as needed
Be as specific or general as needed
Verdent understands various levels of detail. Provide technical specifics when you have requirements, or use general descriptions and let Verdent make informed choices based on your project patterns.
Start exploratory before making changes
Start exploratory before making changes
Before requesting new features, let Verdent understand your codebase with questions like “Analyze the database schema” or “Explain the authentication flow.” This builds context and helps Verdent make better suggestions.
Use Plan Mode for complex or multi-file features
Use Plan Mode for complex or multi-file features
Review detailed implementation plans before execution. Verdent asks clarifying questions and creates structured approaches. After generating the plan, choose Edit to refine or Start Building to execute, ensuring alignment before making changes.
Leverage @-mentions for targeted integration
Leverage @-mentions for targeted integration
Reference specific files when you want changes integrated with existing code. This ensures new features align with current implementations.
Break complex tasks into incremental steps
Break complex tasks into incremental steps
For multi-step features, work incrementally: create database table, then API endpoint, then UI component. This maintains clarity and allows verification at each step.
The more context you provide, the more aligned results will be
The more context you provide, the more aligned results will be
Include details about technology choices, design preferences, validation rules, error handling strategies, or any other requirements that matter to your implementation.