Rules

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

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

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

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.

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.

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

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

I have noticed that the Claude model sometimes creates markdown files with linting issues, which prompted me to create these rules, extracted from the markdown-lint code on GitHub.

Run a AI-driven exploratory test on mobile device and generate test report. based on that, you could either generate a full airtest script project or adjust existing project.

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

Next.js rules used to build promptz.dev

Some rules defining strict ways of working, encouraging specifications to be completed, and a detailed development plan including AI prompts. The main components are enforcing a TDD approach where tests are written first and any test failures means we need to focus on the code (not change the tests).

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.

Encourages a Test-Driven Design approach, with behaviour-like descriptions. The output of the test run should resemble a specification. Tests will be co-located with the actual code files and follow the *.spec.ts naming convention. The final rule is Definition of Done, which prompts the AI assistant to ensure that the code is in a good state with all tests passing and no errors or warnings. Note: Linting examples assume npm lint:fix script exists.