Cursor recommends Agent Skills as the preferred way to extend agent behaviour — dynamic context that loads when a task matches a skill’s description, keeping the context window lean. Rules and the older .cursorrules approach still cover static or path-scoped enforcement; skills remain where Cursor steers agent work in their agent best practices guide. The collection now splits three trees — skills, rules, and agents — meant to be symlinked into ~/.cursor, not treated as an installable app.
When using the AWS Software Development Kit, pagination in API responses is a common and sometimes annoying to deal with. Thanks to a shared interfaced in @aws-sdk clients, can you can establish a common pattern to interact with AWS paginated API actions using the JavaScript SDK v3. Retrieving all AWS Accounts in your AWS Organization is a neat example use case for this.
If you stick to Conventional Commits for your commit messages, you can create tags and releases with GitHub Actions for every code change you push to a repository. This is great for automated and continuous releases!
You can find plenty of frameworks and tools to provision your AWS resources. Some of them do a great job for a specific purpose, others are more generic. Nevertheless, I do prefer to use native CloudFormation templates as much as possible.
The more projects you work on, the more streamlined your tooling gets. Hopefully. Various services using different languages have different tooling requirements, of course. A sweet Makefile can be the entry to a unified tooling interface.