How to write a good ticket

You describe what you want. AdenAI builds it. Everything AdenAI knows about your idea is in the ticket. There is no kickoff call and no follow-up meeting.

One ticket, one change

Keep a ticket to a single thing. "Add a contact form" is one ticket. "Add a contact form, update the prices and change the colours" is three.

The reason is practical. If AdenAI misreads something in one large ticket, you have to describe the whole thing again. With three small tickets you only correct the one that went wrong. Small tickets also finish faster and cost fewer credits.

What belongs in the description

Not how it should be built, but what should come out of it:

• Who uses this and why. "Visitors should be able to reach me without opening their mail app."
• Which fields, which content. Name, email, message. Or: these four products with these prices.
• Where it goes. A new page, or at the bottom of the home page.
• How it should feel. "Calm and professional" or "colourful and playful" is far better than nothing. If you have specific colours in mind, write them down.
• What must not happen. Often the most useful line in the whole ticket.

An example

Too thin:

Make a contact page.

Good:

New page "Contact", linked in the top navigation. Form with name, email and message, all three required. After sending, a short thank-you on the same page, no redirect. Below that, my address and phone number as plain text. Same style as the rest of the site, no new colours.

The second version is not better because it is longer. It is better because it makes decisions. Every decision you do not make, AdenAI makes for you.

What you can leave out

Technology. You do not need to name frameworks, databases or file names. If you do know what you want, say so, but you are not expected to.

Politeness formulas too. "Could you please, if at all possible, build me" only takes up space. Bullet points are perfectly fine.

AdenAI asks when something essential is missing

Before building, AdenAI checks whether something decisive is still open: colours, audience, direction. If so, you get a question as a comment on the ticket, usually with answer options you can click. You answer, and work continues.

This happens rarely on purpose. One good question beats five, and most tickets need none at all.

Credentials do not belong in a ticket

Passwords, API keys and tokens have no place in a ticket. The ticket text goes into every prompt sent to the AI model and stays visible in the thread afterwards.

We filter what we recognise: if the filter finds a key in the title or description, it is masked and you get a note about it. Still, do not rely on every format being caught.

The right place is Credentials in the project settings. Anything you store there is encrypted and only decrypted at deployment time. AdenAI is only told the names of the variables, never the values.

After you submit

• Starting costs nothing. Credits are deducted continuously while the work happens, based on what the run really used. See Credits.
• Only one task runs per account at a time. Further tickets wait in line and start on their own.
• The ticket shows progress. Every few minutes AdenAI posts one sentence about what it is working on. At the end you get the link to the result.
• Something not right? Write it as a comment on the same ticket instead of opening a new one. AdenAI reads the thread.