initial commit

2026-06-09 12:27:22 +09:00
commit f186160e44
79 changed files with 6915 additions and 0 deletions
@@ -0,0 +1,50 @@
+---
+name: abaqus-subroutine-physics-sanity
+description: Use when evaluating Abaqus User Subroutine physical plausibility after validation, including equilibrium, reactions, displacement direction, stress/strain sanity, state variable behavior, energy/residual checks, and model coverage.
+---
+
+# Abaqus Subroutine Physics Sanity
+
+Use this skill to decide whether validation-passing Abaqus User Subroutine outputs are physically credible enough for readiness review. Physics sanity is the owned artifact for this skill.
+
+## Inputs
+
+Read first:
+
+- `AGENTS.md`
+- `docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md`
+- `docs/physics-evaluations/README.md`
+- Reference verification reports
+- Stored reference and generated CSVs
+- Requirements, formulation, interface, and test model documents
+
+## Workflow
+
+1. Check global equilibrium, reaction consistency, displacement direction, symmetry, and boundary condition effects.
+2. Check stress/strain signs, magnitudes, locations, coordinate systems, and state variable evolution.
+3. Check energy/residual quantities when available.
+4. Check model coverage for the claimed behavior.
+5. Classify failures as `physics-implausible | model-inadequate | artifact-gap | upstream-contract | needs-correction`.
+
+## Output Contract
+
+Produce or revise `docs/physics-evaluations/<feature-id>-physics-evaluation.md` with Input Evidence, Physics Checks, Failure Classification, Evaluation Verdict, Handoff Recommendation, and No-Change Assertion.
+
+## Boundaries
+
+- Do not edit source code.
+- Do not edit tests.
+- Do not run Abaqus.
+- Do not generate reference CSVs.
+- Do not change tolerances.
+- Do not approve release readiness.
+
+## Quality Gate
+
+- Physical checks are tied to requirements and model purpose.
+- Passing tolerance comparison is not treated as sufficient by itself.
+- Implausible results name the exact quantity, model, and likely owner.
+
+## Handoff
+
+Send implementation-owned physical failures to Correction Agent, inadequate model coverage to Reference Model Agent, and passing physics evidence to Release Agent.