
Leathercad Ai
- 1 installs
- Updated June 12, 2026
- ahzs645/leathercad
leathercad-ai is a Claude Code skill that generates, validates, and repairs LeatherCad AI Builder JSON for leather templates using leather-native entities.
About
leathercad-ai generates, refines, validates, and repairs LeatherCad AI Builder JSON for leather templates. It treats the AI Builder JSON as the source contract and returns only valid JSON, preferring leather-native entities like stitch_path, pattern_piece, seam_allowance, seam_connection, and hardware_marker over raw geometry. It uses stable snake_case IDs, generates in millimeters, and resolves preflight errors such as unclosed boundaries and seam length mismatches before adding detail. For refinements it emits the full updated JSON document.
- Generates and repairs LeatherCad AI Builder JSON for leather templates
- Uses leather-native entities: pattern pieces, stitch paths, seam allowances
- Enforces millimeter geometry and preflight validation rules
Leathercad Ai by the numbers
- 1 all-time installs (skills.sh)
- Ranked #1,200 of 1,335 Generative Media skills by installs in the Skillselion catalog
- Data as of Jul 7, 2026 (Skillselion catalog sync)
leathercad-ai capabilities & compatibility
- Capabilities
- json generation · template generation · geometry validation
- Use cases
- ui design · web design
- Pricing
- Free
What leathercad-ai says it does
Use when generating, refining, validating, or repairing LeatherCad AI Builder JSON for leather templates
Treat AI Builder JSON as the source contract. Return only valid JSON, never markdown.
Generate in millimeters. Positive x moves right; positive y moves down.
npx skills add https://github.com/ahzs645/leathercad --skill leathercad-aiAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| Last updated | June 12, 2026 |
| Repository | ahzs645/leathercad ↗ |
What it does
Generate, validate, and repair LeatherCad AI Builder JSON for leather patterns using leather-native entities.
Who is it for?
Producing or repairing LeatherCad leather-pattern JSON with pattern pieces, stitch paths, and seam connections.
Skip if: Returning markdown or diffs - the docs require only full valid JSON output.
When should I use this skill?
You need to author, refine, validate, or repair the LeatherCad AI Builder JSON that defines pattern pieces, stitch paths, and hardware for a leather template.
What you get
A valid LeatherCad AI Builder JSON document using leather-native entities that passes preflight checks.
- valid LeatherCad AI Builder JSON document for a leather template
By the numbers
- 5 leather-native entity types (stitch_path, pattern_piece, seam_allowance, seam_connection, hardware_marker)
- 7 preflight checks listed
Files
LeatherCad AI Builder
Workflow
1. Treat AI Builder JSON as the source contract. Return only valid JSON, never markdown. 2. Prefer leather-native entities over raw geometry when intent is known:
stitch_pathfor stitch lines plus generated holes.pattern_piecefor closed cut boundaries.seam_allowancefor piece offsets.seam_connectionfor edge mating intent.hardware_markerfor snaps, rivets, buckles, and custom fittings.
3. Use stable snake_case IDs. LeatherCad exposes compiled objects as @leather[kind:id] refs, so preserve existing IDs during refinements. 4. Generate in millimeters. Positive x moves right; positive y moves down. 5. Keep closed cut boundaries simple and inspectable. Rectangles are the safest boundary primitive; multi-entity boundaries should form a clean closed loop. 6. For refinements, output the full updated JSON document, not a diff. 7. Address preflight errors before adding decorative detail:
- Closed pattern-piece boundaries.
- Seam edge length mismatch.
- Stitch paths with too few holes.
- Fold radius versus material thickness.
- Missing cut-line geometry for export.
Entity Patterns
Use a closed cut entity first, then bind it into a piece:
{
"id": "outer_shell_piece",
"type": "pattern_piece",
"layer_id": "shell",
"boundary_entity_id": "outer_shell_outline",
"name": "Outer Shell",
"quantity": 1
}Use stitch_path instead of manually placing holes:
{
"id": "bottom_stitching",
"type": "stitch_path",
"layer_id": "shell",
"path_type": "line",
"start": { "x": -90, "y": 38 },
"end": { "x": 90, "y": 38 },
"pitch_mm": 4,
"hole_type": "slit",
"render_shape": "diamond",
"width_mm": 1.2,
"height_mm": 0.55,
"tilt_deg": 35
}Use pattern-piece entity IDs for seams and allowances; LeatherCad maps them to native piece IDs during compile.
Related skills
FAQ
What output format does it produce?
Only valid JSON, never markdown; for refinements it outputs the full updated JSON document, not a diff.
What units and coordinates does it use?
Millimeters, with positive x moving right and positive y moving down.