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

update agent, skill and scripts

Browse Source
This commit is contained in:
KOKO\Mimi
2026-09-07 01:15:26 +09:00
parent 42a4847da5
commit d7e9629640
38 changed files with 476 additions and 2946 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/skills/fem-io-contract/SKILL.md
+3 -32
View File
@@ -1,39 +1,10 @@
---
name: fem-io-contract
description: Use when an approved structural FEM feature needs external syntax, validation, internal mapping, result schema, or comparison identity contracts.
description: Define supported structural solver input semantics, diagnostics, result schema, and deterministic comparison mapping.
---
# FEM I/O Contract
Turn approved requirements, mathematics, and logical verification quantities into deterministic interfaces without changing their meaning.
Specify the assigned supported input subset, syntax and semantics, validation/diagnostics, source-label preservation, units, coordinates, components, internal mapping, authoritative output schema, and deterministic comparison projection. Unsupported meaningful semantics fail closed unless an explicit approved warning policy applies.
## Inputs
- Requirements, formulation, numerical review, and reference-model contracts for one `feature_id`
- Project architecture and configured input, output, and comparison backends
- Official specifications for any approved compatibility subset
## Workflow
1. Define the supported external syntax and semantics, defaults, ordering, identifiers, units, coordinates, validation, diagnostics, and unsupported behavior.
2. Map validated input to implementation-neutral model entities while preserving source identity.
3. Define result schema versioning, analysis step/frame identity, quantities, components, locations, units, coordinates, precision, and deterministic ordering.
4. Map logical verification quantities to result and reference identities. Specify missing, extra, duplicate, and nonfinite prechecks before tolerance evaluation.
5. Add parser, schema, round-trip, migration, and comparison contract tests.
Use [workflow and decision authority](../fem-requirements-baseline/references/workflow-and-decisions.md) when a format choice changes public compatibility. Use [evidence and handoff](../fem-requirements-baseline/references/evidence-and-handoff.md) for return data.
## Output
Follow [Feature document management](../../../docs/FEATURE_DOCUMENTATION.md): read the Coordinator's
feature context, keep main reports concise, and link necessary owned details in the same feature folder.
Create or revise `docs/<feature-id>/io.md` with input scope; grammar/semantic rules; validation matrix; internal mapping; output schema; comparison mapping; compatibility/versioning policy; test obligations; limitations; and handoff.
## Evidence
Trace every public field and mapping to a requirement, formulation quantity, numerical-review identity, or authoritative selected-format specification. Include positive and negative examples only where they disambiguate behavior.
## Boundary
Do not claim full compatibility from a subset, infer undocumented reference-product behavior, alter the formulation, redefine logical acceptance quantities, change tolerances, implement code, modify reference artifacts, or run an external solver. Input syntax, result containers, and tabular comparison formats are project-selected contracts, not mandatory solver identity.
Use public Abaqus material only for observable convention. State any supported difference; do not infer private parser, data model, algorithm, or output-database behavior. A compatibility or authoritative-schema change is a user decision when it changes the public contract. Return the contract and open gaps; do not select physics, tolerances, implementation, or alter reference artifacts.