grasscaograssgrasscaograss/AwesomeWeldoneSkills/robim-data-explorer/SKILL.md

robim-data-explorer

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

Explore Robim.Data source code definitions from the local clone at d:/robim_data. Use when the user is working in the weldone project (or any project referencing Robim.Data nuget) and needs to understand types from the Robim.Data namespace or its sub-namespaces (Robim.Data.Geometry, Robim.Data.Math, Robim.Data.Process, Robim.Data.ArcWeldingCraft, Robim.Data.Weld, Robim.Data.Coarse, Robim.Data.Scanning, etc.). Trigger scenarios: (1) user mentions a type name that belongs to Robim.Data, (2) user asks about data structures defined in Robim.Data nuget packages, (3) user needs to understand proto definitions in Robim.Data.Proto, (4) user references fields/properties whose types are in Robim.Data and the definition is not available through standard project references.

In this repository60 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- add-diag-instrumentationSkill
- add-diag-logsSkill
- archive-importSkill
- archive-sessionSkill
- archiveSkill
- ask-mattSkill
- build-publish-runSkill
- coarse-compensation-fitSkill
- codebase-designSkill
- code-simplifySkill
- commitSkill
- create-weld-docSkill
- DDD-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- feishu-webhookSkill
- git-branch-mergeSkill
- gitlab-issueSkill
- gitlab-merge-requestSkill
- gitlab-opsSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- improve-codebase-architectureSkill
- knowledge-reorgSkill
- modelbase-fsmSkill
- modelbase-fsm-updateSkill
- opsx-reindexSkill
- opsx-searchSkill
- parallel-featureSkill
- periodic-reviewSkill
- prototypeSkill
- read-diag-capturesSkill
- robimweld-release-checkSkill
- robimweld-source-debugSkill
- robot-to-worldSkill
- setup-matt-pocock-skillsSkill
- skill-creatorSkill
- superpowersSkill
- tddSkill
- teachSkill
- three-blazor-devSkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- weldone-animationSkill
- weldone-current-urdfSkill
- weldone-db-migrationSkill
- weldone-hybrid-seam-replay-debugSkill
- weldone-mapmatrix-domain-knowledgeSkill
- weldone-project-logsSkill
- weldone-transition-line-domain-knowledgeSkill
- weldone-wsg-merge-domain-knowledgeSkill
- weld-plan-debugSkill
- weld-seam-normal-vectorsSkill
- world-to-robotSkill
- writing-great-skillsSkill

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.

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

Common
Distinctive
Very specific

Very specific:
When this skill is triggered, the user needs to understand a type or data structure that lives in the Robim.Data nuget package.
line 23
Very specific:
If found: Read the corresponding file from d:/robim_data/<file-path>.
line 31
Very specific:
If not found: Use Grep to search d:/robim_data/src for the type name.
line 32
Very specific:
When searching for proto-generated types, grep both the .proto file (for schema) and the obj/ generated .cs files if you need the exact …
line 80
Very specific:
If the user reports that types are missing or outdated, run the index script with pwsh 7 (UTF-8 default): pwsh -NoProfile -ExecutionPolicy …
line 86

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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

SKILL.md

Robim.Data Explorer

When this skill is triggered, the user needs to understand a type or data structure that lives in the Robim.Data nuget package. The source code is available locally at d:/robim_data.

Workflow

Identify the type name the user is asking about.
Look up in the index: Open references/type-index.md and search for the type name.
If found: Read the corresponding file from d:/robim_data/<file-path>.
If not found: Use Grep to search d:/robim_data/src for the type name.
Return the relevant code to the user with context.

Directory Structure of d:/robim_data

d:/robim_data/
  src/
    Robim.Data/               -- Hand-written C# core data models
      Geometry/               -- Point, Box, Plane, Mesh, PolyLineCurve, etc.
      Math/                   -- Vector, Matrix3D, Quaternion, Euler, Transform3D, etc.
      Process/                -- Pose, JointState, ArmPlanData, Process, etc.
      ProfileCutting/         -- Profile, Part, Nest, Macro, etc.
      Common/                 -- Extension methods, diff builder
      Display/                -- Display extensions
      Protobuf/               -- .proto definition files (ArcWeldingCraft, WeldSeam, Cmd, etc.)
    Robim.Data.Proto/         -- Nuget packaging for proto files
    Robim.Service.Core/       -- Service implementations (CommonServer, DeviceServiceImpl, etc.)
    Robim.Data.Wpf/           -- WPF controls and viewmodels
    Robim.Data.Test/          -- Test projects
    robim_data_cpp/           -- C++ bindings
    java/                     -- Java bindings

Key Namespaces and Where to Find Them

Namespace	Likely Source
`Robim.Data`	`src/Robim.Data/*.cs` or `Common/`, `Uitilitys/`
`Robim.Data.Geometry`	`src/Robim.Data/Geometry/*.cs`
`Robim.Data.Math`	`src/Robim.Data/Math/*.cs`
`Robim.Data.Process`	`src/Robim.Data/Process/*.cs`
`Robim.Data.Process.Cutting`	`src/Robim.Data/Process/*.cs`
`Robim.Data.ProfileCutting`	`src/Robim.Data/ProfileCutting/*.cs`
`Robim.Data.ArcWeldingCraft`	`src/Robim.Data/Protobuf/ArcWeldingCraft.proto`
`Robim.Data.Weld`	`src/Robim.Data/Protobuf/WeldSeam.proto` or `WeldSeamV3.proto`
`Robim.Data.Scanning`	`src/Robim.Data/Protobuf/Vision*.proto`
`Robim.Data.Coarse`	`src/Robim.Data/Protobuf/Vision*.proto`
`Robim.Data.Service`	`src/Robim.Data/Protobuf/*.proto` (CloudPlatform, etc.)

Proto File → C# Namespace Mapping

Proto files under src/Robim.Data/Protobuf/ generate C# types in namespaces matching the package declaration in each .proto file. For example:

ArcWeldingCraft.proto → package Robim.Data.ArcWeldingCraft
WeldSeam.proto → package Robim.Data.Weld
VisionBasicModel.proto → contains Robim.Data.Coarse, Robim.Data.Scanning

When searching for proto-generated types, grep both the .proto file (for schema) and the obj/ generated .cs files if you need the exact generated C# code.

Index Maintenance

The file references/type-index.md is a pre-generated index of all public types. If the user reports that types are missing or outdated, run the index script with pwsh 7 (UTF-8 default): pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/update-index.ps1

Download now (ZIP)

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