CLI

TypeScript best practices for AWS CDK development. Following these guidelines will ensure type safety, code consistency, and maintainability across the codebase. TypeScript's static typing capabilities help catch errors early in the development process and provide better tooling support.

This document outlines the recommended project structure for AWS CDK applications. A well-organized project structure is critical for maintainability, scalability, and developer onboarding. Following these guidelines will ensure consistency across the codebase and make navigation easier as the project grows.

Outlines security and compliance best practices for AWS CDK applications. Security is a critical aspect of infrastructure as code, and following these guidelines will help ensure that your CDK applications are secure, compliant, and follow AWS best practices.

Project rules to steer Amazon Q Developer for all things related to implementing authentication with AWS Amplify Gen2

Empowers Amazon Q Developer to maintain Kiro specifications to apply spec-driven developmen the Kiro way.

Outlines best practices for testing AWS CDK applications. Testing is a critical aspect of CDK development to ensure that infrastructure is deployed correctly and behaves as expected. Following these guidelines will help create reliable, maintainable, and well-tested infrastructure code.

Outlines recommended design patterns for AWS CDK development. Design patterns are reusable solutions to common problems in software development. Following these patterns will ensure consistency, maintainability, and scalability across the codebase. The patterns described here are particularly relevant for AWS CDK development.

The project intelligence documentation system transforms Amazon Q Developer from a stateless assistant into a persistent development partner by providing comprehensive context about your application across various sessions. Once the rule was added to your repository, you can ask Q Developer to initialize the project intelligence with "Initialize Project Intelligence". If already in place, you can force an update by asking Q "Update Project Intelligence".

Reverse-Engineered Xcode's Coding Intelligence prompt to be used as Amazon Q Developer Projet Rule

Outlines best practices for developing AWS CDK constructs. Following these guidelines will ensure that constructs are reusable, maintainable, and follow AWS best practices.

Project rules to tune Amazon Q Developer in all things related to data modeling and modeling relationships with AWS Amplify Gen2

Next.js rules used to build promptz.dev

This document explains the standardized naming convention for Amazon Q learning files across different projects and directories.

Helps Q Developer to optimize the creation of end-to-end tests for playwright. Main source for these rules are the best practices listed at the official playwright documentation.

Enable effective collaboration between product teams, engineering teams, and AI agents. The goal is to make all engineers within a team leverage spec-driven development following the standards of Kiro in any IDE.

Keeps your Github backlog up-to-date with feature requests and bug fixes.

Operational troubleshooting and root cause analysis of incidents in your AWS Account

Create frontend experiences following TDD based on Next.js, tailwind, and shadcn that are blazing fast, accessible to all users, and delightful to interact with. The agent is designed to use the github CLI and project-intelligence concept of promptz.dev. Adjust the system prompt to your needs if your tooling or documentation concept differs.

Maintains the documentation system called Project Intelligence as a living documentation for both human engineers and AI assistants. The goal is to help engineers improve their productivity by providing detailed and up-to-date documentation. Make sure to also use the project-intelligence project rules available via promptz.dev.