메뉴
Define and enforce 8-12 architecture principles with rationale and implications. Use when establishing guardrails for technology choices, ADR reviews, or platform paved roads.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | architecture-principles |
| description | Define and enforce 8-12 architecture principles with rationale and implications. Use when establishing guardrails for technology choices, ADR reviews, or platform paved roads. |
Principles are durable, opinionated statements that constrain design space and accelerate decisions. Done well (TOGAF / Spewak style: statement, rationale, implications) they reduce ADR debate, anchor reviews, and become inputs to fitness functions and policy-as-code.
| Concern | Recommended |
|---|---|
| Format | TOGAF 10.x principle template (Name, Statement, Rationale, Implications) |
| Storage | Repo-as-source-of-truth (/docs/principles/*.md), rendered via Backstage TechDocs |
| Linkage | ADRs (MADR 4.0), fitness functions, paved-road catalog |
| Decisioning | Lightweight RFC + architecture council (async-first) |
| Enforcement | OPA/Conftest, ArchUnit, Backstage scorecards |
| Reference | TOGAF 10.x; Spewak EAP; Team Topologies |
flowchart LR
V[Vision + constraints] --> D[Draft 8-12 principles]
D --> R[Review w/ stakeholders]
R --> P[Publish in repo + Backstage]
P --> E[Enforce: ADRs, fitness, OPA]
E --> M[Measure adherence]
M --> U[Revise yearly]
## P-04: Buy or adopt before build
- Statement: Prefer managed or open-source solutions over bespoke for non-differentiating capabilities.
- Rationale: Engineering capacity is finite; differentiation lives in the domain.
- Implications:
- ADRs must justify build with explicit differentiation hypothesis.
- Vendor and OSS evaluation template required (license, SLSA level, exit cost).
- Platform team curates an approved catalog; off-catalog choices need exception.
# OPA enforcement of P-07: All services emit OpenTelemetry
package paved_road
deny[msg] {
input.kind == "Service"
not input.spec.observability.otel.enabled
msg := "Principle P-07 violation: OpenTelemetry must be enabled"
}
| Pitfall | Mitigation |
|---|---|
| Vague slogans | Test: does it forbid a real option? If no, rewrite |
| 30+ principles | Cap at 12; archive the rest as guidelines |
| No enforcement | Tie each to ADR prompt, fitness function, or policy |
| Principles ignored in reviews | Add "Principles considered" section to ADR template |
| Static forever | Schedule annual review; allow deprecation |
/docs/principles/index.md plus one file per principle.Build production integrations with Anthropic Claude (Claude 4.5 Sonnet, Claude Opus 4, Claude Haiku 4) via the Messages API — system prompts, multi-turn conversations, tool use (function calling), prompt caching, extended thinking, vision, batched requests, and streaming. Use when wiring Claude into backends, agentic workflows, or evaluating it against other foundation models. Requires ANTHROPIC_API_KEY.
Deploy Cloudflare Workers, Pages, and Workers-with-static-assets safely using Wrangler 4.x with versioned uploads, gradual deployments, preview/production environments, secret bindings, observability, and one-command rollback. Use when shipping edge workloads, API routes, or full-stack apps to Cloudflare. Requires CLOUDFLARE_API_TOKEN with scoped permissions or an authenticated Wrangler session.
Deploy static sites, framework apps (Next.js, Astro, Remix, SvelteKit, Nuxt), Edge Functions, and serverless Functions to Netlify with deploy previews, branch deploys, atomic production promotion, scoped env vars, and instant rollback. Use when releasing on Netlify via CLI, API, or Git-triggered builds. Requires NETLIFY_AUTH_TOKEN (PAT) and NETLIFY_SITE_ID.
Transcribe audio with OpenAI speech-to-text models (gpt-4o-transcribe, gpt-4o-mini-transcribe, whisper-1) using prompt-guided terminology, segment-level timestamps, optional diarization via post-processing, and reliable artifact delivery. Use when converting interviews, calls, podcasts, or meeting recordings into reviewable text. Requires OPENAI_API_KEY.
Deploy Web Services, Private Services, Background Workers, Cron Jobs, Static Sites, PostgreSQL, and Key-Value (Redis-compatible) on Render via Blueprints (`render.yaml`) or the Render API with preview environments, zero-downtime rolling deploys, health checks, env-group secret scoping, and one-click rollback. Use when releasing services, applying schema migrations, or syncing infra-as-code on Render. Requires RENDER_API_KEY (owner- or workspace-scoped).
Operate Sentry end-to-end — error monitoring, performance tracing, session replay, profiling, release health, source-map upload, ownership routing, alert tuning, issue triage, and CI integration via sentry-cli — across web, mobile, and backend stacks. Use when instrumenting an app, wiring releases into deploy pipelines, or running incident-grade triage. Requires SENTRY_AUTH_TOKEN (org-scoped, `project:releases project:write`), project DSN, and (for source maps) `org` + `project` slugs.