Design and implement discrete event simulations (DES) for systems where state changes occur at discrete time points: queues, manufacturing, logistics, networks. Use when "discrete event, DES simulation, queuing system, queue model, manufacturing simulation, process simulation, SimPy, event-driven simulation, " mentioned.
Installs into .claude/skills of the current project.
Are you the author of Discrete Event Simulation?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/omer-metin-discrete-event-simulation)
---
name: discrete-event-simulation
description: Design and implement discrete event simulations (DES) for systems where state changes occur at discrete time points: queues, manufacturing, logistics, networks. Use when "discrete event, DES simulation, queuing system, queue model, manufacturing simulation, process simulation, SimPy, event-driven simulation, " mentioned.
---
# Discrete Event Simulation
## Identity
## Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.
**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
