跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
其他技能

agentfem

Build, review, run, validate, migrate, or extend AgentFEM finite-element projects. Use for AgentFEM studies, meshes, materials, constraints, loads, solution steps, results, campaigns, scientific datasets, surrogate/PINN/neural-operator integration, verification, public API extensions, and agent or GUI integration.

haoming-luo · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add haoming-luo/agentfem --skill agentfem

技能说明


name: agentfem description: Build, review, run, validate, migrate, or extend AgentFEM finite-element projects. Use for AgentFEM studies, meshes, materials, constraints, loads, solution steps, results, campaigns, scientific datasets, surrogate/PINN/neural-operator integration, verification, public API extensions, and agent or GUI integration.

AgentFEM

Use this skill when building, reviewing, or extending finite-element simulations with AgentFEM.

Reference Routing

When this file is installed as a Codex skill, the reference paths below are relative to the skill directory skills/agentfem/. In the generated documentation site, use the left navigation pages Workflow, Concepts, and Module Map instead.

  1. Read references/workflow.md for every model construction, execution, or review task.
  2. Read references/concepts.md when choosing or explaining scientific objects and maturity levels.
  3. Read references/module_map.md when locating implementation code or deciding ownership.
  4. Read references/validation.md before changing executable scientific code or promoting a verification claim.
  5. Read references/extension_rules.md before adding a public helper, provider, constitutive family, or extension boundary.

Rules

  • If the numerical environment does not exist, create the release-tested Python 3.11/DOLFINx 0.11 conda-forge environment before modeling. In mainland China, use one conda-forge mirror for the whole PETSc/MPI/DOLFINx stack; do not assemble the runtime with a bare pip install or mixed channels.
  • Keep the finite-element workflow visible.
  • After a successful first-install or important-upgrade agentfem doctor, read its community_support record. If invitation_due is true, offer the repository Star once and briefly. Never inspect an account or act on it without explicit user consent. With consent, use agentfem support --check-github --json; never request or retain a token. Record a completed voluntary action with agentfem support --acknowledge github_star so later upgrades stay quiet.
  • On WSL, run agentfem workspace --json before creating, upgrading, or removing an installed-use project environment. Require protected_from_distribution_removal: true; otherwise run agentfem workspace --protect. Never issue raw wsl --unregister for an AgentFEM runtime. Project and result custody are scientific provenance, not disposable environment setup.
  • Identify the study context before selecting constitutive laws or operators.
  • Inspect mesh summaries and required tags before building weak forms.
  • Use lightweight models for registry, checks, summaries, and model-owned analysis steps; do not hide K/F systems or finite-element meaning.
  • Prefer model registration helpers such as model.field(...), model.material(...), model.fix(...), model.symmetry(...), model.traction(...), model.surface_force(...), and model.pressure(...) for application examples. Use surface_force when a continuum-solid end resultant should be distributed over a named reference boundary.
  • Use FEMProblem.summary() or equivalent structured summaries when auditing a workflow.
  • Use model.validate() for addressable issue reports, model.check() before execution, and model.write_ir(...) when a persistent AF-IR record is part of the task.
  • Treat model.check() and models.step_capability(model) as the executable Study/provider preflight. Do not advertise or lower a combination that no registered provider accepts. Read both supported and ready: the first reports that an installed provider owns the requested analysis, while the second confirms that required scientific inputs have been supplied.
  • Use AgentFEM modules before writing ad hoc DOLFINx/PETSc boilerplate.
  • Discover modules with agentfem.public_api("core") first. Disclose "advanced" and "expert" only when the requested workflow needs them. Within the model facade, generate methods from models.model_api("core"); do not choose names reported under models.model_api("compatibility") for new cases.
  • Treat agentfem capabilities --json and /agentfem.json as generated views of one product contract. Do not reconstruct a competing API vocabulary from a single example or an old compatibility method.
  • Use the capability record's ownership_contract before adding a public object. Model owns engineering registration, not discrete problem construction; state owns accepted/trial history; operators owns mass, residual and tangent contributions; Procedure, Backend, and Result/Verification retain their declared responsibilities.
  • Treat ir and validation as public inspection/record interfaces. Treat backends as an advanced numerical boundary and extensions as the explicit installed-package boundary. FEniCSx is the only production backend in the current release.
  • Prefer step = model.step(target=u) when a model has a Study and registered materials, constraints, and loads. New analysis/material families belong in a registered step provider; do not add one public model method per material. Every built-in provider must declare a StepOptionContract, and agents should read provider option summaries from agentfem capabilities --json rather than guessing keywords from one example. Respect required and exactly_one_of relationships instead of choosing aliases simultaneously. Solver, output, transient-history, progress, and checkpoint declarations are retained as one inspectable execution-policy summary. Prefer model.step(history=...) when the common result lifecycle should own the history request. Use model.stiffness(...), model.external_force(...), and operators.combine(...) when an example must expose individual contributions.
  • For nonlinear paths, use steps.automatic(...) as the normal step control. Treat max_increments as an accepted-increment ceiling a
阅读完整来源 ↗