i18n/de/skills/derive-theoretical-result/SKILL.md
Derive a theoretical result step-by-step from first principles or established theorems, with every step explicitly justified and special cases checked. Verwenden wenn deriving a formula or theorem from first principles, proving a mathematical statement by logical deduction, re-deriving a textbook result for verification or adaptation, extending a known result to a more general setting, or producing a self-contained derivation for a paper or thesis.
npx skillsauth add pjt222/agent-almanac derive-theoretical-resultInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Erzeugen a rigorous, step-by-step derivation of a theoretical result starting from stated axioms, first principles, or established theorems. Every algebraic or logical step is explicitly justified, limiting cases are verified, and the final result is presented with a complete notation glossary.
Schreiben the derivation's contract explicitly vor any calculation:
## Derivation Contract
- **Starting from**: [axioms, postulates, or established results]
- **Target**: [precise mathematical statement]
- **Domain of validity**: [restrictions and assumptions]
- **Notation**:
- [symbol]: [meaning and units]
- ...
Erwartet: A complete, unambiguous statement of what is being derived from what, with all notation defined upfront.
Bei Fehler: If das Ziel result is ambiguous or the starting assumptions are incomplete, clarify vor proceeding. A derivation with hidden assumptions is unreliable.
Survey the tools needed and verify their applicability:
## Mathematical Toolkit
- **Algebra**: [techniques and prerequisites]
- **Analysis**: [calculus tools and regularity conditions]
- **Symmetry**: [group theory tools]
- **Identities to invoke**: [list with precise statements]
Erwartet: A checklist of mathematical tools with their applicability conditions verified for the specific problem at hand.
Bei Fehler: If a required tool has unverified prerequisites (e.g., term-by-term differentiation of a series whose uniform convergence is unknown), flag it as a gap. Either prove the prerequisite or state it as an additional assumption.
Carry out the derivation with every step labeled and justified:
[by assumption] -- invoking a stated axiom or assumption[by definition] -- using a zuvor declared definition[by {identity name}] -- applying a named identity (e.g., "by Jacobi identity")[by Step N] -- citing a previous step in this derivation[by {theorem name}] -- invoking an external theorem (stated in Step 2)## Derivation
**Step 1.** [Starting expression]
*Justification*: [by assumption / definition]
**Step 2.** [Result of operation on Step 1]
*Justification*: [specific reason]
...
**Checkpoint (after Step N).** Verify:
- Dimensions: [check]
- Symmetry: [check]
...
**Step M.** [Final expression = Target result]
*Justification*: [final operation] QED
Erwartet: A linear sequence of steps from the starting point to das Ziel result, with no gaps in logic. Every step is independently verifiable.
Bei Fehler: If a step nicht follow from the previous one, the derivation has a gap. Either insert the missing intermediate steps or identify the additional assumption needed. Never skip a step with "it kann shown that" unless the omitted result is a well-known identity listed in Step 2.
Validieren the derived result gegen known physics or mathematics:
Limiting cases: Identifizieren mindestens three limiting cases where das Ergebnis should reduce to something known:
Special values: Substitute specific values of parameters where the answer is known independently (e.g., n=1 for the hydrogen atom, d=3 for three-dimensional results).
Symmetry checks: Sicherstellen, dass das Ergebnis transforms korrekt under the symmetry group. If das Ergebnis sollte a scalar, check that it is invariant. If it sollte a vector, check its transformation law.
Consistency with related results: Pruefen, dass the derived result is consistent with other known results in the same theory (e.g., Ward identities, sum rules, reciprocity relations).
## Limiting Case Verification
| Case | Condition | Expected Result | Derived Result | Match |
|------|-----------|----------------|----------------|-------|
| [name] | [parameter limit] | [known result] | [substitution] | [Yes/No] |
| ... | ... | ... | ... | ... |
Erwartet: All limiting cases and special values produce the expected results. The derivation is internally consistent.
Bei Fehler: A failed limiting case indicates an error in the derivation. Trace the failure back by checking which step first produces an expression that fails the limit. Common causes: incorrect sign, missing factor of 2 or pi, wrong combinatorial coefficient, or a step where an order of limits matters.
Assemble the final, polished derivation:
## Final Result
> **Theorem/Result**: [precise statement with equation number]
## Notation Glossary
| Symbol | Meaning | Units | First appears |
|--------|---------|-------|---------------|
| [sym] | [meaning] | [units or dimensionless] | [Step N] |
| ... | ... | ... | ... |
## Assumptions
1. [Fundamental postulate 1]
2. [Technical assumption 1]
3. ...
Erwartet: A self-contained document that a reader can follow from start to finish ohne consulting external references, except for the explicitly cited identities and theorems.
Bei Fehler: If the derivation is too long for a single document (more than ~50 steps), break it into lemmas. Derive each lemma separately, then assemble the main result by citing the lemmas.
formulate-quantum-problem -- formulate the quantum mechanical framework vor deriving results from itsurvey-theoretical-literature -- find prior derivations of the same or related results for comparisontesting
Launch all available agents in parallel waves for open-ended hypothesis generation on problems where the correct domain is unknown. Use when facing a cross-domain problem with no clear starting point, when single-agent approaches have stalled, or when diverse perspectives are more valuable than deep expertise. Produces a ranked hypothesis set with convergence analysis and adversarial refinement.
tools
Write integration tests for a Node.js CLI application using the built-in node:test module. Covers the exec helper pattern, output assertions, filesystem state verification, cleanup hooks, JSON output parsing, error case testing, and state restoration after destructive tests. Use when adding tests to an existing CLI, testing a new command, verifying adapter behavior across frameworks, or setting up CI for a CLI tool.
development
Screen a proposed trademark for conflicts and distinctiveness before filing. Covers trademark database searches (TMview, WIPO Global Brand Database, USPTO TESS), distinctiveness analysis using the Abercrombie spectrum, likelihood of confusion assessment using DuPont factors and EUIPO relative grounds, common law rights evaluation, and goods/services overlap analysis. Produces a conflict report with a risk matrix. Use before adopting a new brand name, logo, or slogan — distinct from patent prior art search, which uses different databases, legal frameworks, and analysis methods.
tools
Scaffold a new CLI command using Commander.js with options, action handler, three output modes (human-readable, quiet, JSON), and optional ceremony variant. Covers command naming, option design, shared context patterns, error handling, and integration testing. Use when adding a command to an existing Commander.js CLI, designing a new CLI tool from scratch, or standardizing command structure across a multi-command CLI.