CLAUDE.md · diff
git:20260302.b4914b4 to git:20261016.361f1a2
27 added, 35 removed. Audit A to A.
- ## Code Style Guidelines
-
- - Write simple, clean, and readable code with minimal indirection
- - Avoid unnecessary object attributes and local variables and config variables
- - No redundant abstractions or duplicate code and config code
- - Each function should do one thing well
- - Use clear, descriptive names
- - NO need to write documentations or comments unless absolutely necessary
- - Public methods MUST have full documentation.
- - Check and test the code you have written
-
- ## Testing Requirements
-
- - Run lint and typecheckers and fix any lint and typecheck errors
- - Generate comprehensive tests so that you achieve 100% branch coverage
- - Tests MUST NOT use mocks, patches, or any form of test doubles
- - Integration tests are HIGHLY encouraged
- - You MUST not add tests that are redundant or duplicate of existing
- tests or that do not add new coverage over existing tests
- - Generate meaningful stress tests for the code if you are
- optimizing the code for performance
- - Each test should be independent and verify actual behavior
-
- ## Use tools when you need to:
+ <!-- BEGIN AWS Agent Toolkit rules -->
+ # AWS Guidance
- - Look up API documentation or library usage from the internet
- - Find examples of similar implementations
- - Understand existing code in the project
+ - Where these AWS rules conflict with the project's own instructions, the
+ project's instructions take precedence.
+ - Prefer the AWS MCP Server for AWS interactions — it provides sandboxed
+ execution, observability, and audit logging. If unavailable, use the
+ AWS CLI directly.
+ - Before starting a task, check whether a relevant AWS skill is available.
+ Load the skill with `retrieve_skill` and prefer its guidance over
+ general knowledge.
+ - When uncertain about specific AWS details (API parameters, permissions,
+ limits, error codes), verify against documentation rather than guessing.
+ State uncertainty explicitly if you cannot confirm.
+ - When creating infrastructure, prefer infrastructure-as-code (AWS CDK or
+ CloudFormation) over direct CLI commands.
+ - When working with infrastructure, follow AWS Well-Architected Framework
+ principles.
+ - Do not use em dashes in AWS resource names or descriptions. Use
+ hyphens instead.
- ## After you have implemented the task, aggressively and carefully simplify and clean up the code
+ ## Secret Safety
- - Remove unnecessary object/struct attributes, variables, config variables
- - Avoid object/struct attribute redirections
- - Remove unnecessary conditional checks
- - Remove redundant and duplicate code
- - Remove unnecessary comments
- - Make sure that the code is still working correctly
- - Simplify and clean up the test code
+ - MUST load the `aws-secrets-manager` skill first for any secret,
+ credential, API key, token, or password task. MUST NOT call
+ `secretsmanager get-secret-value` or `batch-get-secret-value`, and MUST
+ NOT hit the Secrets Manager Agent daemon directly. MUST use
+ `{{resolve:secretsmanager:secret-id:SecretString:json-key}}` with
+ `asm-exec` so the secret resolves at runtime without entering context.
+ <!-- END AWS Agent Toolkit rules -->