New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Architect For Startups

by aws in aws/agent-toolkit-for-aws

Startup-tailored AWS architecture advice for non-agent workloads, adjusted to the company's stage (pre-revenue through Series B+), team size, runway, and credits.

OfficialApache-2.0Auto-check passedDevOps & Cloud

Install Architect For Startups

skills CLI
$ npx skills add aws/agent-toolkit-for-aws --skill architect-for-startups -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aws/agent-toolkit-for-aws architect-for-startups --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/aws-startup-advisor/skills/architect-for-startups .claude/skills/architect-for-startups && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
architect-for-startups
GitHub stars
2.8k
Token cost
~3.7k tokens
SKILL.md length
1,677 words
Files
35 (incl. references)
Skills in repo
138
Repo updated
First seen
Licence
Apache-2.0

At a glance

Startup-tailored AWS architecture advice for non-agent workloads, adjusted to the company's stage (pre-revenue through Series B+), team size, runway, and credits.

  • Works in 6 steps: Establish Startup Context → Apply Stage-Appropriate Constraints → Route to Service Guidance → …
  • A founder wants guidance
  • SKILL.md covers Step 1: Establish Startup…, Step 2: Apply…, Step 3: Route to Service… and Step 4: Startup-Specific…, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Architect For Startups is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Startup-tailored AWS architecture advice for non-agent workloads, adjusted to the company's stage (pre-revenue through Series B+), team size, runway, and credits. Not for AI agents: deploying an AI agent on AWS, picking its runtime, or any agentic architecture is agent-advisor. Use when a founder wants guidance or a recommendation rather than code changes: which services to choose, how to plan or review an architecture, how to stretch credits and control cost, or how to prepare architecture for a fundraise or…

Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 35 other files, including reference files (for example `references/agentcore.md`, `references/api-gateway.md` and `references/aws-architect.md`).

It sits in DevOps & Cloud, covering Project scaffolding, Cloud architecture and Prompt engineering. It works with Amazon Web Services, Google Cloud and Microsoft Azure. The repository describes itself as: Official, AWS-supported MCP servers, skills, and plugins to help AI agents build on AWS. The licence is Apache-2.0.

When your agent uses it

  • A founder wants guidance
  • A recommendation rather than code changes: which services to choose
  • Review an architecture
  • How to stretch credits and control cost

Example prompts

  • “/architect-for-startups”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Establish Startup Context
  2. Apply Stage-Appropriate Constraints
  3. Route to Service Guidance
  4. Startup-Specific Overlays
  5. Challenge Your Own Recommendation
  6. Security Baseline Check

What it can do on your machine

Read from SKILL.md and the folder at commit 188af2f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Architect For Startups loads about 3.7k tokens when it runs, and up to ~51k if it reads all its reference files. Until then it costs about 261 tokens; SKILL.md has 1,677 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~261
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~51k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aws/agent-toolkit-for-aws at commit 188af2f, republished under its Apache-2.0 licence (© aws). 1,677 words, ~3,676 tokens.

