Nice!
31.12.2025 18:23
👍 2
🔁 0
💬 0
📌 0
Nice!
Tons of great feedback on @erikch.bsky.social's talk at GitKon on learning Spec-Driven Development!
We're still live: gitkon.wistia.com/live/events/...
You got to check out the Caesar Forum! So many events happening there all week! I just saw a chicken eating contest and the Road to re:Invent. Plus I met these guys! #AWSreInvent
I made it to re:Invent! And I found the Kiro house!
Next js booth picture was
Come by and talk to us about AWS at Next.js Conf 👋 !
✅ Also check out our workshop at 11:35
✅ Get free swag at our booth!
✅ See a demo!
Picture of Aaron showing a slide about doing things
Awesome advice from @aaronfrancis.com at #cyc25!
Oops @commityourcode.bsky.social and @chrisdemars.net !
I’m leaning all about SBOMs from @saltnburnem at @CommitYourCode !
Autocomplete text
🔥 By default autocomplete is turned off in Kiro, however you can easily turn it on by clicking the Autocomplete in the status bar at the bottom. Or bringing up the command pallete (Cmd + Shift + P / Ctrl + Shift + P) and searching for the Kiro autocomplete (Cmd K, Cmd A). 🔥
A few more! And thanks you for everyone who came to my talk on Kiro!
It was great seeing everyone at CascadiaJS! Here are some pictures! Until next year!
🔥 Lot's happening in the Kiro world today! Check out our blog post on our new Auto mode and pricing plans! 🔥
kiro.dev/blog/new-pri...
This will then complete tasks one-by-one until it hits task four then stops. This is a good pattern because you can double check that each step is completed before continuing on. For a full list of Kiro tips check out my latest blog post -> kiro.hashnode.dev/top-8-tips-w...
Screenshot of Kiro tasks.md file with Start task showing
🔥Kiro Tip: When creating a new spec, you'll be presented with a task list after the requirements and design is created. Instead of clicking "Start task" use the chat to tell Kiro how to complete the tasks. For example you could type:👇
Please complete tasks 1-4, stop at 4. 🔥
For more Kiro tips, see my full blog post! kiro.hashnode.dev/top-8-tips-w...
Image shows inclusion and fileMatchPattern
🔥Kiro Tip: Use file matching patterns when creating your steering files! Files are automatically included only when working with ones that match the specified pattern. In this example steering files will only be included in the context for components with the *.tsx extension🔥
I’m at the AWS Summit in Toronto today! Come by the developer community lounge and say hi! You’ll also see me at 1:00pm in room 713a for a talk on MCP!
Can't wait!
Yes! We are aware of this issue of updating on Linux. We are working on this . I believe there is a github issue tracking it. I’ll find it Monday :)
I’ll pass this along.
Ok, well glad it’s logged.
Ok! We have some issues on our github on Linux. I’ll add Linux mint to it .
Good to hear!
Hey Scott! Not yet, unfortunately. We are are looking at the next steps right now.
Thanks for trying it out! Check our our new announcement on our Discord channel. We are working on the capacity issues and some usage limits.
Oh know. Feel free to reach out, let me know what you're running into. Or if you were able to get past it.
Thanks for mentioning Kiro! Feel free to reach out with any questions
Sorry that happened. Were you able to figure out what happened?
Hey Grant, sorry this is happening. Feel free to message me and we can look into this.
Sorry this is happening! You can post on our Discord channel, and we can see what's happening in more detail. Or just DM me.