This commit is contained in:
김경종
2026-06-10 10:03:11 +09:00
parent 87529c811a
commit 0912ee6f3b
174 changed files with 414 additions and 8544 deletions
+9 -12
View File
@@ -1,6 +1,6 @@
---
name: fesa-io-contract
description: Use when defining FESA solver I/O contracts, Abaqus .inp keyword subsets, internal model mapping, validation rules, HDF5 result/reference schemas, and optional CSV export schemas for solver outputs or reference comparison.
description: Use when defining FESA solver I/O contracts, Abaqus .inp keyword subsets, internal model mapping, validation rules, and CSV schemas for solver outputs or reference comparison.
---
# FESA I/O Contract
@@ -12,7 +12,7 @@ Use this skill to define exactly what input and output data the solver feature a
Read these first:
- `AGENTS.md`
- `docs/AGENT_RULES.md`
- `docs/SOLVER_AGENT_DESIGN.md`
- `docs/io-definitions/README.md`
- `docs/requirements/<feature-id>.md`
- `docs/formulations/<feature-id>-formulation.md`
@@ -25,10 +25,9 @@ Read these first:
3. Separate Model Data Mapping from History Data Mapping.
4. Define supported keywords such as `*NODE`, `*ELEMENT`, `*MATERIAL`, `*ELASTIC`, `*BOUNDARY`, `*CLOAD`, `*STEP`, `*OUTPUT`, `*NODE OUTPUT`, and `*ELEMENT OUTPUT` only when required.
5. Define Internal Model Contract at a semantic level without C++ APIs.
6. Define HDF5 Result and Reference Schemas for `results.h5`, including metadata, mesh, step/frame groups, field output datasets, history output datasets, component naming, and matching keys.
7. Define optional CSV export schemas only when upstream requirements explicitly request CSV files or a comparison helper format.
8. Define units, coordinate system, component naming, output location, step/frame identity, and ID matching rules.
9. Define validation rules and open issues.
6. Define Output and CSV Schemas for `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv`, and optional result files.
7. Define units, coordinate system, component naming, output location, step/frame identity, and ID matching rules.
8. Define validation rules and open issues.
## Output Contract
@@ -39,8 +38,7 @@ Produce or revise `docs/io-definitions/<feature-id>-io.md` with:
- Model Data Mapping
- History Data Mapping
- Internal Model Contract
- HDF5 Result and Reference Schemas
- Optional CSV Export Schemas
- Output and CSV Schemas
- Validation Rules
- Downstream Handoff
@@ -50,17 +48,16 @@ Produce or revise `docs/io-definitions/<feature-id>-io.md` with:
- Do not design C++ APIs.
- Do not claim full Abaqus compatibility.
- Do not run Abaqus, Nastran, or any reference solver.
- Do not generate reference HDF5 artifacts or reference CSVs.
- Do not generate reference CSVs.
- Do not approve release readiness.
## Quality Gate
- Every supported keyword has a documented purpose, required data, and unsupported-case behavior.
- HDF5 schemas carry units, coordinate system, component naming, output location, step/frame identity, dataset paths, and ID matching rules.
- Optional CSV schemas carry the same semantics when explicitly required.
- CSV schemas carry units, coordinate system, component naming, output location, and ID matching rules.
- Unsupported Abaqus input is explicit: unsupported, ignored-with-warning, or requires user decision.
- The I/O contract is compatible with requirements, formulation, and reference comparison needs.
## Handoff
Send keyword and HDF5 schema contracts to Reference Model Agent and Implementation Planning Agent. Send dataset paths, comparison schema, ID matching, and tolerance-source constraints to Reference Verification Agent.
Send keyword and schema contracts to Reference Model Agent and Implementation Planning Agent. Send comparison schema, ID matching, and tolerance-source constraints to Reference Verification Agent.
@@ -1,4 +1,4 @@
interface:
display_name: "FESA I/O Contract"
short_description: "Define solver I/O contracts"
default_prompt: "Use $fesa-io-contract to define Abaqus input and HDF5 result contracts."
default_prompt: "Use $fesa-io-contract to define Abaqus input and result CSV contracts."