DEV Community

Cover image for Amazon Q Developer Tips: No.10 Personalise Amazon Q's output
Ricardo Sueiras for AWS

Posted on • Edited on

2 1 1

Amazon Q Developer Tips: No.10 Personalise Amazon Q's output

In this series I will be sharing daily hints and tips to help you get ahead and start to accelerate you on your own journey with Amazon Q Developer. Each day I will share a new tip, categorised against a few themes and topics. If you have your own tips or your own experiences with tips I share, please use the comment feature or feel free to contact me directly. Check out the previous tips here.

Ok, time for today's tip....

Tip 10 - Guiding Amazon Q : Personalise Amazon Q's output

In the previous Amazon Q Developer tip I walked you through setting up Amazon Q Developer Workspace Index, a powerful feature than enables Amazon Q Developer to index all the files in your IDE workspace, and then use that to provide useful context when using the @workspace command.

Today's tip uses this capability.

When I am interacting with Amazon Q Developer via the chat interface, I often have to repeat or add the following to prompts to influence the output:

  • Provide no explaination
  • Generate all code suggestions for the Flask framework
  • Use only open source libraries and projects

These have become second nature, but it would be great to simplify this. After reading Massimo's blog post (DIY personalization for Amazon Q Developer) I tried this out for myself and found that this is a really great tip for providing consistent or "personalised" output.

To do this I create a folder in my local workspace - I always call this ".qdeveloper" but it does not matter what you call this. Within this folder I create a series of markdown files that I want to use to personalise the output. For example, I might want to create personalisations for database code suggestions, so I would create a file called DBA.md and in this file add the following:

DBA

Only when I explicitly ask for code, follow this guidance:

- Only provide SQL code unless I explicitly ask for another language
- I am an expert in SQL and I did not need a walk through
- I have a strong preference for Sqlite and PostgreSQL
Enter fullscreen mode Exit fullscreen mode

After saving the file, I can now invoke this personalisation by using " @workspace DBA ....." followed by the rest of the prompt.

Check out this short video of this in action.

You can see some additional examples of how I use this here. Here is an example of me personalising the output for a Java developer.

Image description

That's it for today's tip. Let me know how you get on with this tip, and if you have your own drop me a message or reply. I would love to feature them here.

Try Amazon Q Developer today, and claim your free Builder ID

You can try Amazon Q Developer for free today, by signing up for a Builder ID. You can also check out my other posts on community.aws, as I have been sharing a lot of tips and use cases of how I am using Amazon Q Developer. You can also keep up to date with all the new features and improvements of Amazon Q Developer by checking out the changelog.


Made with ♥ from DevRel

Image of Timescale

Timescale – the developer's data platform for modern apps, built on PostgreSQL

Timescale Cloud is PostgreSQL optimized for speed, scale, and performance. Over 3 million IoT, AI, crypto, and dev tool apps are powered by Timescale. Try it free today! No credit card required.

Try free

Top comments (0)

A Workflow Copilot. Tailored to You.

Pieces.app image

Our desktop app, with its intelligent copilot, streamlines coding by generating snippets, extracting code from screenshots, and accelerating problem-solving.

Read the docs

👋 Kindness is contagious

Discover a treasure trove of wisdom within this insightful piece, highly respected in the nurturing DEV Community enviroment. Developers, whether novice or expert, are encouraged to participate and add to our shared knowledge basin.

A simple "thank you" can illuminate someone's day. Express your appreciation in the comments section!

On DEV, sharing ideas smoothens our journey and strengthens our community ties. Learn something useful? Offering a quick thanks to the author is deeply appreciated.

Okay