김경종
51 lines
2.2 KiB
Markdown
51 lines
2.2 KiB
Markdown
---
|
|
name: abaqus-subroutine-interface
|
|
description: Use when defining Abaqus User Subroutine input/output parameter contracts, Abaqus ABI argument semantics, supported .inp test scope, validation rules, and extracted CSV schemas for reference comparison.
|
|
---
|
|
|
|
# Abaqus Subroutine Interface
|
|
|
|
Use this skill to define exactly what Abaqus passes into a User Subroutine and what the subroutine must return or update.
|
|
|
|
## Inputs
|
|
|
|
Read first:
|
|
|
|
- `AGENTS.md`
|
|
- `docs/ABAQUS_SUBROUTINE_AGENT_DESIGN.md`
|
|
- `docs/io-definitions/README.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.
|
|
|
|
## Output Contract
|
|
|
|
Produce or revise `docs/io-definitions/<feature-id>-io.md` with Abaqus Input Scope, Abaqus ABI Contract, Syntax Policy, Model Data Mapping, History Data Mapping, Subroutine Parameter Contract, Output and CSV Schemas, Validation Rules, and Downstream Handoff.
|
|
|
|
## Boundaries
|
|
|
|
- Do not implement parsers.
|
|
- Do not implement wrappers.
|
|
- Do not design Fortran source layout.
|
|
- Do not claim full Abaqus compatibility.
|
|
- Do not run Abaqus.
|
|
- Do not generate reference CSVs.
|
|
- Do not approve release readiness.
|
|
|
|
## Quality Gate
|
|
|
|
- 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.
|
|
|
|
## Handoff
|
|
|
|
Send input examples and schema needs to Reference Model Agent, implementation constraints to Implementation Planning Agent, and comparison matching rules to Reference Verification Agent.
|