brenocqbrenocq/implot3d/.github/copilot-instructions.md

implot3d

Copilot instructions1.3k starsChanged 18 months agoMITView on GitHub

ImPlot3D is a C++ library for 3D plotting, extending Dear ImGui. It is designed to be efficient, flexible, and easy to use for real-time 3D data visualization. If you need to consult the ImGui/ImPlot codebase for reference, you need to first build the example code to have their files available in the build/ directory. You can find them in example/build/deps/implot-src/ and example/build/deps/imgui-src/

We split this copilot-instructions.md into the rules it gives an agent

7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Maintain ImGui/ImPlot3D Style: Ensure new code integrates seamlessly with the existing codebase's style and API patterns.
line 8
Very specific:
Code Formatting: Use clang-format. Ensure code is formatted correctly before proposing changes.
line 15
Distinctive:
Documentation: Document public APIs and complex logic.
line 16
Very specific:
Demos: When a new feature is added, include a demo in implot3d_demo.cpp to showcase its usage.
line 17
Very specific:
Commit Messages: Follow Conventional Commits (feat:, fix:, refactor:, docs:, style:, test:, chore:, merge:).
line 23
Very specific:
Breaking Changes: When making changes to public API signatures (function parameters, return types, struct members, etc.), always add an …
line 24
Very specific:
If you need to consult the ImGui/ImPlot codebase for reference, you need to first build the example code to have their files available in …
line 40

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

copilot-instructions.md

ImPlot3D Copilot Instructions

ImPlot3D is a C++ library for 3D plotting, extending Dear ImGui. It is designed to be efficient, flexible, and easy to use for real-time 3D data visualization.

General Guidelines:

Prioritize C++ Best Practices: Adhere to idiomatic C++ and maintain high code quality.
Maintain ImGui/ImPlot3D Style: Ensure new code integrates seamlessly with the existing codebase's style and API patterns.
ImPlot Reference Some of the feature requests may already be implemented in ImPlot. Before implementing a new feature, check the ImPlot documentation and codebase to see if it can be adapted for ImPlot3D.
Focus on 3D Plotting: Solutions should be specific to 3D visualization within the ImPlot3D framework.
Performance & Real-time: Solutions should consider performance for real-time 3D rendering.

Development Flow & Standards:

Code Formatting: Use clang-format. Ensure code is formatted correctly before proposing changes.
Documentation: Document public APIs and complex logic.
Demos: When a new feature is added, include a demo in implot3d_demo.cpp to showcase its usage.

Contribution Specifics:

Bug Fixes: Provide concise and effective fixes.
Feature Implementation: Implement features aligned with the existing structure.
Commit Messages: Follow Conventional Commits (feat:, fix:, refactor:, docs:, style:, test:, chore:, merge:).
Breaking Changes: When making changes to public API signatures (function parameters, return types, struct members, etc.), always add an entry to the "API BREAKING CHANGES" section at the top of implot3d.cpp with the date and version number.

Build Example Code:

cd examples/
cmake -B build && cmake --build build

File Structure Reference:

Below is a brief overview of the key files in the ImPlot3D repository:

implot3d.h, implot3d.cpp: Core ImPlot3D API.
implot3d_internal.h, implot3d_items.cpp: Internal implementation details.
implot3d_demo.cpp: Comprehensive examples and demo.
implot3d_meshes.cpp: Pre-loaded meshes support.

If you need to consult the ImGui/ImPlot codebase for reference, you need to first build the example code to have their files available in the build/ directory. You can find them in example/build/_deps/implot-src/ and example/build/_deps/imgui-src/

Download now (ZIP)

Aug 5, 2026Reworked ImDrawList functions for 1.93 (now merged! some breakage!) — ocornut/imgui16 reactions · 10 comments
May 5, 2026Sugerencias sobre Formato de Repositorio — wabohorquezr/PEM1 reaction
Feb 16, 2025[implot3d] New port — microsoft/vcpkg1 reaction · 1 comment
Jan 8, 2025Add cimplot3d wrapper — sonoro1234/LuaJIT-ImGui1 reaction
Sep 11, 2026[request] implot3d/v0.4 — conan-io/conan-center-index0 reactions

7 more on GitHub

Jun 9, 2026[Feature] Add implot3d as a vcpkg dependency and expose it in the public API — Jgocunha/imgui-platform-kit0 reactions
Dec 31, 2025Feature: Implementation of Per Point Custom Color for Line, Scatter and nd Contour — epezent/implot0 reactions · 2 comments
Dec 19, 2025[implot3d] update to 0.3 — microsoft/vcpkg0 reactions
Dec 19, 2025[implot3d] update to 0.3 — microsoft/vcpkg0 reactions
Nov 4, 2025Improve `README.md` — gumyr/build123d0 reactions
Jan 4, 2025Add brenocq/implot3d — matiassingers/awesome-readme0 reactions · 1 comment
Jan 3, 2025ImPlot3D Integration — eldritch-codex/nodens0 reactions

On Bluesky · 2

Dec 17, 2024ImPlot3D: A 3D Plotting Library for Dear ImGui github.com/brenocq/impl... — @ocornut.bsky.social173 likes and reposts · 6 replies
Feb 26, 2026github.com/brenocq/impl... i'm ashamed to say i didn't know about this. DearImGui extension that does what ImPlot does, but in 3D. its… — @robotsmakegames.bsky.social4 likes and reposts

On Hacker News · 1

Dec 18, 2024Show HN: ImPlot3D – A 3D Plotting Library for Dear ImGui170 points · 42 comments

Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free