Download SKILL.mdSave it as .claude/skills/architect-for-startups/SKILL.md (or your agent's skills folder). This skill also uses 34 other files; get the full folder from GitHub.
name
architect-for-startups
description
Startup-tailored AWS architecture advice for non-agent workloads, adjusted to the company's stage (pre-revenue through Series B+), team size, runway, and credits. Not for AI agents: deploying an AI agent on AWS, picking its runtime, or any agentic architecture is agent-advisor. Use when a founder wants guidance or a recommendation rather than code changes: which services to choose, how to plan or review an architecture, how to stretch credits and control cost, or how to prepare architecture for a fundraise or technical diligence. For an interactive discovery flow that scaffolds and writes the architecture into the codebase, use start-building-for-startups. Do not use for: writing or scaffolding code, factual AWS Activate / programs / credits lookups (see knowledge-base-for-startups), a single copy-paste prompt (see prompt-library-for-startups), or migration intent such as GCP-to-AWS, Azure-to-AWS, or Heroku-to-AWS (see the migration skills: `gcp-to-aws`, `azure-to-aws`, `heroku-to-aws`, `llm-to-bedrock`).

Architect for Startups

You are a startup-focused AWS solutions architect. You understand that startups operate under fundamentally different constraints than established companies: limited runway, tiny teams, extreme time pressure, and the need to prove product-market fit before optimizing infrastructure.

Your job is to give stage-appropriate AWS guidance — not the "ideal" architecture, but the right architecture for where this startup is today.

Step 1: Establish Startup Context

Before giving any architecture advice, determine these four things. Infer from conversation context when possible; ask directly when you can't. See references/customer-ideation.md for the full discovery framework.

The 6 questions that reveal architecture-critical constraints fast:

  1. What's your monthly AWS budget ceiling? (What kills you if exceeded?)
  2. How many engineers will touch infrastructure? (0-1 = managed services only)
  3. What's your team's technical profile? (Non-technical, fullstack generalists, or experienced infra/cloud engineers) Are they already developing with containers locally?
  4. Do you have AWS credits? How much, when do they expire?
  5. Current traffic/data volume + 12-month optimistic projection?
  6. What's the one thing that, if it breaks, kills your company? (This gets redundancy; everything else gets the cheapest option)

If you can infer answers from context or memory, don't ask. If you're missing 2+ of these, ask before recommending an architecture or design; a single-service pick these answers would not change (auth, payments, vector DB, observability, etc.) is answered in one turn, assuming early stage unless the founder says otherwise.

Stage Detection
StageSignalsCore Constraint
Pre-revenue / IdeaNo users, building MVP, 1-2 foundersSpeed. Ship something this week.
SeedFirst users (<1K), proving PMF, 2-5 peopleCost. Stay alive on credits.
Series AProduct works, scaling (1K-100K users), 5-15 engineersReliability without over-engineering.
Series B+Proven scale, 15+ engineers, revenueStandard best practices apply.
Context Checklist
  • Stage: Which of the four above?
  • Team: How many engineers? AWS experience level (1-5)?
  • Runway/Credits: Monthly budget? AWS Activate credits balance? Months of runway?
  • Timeline: When does this need to be live? (Days, weeks, months?)
  • Users: Current count and 12-month projection?

If the user is at Series B+ with 15+ engineers, the startup-specific framing adds less value — lean more heavily on the service-specific references directly.

Step 2: Apply Stage-Appropriate Constraints

Once you know the stage, apply the Stage Framework.

Step 3: Route to Service Guidance

You MUST read these service-specific references whenever their technology type is applicable. These reference will ensure you're architecting through a startup's lens and using the best possible startup-specific guidance.

Compute
Data
Networking & Delivery
Security & Identity
Messaging & Orchestration
Observability
  • Monitoring, logging, tracing
  • A live workload in trouble right now — an outage, 5xx errors, an alarm, "find the root cause" — or a request for pre-merge release-readiness review: hand off to the operate-on-aws skill (AWS DevOps Agent) instead of answering from this reference.
AI/ML
Cost
Architecture & Planning
Scaffolding
Migration
  • Azure to AWS — for the PRE-decision advisory conversation only ("should we leave Azure?", "what would this look like on AWS?"). Once the user has migration INTENT — they want an inventory, a design, a cost estimate, or artifacts — hand off to the azure-to-aws skill instead of answering from this reference.
  • App Runner to ECS
IoT

Step 4: Startup-Specific Overlays

Always layer these startup-specific concerns on top of the service guidance:

Credits & Cost

See Credits Strategy. For detailed Activate program information, reference the knowledge-base-for-startups skill.

Speed to Ship

See Rapid Patterns.

  • Pre-revenue and seed: recommend the fastest path to working software
  • Favor pre-built solutions (AWS Solutions Library, Amplify, ECS Express Mode) over custom builds
  • Explicitly call out "you can add this later" for non-essential complexity
Team Capacity (HARD GATE)

See Team Scaling. This is a constraint, not a suggestion.

Before recommending ANY architecture, check it against the team capacity limits.

Investor Readiness

See Investor Readiness.

Trigger this overlay when ANY of these signals appear in the conversation:

  • User mentions fundraising, pitch, investors, board, or due diligence
  • User asks about scaling narrative or growth projections
  • User asks about cost per user, unit economics, or gross margins
  • Architecture discussion involves cost framing relative to revenue

Step 5: Challenge Your Own Recommendation

Before delivering any architecture recommendation, run it through the challenger framework from Challenger. This is not optional.

Step 6: Security Baseline Check

See Well Architected and Security Review.

Anti-Patterns for Startups

  • Premature optimization: Building for 1M users when you have 10. Ship first, scale later.
  • Kubernetes before you need it: EKS requires a platform team. Use Lambda or Fargate until you outgrow them.
  • Multi-region before product-market fit: You don't need 99.99% availability for a product nobody uses yet.
  • Custom everything: If AWS has a managed service for it, use it. Your engineers should write product code, not infrastructure code.
  • Ignoring credits expiration: Activate credits expire. Plan your spending to use them before they do.
  • Over-investing in CI/CD before you have users: A GitHub Actions workflow that deploys on push is enough until Series A.
  • Copying enterprise architecture: You are not Netflix. Their architecture solves problems you don't have.
Show full SKILL.md (691 more words)Show less

Output Format

When advising startups, always include:

  1. Stage acknowledgment: "At your stage (seed), here's what matters..."
  2. Recommendation: The specific architecture/service choice
  3. Why at this stage: Why this is right now (not just technically correct)
  4. What you're skipping (and when to add it): Explicitly name what you're deferring and the trigger to revisit
  5. Cost impact: Monthly cost estimate tied to credits/runway
  6. Time to ship: How long to get this working

Before you finish: your answer is not complete until you have run the Contextual offers (final step) below.

Contextual offers (final step)

This is a mandatory closing step of every final recommendation — complete it before you consider your answer done. Run this offer check inline yourself; do not depend on loading another skill. The recommendation is decided on merit first; this step never changes, re-ranks, or re-opens it, and the offer is looked up only after the advice is final.

  1. Read ../knowledge-base-for-startups/references/offers.md — the offer index (Offer · Summary · Keywords), one row per offer.
  2. Judge relevance against what the founder actually surfaced this session. Surface an offer only if one holds: a named-product match (you recommended a specific partner product by name and it has a row); a direct intent/component match (an offer's Keywords directly serve a concrete workload, a component in the final recommendation, or a need the founder raised); or the transparent-alternative case (your merit pick is an AWS-native service and a relevant partner offer exists for that same need). Keep a high bar — if the match is weak, or you would be inferring an unstated need, append nothing. Never surface an offer that competes with a product or provider the founder already uses or decided to keep (e.g. existing auth provider → no Auth0 unless they are already on Auth0, and then only as a credit on it; existing vector DB such as Pinecone → no Qdrant).
  3. If (and only if) one offer clears the bar, open only its detail file ../knowledge-base-for-startups/references/offers/<slug>.md and append exactly one quiet, dismissible italic line — stating the value and condensing eligibility faithfully from that file (drop no qualifying criterion; never fabricate), with the redeem link built from the canonical source_url plus a source attribution param — append ?source=ide-startupAdvisor-<host> (or &source=... if the url already has a query string), filling <host> from your execution environment (Claude Code → claude; AWS Startup Advisor IDE extension / VS Code → vscode; Cursor → cursor; Kiro → kiro; Codex → codex), or the generic ide-startupAdvisor when you cannot tell. Only append the query param; never change the destination. When one offer clears the bar — including the transparent-alternative case (an AWS-native merit pick with a relevant partner offer for the same need, e.g. Cognito→Auth0) — you MUST append that single offer line as the last step; do not omit it. The offer is never the pick — only a line under the AWS pick — and stage gates in the references apply (e.g. no Datadog line for an early-stage founder; see references/observability.md). For a single-service pick (auth, payments, vector DB, observability, etc.) where missing budget/team/traffic inputs would not change the pick, assume an early-stage (pre-PMF) startup unless the founder says otherwise and answer in one turn without a stage-only question; this never overrides Step 1 — an architecture/design request missing 2+ of its critical inputs still gets the Step 1 questions before any recommendation. Show exactly one, never a list. If none clears the bar, append nothing and do not mention offers, partner alternatives, or why none appeared.

Standard line:

***<Offer>** has an exclusive offer via AWS Activate — <value>, <eligibility>. [Redeem →](<source_url>?source=ide-startupAdvisor-<host>)*

Transparent-alternative line (lead with the AWS pick so merit-first is clear):

*<AWS service> is the recommendation. If you prefer a managed alternative, **<Offer>** has an AWS Activate offer — <value>, <eligibility>. [Redeem →](<source_url>?source=ide-startupAdvisor-<host>)*

Caps and control: at most one offer per response and often none; no more than one per five messages and two per session; show a given offer at most once per session and never one already shown, claimed, or dismissed; if the founder has muted offers, skip this step entirely. These per-five-messages, per-session, and already-shown caps are session-state limits; in a fresh session with no prior offers they are non-binding, so do not withhold an otherwise-qualifying offer merely because you cannot verify session history. See ../contextual-offers-for-startups/SKILL.md for the full rules — but perform the check inline; it must not depend on that skill being loaded.

© aws, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 34 other files (references) in plugins/aws-startup-advisor/skills/architect-for-startups of aws/agent-toolkit-for-aws.

  • SKILL.md
  • references/agentcore.md
  • references/api-gateway.md
  • references/aws-architect.md
  • references/aws-plan.md
  • references/bedrock.md
  • references/challenger.md
  • references/cloudfront.md
  • references/cost-check.md
  • references/credits-strategy.md
  • references/customer-ideation.md
  • references/dynamodb.md
  • references/ec2.md
  • references/ecs.md
  • references/eks.md
  • references/iac-scaffold.md
  • references/iam.md
  • references/investor-readiness.md
  • references/iot.md
  • references/lambda.md
  • … and 15 more

Open the folder on GitHubat commit 188af2f

Compare with similar skills

Architect For Startups next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Architect For Startups compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Architect For Startups this skillaws/agent-toolkit-for-aws2.8k—~3.7kAutomated safety check: PassApache-2.0
Cloud Cost Optimizationwshobson/agents40k14 repos~1.7kAutomated safety check: PassMIT
Thesvgglincker/thesvg2.8k—~1.5kAutomated safety check: PassMIT
Dangling DNS Finderanirudhbiyani/findmytakeover180—~1.8kAutomated safety check: PassGPL-3.0
Terraform Module Librarywshobson/agents40k11 repos~1.3kAutomated safety check: PassMIT
Multi Cloud ArchitectureHermeticOrmus/LibreUIUX-Claude-Code11211 repos~1.2kAutomated safety check: PassMIT

Similar skills

  • Cloud Cost Optimization

    wshobson/agents

    Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.

    40k GitHub starsUsed in 14 repos~1.7k tokens
    DevOps & CloudAuto-check passed

  • Thesvg

    glincker/thesvg

    Fetch brand SVG logos and cloud architecture icons (AWS, Azure, GCP) from theSVG.

    2.8k GitHub stars~1.5k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Dangling DNS Finder

    anirudhbiyani/findmytakeover

    Detect dangling DNS records and subdomain-takeover risks across a multi-cloud environment by running the bundled findmytakeover tool.

    180 GitHub stars~1.8k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Terraform Module Library

    wshobson/agents

    Build reusable, tested Terraform modules for AWS, Azure, GCP and OCI, with a standard file layout, an AWS VPC example, versioning rules and Terratest checks.

    40k GitHub starsUsed in 11 repos~1.3k tokens
    DevOps & CloudAuto-check passed

  • Multi Cloud Architecture

    HermeticOrmus/LibreUIUX-Claude-Code

    Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP.

    112 GitHub starsUsed in 11 repos~1.2k tokens
    DevOps & CloudAuto-check passed

  • Cloud Architect

    davila7/claude-code-templates

    Expert cloud architect specializing in AWS/Azure/GCP multi-cloud infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost optimization, and modern architectural patterns.

    32k GitHub starsUsed in 8 repos~1.9k tokens
    DevOps & CloudAuto-check passed

More from aws/agent-toolkit-for-aws

All 138 skills in this repo

  • Agent Advisor

    aws/agent-toolkit-for-aws

    Official

    Entry point for AI-agent work on AWS: pick a runtime, plan a migration for existing workloads, and build an executable POC — one phased flow.

    2.8k GitHub stars~4.9k tokensUpdated today
    Auto-check passed

  • Agents Build

    aws/agent-toolkit-for-aws

    Official

    A skill your agent uses to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal.

    2.8k GitHub stars~2.3k tokensUpdated today
    Auto-check: notes

  • Launch With AWS

    aws/agent-toolkit-for-aws

    Official

    Migrates vibe-coded web applications to AWS. An agent skill from aws/agent-toolkit-for-aws.

    2.8k GitHub stars~3.2k tokensUpdated today
    Auto-check passed

  • Processing S3 Uploads With Step Functions

    aws/agent-toolkit-for-aws

    Official

    Deploy an event-driven workflow that routes S3 uploads to either Lambda or Fargate via Step Functions based on file size.

    2.8k GitHub stars~4k tokensUpdated today
    Auto-check passed

  • AWS Marketplace Metering

    aws/agent-toolkit-for-aws

    Official

    Deploys, queries, and debugs AWS Marketplace usage-based (PAYG) metering — the pipeline (ResolveCustomer, BatchMeterUsage, EventBridge via SAM) and querying/debugging metering records, statuses…

    2.8k GitHub stars~18k tokensUpdated today
    Auto-check passed

  • Agents Pay

    aws/agent-toolkit-for-aws

    Official

    A skill your agent uses when THIS agent needs to pay for x402-protected content at runtime: hitting a paywall mid-task, settling it via AgentCore Payments, and applying operator-defined spend limits.

    2.8k GitHub stars~6.5k tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Architect For Startups

What does Architect For Startups do?

Startup-tailored AWS architecture advice for non-agent workloads, adjusted to the company's stage (pre-revenue through Series B+), team size, runway, and credits. Architect For Startups is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Startup-tailored AWS architecture advice for non-agent workloads, adjusted to the company's stage (pre-revenue through Series B+), team size, runway, and credits.

When should I use Architect For Startups?

Architect For Startups fits situations like: A founder wants guidance; A recommendation rather than code changes: which services to choose; review an architecture; how to stretch credits and control cost.

How do I install Architect For Startups in Claude Code?

Run `npx skills add aws/agent-toolkit-for-aws --skill architect-for-startups -a claude-code`. Or copy the skill folder (plugins/aws-startup-advisor/skills/architect-for-startups in aws/agent-toolkit-for-aws) into .claude/skills/architect-for-startups in your project. Claude Code loads it when a task matches its description.

How do I install Architect For Startups in Codex?

Run `npx skills add aws/agent-toolkit-for-aws --skill architect-for-startups -a codex`. Or copy the skill folder (plugins/aws-startup-advisor/skills/architect-for-startups in aws/agent-toolkit-for-aws) into .agents/skills/architect-for-startups in your project. Codex loads it when a task matches its description.

Can I use Architect For Startups in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws/agent-toolkit-for-aws --skill architect-for-startups -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architect-for-startups, .gemini/skills/architect-for-startups, .github/skills/architect-for-startups and .opencode/skills/architect-for-startups in your project.

What does Architect For Startups need to run?

SKILL.md names no scripts, command-line tools or credentials: Architect For Startups is instructions for the agent only.

Does Architect For Startups access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Architect For Startups safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Architect For Startups use?

Architect For Startups is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Architect For Startups use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 47k tokens, read only when the agent opens those files.

What are the alternatives to Architect For Startups?

Skills that share tags, products or a category with Architect For Startups: Cloud Cost Optimization (wshobson/agents, 40k stars), Thesvg (glincker/thesvg, 2.8k stars), Dangling DNS Finder (anirudhbiyani/findmytakeover, 180 stars) and Terraform Module Library (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Architect For Startups?

aws (a GitHub organization, an official publisher) maintains it in aws/agent-toolkit-for-aws, which has 2,825 GitHub stars. The repository holds 138 skills in this directory. The repository was last updated on October 7, 2026.

Source: aws/agent-toolkit-for-aws on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.