本文へ移動
cccskills
無料GitHub で公開

derive-theoretical-result

Derive a theoretical result step-by-step from first principles or established theorems, with every step explicitly justified and special cases checked. Use when 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.

インストール方法を見る

含まれるファイル(3)

  • SKILL.md12.8 KB
  • references/CITATIONS.bib1.4 KB
  • references/CITATIONS.md591 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Derive Theoretical Result

Produce 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.

When to Use

  • Deriving a formula, relation, or theorem from first principles (e.g., deriving the Euler-Lagrange equation from the action principle)
  • Proving a mathematical statement by logical deduction from axioms
  • Re-deriving a textbook result to verify it or adapt it to a modified context
  • Extending a known result to a more general setting (e.g., from flat spacetime to curved spacetime)
  • Producing a self-contained derivation for a paper, thesis, or technical report

Inputs

  • Required: Target result to derive (equation, inequality, theorem statement, or relation)
  • Required: Starting point (axioms, postulates, previously established results, or Lagrangian/Hamiltonian)
  • Optional: Preferred proof technique (direct, by contradiction, by induction, variational, constructive)
  • Optional: Notation conventions to follow (if matching a specific textbook or collaborator's conventions)
  • Optional: Known intermediate results that may be cited without re-derivation

Procedure

Step 1: State Starting Assumptions and Target Result

Write the derivation's contract explicitly before any calculation:

  1. Axioms and postulates: List every assumption the derivation rests on. For physics, this includes the symmetry group, the action principle, or the postulates of quantum mechanics. For mathematics, this includes the axiom system and any previously proven lemmas.
  2. Target result: State the result to be derived in precise mathematical notation. If the result is an equation, write both sides. If it is an inequality, state the direction and the conditions for equality.
  3. Scope and restrictions: State the domain of validity (e.g., "valid for non-relativistic, spinless particles in three dimensions"). Identify what the derivation does not cover.
  4. Notation declaration: Define every symbol that will appear. This prevents ambiguity and makes the derivation self-contained.
## Derivation Contract
- **Starting from**: [axioms, postulates, or established results]
- **Target**: [precise mathematical statement]
- **Domain of validity**: [restrictions and assumptions]
- **Notation**:
  - [symbol]: [meaning and units]
  - ...

Expected: A complete, unambiguous statement of what is being derived from what, with all notation defined upfront.

On failure: If the target result is ambiguous or the starting assumptions are incomplete, clarify before proceeding. A derivation with hidden assumptions is unreliable.

Step 2: Identify Required Mathematical Machinery

Survey the tools needed and verify their applicability:

  1. Algebraic techniques: Identify required manipulations (tensor algebra, commutator algebra, matrix operations, series expansions). Verify that the structures involved satisfy the prerequisites (e.g., convergence conditions for series, invertibility for matrix operations).
  2. Calculus and analysis: Identify whether the derivation requires ordinary or partial differentiation, integration (and over what domain), functional derivatives, contour integration, or distribution theory. Verify regularity conditions (differentiability, integrability, analyticity).
  3. Symmetry and group theory: Identify representation-theoretic tools needed (irreducible representations, Clebsch-Gordan coefficients, character orthogonality, Wigner-Eckart theorem).
  4. Topology and geometry (if applicable): Identify geometric structures (manifolds, fiber bundles, connections) and topological constraints (boundary terms, winding numbers, index theorems).
  5. Known identities and lemmas: Collect the specific identities that will be invoked (e.g., Jacobi identity, Bianchi identity, integration by parts, Stokes' theorem). State each one explicitly so the derivation can cite them by name.
## Mathematical Toolkit
- **Algebra**: [techniques and prerequisites]
- **Analysis**: [calculus tools and regularity conditions]
- **Symmetry**: [group theory tools]
- **Identities to invoke**: [list with precise statements]

Expected: A checklist of mathematical tools with their applicability conditions verified for the specific problem at hand.

On failure: 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.

Step 3: Execute Derivation with Step-by-Step Justification

Carry out the derivation with every step labeled and justified:

  1. One operation per step: Each numbered step performs exactly one algebraic or logical operation. Do not combine multiple manipulations into a single step.
  2. Justification labels: Tag each step with its justification. Common labels:
    • [by assumption] -- invoking a stated axiom or assumption
    • [by definition] -- using a previously 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)
  3. Intermediate checkpoints: After every 5-10 steps, pause and verify:
    • Units/dimensions are consistent on both sides
    • Known symmetries are preserved
    • The expression has the correct transformation properties
  4. Branch points: If the derivation branches (e.g., case analysis for degenerate vs. non-degenerate eigenvalues), treat each branch as a labeled sub-derivation and merge the results.
## 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

Expected: A linear sequence of steps from the starting point to the target result, with no gaps in logic. Every step is independently verifiable.

On failure: If a step does not 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 can be shown that" unless the omitted result is a well-known identity listed in Step 2.

Step 4: Check Limiting Cases and Special Values

Validate the derived result against known physics or mathematics:

  1. Limiting cases: Identify at least three limiting cases where the result should reduce to something known:

    • A simpler, previously derived formula (e.g., non-relativistic limit of a relativistic result)
    • A trivial case (e.g., setting a coupling constant to zero)
    • An extreme parameter regime (e.g., high-temperature or low-temperature limit)
  2. 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).

  3. Symmetry checks: Verify that the result transforms correctly under the symmetry group. If the result should be a scalar, check that it is invariant. If it should be a vector, check its transformation law.

  4. Consistency with related results: Check that 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] |
