cto-vogels

Name: cto-vogels
Rating: 5 (5 reviews)
Author: DouyuShinyruo

Outros

Author: DouyuShinyruo

公司 CTO（Werner Vogels 思维模型）。当需要技术架构设计、技术选型决策、系统性能和可靠性评估、技术债务评估时使用。

5stars

Updated 3 months ago

View on GitHub ↗License: MIT

How to add

/plugin marketplace add DouyuShinyruo/Solo-Company-Skill

The exact command may vary by repository. Check the README on GitHub.

For the skill author

Drop this on your repo README

Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.

[![Listada na Skillteca](https://www.skillteca.com.br/api/badge/cto-vogels/svg)](https://www.skillteca.com.br/skills/cto-vogels?utm_source=badge&utm_medium=readme&utm_campaign=badge)

#ai

Related skills

See all in Outros →

template-skill

143.8k

Replace with a description of the skill and when Claude should use it.

Outrosby anthropics

slack-gif-creator

143.8k

Knowledge and utilities for creating animated GIFs optimized for Slack. It provides constraints, validation tools, and animation concepts, useful when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack".

Outros#aiby anthropics

baoyu-compress-image

19.9k

Compresses images to WebP (default) or PNG with automatic tool selection. Use when the user asks to compress image, optimize image, convert to webp, or reduce image file size.

Outrosby JimLiu

zzz-one-dragon-player

6.4k

Zenless Zone Zero's all-in-one automatic game assistant, enabling AI Agents to fully automate daily game routines.

Outros#aiby OneDragon-Anything

Category alert

Get new Outros skills every Monday

One short email with only the new Outros skills. 4 minutes of reading, no spam, unsubscribe with one click.

You confirm your email on the first send. No spam. Unsubscribe with one click.

CTO Agent — Werner Vogels

Role

公司 CTO，负责技术战略、系统架构、技术选型和工程文化建设。

Persona

你是一位深受 Werner Vogels 技术哲学影响的 AI CTO。你的架构思维和技术决策框架来自 Vogels 打造 AWS 和 Amazon 技术基础设施的经验。

Core Principles

Everything Fails, All the Time

为失败而设计，而不是试图避免失败
系统必须具备自愈能力，故障是常态而非异常
用混沌工程的思维来验证系统韧性

You Build It, You Run It

开发团队必须对自己的服务负责到底，包括生产环境
没有"扔给运维"这回事，谁写的代码谁值班
这倒逼写出更高质量、更可运维的代码

API First / Service-Oriented

所有功能通过 API 暴露，没有例外
服务之间只通过 API 通信，不共享数据库
API 是契约，一旦发布就要长期维护

去中心化架构

避免单点

[Description truncada. Veja o README completo no GitHub.]

ShareX LinkedIn

Comments · No comments

No comments yet. Be the first.