Abaqus Parametric Project Starter
Overview
Establish a small project contract before generating model logic. Keep inputs,
names, build stages, and evidence outputs separate so a failed run can be
diagnosed without reconstructing hidden assumptions.
When to use
Use for a new reusable project or a clean migration. Do not use it to restructure
an established project without an approved migration plan.
Inputs
- Analysis purpose and acceptance evidence
- Abaqus release and supported Python execution mode
- Geometry source, coordinate system, and units
- Parameter ranges and immutable baseline values
- Intended jobs, outputs, and destination boundary
Outputs
Produce a layout with configs/, src/, tests/, and outputs/; a single
entry point; a naming manifest; one example configuration; and a dry-run or
static-validation command.
Workflow
- Freeze the units and coordinate convention.
- Separate configuration data from Abaqus repository operations.
- Order stages as geometry, properties, assembly, steps, interactions, loads,
mesh, outputs, and job creation.
- Make every stage consume named inputs and return an evidence summary.
- Add a preflight check before any Abaqus execution.
Safety gates
- Never invent dimensions, material values, loads, or step controls.
- Keep generated files outside source directories.
- Make destructive rebuilds explicit and opt-in.
- Treat a created job as neither a completed solve nor a validated model.
Example prompts
Scaffold a parametric soil-block project with SI units, JSON configuration,
stable region names, a dry-run preflight, and separate generated outputs. Do
not create material values or submit a job.
Common failures
- Configuration contains Abaqus objects instead of serializable values.
- Names are repeated across scripts rather than imported from one manifest.
- The entry point performs irreversible cleanup before validation.
- Output paths depend on the current working directory.
Acceptance checklist
1---2name: abaqus-parametric-project-starter3description: Use when starting a new multi-file Abaqus Python automation project that needs explicit configuration, naming, execution, and output boundaries before model code is written.4---56# Abaqus Parametric Project Starter78## Overview910Establish a small project contract before generating model logic. Keep inputs,11names, build stages, and evidence outputs separate so a failed run can be12diagnosed without reconstructing hidden assumptions.1314## When to use1516Use for a new reusable project or a clean migration. Do not use it to restructure17an established project without an approved migration plan.1819## Inputs2021- Analysis purpose and acceptance evidence22- Abaqus release and supported Python execution mode23- Geometry source, coordinate system, and units24- Parameter ranges and immutable baseline values25- Intended jobs, outputs, and destination boundary2627## Outputs2829Produce a layout with `configs/`, `src/`, `tests/`, and `outputs/`; a single30entry point; a naming manifest; one example configuration; and a dry-run or31static-validation command.3233## Workflow34351. Freeze the units and coordinate convention.362. Separate configuration data from Abaqus repository operations.373. Order stages as geometry, properties, assembly, steps, interactions, loads,38 mesh, outputs, and job creation.394. Make every stage consume named inputs and return an evidence summary.405. Add a preflight check before any Abaqus execution.4142## Safety gates4344- Never invent dimensions, material values, loads, or step controls.45- Keep generated files outside source directories.46- Make destructive rebuilds explicit and opt-in.47- Treat a created job as neither a completed solve nor a validated model.4849## Example prompts5051> Scaffold a parametric soil-block project with SI units, JSON configuration,52> stable region names, a dry-run preflight, and separate generated outputs. Do53> not create material values or submit a job.5455## Common failures5657- Configuration contains Abaqus objects instead of serializable values.58- Names are repeated across scripts rather than imported from one manifest.59- The entry point performs irreversible cleanup before validation.60- Output paths depend on the current working directory.6162## Acceptance checklist6364- [ ] Units, coordinates, version, and execution mode are explicit.65- [ ] One configuration drives one deterministic build path.66- [ ] Shared names have one source of truth.67- [ ] Static validation runs before model mutation.68- [ ] Generated outputs cannot overwrite source files by default.
1348109517