Scaffold-time observability so a shipped product is not blind in prod from day one — error capture (Sentry), request-id structured logging, and /healthz + /readyz endpoints. stack-baseline pins Sentry but nothing wires it; this is the wiring. Loaded by app-scaffolder (bake into the scaffold), infra-provisioner (prod env + probes), and consumed by l3-support (traces) and devops (deploy gate).
中文简介正在准备中。当前显示原文说明。
安装前可以查看交给 AI 代理的指令内容。
stack-baseline names Sentry and wires it nowhere — so every shipped product's first prod incident is invisible, and l3-support triages blind. This skill makes three things exist at scaffold time. Defaults baked in; no founder question.
instrumentation.ts (Next.js) / SDK init at process start; DSN from SENTRY_DSN
env (never hardcoded).console.log prose) with a per-request
request_id (generate at the edge, propagate via header/async-local-storage).GET /healthz — liveness (process up). GET /readyz — readiness (deps reachable:
db, cache). Cheap, unauthenticated, no PII.| Consumer | What it does with this skill |
|---|---|
| app-scaffolder | bakes instrumentation.ts + the JSON logger + /healthz+/readyz into the generated app; adds SENTRY_DSN to .env.example |
| infra-provisioner | sets SENTRY_DSN in the prod env list; points the platform health probe at /readyz; records the Sentry project in PROVISION |
| l3-support | first triage step reads Sentry + the request-id logs (a trace now exists to read) |
| devops | deploy gate fails if /readyz doesn't return 200 post-deploy |
A scaffolded app where the first prod error is captured, every request is traceable
by id, and the platform can health-check it. Record the Sentry project + endpoints
in docs/infra/PROVISION-{slug}.md. Done = the three pieces exist AND are wired
into the prod env, not just present in code.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
great_cto's own committed aesthetic — the instrument panel. Dark five-step surface ladder, exactly one accent, two faces divided by MEANING (Geist speaks, Geist Mono is machine-truth), tabular numerals, and a dash that is not a nought. Twelve checkable rules measured from packages/board and greatcto.systems, not designed for this file. Use when building or extending any great_cto surface — the board, the site, a report, a share page.
中文简介正在准备中。当前显示原文说明。
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
中文简介正在准备中。当前显示原文说明。
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does this site use', 'how is this built'. Also for single elements: 'copy this navbar', 'recreate this illustration', 'give me a prompt to regenerate this graphic' — element mode outputs a focused element.md, with token-grounded image-model prompts when the element is visual art. If the user brings any visual source and wants to understand it at a design level — this skill should activate.
中文简介正在准备中。当前显示原文说明。
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
中文简介正在准备中。当前显示原文说明。
Structured idea generation + multi-LLM debate for the product-owner stage. Diverge (generate genuinely different bets), debate (a 4-persona panel on 4 models argues over 2 rounds), converge (synthesize a recommendation). Used by product-owner before architect; available to architect for design-space exploration.
中文简介正在准备中。当前显示原文说明。
Run the great_cto controlled Codex lifecycle with controller-owned writes, verifier evidence, human gates and optional artifact release.
中文简介正在准备中。当前显示原文说明。