agentleFS
tangency-labstangency-labs/solidcraft/skills/solidcraft-layers/SKILL.md

solidcraft-layers

Skill17k starsChanged 20 days agoApache-2.0View on GitHub

Use when deciding whether code goes in SolidCraft or in solidcore (the vendored kernel in solidcore/), and in which solidcore crate: geometry, a modelling workflow, kernel work, or a review comment about the layer split.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 61 mentionsNov 2026: 31 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the tangency-labs/solidcraft repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about tangency-labs/solidcraft

The biggest 5 of 92 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 92

Talked about on GitHub, YouTube, Bluesky and the web (92 times).

On GitHub · 50

45 more on GitHub

On YouTube · 25

20 more on YouTube

On Bluesky · 9

4 more on Bluesky

On the web · 8

3 more on the web

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before writing STEP, meshing, surface intersection, tangent chains or frames, look for solidcore's: a second implementation is flagged.

    line 17
  2. Very specific:

    Follow solidcore/AGENTS.md and the reference doc for the area (solidcore/docs/).

    line 24

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

Where code goes: SolidCraft or solidcore

The authority is solidcore/docs/layers.md; this is its short form. Every job lives in exactly one layer, and two implementations of one job are a bug.

Decide

  1. Does it compute geometry? Anything computed from coordinates: a point, vector, length, angle, curvature, curve or surface, a solve, an intersection, a fit, a mesh, a STEP parse. Then it is a kernel primitive in solidcore/crates/solidcore, with its own tests. Dot and cross products, normalising, square roots or trigonometry on coordinates count, however small.
  2. Is it a workflow recipe of kernel calls? It picks entities, parameters and defaults, sequences kernel calls, compares what they return with tolerances and reports. Then it is solidcore/crates/solidcore-ops. Ops computes no geometric quantity of its own: when it needs one the kernel lacks, add a kernel primitive and call it.
  3. Is it state, selection, commands, settings, history or UI? Then it is SolidCraft (crates/, apps/), which computes no geometry.

What SolidCraft may use

  • solidcore-ops (modelling), solidcore-tess (display meshes, polylines) and solidcore-record (geometry as data). CI enforces this seam through cargo xtask layers (#13498): solidcore's public API is listed in xtask/solidcore-public.txt, and the remaining direct uses in xtask/solidcore-seam.txt, a list that only shrinks. Within those crates, xtask/solidcore-paths.txt holds each crate's count of paths into solidcore internals (#15031): a count may not go up, and a PR that removes paths lowers its line (cargo xtask layers --paths <crate> lists them). The same command keeps solidcore/ self-contained: no manifest under it may use a path that leaves solidcore/ or depend on a solidcraft-* crate, and CI's "SolidCore builds on its own" job runs cargo check --workspace --all-targets --locked on an export of solidcore/ alone.
  • Before writing STEP, meshing, surface intersection, tangent chains or frames, look for solidcore's: a second implementation is flagged.

Lists that only shrink

  • xtask/mesh-decisions.txt: model decisions made from a mesh (cargo xtask mesh-decisions).
  • solidcore/plan/panic-sites.tsv: panic-prone calls in solidcore (SolidCore checks in CI).

Working in solidcore/

  • Follow solidcore/AGENTS.md and the reference doc for the area (solidcore/docs/). A change there needs a code owner's review (.github/CODEOWNERS) and runs SolidCore checks (its tests, goldens, kernel rig, clippy, fmt, panic sites) in .github/workflows/ci.yml.
  • New kernel cases go in solidcore/crates/solidcore/tests/kernel_cases/, never in SolidCraft (cargo xtask lists).
  • Kernel work goes here: CONTRIBUTING.md, "Kernel work goes in solidcore/". Kernel PRs target main; big multi-step work goes as stacked PRs into main.
  • Issues and claims for solidcore are in this repository, like any other change (skills/solidcraft-contributing/SKILL.md): the vendored tree is mirrored to tangency-labs/solidcore by .github/workflows/solidcore-mirror.yml, so pull requests are not opened there.

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.