NINI
32 lines
1.1 KiB
Markdown
32 lines
1.1 KiB
Markdown
---
|
|
name: fesa-abaqus-subset
|
|
description: Design or review Abaqus input parsing against the documented FESA Phase 1 keyword subset.
|
|
---
|
|
|
|
# FESA Abaqus Subset
|
|
|
|
Use this skill when parser scope, input compatibility, Nset/Elset handling, or unsupported keyword behavior is involved.
|
|
|
|
## Read First
|
|
|
|
- `/AGENTS.md`
|
|
- `/PROGRESS.md`
|
|
- `/PLAN.md`
|
|
- `/docs/ABAQUS_INPUT_SUBSET.md`
|
|
- `/docs/NUMERICAL_CONVENTIONS.md`
|
|
- `/docs/ARCHITECTURE.md`
|
|
- `/docs/VERIFICATION_PLAN.md`
|
|
|
|
## Workflow
|
|
|
|
1. Map each requested keyword to the documented Phase 1 subset.
|
|
2. Check `*Nset` and `*Elset` semantics, ordering, generated sets, and use by boundary/load/result requests.
|
|
3. Keep Abaqus keyword parsing separated from internal object creation through Factory + Registry.
|
|
4. Require explicit diagnostics for unsupported keywords instead of silent partial parsing.
|
|
5. Record parser-scope changes in ADRs or subset docs when they affect project policy.
|
|
|
|
## Do Not
|
|
|
|
- Do not silently expand support beyond the documented subset.
|
|
- Do not store parser-only details in solver core objects unless the architecture document requires it.
|