Recognize that measurements and observations depend on frame of reference—absolute values are less meaningful than relationships and context
Scanned 9/20/2026
Install to Claude Code
npx -y skills add lev-os/agents --skill relativity --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Relativity?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/lev-os-relativity)More formats (shields.io, HTML) on the badges page.
---
name: relativity
description: Recognize that measurements and observations depend on frame of reference—absolute values are less meaningful than relationships and context
---
# Relativity
**What**: The principle that physical measurements (space, time, velocity) depend on the observer's frame of reference—there is no absolute perspective; only relationships between frames matter.
**When to use**: When interpreting metrics, comparing systems in different contexts, or recognizing that "absolute" measures are often frame-dependent.
**Introduced by**: Albert Einstein (1905 Special Relativity, 1915 General Relativity)
## Core Mechanism
**Key insights:**
- No absolute space or time—measurements depend on observer's motion
- Speed of light is constant in all frames
- Time dilates, length contracts at high velocities
- Metaphorically: Context determines measurement; absolute values mislead
## Execution Steps (Metaphorical Application)
### 1. Identify Frame of Reference
From what perspective is this measurement taken? User context, business context, technical constraints?
### 2. Compare Across Frames
How does same phenomenon appear from different perspectives?
### 3. Focus on Invariants
What relationships hold across all frames? These are the meaningful measures.
### 4. Avoid Absolute Claims
Recognize context-dependence. "Fast" depends on baseline; "good metric" depends on goals.
## Real-World Applications
**Performance Metrics**: "Slow" is relative—acceptable for batch job, unacceptable for API endpoint
**Product Value**: Feature value depends on user context—power user vs. casual user frames
**Business Metrics**: Revenue growth "good" or "bad" relative to market, stage, investment
## Scoring Criteria
**Practitioner Weight**: 10/10 — Einstein's theory validated experimentally; foundational to modern physics, GPS, particle physics
**Clarity & Executability**: 6/10 — Physics is clear; metaphorical application requires interpretation
**Proven ROI**: 10/10 — Enables GPS, particle accelerators, cosmology; metaphor useful in context-aware thinking
**Novelty**: 10/10 — Revolutionary physics; challenges absolute space/time intuitions
**Cross-Domain Applicability**: 7/10 — Direct application in physics; metaphorical in business/software
**Total Score**: 43/50 (Tier 1: Canonical)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!