infrastructure-stack-patterns

Project rules for building AWS CDK stacks, which are code-defined descriptions of cloud infrastructure, for API services in the T6C project.

In plain words
What is it for?
Use them when creating or maintaining CDK stacks that deploy API services, serverless functions, databases, and API Gateway resources.
Why use it?
They keep stacks consistent in their imports, class structure, shared resources, API connections, and environment settings.

Cursor rule

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/charlee-x/effect-cursor-rules/infrastructure-stack-patterns
Clone the repo
git clone --depth 1 https://github.com/CharLEE-X/effect-cursor-rules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 4,191 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.04191
Opus 5 $0.00000 $0.02096
Sonnet 5 $0.00000 $0.00838
Haiku 4.5 $0.00000 $0.00419

Measured yesterday against content hash 03b81f209d7a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

infrastructure-stack-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

rules/infrastructure-stack-patterns.mdc · 565 lines

How it starts

The opening of the file, as written. The whole thing — 565 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Infrastructure Stack Patterns

Guidelines for creating and maintaining CDK stacks for API services in the T6C project.

MANDATORY Stack Structure

Required Imports and Setup

EVERY stack MUST follow this exact import and setup pattern:

import path from 'node:path'
import { fileURLToPath } from 'node:url'
import * as cdk from 'aws-cdk-lib'
import type * as apigateway from 'aws-cdk-lib/aws-apigateway'
import {
  AttributeType,
  type ITable,
  ProjectionType,
} from 'aws-cdk-lib/aws-dynamodb'
import type { Construct } from 'constructs'
import 'source-map-support/register'
import {
  ApiConstruct,
  ApiGatewayHandlerLambda,
  BaseStack,
  type BaseStackProps,
  DynamoDatabaseTableWithCompositeKey,
} from './constructs/index.js'
import { getEnvVarOrThrow } from './util/index.js'

const __filename = fileURLToPath(import.meta.url)
const __dirname = path.dirname(__filename)

Required Stack Class Structure

EVERY stack MUST extend BaseStack and follow this pattern:

type {Service}StackProps = {
  // Dependencies from other stacks
  userServiceUrl: string
} & BaseStackProps

export class {Service}Stack extends BaseStack {
  // Public resources for other stacks
  public readonly table: ITable
  public readonly api: apigateway.RestApi

  constructor(scope: Construct, props: {Service}StackProps) {
    const prefix = `${props.productName}-${props.stageName}`
    super(scope, `${prefix}-{Service}Stack`, props)

    // 1. Create API Gateway using ApiConstruct
    const {service}Api = new ApiConstruct(this, '{Service}Api', { ...props })
    this.api = {service}Api.api

    // 2. Create Database Table using DynamoDatabaseTableWithCompositeKey
    const { table: {service}Table } = new DynamoDatabaseTableWithCompositeKey(
      this,
      `${prefix}-{Service}Table`,
      {
        tableName: `${prefix.toLowerCase()}-{service}`,
        partitionKey: { name: 'PK', type: AttributeType.STRING },
        sortKey: { name: 'SK', type: AttributeType.STRING },
        stream: true,
        globalSecondaryIndexes: [
          {
            indexName: 'GSI1',
            partitionKey: { name: 'GSI1PK', type: AttributeType.STRING },
            sortKey: { name: 'GSI1SK', type: AttributeType.STRING },
            projectionType: ProjectionType.ALL,
          },
          {
            indexName: 'GSI2',
            partitionKey: { name: 'GSI2PK', type: AttributeType.STRING },
            sortKey: { name: 'GSI2SK', type: AttributeType.STRING },
            projectionType: ProjectionType.ALL,
          },
        ],
      },
    )
    this.table = {service}Table

    // 3. Common Props with proper environment variables
    const commonProps = {
      description: prefix,
      apiGatewayResource: this.api.root,
      apiKeyRequired: true,
      env: {
        {SERVICE}_TABLE: {service}Table.tableName,
        USER_SERVICE_URL: props.userServiceUrl,
        USER_SERVICE_API_KEY: getEnvVarOrThrow('USER_SERVICE_API_KEY'),
        // Add other environment variables as needed
      },
    }

    // 4. Register ALL handlers from packages/{service}-api/src/lambdas/
    // ... handler registrations

    // 5. Outputs
    new cdk.CfnOutput(this, '{Service}TableName', {
      value: {service}Table.tableName,
    })
  }
}

Read the full file on GitHub · 565 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 565 lines · 4,191 tokens per session scan A 03b81f209d7a

Subscribe to this mod's changes

infrastructure-stack-patterns is a cursor rule published in the GitHub repository CharLEE-X/effect-cursor-rules (6 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,191 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.