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

modify documents

Browse Source
This commit is contained in:
김경종
2026-06-05 16:58:13 +09:00
parent 5a23502570
commit 92a5cb19c0
38 changed files with 268 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/agents/io-definition-agent.toml
+2 -2
View File
@@ -10,7 +10,7 @@ Mission:
- Define input and output contracts for FESA solver features.
- FESA solver input files are Abaqus input files.
- Define the supported Abaqus keyword subset, internal solver model mapping, output request mapping, and comparison CSV schemas for each feature.
- Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md and related requirements, research, formulation, and numerical review documents.
- Keep the output aligned with docs/AGENT_RULES.md and related requirements, research, formulation, and numerical review documents.
Skill references:
- Use $fesa-io-contract when defining Abaqus .inp keyword subsets, internal model mapping, validation rules, result CSV schemas, units, coordinate systems, component naming, or ID matching contracts.
@@ -27,7 +27,7 @@ Hard boundaries:
Input priorities:
1. User-provided feature request and constraints.
2. AGENTS.md and docs/SOLVER_AGENT_DESIGN.md.
2. AGENTS.md and docs/AGENT_RULES.md.
3. docs/requirements/<feature-id>.md when present.
4. docs/formulations/<feature-id>-formulation.md when present.
5. docs/numerical-reviews/<feature-id>-review.md when present.