about 1 month ago
Pro tips for your project
Hey there,
Two required pieces that are easy to rush when you're deep in the code: your text description and your public repo. Plus a quick word on using AI tools while you build.
📝 Text description:
-
Explain what your project does, who it's for, and how it works — plain language, not just a feature list.
-
Lead with the problem. Could a judge tell what you built just from this plus your video?
-
Name Strands Agents explicitly — it's one of the first things reviewed.
📂 Public code repo:
-
Per the Official Rules: must include "all necessary source code, assets, and instructions required for the project to be functional."
-
MIT or Apache license visible in the About section — an actual license file, not just a README mention.
-
Setup instructions good enough that a stranger could get it running cold.
🤖 Using AI to build? A few things worth knowing:
-
AI coding assistants are explicitly allowed — use them for boilerplate, tests, debugging, whatever speeds you up.
-
Disclosure matters: per the Official Rules, you must disclose any pre-existing code or work you incorporate that isn't a standard tool. Writing new code with an assistant during the Submission Period is fine; reusing an old AI-built project isn't.
-
Don't let AI overstate your pitch. Judges aren't required to test your project and may score based only on your text description, images, and video.
-
Verify before you rely on it. AI tools hallucinate APIs with confidence — test what you plan to show in your demo ahead of time.
Check the Resources tab if you need a refresher on any of the Strands basics.