Tag: design-md

Categoria: Workflows/SDD

You are a coding assistant--with access to tools--specializing in analyzing codebases. Below is the content of the file the user is working on. Your job is to to answer questions, provide insights, and suggest improvements when the user asks questions.

Categoria: Workflows/SDD

- Always write tests first following Test-Driven Development principles - Tests serve as specification documents for the code - Each test should be written before the implementation code

Categoria: Workflows/SDD

The testing strategy is built upon the remocal testing concept, combining the speed of local execution with the confidence of real AWS service integration. This approach enables effective TDD while maintaining high confidence in our serverless infrastructure.

Categoria: Workflows/SDD

This file contains Python programming rules for clean coding and project maintenance.

Categoria: Workflows/SDD

- Before writing the documentation, ask all relevant questions to understand the context of this codebase. - The documentation must be specific with a focus on simplicity and clearance. - Write documentation in prose. - Prevent repetitions and ambiguity in the documentation.

Categoria: Workflows/SDD

- Follow the user’s requirements carefully & to the letter. - Always write correct, best practice, DRY principle (Dont Repeat Yourself), bug free, fully functional and working code also it should be aligned to listed rules down below at Code Implementation Guidelines . - Focus on easy and readability code, over being performant. - Fully implement all requested functionality. - Include all required imports, and ensure proper naming of key components. - Use next.js app router.

Categoria: Workflows/SDD

when you do exploratory test follow below steps: 1. dump xml for every new ui page by uiautomator dump, name as step1dump.xml, step2dump.xml, etc 2. detect all clickable element 3. if click successful, mark the click position with magick input.png -fill "rgba(255,0,0,0.5)" -draw "circle 100,100 125,100" output.png 4. after finished the session. output a document androidexploratorytestreport.md with use cases. each step contain screenshot with click area highlighted. 5. IMPORTANT: ALL screenshots

Categoria: Workflows/SDD

Use ATX-style headings with hash signs (#) and a space after (# Heading) Increment headings by one level only (don't skip from # to ###) No duplicate heading text among siblings One top-level (#) heading per document as the first line No punctuation at end of headings Surround with single blank line before other content

Categoria: Workflows/SDD

This document describes guidelines on how to leverage the specs concept of Kiro. Specs are structured markdown files that formalize the development process for complex features. They provide a systematic approach to transform high-level ideas into detailed implementation plans with clear tracking and accountability.

Categoria: Workflows/SDD

When asked to generate application:

Categoria: Workflows/SDD

- You are given a scenario and you need to generate a playwright test for it. - Do run steps one by one using the tools provided by the Playwright MCP. - Only after all steps are completed, emit a Playwright TypeScript test that uses @playwright/test based on the message history - Save the generated test file in the e2e-tests directory - Execute the test file and iterate until the test passes

Categoria: Workflows/SDD

- Follow Conventional Commits format: type(scope): description - Use these commit types to maintain clear project history: - feat: New feature - fix: Bug fix - docs: Documentation changes - refactor: Code restructuring without behavior changes - test: Test additions or modifications - Include scope when relevant to identify the affected area (e.g., feat(auth): add OAuth2 support) - Keep descriptions concise and in imperative mood (e.g., "add" not "added") - Why: Conventional Commits enable autom

Categoria: Workflows/SDD

- Use camelCase for variable and function names. - Use PascalCase for class names and interface names. - Use camelCase for interface members. - Use PascalCase for type names and enum names.

Categoria: Workflows/SDD

- Follow a test-driven development approach. - Keep tests simple and focused on one aspect of behavior - Use Jest as the testing framework - Use the AWS CDK assertions module for testing CDK constructs - Use the Arrange-Act-Assert pattern - Organize tests by construct or stack - Use descriptive test names that explain the expected behavior - Aim for high test coverage (at least 80%) - Focus on testing critical infrastructure components - Ensure all resource properties are tested

Categoria: Workflows/SDD

- Grant only the permissions required for a specific task - Avoid using wildcard permissions () in IAM policies - Use IAM roles instead of access keys for service-to-service authentication - Configure service roles with appropriate permissions - Use managed policies when appropriate, but prefer custom policies for more control - Use temporary credentials instead of long-term access keys - Implement credential rotation for any long-term credentials - Set appropriate expiration times for temporary

Categoria: Workflows/SDD

- Functions and variables: snakecase - Classes: PascalCase - Constants: UPPERSNAKECASE - Private attributes: leadingunderscore - Modules: snakecase.py - Test files: test.py or test.py - Use logical IDs that describe the resource's purpose - Include the resource type in the logical ID - Avoid using generic names like "Bucket" or "Function" - Use generated resource names instead of physical names whenever possible. - If the construct has only one or a single main child resource, call it "Resource"

Categoria: Workflows/SDD

- Use kebab-case for directory names: data-storage/, search/ - Use kebab-case for file names: search-stack.ts, lambda-function.ts - Use PascalCase for class names: SearchStack, LambdaFunction - Use camelCase for variable and function names: createInstance, databaseConfig

Categoria: Workflows/SDD

- Use separate stacks to model individual deployable services within a bounded context. - Use stacks only to describe how constructs are composed and connected for various deployment scenarios. - Create separate stacks for common resources such as networking that are shared across multiple bounded contexts. - Keep stateful and stateless resources within a stack together to achieve high cohesion.

Categoria: Workflows/SDD

- Separate business logic from infrastructure code. - Add the function handler code in a file with a .lambda.ts suffix. - Group function handlers in a functions folder. - Configure appropriate memory and timeout settings. - Use environment variables for configuration. - Set up appropriate IAM permissions with least privilege.

Categoria: Workflows/SDD

THIS FILE IS TO HELP UNDERSTAND THE RELATIONSHIPS, HOW TO MODEL SCHEMAS, WHAT IS THE CORRECT WAY TO CODE FOR ACCURACY. USE THIS TO UNDERSTAND HOW DATA SCHEMAS ARE DESIGNED.

Categoria: Workflows/SDD

ALL RULES MUST BE ADHERED TO THE LAST WORD.

Categoria: Workflows/SDD

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

Categoria: Workflows/SDD

You have a Workload in AWS Well-Architected Tool with the arn arn:aws:wellarchitected:::workload/. You are tasked to conduct a Well-Architected-Review based on the application that is described in Cloudformation.

Categoria: Workflows/SDD

Please review this code, and write out a list of missing test cases, and code tests that should exist. The list will be given to a developer, so they should be in a format that is compatible with gitlab issues. and write them down to test.md