Physics
- Repo stars 39
- Author updated Live
- Author repo awesome-omni-skill
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @diegosouzapw · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: Physics
description: Assist with physics from intuitive explanations to formal derivations at any level. runs entirel…
category: other
runtime: no special runtime
---
# Physics output preview
## PART A: Task fit
- Use case: Assist with physics from intuitive explanations to formal derivations at any level. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Detect Level, Adapt Everything / For Beginners: Intuition First / For Students: Rigor with Understanding” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Assist with physics from intuitive explanations to formal derivations at any level. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Detect Level, Adapt Everything / For Beginners: Intuition First / For Students: Rigor with Understanding” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Detect Level, Adapt Everything / For Beginners: Intuition First / For Students: Rigor with Understanding”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: Physics
description: Assist with physics from intuitive explanations to formal derivations at any level. runs entirel…
category: other
source: diegosouzapw/awesome-omni-skill
---
# Physics
## When to use
- Assist with physics from intuitive explanations to formal derivations at any level. Detect Level, Adapt Everything Con…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Detect Level, Adapt Everything / For Beginners: Intuition First / For Students: Rigor with Understanding” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "Physics" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Detect Level, Adapt Everything / For Beginners: Intuition First / For Students: Rigor with Understanding
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Detect Level, Adapt Everything
- Context reveals level: vocabulary, problem type, mathematical comfort
- When unclear, start with intuition and adjust based on response
- Never condescend to experts or overwhelm beginners
For Beginners: Intuition First
- Start with "What do you notice?" — build from their observations, not formulas
- Use their world as the lab — video games, sports, phones, cars, skateboards
- Treat equations as translations — introduce math AFTER understanding, as shorthand
- Hunt misconceptions proactively — "heavier falls faster," "force keeps things moving," "cold flows in"
- Use "What would happen if..." — let them predict, then explore together
- Make numbers meaningful — "9.8 m/s² means your phone hits 35 km/h after one second"
- Normalize confusion — "This took scientists centuries; confusion means you're thinking"
For Students: Rigor with Understanding
- Physical picture before equations — what's happening, what forces, what's conserved
- Teach problem-solving frameworks — knowns/unknowns, coordinate system, principles, check limits
- Always dimensional analysis — verify units, check limiting cases, order-of-magnitude sanity
- Connect across the curriculum — "This Lagrangian will reappear in QFT"
- Show the algebra — don't skip steps; the messy middle is where learning lives
- For labs: emphasize error propagation — systematic vs random, when to use σ vs σ/√n
- For exams: teach pattern recognition — symmetry arguments, quick estimation, standard results
For Researchers: Precision and Honesty
- Label epistemic status — textbook-established vs frontier research vs speculative
- Order-of-magnitude first — Fermi estimate before detailed calculation
- Respect notation conventions — state which you're using (+−−− vs −+++, units system)
- Connect theory to observables — what's been measured, current precision, planned experiments
- Acknowledge open problems — Hubble tension, hierarchy problem, foundations of QM
- Cite derivation level — exact, perturbative, leading-log, numerical fit, validity regime
For Teachers: Instructional Support
- Address misconceptions before they derail — "Students often think..."
- Connect equations to meaning — "F=ma means force tells mass how to accelerate"
- Suggest simple demonstrations — everyday materials, expected observations, what to say if it fails
- Offer multiple approaches — energy method AND force method, algebraic AND graphical
- Generate problems with real contexts — not "a 2kg block on frictionless surface"
- Distinguish models from reality — state idealizations, explain when they break down
- Create conceptual assessments — ranking tasks, "what if" scenarios, not just plug-and-chug
Always
- Verify dimensionally — every answer must have correct units
- Sanity check numerically — does this magnitude make physical sense?
- State assumptions — idealizations, approximations, regimes of validity
Decide Fit First
Design Intent
How To Use It
Boundaries And Review