القائمة
Establishes logging, metrics, and tracing conventions for the codebase. Use when setting up or auditing the observability stack and standards.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Interactive setup wizard for Company OS. Configures company.config.yaml, generates .claude/settings.json with tech-stack-specific permissions, and scaffolds directories. Supports three modes — interactive wizard, express config block, or auto-extract from a URL/unstructured text.
Produces RFC/ADR defining system boundaries, modules, data model, and integration points. Use when translating a PRD into technical design, making architectural decisions, or designing new system components.
Produces architecture diagrams, data flow diagrams, ERDs, and system overviews in Mermaid (inline) and Excalidraw JSON (standalone). Use when an RFC, threat model, or documentation needs visual diagrams.
Performs data flow threat analysis with structured mitigations. Use when assessing security threats for new features, architecture changes, or compliance reviews.
Creates platform-specific marketing playbooks for acquisition channels. Use when launching or optimizing a specific growth channel (e.g., LinkedIn, Twitter, email, Product Hunt).
Prepares pre-call briefings, captures post-call debriefs, and routes insights to ICP refinement and PRD evidence. Stores conversation logs as CONV- artifacts in artifacts/decision-memos/.
| name | observability-baseline |
| description | Establishes logging, metrics, and tracing conventions for the codebase. Use when setting up or auditing the observability stack and standards. |
| user-invokable | false |
Defines the baseline conventions for structured logging, application metrics, and distributed tracing so that every service produces consistent, queryable telemetry data from day one.
Read observability.* from company.config.yaml to determine logging, metrics, and tracing providers.
Provider-specific patterns:
| Provider | Logging | Metrics | Tracing |
|---|---|---|---|
| Datadog | Pino → dd-trace auto-inject | StatsD via hot-shots | dd-trace auto-instrumentation |
| Sentry | @sentry/node breadcrumbs | Sentry performance metrics | Sentry transactions |
| OpenTelemetry | OTLP exporter | OTLP metrics | OTLP spans |
| CloudWatch | winston + CloudWatch transport | CloudWatch embedded metrics | X-Ray SDK |
Structured log required fields:
{
"timestamp": "ISO-8601",
"level": "info|warn|error|debug",
"message": "Human-readable description",
"request_id": "uuid",
"user_id": "optional",
"tenant_id": "optional (if multi-tenant)",
"duration_ms": "optional (for timed operations)",
"error": { "code": "string", "stack": "string" }
}
Cross-references: See deployment-strategy for infrastructure setup, incident-response for alert routing.
artifacts/engineering/../tools/artifact/validate.sh.