Back to skills
SkillHub ClubShip Full StackFull Stack

project-structure

Overview of the main directories and important files in the repository. Use this to understand the project layout and find where code lives.

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars
240
Hot score
98
Updated
March 20, 2026
Overall rating
C3.2
Composite score
3.2
Best-practice grade
B84.0

Install command

npx @skill-hub/cli install spirimirror-libuipc-project-structure

Repository

spiriMirror/libuipc

Skill path: .cursor/skills/project-structure

Overview of the main directories and important files in the repository. Use this to understand the project layout and find where code lives.

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: spiriMirror.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

  • Install project-structure into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
  • Review https://github.com/spiriMirror/libuipc before adding project-structure to shared team environments
  • Use project-structure for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: project-structure
description: Overview of the main directories and important files in the repository. Use this to understand the project layout and find where code lives.
---

# Project Structure Guide

Overview of the main directories and important files in the repository.

## Top-Level Directories

- `apps/` - C++ apps, benchmarks, examples, and tests (see `apps/CMakeLists.txt`).
- `assets/` - Scene assets and simulation data.
- `cmake/` - Shared CMake utilities and macros.
- `docs/` - Documentation, specs, and site assets.
- `external/` - Third-party dependencies (e.g., `external/muda/`).
- `include/` - Public C++ headers.
- `output/` - Generated outputs from simulations. (the contents is ignored by git)
- `python/` - Python package, tests, and metadata.
- `scripts/` - Utility scripts and notebooks.
- `src/` - Core C++ implementation.
- `xmake/` - XMake rules and build helpers.

## Subfolder Purposes

### `apps/`

- `app/` - Shared app utilities and test helpers.
- `benchmarks/` - Benchmark executables.
- `examples/` - Example applications (each in its own subfolder).
- `tests/` - C++ test suites grouped by feature area.

### `assets/`

- `scenes/` - Scene README and references.
- `sim_data/` - Mesh assets (`linemesh/`, `tetmesh/`, `trimesh/`).

### `docs/`

- `build_install/` - Build and install guides.
- `development/` - Developer docs and diagrams.
- `specification/` - API/spec references and constitutions.
- `tutorial/` - Tutorial content and media.
- `overrides/` - MkDocs HTML overrides.
- `stylesheets/` - Docs CSS.
- `javascripts/` - Docs JS.
- `media/` - Images for docs pages.
- `misc/` - Miscellaneous documentation.

### `external/`

- `muda/` - Third-party CUDA/math dependency (source + docs + tests).

### `include/`

- `uipc/` - Public headers grouped by module (backend, core, geometry, io, etc.).
- `uipc_gui/` - Public GUI-related headers. (now not supported)

### `python/`

- `src/uipc/` - Pure python code to enhance the C++ pybind11 bindings.
- `tests/` - Python test suite.

### `scripts/`

- `optional_import/` - Optional dependency loaders.
- `symbol_calculation/` - Symbolic derivation notebooks and helpers.
- `SymEigen/` - SymEigen utilities, notebooks, and tests.

### `src/`

- `backends/` - Backend implementations (`common/`, `cuda/`, `none/`).
  - `common/` - Common utilities for all backends.
  - `cuda/` - CUDA backend with CUDA kernels.
  - `none/` - An empty backend that does nothing, as a template for creating a new backend or checking the basic functionality.
- `constitution/` - Physical constitution implementations.
- `core/` - Core engine systems and modules.
- `geometry/` - Geometry algorithms and data types.
- `gui/` - GUI runtime components. (now not supported)
- `io/` - Serialization and I/O.
- `pybind/` - C++/Python bindings.
- `sanity_check/` - Internal scene sanity checks to ensure the correctness of scene before the simulation.
- `usd/` - USD integration.
- `vdb/` - VDB integration.
project-structure | SkillHub