| ... | ... | ... | ... | ... |

Expected: All limiting cases and special values produce the expected results. The derivation is internally consistent.

On failure: 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.

Step 5: Present Complete Derivation with Notation Glossary

Assemble the final, polished derivation:

  1. Narrative structure: Write a brief introductory paragraph stating the physical or mathematical motivation, the approach, and the main result.
  2. Derivation body: Present the steps from Step 3, cleaned up for readability. Group related steps into logical blocks with descriptive headings (e.g., "Expanding the action to second order", "Applying the stationary phase condition").
  3. Result box: State the final result in a highlighted block, clearly separated from the derivation.
  4. Notation glossary: Compile every symbol used in the derivation with its meaning, units (if physical), and first occurrence.
  5. Assumptions summary: List all assumptions in a single place, distinguishing fundamental postulates from technical assumptions (e.g., smoothness, convergence).
## 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. ...

Expected: A self-contained document that a reader can follow from start to finish without consulting external references, except for the explicitly cited identities and theorems.

On failure: 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.

Validation

  • All starting assumptions are explicitly stated before the first calculation step
  • Every derivation step has a labeled justification (no unjustified leaps)
  • Units and dimensions are consistent at every intermediate checkpoint
  • At least three limiting cases are checked and produce expected results
  • Special values match independently known answers
  • The result transforms correctly under the stated symmetry group
  • A notation glossary defines every symbol used
  • The derivation is complete: no steps are deferred with "it can be shown"
  • The domain of validity is explicitly stated with the final result

Common Pitfalls

  • Hidden assumptions: Assuming a function is analytic, a series converges, or an integral exists without stating it. Every regularity condition is an assumption and must be declared.
  • Sign errors: The most common mechanical error. Verify signs at every step by tracking them through substitutions. Cross-check against dimensional analysis (a sign error often produces a dimensionally inconsistent expression).
  • Dropped boundary terms: When integrating by parts or applying Stokes' theorem, boundary terms vanish only if specific conditions are met. State why they vanish (e.g., "because the field decays faster than 1/r at infinity").
  • Order of limits: Taking limits in the wrong order can give different results (e.g., thermodynamic limit before zero-temperature limit). State the order explicitly and justify it.
  • Circular reasoning: Using the result to be derived as an intermediate step. This is especially subtle when the result is a well-known formula that "seems obvious." Every step must follow from the stated starting point, not from familiarity with the answer.
  • Notation collisions: Using the same symbol for different quantities (e.g., 'E' for energy and for electric field). The notation glossary prevents this, but only if it is written before the derivation rather than after.

Related Skills

  • formulate-quantum-problem -- formulate the quantum mechanical framework before deriving results from it
  • survey-theoretical-literature -- find prior derivations of the same or related results for comparison

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as READY for transformation, when migrating from monolith to microservices, when replacing a core subsystem while dependents continue operating, or when any architectural change must be gradual rather than big-bang.

日本語の概要は準備中です。原文の説明を表示しています。

pjt222/agent-almanac372026年10月12日 更新

adaptic

無料

Master skill composing the 5-step synoptic cycle for panoramic synthesis across multiple domains. Orchestrates meditate, expand-awareness, observe, awareness, integrate-gestalt, and express-insight into a coherent process that produces unified understanding rather than sequential compromise. Use when a problem genuinely spans 3+ domains and the interactions between domains matter more than depth in any one, when sequential analysis feels like compromise rather than integration, or before major architectural decisions affecting multiple stakeholders.

日本語の概要は準備中です。原文の説明を表示しています。

pjt222/agent-almanac372026年10月12日 更新

Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive test suite. Use when adding a completely new puzzle type to the package or following the 10-point integration checklist to ensure nothing is missed end-to-end.

日本語の概要は準備中です。原文の説明を表示しています。

pjt222/agent-almanac372026年10月12日 更新

Add Rcpp or RcppArmadillo integration to an R package for high-performance C++ code. Covers setup, writing C++ functions, RcppExports generation, testing compiled code, and debugging. Use when an R function is too slow and profiling confirms a bottleneck, when you need to interface with existing C/C++ libraries, or when implementing algorithms (loops, recursion, linear algebra) that benefit from compiled code.

日本語の概要は準備中です。原文の説明を表示しています。

pjt222/agent-almanac372026年10月12日 更新

aikido

無料

Practice aikido as a defensive martial art emphasizing harmony, redirection, and controlled resolution. Covers centering and grounding, ukemi (safe falling and rolling), core techniques (irimi-nage, shiho-nage, kote-gaeshi, ikkyo), blending and tai sabaki (body movement), randori (multiple attacker practice), weapons awareness, and applying principles off the mat. Use when learning a defensive martial art that prioritizes de-escalation, developing the ability to redirect aggression without causing unnecessary harm, building safe falling skills, or cultivating calm centeredness under physical pressure.

日本語の概要は準備中です。原文の説明を表示しています。

pjt222/agent-almanac372026年10月12日 更新

Analyze an arbitrary codebase to identify functions, APIs, and data sources suitable for exposure as MCP tools, producing a tool specification document. Use when planning an MCP server for an existing project, auditing a codebase before wrapping it as an AI-accessible tool surface, comparing what a codebase can do versus what is already exposed via MCP, or generating a tool spec to hand off to scaffold-mcp-server.

日本語の概要は準備中です。原文の説明を表示しています。

pjt222/agent-almanac372026年10月12日 更新

pjt222 のスキルをすべて見る

このスキルの問題を報告する