sst-dev

Guide TypeScript-based SST.dev infrastructure with resource bindings and deployment patterns.

1|Updated Aug 7, 2024
One-click install
npx skills add https://github.com/tejovanthn/rasikalife --skill sst-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sst-dev
Source: https://github.com/tejovanthn/rasikalife/tree/main/.opencode/skill/sst-dev
Command: npx skills add https://github.com/tejovanthn/rasikalife --skill sst-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This Skill provides practical guidelines and patterns for building and maintaining infrastructure with SST.dev on AWS, helping teams adopt consistent, scalable serverless architectures.

## Core Features & Use Cases

  • Type-safe SST.dev patterns: guidance on structuring sst.config.ts, resource bindings, and deployment flows.
  • Best practices for developing, testing, and shipping serverless apps with SST in real-world projects.
  • Use Case: teams migrating from ad-hoc scripts to a structured SST-based infrastructure.

### Quick Start To begin, review the SST.dev conventions in your project and apply the recommended patterns in your sst.config.ts and resource definitions.

  • Start by defining a simple bucket and function, then iterate to add bindings and transforms.

Frequently Asked Questions about sst-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure TypeScript infrastructure-as-code patterns in SST.dev?▼

To structure TypeScript infrastructure-as-code in SST.dev, define your resources in sst.config.ts using type-safe patterns. Start with a simple bucket and function, then iterate by adding resource bindings and transforms for production-ready deployments.

What's the best way to add resource bindings to an SST.dev project?▼

The best way to add resource bindings in an SST.dev project is to define a simple bucket and function first, then iteratively apply bindings and transforms within your sst.config.ts file to ensure type-safe access across your serverless architecture.

Can I migrate ad-hoc AWS scripts to a structured SST.dev setup?▼

Yes, you can migrate ad-hoc scripts to a structured SST.dev setup. This transition helps teams adopt consistent, scalable serverless architectures by applying best-practice guidelines for developing, testing, and shipping serverless apps on AWS.

How do resource bindings work in AWS serverless applications using SST?▼

Resource bindings in AWS serverless applications using SST work by securely connecting infrastructure components like buckets and functions. They enable type-safe patterns within sst.config.ts, allowing your TypeScript code to interact with AWS resources directly and predictably.

Does SST.dev support production-ready deployment patterns for TypeScript?▼

Yes, SST.dev supports production-ready deployment patterns for TypeScript. It provides best-practice guidance for structuring sst.config.ts, configuring resource bindings, and managing deployment flows to build resilient AWS infrastructure.

What are the limitations of using SST.dev for serverless infrastructure?▼

SST.dev is focused on AWS serverless infrastructure, so its patterns are tailored to that environment. Teams migrating from ad-hoc scripts should ensure their workflows align with SST's TypeScript-based sst.config.ts structure and resource binding conventions.