trove-cdk
AWS CDK (TypeScript) conventions for infrastructure as code. Auto-activates on CDK project files. Use when: cdk stack; aws cdk; infrastructure as code.
- License 许可
- MIT
- 所属仓库
- bravew/trove
- 最近更新
- 2026-11-12
- Stars
- ★ 10
- Forks
- 1
01 前言 Front Matter
- name
- trove-cdk
- description
- AWS CDK (TypeScript) conventions for infrastructure as code. Auto-activates on CDK project files. Use when: cdk stack; aws cdk; infrastructure as code.
03 SKILL.md 正文
<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run build:skills -->
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
AWS CDK Conventions
Construct Structure
export class MyServiceStack extends cdk.Stack {
constructor(scope: Construct, id: string, props: MyServiceProps) {
super(scope, id, props);
const queue = new sqs.Queue(this, 'ProcessingQueue', {
visibilityTimeout: cdk.Duration.seconds(300),
retentionPeriod: cdk.Duration.days(14),
});
const fn = new lambda.Function(this, 'Handler', {
runtime: lambda.Runtime.PYTHON_3_12,
handler: 'handler.main',
code: lambda.Code.fromAsset('lambda/'),
timeout: cdk.Duration.seconds(30),
memorySize: 256,
environment: {
QUEUE_URL: queue.queueUrl,
},
});
queue.grantSendMessages(fn);
}
}
Best Practices
- One construct per logical resource group
- Use
cdk.Duration,cdk.Sizefor type-safe values - Grant permissions via
.grant*()methods (not inline IAM) - Use
cdk.RemovalPolicy.RETAINfor stateful resources (databases, S3) - Stage-aware config via context (
-c stage=production)
AI Gotchas
- Logical IDs: Changing construct IDs causes resource replacement
- Cross-stack refs: Use
cdk.Fn.importValue()or shared props, not hardcoded ARNs - Synth vs Deploy: Always
cdk synthbeforecdk deployto validate
04 同仓库更多 Skills
using-trove
Skill discipline anchor for the Trove marketplace. Loaded once per session; routes the agent to the right trove-* skill before code, planning, review, or git actions.
trove-write-skill
Skill authoring workflow. Use when creating or updating a Codex or Trove skill, including rubrics, tasks, metadata, and validation.
trove-worktree
Git worktree workflow for spikes, risky experiments, and broad refactors that should not disturb the user's current branch.
trove-why
Reconstruct design rationale and decision history from evidence — source control, issue tracker (Linear), docs (Notion), chat (Slack), error tracking (Sentry) — with calibrated confidence. Use for "why does X work this way", "why did we pick Y", regressions, and postmortems. Use trove-explain for how it works now.
trove-verify
Completion verification workflow. Use before claiming done, fixed, complete, ready, or shipped.
trove-unslop
Cut AI tells from writing — PR descriptions, release notes, specs, commit bodies, and replies. Use before finalizing prose, or when the user asks to clean up, de-slop, or make text sound human.