القائمة
Provides high-level understanding of the Datum Cloud platform architecture. Use when onboarding to the codebase, understanding the system structure, or learning about multi-tenancy, resource hierarchy, and service architecture.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Covers GitHub conventions for pull requests, issues, and comments including linking, language style, formatting, and callout syntax. Use when creating PRs, writing issues, or posting comments on Datum Cloud repositories.
Turn raw engineering notes, PR/issue links, commit messages, or a one-line feature description into a changelog entry for Datum Cloud's GitHub Discussions Changelog category: a benefit-led title plus a markdown body, drafted for users and ready to hand off for final capture and publish. Use when someone says "write a changelog entry", "announce this in the changelog", or "post this to the changelog discussions" — this is the community-facing changelog POST, not the Keep a Changelog release file (that lives in `gtm-templates`).
Provides templates for go-to-market communications including blog posts, changelogs, social media, and enablement briefs. Use when writing launch announcements or marketing content.
Create a new GitHub release. Verifies CI is green on the release commit and refreshes the third-party NOTICE file before tagging, determines the next version from the latest tag, summarizes merged PRs since the last release, drafts release notes in the established style, and publishes via gh release create. Works for any datum-cloud service repository.
Scan a project repository for strict AGPL-3.0 license compliance across Go, Rust, and JavaScript/React codebases. Use this skill whenever the user asks to check, audit, verify, or enforce AGPL license compliance on a project, repo, or codebase. Triggers on phrases like "check agpl compliance", "audit license headers", "is this project agpl compliant", "scan for license headers", "check my license files", "agpl audit", or any request involving ensuring a project is properly licensed under AGPL. Always use this skill — don't wing AGPL compliance checks from general knowledge.
Covers producing weekly operational reports for the Datum AI Edge. Use when asked for an ops review, traffic report, latency analysis, provisioning report, or edge performance summary. Guides metric queries, anomaly detection, and publishing to datum-cloud/engineering.
| name | platform-knowledge |
| description | Provides high-level understanding of the Datum Cloud platform architecture. Use when onboarding to the codebase, understanding the system structure, or learning about multi-tenancy, resource hierarchy, and service architecture. |
| user-invocable | false |
This skill provides high-level understanding of the Datum Cloud platform architecture.
Datum Cloud is a multi-tenant cloud platform built on Kubernetes primitives. The control plane is Milo — an extensible multi-tenant control plane built with the Kubernetes API library.
Organization
└── Project
└── Resources (service-specific)
Top-level tenant boundary. Contains:
Workload isolation within an organization. Contains:
Every API request carries tenant context:
Some platform operations span tenants:
Services in Datum Cloud follow a consistent pattern:
Each service is a Kubernetes aggregated API server that:
Datum Cloud services can use either approach to integrate with the control plane:
The choice depends on two primary factors:
| Factor | Use Aggregated API Server | Use Controller-Runtime |
|---|---|---|
| Storage | Need custom backend (database, external system) | etcd is sufficient |
| API Control | Need custom subresources, streaming, or fine-grained request handling | Standard CRUD semantics |
For detailed guidance: Read k8s-apiserver-patterns/architecture-decision.md which covers:
Services use the pattern: {service}.miloapis.com
Examples:
resourcemanager.miloapis.com — Organizations and projectsiam.miloapis.com — Identity and access managementactivity.miloapis.com — Activity timelinesinsights.miloapis.com — Proactive issue detectionquota.miloapis.com — Resource quota enforcementResources follow Kubernetes conventions:
VirtualMachine)virtualmachines)vm)The platform uses a Kubernetes-native IAM system. Key concepts:
| Resource | Purpose |
|---|---|
ProtectedResource | Declares a resource type and its permissions |
Role | Collection of permissions that can be granted |
PolicyBinding | Binds a role to users/groups on a resource |
User | Platform user identity |
Group | Collection of users |
Permissions flow down the resource hierarchy:
Read milo-iam/SKILL.md for comprehensive IAM documentation.
Every service can integrate with these platform capabilities:
| Capability | Purpose | Integration Point |
|---|---|---|
| IAM | Authorization | ProtectedResource + Role definitions |
| Quota | Limit resource consumption | Admission control |
| Insights | Proactive issue detection | InsightPolicy resources |
| Telemetry | Observability data | Metrics, traces, logs |
| Activity | Audit trail | ActivityPolicy resources |
Read the individual capability skills for integration details.
services-catalog.md — Catalog of platform services