Skip to content

docs: Add SDK-first guidance to AGENTS.md and llms.txt - #5997

Merged
jam-jee merged 1 commit into
aws:masterfrom
jam-jee:sdk-first-guidance
Jul 7, 2026
Merged

jam-jee merged 1 commit into
aws:masterfrom
jam-jee:sdk-first-guidance

Conversation

@jam-jee

@jam-jee jam-jee commented Jul 7, 2026 •

Copy link
Copy Markdown
Collaborator

What

Adds an SDK-first section to AGENTS.md and llms.txt (both merged earlier in #5982).

The prior files already steer agents from SDK v2 → v3. This change addresses a distinct
gap: when a task doesn't name the SDK (e.g. "generate training code for a SageMaker serverless
job"), agents often drop to raw boto3 (create_training_job/create_endpoint), the AWS CLI,
or a hand-rolled framework script instead of the SageMaker Python SDK.

Changes

  • New "SDK-first" guidance: for any SageMaker task, default to the SageMaker Python SDK v3 as
    the primary interface.
  • A natural-language intent → v3 interface table (train → ModelTrainer, deploy →
    ModelBuilder, process → ProcessingJob, pipeline → sagemaker.mlops, image →
    image_uris.retrieve).

Notes

Docs-only change (AGENTS.md, llms.txt); no SDK source touched.

Add an "SDK-first" section (with a natural-language intent -> v3 interface
table) so AI coding agents default to the SageMaker Python SDK v3 as the
primary interface for SageMaker tasks, rather than dropping to raw boto3
(create_training_job/create_endpoint), the AWS CLI, or hand-rolled framework
scripts.

---
X-AI-Prompt: Add SDK-first (library-selection) guidance so agents default to the SageMaker Python SDK v3 without an explicit nudge
X-AI-Tool: Kiro
@jam-jee
jam-jee merged commit 3982ca6 into aws:master Jul 7, 2026
6 checks passed

This branch was previously deployed

1 inactive deployment
auto-approve — db3d7413 Deployed Jul 7, 2026 by jam-jee via wait-for-approval #886
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants