patrickchugh/terravision / skills/terravision-cloud-diagrams
terravision-cloud-diagrams
VerifiedDraw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision. Use whenever the user asks to draw, diagram, sketch or visualize a system on AWS, Azure or Google Cloud, or one built from their services (Lambda, DynamoDB, S3, EC2, EKS, RDS, API Gateway, Azure Functions, App Service, AKS, Cosmos DB, Cloud Run, GKE, BigQuery and the like), even if they never say 'cloud', 'diagram' or a tool name; also for a diagram of Terraform code. Prefer it over Mermaid, PlantUML, hand-written SVG or ASCII, which cannot use the official icons or VPC/subnet grouping. Not for diagrams that are not cloud infrastructure: sequence diagrams, flowcharts, class or ER diagrams, code or module structure, org charts, on-premises-only networks; use Mermaid or similar for those. Works with or without Terraform: with Terraform code the diagram comes from terraform plan; without it, write a small JSON graph and render it.
examples/gallery/aws-sagemaker-mlops.annotations.yml
View on GitHub# Title, CIDR ranges, arrow labels and flow steps for the gallery diagram. Use with:
# terravision draw --source aws-sagemaker-mlops.tvg.json --annotate aws-sagemaker-mlops.annotations.yml
format: '0.3'
title: Amazon SageMaker MLOps with a private Studio, Pipelines and a real-time endpoint
update:
aws_vpc.ml:
cidr_block: 10.30.0.0/16
aws_subnet.studio~1:
cidr_block: 10.30.16.0/20
aws_subnet.inference~1:
cidr_block: 10.30.64.0/24
aws_subnet.endpoints~1:
cidr_block: 10.30.240.0/24
aws_subnet.studio~2:
cidr_block: 10.30.32.0/20
aws_subnet.inference~2:
cidr_block: 10.30.65.0/24
aws_subnet.endpoints~2:
cidr_block: 10.30.241.0/24
aws_sagemaker_domain.studio~1:
label: SageMaker Studio
aws_sagemaker_domain.studio~2:
label: SageMaker Studio
aws_sagemaker_pipeline.churn_training:
label: SageMaker Pipelines Churn Training
aws_sagemaker_feature_group.customer_features:
label: Feature Store Customer Features
aws_sagemaker_model_package_group.churn_models:
label: Model Registry Churn Models
connect:
aws_ec2_client_vpn_endpoint.data_science:
- aws_sagemaker_domain.studio~1: VPC-only Studio
aws_scheduler_schedule.weekly_retrain:
- aws_sfn_state_machine.retrain: Weekly
aws_sfn_state_machine.retrain:
- aws_sagemaker_pipeline.churn_training: StartPipelineExecution
- aws_sagemaker_endpoint.churn~1: Blue/green deploy
- aws_sagemaker_endpoint.churn~2: Blue/green deploy
aws_sagemaker_pipeline.churn_training:
- aws_sagemaker_model_package_group.churn_models: Register version
aws_vpc_endpoint.sagemaker_runtime~1:
- aws_sagemaker_endpoint.churn~1: InvokeEndpoint
aws_vpc_endpoint.sagemaker_runtime~2:
- aws_sagemaker_endpoint.churn~2: InvokeEndpoint
flows:
Experiment:
description: A data scientist builds features
steps:
- resource: tv_aws_users.data_scientists -> aws_ec2_client_vpn_endpoint.data_science
xlabel: VPN
detail: Data scientists connect through Client VPN
- resource: aws_ec2_client_vpn_endpoint.data_science -> aws_sagemaker_domain.studio~1
xlabel: Studio
detail: to SageMaker Studio, which runs in VPC-only mode with no internet access
- resource: aws_sagemaker_domain.studio~1 -> aws_vpc_endpoint.sagemaker_api~1
xlabel: API
detail: Notebooks call SageMaker through the interface endpoint
- resource: aws_vpc_endpoint.sagemaker_api~1 -> aws_sagemaker_feature_group.customer_features
xlabel: Features
detail: to define and fill feature groups in Feature Store
Retrain and deploy:
description: A new model reaches production
steps:
- resource: aws_scheduler_schedule.weekly_retrain -> aws_sfn_state_machine.retrain
xlabel: Start
detail: An EventBridge Scheduler schedule starts the Step Functions workflow each week
- resource: aws_sfn_state_machine.retrain -> aws_sagemaker_pipeline.churn_training
xlabel: Train
detail: which runs the SageMaker pipeline
- resource: aws_sagemaker_pipeline.churn_training -> aws_sagemaker_feature_group.customer_features
xlabel: Read
detail: The pipeline trains on offline features and the training data in S3
- resource: aws_sagemaker_pipeline.churn_training -> aws_sagemaker_model_package_group.churn_models
xlabel: Register
detail: and registers the evaluated model in the Model Registry
- resource: aws_sfn_state_machine.retrain -> aws_sagemaker_endpoint.churn~1
xlabel: Deploy
detail: Once the version is approved, the workflow updates the endpoint with a blue/green deployment
Prediction:
description: The app asks for a churn score
steps:
- resource: tv_aws_mobile_client.customer_app -> aws_api_gateway_rest_api.predictions
xlabel: Request
detail: The customer app calls the predictions API
- resource: aws_api_gateway_rest_api.predictions -> aws_lambda_function.predict~1
xlabel: Invoke
detail: API Gateway invokes a Lambda function in the VPC
- resource: aws_lambda_function.predict~1 -> aws_vpc_endpoint.sagemaker_runtime~1
xlabel: Score
detail: which calls the SageMaker runtime through its interface endpoint
- resource: aws_vpc_endpoint.sagemaker_runtime~1 -> aws_sagemaker_endpoint.churn~1
xlabel: Infer
detail: and the real-time endpoint returns the score
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |