forgecad-design-spec

Create ForgeCAD design briefs, HLDs, and LLDs before writing parametric CAD code.

927|103|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/KoStard/forgecad-public-kit --skill forgecad-design-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forgecad-design-spec
Source: https://github.com/KoStard/forgecad-public-kit/tree/main/skills/forgecad-design-spec
Command: npx skills add https://github.com/KoStard/forgecad-public-kit --skill forgecad-design-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Jumping straight into CAD code from a vague request produces designs with hidden gaps, unjustified numbers, and wrong manufacturing assumptions. This Skill structures the pre-coding phase so every dimension has a rationale and every design gap is caught before implementation.

Core Features & Use Cases

  • Three-phase design pipeline: Intake converts fuzzy requests into engineering briefs and master prompts, HLD aligns on what to build with alternatives and a Decisions table, and LLD details how to build it with typed parameters and verification checklists.
  • Family-scoped intake profiles: Starter assumptions for grippers, fixtures, enclosures, furniture, chassis, and rideable vehicles, with honest manufacturing process selection instead of defaulting to 3D printing.
  • Git-based review loop: Design documents are committed and iterated through git diffs, making the diff the review artifact rather than chat conversation.
  • Use Case: A user asks for a robot gripper with no specifications. The Skill normalizes the request, invents a concrete operating story, picks duty and scale levers, writes an engineering brief and master prompt, then produces an HLD and LLD ready for the forgecad-build-model skill.

Quick Start

Use the forgecad-design-spec skill to turn my vague request for a bench-top PCB enclosure into an engineering brief and high-level design document.

Frequently Asked Questions about forgecad-design-spec

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

FAQPage Schema
How do I write a design spec before coding a parametric CAD model?

Start with the intake phase to normalize the request into an engineering brief, then write an HLD covering problem, approach, interfaces, alternatives, and concerns. Once the Decisions table is filled after user review, write an LLD with typed parameters, derived dimensions, and a verification checklist.

What is the difference between an HLD and an LLD in CAD design?

An HLD aligns on what to build: decision-driving dimensions, genuinely different alternatives, and a Decisions table filled only after user review. An LLD details how to build it: narrative description, typed parameter tables with units and rationale, constraints, and a mandatory verification checklist.

Does the design spec process assume 3D printing as the manufacturing method?

No. Manufacturing process is treated as a design decision derived from artifact family, load path, scale, and safety expectations. The Skill explicitly warns against defaulting to FDM and provides process stacks for metal, wood, sheet goods, machining, and hybrid approaches.

When should I skip the HLD and go straight to an LLD?

Simple single-body parts can skip the HLD and start directly at the LLD, or even go from HLD straight to code. The HLD is needed when the design could be wrong in approach and genuinely different alternatives exist.

How are design documents reviewed and iterated?

All HLDs and LLDs are committed to git and iterated through commits rather than chat. Feedback arrives as file edits or chat, the git diff serves as the review artifact, and the loop repeats until the Decisions table is filled and the user approves.