fix skills rules
This commit is contained in:
9
.agents/rules/context_exclude_vtk.md
Normal file
9
.agents/rules/context_exclude_vtk.md
Normal file
@@ -0,0 +1,9 @@
|
||||
---
|
||||
trigger: manual
|
||||
---
|
||||
# Context Restriction: No VTK
|
||||
When this rule is active, restrict the operational context to libraries excluding the VTK layer.
|
||||
- **Exclude Path**: `src/Vtk`
|
||||
- **Include Paths**: `src/Core`, `src/Math`, `src/HEP`, `src/Root`, `src/Python`, `src/utils`
|
||||
- **Focus**: Tomographic reconstruction algorithms, data structures in `Core`, and physical modeling in `HEP`.
|
||||
- **Constraint**: Avoid referencing `Puppet`, `Viewport`, or any VTK-specific headers unless the user overrides this restriction.
|
||||
9
.agents/rules/context_gcompose.md
Normal file
9
.agents/rules/context_gcompose.md
Normal file
@@ -0,0 +1,9 @@
|
||||
---
|
||||
trigger: manual
|
||||
---
|
||||
# Context Focus: gcompose Application
|
||||
When this rule is active, prioritize the `gcompose` GUI application.
|
||||
- **Primary Path**: `app/gcompose`
|
||||
- **Focus**: `MainPanel`, `ContextPanel`, `PropertiesPanel`, and `ViewportPane`.
|
||||
- **Integration**: Wiring of Qt signals/slots between the `uLib` core model and the GUI widgets.
|
||||
- **Dependency**: Reference `src/Vtk` and `src/Core` as the underlying framework for the application.
|
||||
9
.agents/rules/context_vtk.md
Normal file
9
.agents/rules/context_vtk.md
Normal file
@@ -0,0 +1,9 @@
|
||||
---
|
||||
trigger: always_on
|
||||
---
|
||||
# Context Inclusion: VTK
|
||||
When this rule is active, include the VTK visualization layer in the operational context.
|
||||
- **Priority Path**: `src/Vtk`
|
||||
- **Focus**: `Puppet` hierarchy, `Viewport` management, and the synchronization between domain objects and VTK props.
|
||||
- **Key Classes**: `vtkViewport`, `vtkQViewport`, `vtkObjectsContext`, and all classes in `src/Vtk/HEP/Geant`.
|
||||
- **Logic**: Ensure transformations (TRS) applied to domain objects are correctly mirrored in the visualization layer and vice versa.
|
||||
@@ -1,8 +0,0 @@
|
||||
---
|
||||
trigger: always_on
|
||||
---
|
||||
|
||||
build in build directory using always micromamba "uLib" env.
|
||||
build with:
|
||||
make flag -j$(nproc)
|
||||
ninja -C build
|
||||
39
.agents/skills/micromamba_build.md
Normal file
39
.agents/skills/micromamba_build.md
Normal file
@@ -0,0 +1,39 @@
|
||||
# Skill: Build uLib with Micromamba
|
||||
|
||||
This skill provides instructions for building the uLib project using the micromamba environment.
|
||||
|
||||
## Context
|
||||
- **Environment**: micromamba `uLib`
|
||||
- **Output Directory**: `build`
|
||||
- **CPU Usage**: All available cores
|
||||
|
||||
## Instructions
|
||||
|
||||
1. **Environment Setup**:
|
||||
Ensure micromamba is properly initialized and the `uLib` environment is active.
|
||||
```bash
|
||||
export MAMBA_EXE="/home/share/micromamba/bin/micromamba"
|
||||
export MAMBA_ROOT_PREFIX="/home/share/micromamba"
|
||||
eval "$(/home/share/micromamba/bin/micromamba shell hook --shell bash)"
|
||||
micromamba activate uLib
|
||||
```
|
||||
|
||||
2. **Full Rebuild (if needed)**:
|
||||
If the `build` directory does not exist or a full reconfiguration is required:
|
||||
```bash
|
||||
conan profile detect --force
|
||||
conan install . --output-folder=build --build=missing
|
||||
cmake --preset conan-release
|
||||
```
|
||||
|
||||
3. **Incremental Build**:
|
||||
Run the build command from the root directory, pointing to the `build` folder and using all cores.
|
||||
```bash
|
||||
cmake --build build -j$(nproc)
|
||||
```
|
||||
|
||||
4. **Specific Target Build**:
|
||||
To build a specific target (e.g., gcompose):
|
||||
```bash
|
||||
cmake --build build --target gcompose -j$(nproc)
|
||||
```
|
||||
Reference in New Issue
Block a user