docs: refresh Abaqus subroutine guidance

This commit is contained in:
KOKO\Mimi
2026-08-18 11:27:22 +09:00
parent a3197dc2e3
commit e76c1b96fd
64 changed files with 498 additions and 4560 deletions
@@ -13,9 +13,6 @@ Read first:
- `AGENTS.md`
- `docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md`
- `docs/implementation-plans/README.md`
- `docs/build-test-reports/README.md`
- `docs/corrections/README.md`
- Related requirements, formulation, numerical review, interface, and test model documents
## Workflow
@@ -7,13 +7,14 @@ description: Use when drafting Abaqus User Subroutine finite element formulation
Use this skill to convert approved requirements and research evidence into a finite element formulation suitable for Abaqus User Subroutine implementation. Finite element formulation is the owned artifact for this skill.
**REQUIRED SUB-SKILL:** Use `fem-theory-query` for finite element theory, constitutive integration, tangent, benchmark, and numerical verification knowledge.
## Inputs
Read first:
- `AGENTS.md`
- `docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md`
- `docs/formulations/README.md`
- `docs/requirements/<feature-id>.md`
- `docs/research/<feature-id>-research.md`
@@ -7,23 +7,28 @@ description: Use when defining Abaqus User Subroutine input/output parameter con
Use this skill to define exactly what Abaqus passes into a User Subroutine and what the subroutine must return or update.
**REQUIRED SUB-SKILL:** Use `fem-theory-query` when interface decisions need FEM output semantics, tensor conventions, or numerical context.
## Inputs
Read first:
- `AGENTS.md`
- `docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md`
- `docs/io-definitions/README.md`
- `docs/AbaqusUserSubroutineManual/INDEX_MAP.md`
- `docs/AbaqusUserSubroutineManual/INDEX.md`
- Requirements, research, formulation, and numerical review documents
## Workflow
1. Define the Abaqus ABI Contract for each entry point.
2. Record required parameter semantics for UMAT, VUMAT, UEL, or other selected entry points.
3. Define input parameters, output parameters, in-place updates, units, coordinate system, and storage conventions.
4. For UMAT, define STRESS, STRAN, DSTRAN, TIME, DTIME, TEMP, PREDEF, PROPS, NPROPS, COORDS, DROT, DDSDDE, STATEV, PNEWDT, NOEL, NPT, KSTEP, and KINC usage as applicable.
5. Define supported `.inp` model scope for tests and output requests needed for extracted CSV comparison.
6. Define Validation Rules and failure messages.
1. Locate each selected entry point in `INDEX_MAP.md`, read its complete `INDEX.md` record, and read every listed `source_ranges` span in order.
2. Treat `INDEX.md` summaries, keywords, and content anchors as retrieval metadata, not authoritative interface evidence.
3. Define the Abaqus ABI Contract for each entry point from the manual source spans.
4. Record required parameter semantics for UMAT, VUMAT, UEL, or other selected entry points.
5. Define input parameters, output parameters, in-place updates, units, coordinate system, and storage conventions.
6. For UMAT, define STRESS, STRAN, DSTRAN, TIME, DTIME, TEMP, PREDEF, PROPS, NPROPS, COORDS, DROT, DDSDDE, STATEV, PNEWDT, NOEL, NPT, KSTEP, and KINC usage as applicable.
7. Define supported `.inp` model scope for tests and output requests needed for extracted CSV comparison.
8. Define Validation Rules and failure messages.
## Output Contract
@@ -44,6 +49,7 @@ Produce or revise `docs/io-definitions/<feature-id>-io.md` with Abaqus Input Sco
- Unsupported Abaqus input is explicit: unsupported, ignored-with-warning, or requires user decision.
- CSV schema includes units, coordinate system, output location, components, step/frame identity, and ID matching.
- ABI parameter direction and update responsibility are explicit for every used argument.
- Abaqus-specific claims cite the manual section and source spans used.
## Handoff
@@ -7,13 +7,14 @@ description: Use when independently reviewing Abaqus User Subroutine formulation
Use this skill to review whether a formulation is numerically sound enough for Abaqus User Subroutine interface definition and Fortran implementation planning. Numerical review is the owned artifact for this skill.
**REQUIRED SUB-SKILL:** Use `fem-theory-query` for finite element theory, patch tests, tangent consistency, stability, and benchmark evidence.
## Inputs
Read first:
- `AGENTS.md`
- `docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md`
- `docs/numerical-reviews/README.md`
- `docs/formulations/<feature-id>-formulation.md`
- Related requirements and research documents
@@ -7,13 +7,14 @@ description: Use when evaluating Abaqus User Subroutine physical plausibility af
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.
**REQUIRED SUB-SKILL:** Use `fem-theory-query` for equilibrium, benchmark, stress/strain interpretation, energy, residual, and model-adequacy knowledge.
## 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
@@ -13,7 +13,6 @@ Read first:
- `AGENTS.md`
- `docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md`
- `docs/releases/README.md`
- Requirements, research, formulation, numerical review, interface, test model, implementation, validation, and physics reports
## Workflow
@@ -13,7 +13,6 @@ Read first:
- `AGENTS.md`
- `docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md`
- `docs/requirements/README.md`
- User request, target Abaqus entry point, material/element behavior, constraints, and exclusions
- Existing `docs/requirements/<feature-id>.md` when revising a feature
@@ -7,6 +7,8 @@ description: Use when collecting Abaqus User Subroutine research evidence from o
Use this skill to collect source-backed Research evidence for Abaqus User Subroutine work while separating verified facts from inference.
**REQUIRED SUB-SKILL:** Use `fem-theory-query` for finite element theory, formulation, solver behavior, benchmark, or numerical verification knowledge.
## Inputs
Read first:
@@ -15,17 +17,22 @@ Read first:
- `docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md`
- `docs/research/README.md`
- `docs/requirements/<feature-id>.md`
- `docs/AbaqusUserSubroutineManual/INDEX_MAP.md`
- `docs/AbaqusUserSubroutineManual/INDEX.md`
- User-provided references, official Abaqus documentation links, books, papers, and benchmark sources
## Workflow
1. Define exact research questions from requirements and open issues.
2. Search source priorities in order: official Abaqus documentation, Abaqus User Subroutines Reference Guide, Abaqus Analysis User's Guide, books, papers, and benchmark sources.
3. Record source reliability tier, citation, scope, assumptions, and applicability limits.
4. Extract only facts needed by downstream formulation, Abaqus ABI interface definition, TDD test models, and Fortran implementation.
5. Separate verified facts from inference.
6. Identify candidate benchmark models, closed-form checks, patch tests, tangent checks, and negative tests.
7. Record unresolved conflicts or missing evidence as open issues.
2. For FEM knowledge, use `fem-theory-query` and retain the returned wiki evidence.
3. For Abaqus User Subroutine manual facts, locate the section in `INDEX_MAP.md`, read the complete `INDEX.md` record, then read every listed `source_ranges` span in order.
4. Treat `INDEX.md` summaries, keywords, and content anchors as retrieval metadata rather than authoritative facts.
5. Search other sources as needed: books, peer-reviewed papers, official benchmarks, and project-provided references.
6. Record source reliability tier, citation, scope, assumptions, and applicability limits.
7. Extract only facts needed by downstream formulation, Abaqus ABI interface definition, TDD test models, and Fortran implementation.
8. Separate verified facts from inference.
9. Identify candidate benchmark models, closed-form checks, patch tests, tangent checks, and negative tests.
10. Record unresolved conflicts or missing evidence as open issues.
## Output Contract
@@ -44,6 +51,7 @@ Produce or revise `docs/research/<feature-id>-research.md` with Source Inventory
- Source tiers are explicit.
- Each extracted fact links to a cited source.
- Each FEM claim traces to `fem-theory-query` evidence; each Abaqus manual claim traces to a section and every source span used.
- Inference is labeled as inference.
- Benchmark applicability limits are clear enough for Formulation and Reference Model Agents.
@@ -7,13 +7,14 @@ description: Use when designing Abaqus User Subroutine TDD test models, no-Abaqu
Use this skill to define the TDD test model portfolio before Fortran implementation and Abaqus validation.
**REQUIRED SUB-SKILL:** Use `fem-theory-query` for benchmark selection, patch tests, analytical expectations, and numerical verification design.
## Inputs
Read first:
- `AGENTS.md`
- `docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md`
- `docs/reference-models/README.md`
- Requirements, research, formulation, numerical review, and interface documents
## Workflow
@@ -13,7 +13,6 @@ Read first:
- `AGENTS.md`
- `docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md`
- `docs/reference-verifications/README.md`
- `docs/reference-models/<feature-id>-reference-models.md`
- `references/<feature-id>/<model-id>/metadata.json`
- Generated no-Abaqus and extracted CSV outputs