From datum-platform
Decision framework for determining which platform capabilities a feature needs (Quota, Insights, Telemetry, Activity). Use when planning a new feature to assess which capabilities apply.
npx claudepluginhub datum-cloud/claude-code-plugins --plugin datum-platformThis skill uses the workspace's default tool permissions.
This skill provides a decision framework for determining which platform capabilities a feature needs.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
This skill provides a decision framework for determining which platform capabilities a feature needs.
| Capability | Question to Ask | When to Use |
|---|---|---|
| Quota | What needs limits to prevent abuse? | Resource consumption |
| Insights | What can the platform detect that users can't? | Proactive issue detection |
| Telemetry | What do operators need to observe? | Debugging and SLOs |
| Activity | What actions need to be auditable? | Compliance and security |
| Feature Type | Likely Capabilities |
|---|---|
| New resource type | All four |
| New API operation | Activity, Telemetry |
| UI feature only | Telemetry (maybe) |
| Configuration change | Activity |
| Performance improvement | Telemetry |
Skip quota if: The resource is inherently limited by other means or has no abuse potential.
Skip insights if: Issues are immediately obvious to users or no early warning is possible.
Note: Insights uses a policy-driven model—services define InsightPolicy resources with CEL expressions that detect issues. No code changes are required to emit insights.
Skip telemetry if: The feature has no runtime behavior to observe.
Skip activity if: The action has no security or compliance implications.
Note: Activity uses a policy-driven model—services define ActivityPolicy resources that translate audit logs and Kubernetes events into human-readable summaries. No code changes are required to emit activities.
Read capability-activity/consuming-timelines.md for how to expose activity timelines to users via CLI, UI, or API.
Use this template:
## Platform Capability Assessment
### Quota
- **Applies**: Yes/No
- **Rationale**: Why or why not
- **If yes**: Dimensions to limit, tier defaults
### Insights
- **Applies**: Yes/No
- **Rationale**: Why or why not
- **If yes**: InsightPolicy rules to create, CEL conditions to evaluate
### Telemetry
- **Applies**: Yes/No
- **Rationale**: Why or why not
- **If yes**: Metrics, traces, logs needed
### Activity
- **Applies**: Yes/No
- **Rationale**: Why or why not
- **If yes**:
- Resource kinds needing policies
- Events to emit from controller (reason codes)
- Key operations to surface in timelines
Almost always needs all four:
Usually needs:
Usually skips:
Usually needs:
Usually skips:
capability-quota — Detailed quota integrationcapability-insights — Detailed insights integrationcapability-telemetry — Detailed telemetry integrationcapability-activity — Detailed activity integration