본문으로 건너뛰기
cccskills
무료GitHub에 공개

observability-baseline

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).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

avelikiy/great_cto
연동 도구Sentry
설치 방법 보기

포함된 파일(1)

  • SKILL.md3.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

observability-baseline

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.

1. Error capture (Sentry)

  • instrumentation.ts (Next.js) / SDK init at process start; DSN from SENTRY_DSN env (never hardcoded).
  • CI uploads source maps on release so stack traces are readable (release = git sha).
  • Capture unhandled rejections + a global error boundary on the client.

2. Request-id structured logging

  • A logger that emits JSON (not console.log prose) with a per-request request_id (generate at the edge, propagate via header/async-local-storage).
  • Levels: error / warn / info / debug — diagnostics go to stderr, never mixed into user-facing stdout. (Same discipline as the CLI logging gap, DEEPEN d94.)
  • One log line per request with: request_id, method, path, status, latency_ms.

3. Health endpoints

  • GET /healthz — liveness (process up). GET /readyz — readiness (deps reachable: db, cache). Cheap, unauthenticated, no PII.
  • These are what infra-provisioner probes and what a load balancer checks.

Wiring (a skill is shelfware unless a consumer loads it)

ConsumerWhat it does with this skill
app-scaffolderbakes instrumentation.ts + the JSON logger + /healthz+/readyz into the generated app; adds SENTRY_DSN to .env.example
infra-provisionersets SENTRY_DSN in the prod env list; points the platform health probe at /readyz; records the Sentry project in PROVISION
l3-supportfirst triage step reads Sentry + the request-id logs (a trace now exists to read)
devopsdeploy gate fails if /readyz doesn't return 200 post-deploy

Output

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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

aesthetic-instrument

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

avelikiy/great_cto1052026년 10월 22일 업데이트

anti-patterns

무료

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).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

avelikiy/great_cto1052026년 10월 22일 업데이트

anydesign

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

avelikiy/great_cto1052026년 10월 22일 업데이트

archetype-review-base

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

avelikiy/great_cto1052026년 10월 22일 업데이트

brainstorming

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

avelikiy/great_cto1052026년 10월 22일 업데이트

codex-host

무료

Run the great_cto controlled Codex lifecycle with controller-owned writes, verifier evidence, human gates and optional artifact release.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

avelikiy/great_cto1052026년 10월 22일 업데이트

avelikiy의 스킬 모두 보기

이 스킬의 문제 신고