Agent skill
rule-lambda
Rule mapping for lambda
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/rule-lambda-carrot-foundation-methodology-rules
SKILL.md
Rule lambda
Apply this rule whenever work touches:
**/*.lambda.ts
Lambda handlers are the entry points for AWS Lambda invocations. They must remain thin wrappers that connect the Lambda runtime to the processor.
Handler structure
A typical Lambda handler file:
import { wrapHandler } from '@carrot-fndn/shared/lambda';
import { VehicleValidationProcessor } from './vehicle-validation.processor';
const processor = new VehicleValidationProcessor();
export const handler = wrapHandler(processor);
The handler should contain no business logic. All evaluation, validation, and transformation happens in the processor.
Error handling
Let errors propagate naturally to the Lambda runtime:
// Correct - errors propagate for retry
export const handler = wrapHandler(processor);
// Wrong - swallowing errors prevents retries
export const handler = async (event: unknown) => {
try {
return await processor.execute(event);
} catch {
return { statusCode: 500, body: 'Error' };
}
};
AWS Lambda has built-in retry mechanisms for asynchronous invocations. Swallowing errors defeats this reliability mechanism.
E2E testing
E2E tests exercise the full handler path including event deserialization:
import { handler } from './vehicle-validation.lambda';
import { validInput, invalidInput } from './vehicle-validation.test-cases';
describe('VehicleValidation Lambda E2E', () => {
it('should return approved for valid input', async () => {
const result = await handler(validInput);
expect(result.resultStatus).toBe('APPROVED');
});
});
These tests complement the processor unit tests by verifying the integration between the handler and processor layers.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?