picogk

Generates and verifies PicoGK voxel CAD geometry from CEM manifests for titanium forest-sensor parts.

23|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Alexey-Lukin/silken_net --skill picogk-alexey-lukin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: picogk
Source: https://github.com/Alexey-Lukin/silken_net/tree/main/.claude/skills/picogk
Command: npx skills add https://github.com/Alexey-Lukin/silken_net --skill picogk-alexey-lukin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working on the silken_net Code-as-CAD surface means navigating PicoGK voxel/SDF geometry generation, CEM (Computational Engineering Model) manifests, engineering drawings, voxel-FE elasticity runs, and verification gates — with many non-obvious kernel traps (native aborts, hollow solids, phase-locked sweeps) that are easy to hit and hard to diagnose. This Skill routes you to the correct source-of-truth documents, gotchas, and task recipes before you touch a generator, manifest, drawing, FE run, or verify gate. ## Core Features & Use Cases - CEM-driven geometry generation: Create or modify parts (Ti-coin coupon, Zone-1 gyroid anode, mechanical lock, cathode flange, PEEK radome) by editing cem/*.json manifests and C# generators, with every numeric field carrying a declared provenance ground. - Verification and measurement gates: Run verify for golden-metric regression, fea/fea --fit for measured Gibson-Ashby stiffness coefficients, converge for topology ladders, and resolution-adequacy checks against voxel size. - Engineering drawings: Emit SVG (human) and DXF (factory, via netDxf) drawings derived from the CEM with loud-absence NOT SPECIFIED IN CEM semantics instead of silent defaults. - Use Case: You need to change the anchor's pore period for a new tree-species SKU — the Skill directs you to edit the anchor CEM manifest, re-solve wallParam against the porosity target, re-measure via verify, and regenerate the golden baseline and drawing gallery. ## Quick Start Ask the assistant to generate the gyroid anchor STL from the anchor_zone1 CEM manifest and run the local verify gate on it.

Frequently Asked Questions about picogk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate the gyroid anchor STL with PicoGK?

Edit the anchor_zone1 CEM manifest (diameter, period, wallParam), then run the build verb through the SilkenCad CLI and measure porosity with `dotnet run -- verify`. Render lattices via `new Voxels(IImplicit, BBox3)` plus BoolIntersect, never the bounding-box intersect helper which aborts natively.

How do I add a new part or per-species SKU to the CEM pipeline?

Write a `cem/<name>.json` manifest with a `kind`, add a generator in `src/SilkenCad/`, wire the build/verify switch in Program.cs, and declare a provenance ground for every numeric field. New anchor SKUs also need a golden baseline via `verify --write-golden`.

Why does PicoGK crash with 'outside value 0' at fine voxel sizes?

A PicoGK runtime bug passes millimetres where a voxel count is expected, so below 1/3 mm the narrow band truncates to zero and the process aborts (0.33 mm dies, 0.34 mm survives). It is already reported upstream; use the Voxels constructor route instead.

Can PicoGK verify run in headless CI?

No. `Library.Go` needs a display and SIGSEGVs on headless runners, and PicoGK 2.2 ships no Linux runtime, so CI verify is best-effort only. Local `verify` on a desktop machine is the actual gate.

How do I measure lattice stiffness with the voxel-FE tract?

Run `fea <cem> --sweep` for a part or `fea --fit` to fit Gibson-Ashby C and n over a wallParam sweep, always with a convergence ladder since a single row is an upper bound. Use Release build config; Debug runs are roughly four times slower.

Why does a solid body render hollow through the SDF constructor?

A field left open at the bounding-box caps produces a non-watertight mesh, so the interior is lost during property calculation. Use ShapeKernel `voxConstruct` for filled solids, or ensure your SDF is closed on every side of the bounding box.