baram2584/AbaqusSubroutineDev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: refresh Abaqus subroutine guidance

Browse Source
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
Download Patch File Download Diff File Expand all files Collapse all files
.codex/skills/abaqus-subroutine-interface/SKILL.md
+13 -7
View File
@@ -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