vibeflow-lammps

Generate LAMMPS inputs, data, potentials, dumps, restarts, and post-processing artifacts from caseDict.

12|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/sunrise-hjx/vibeFlow-skills --skill vibeflow-lammps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibeflow-lammps
Source: https://github.com/sunrise-hjx/vibeFlow-skills/tree/main/vibeflow-lammps
Command: npx skills add https://github.com/sunrise-hjx/vibeFlow-skills --skill vibeflow-lammps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

LAMMPS as VibeCAE's backend for molecular dynamics and particle simulations, enabling automated input generation, execution, and post-processing from 0-caseDict/caseDict, with optional custom styles or packages.

Core Features & Use Cases

  • Automated generation of in.case, data.*, potentials, dumps, restarts, and post-processing scripts from caseDict.
  • Development of reusable LAMMPS workflows, templates, Python analysis tools, or custom styles/packages when needed.
  • Use cases include MD and particulate simulations, diffusion, heat transport, and coarse-grained models that require coupling to higher-level CAE workflows.

Quick Start

Generate a minimal LAMMPS workflow from 0-caseDict/caseDict to verify input parsing with a simple LJ system.

Frequently Asked Questions about vibeflow-lammps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate LAMMPS molecular dynamics workflows from a caseDict?

LAMMPS molecular dynamics workflows are automated by generating in.case, data files, potentials, dumps, and restarts directly from a 0-caseDict/caseDict mapping. This process applies to atomic, molecular, coarse-grained, and particulate simulations requiring trajectories and thermodynamics.

Can I generate LAMMPS input files and post-processing scripts automatically?

LAMMPS input files and post-processing scripts are generated automatically from your caseDict configuration. The workflow produces in.case, data.*, potentials, dumps, restarts, and post-processing artifacts while recording versioned run metadata.

Does this workflow support custom LAMMPS styles and packages for particle simulations?

Custom LAMMPS styles and packages are supported for particle simulations when needed. The workflow accommodates atomic, molecular, coarse-grained, and particulate simulations, allowing optional custom styles or packages to be integrated into the automated run.

What is the best way to run end-to-end LAMMPS simulations with restart capabilities?

End-to-end LAMMPS simulations with restart capabilities are run by generating inputs, data, potentials, dumps, and restart files from a caseDict. This approach ensures trajectories and thermodynamics are captured while recording versioned artifacts and run metadata.

How do I set up a minimal LAMMPS workflow to verify caseDict input parsing?

A minimal LAMMPS workflow verifies caseDict input parsing by generating a simple LJ system from 0-caseDict/caseDict. This quick start confirms that input generation and execution mapping function correctly before running complex molecular dynamics simulations.

Are there limitations when using LAMMPS for coarse-grained models requiring coupling to higher-level CAE workflows?

LAMMPS coarse-grained models requiring coupling to higher-level CAE workflows need references to LAMMPS documentation and scripts for input generation and post-processing. Development of reusable templates, Python analysis tools, or custom styles may be required to handle specialized coupling requirements.