forgecad-prepare-prompt

Convert vague product requests into a ForgeCAD build brief and master modeling prompt.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill converts a fuzzy, manufacturing-incomplete request for a real physical artifact into a concrete, manufacture-realistic ForgeCAD build brief plus one master modeling prompt, reducing generic or unbuildable outcomes.

Core Features & Use Cases

  • Brief normalization & engineering framing: Restates the request in proper mechanism/artifact terms and defines what “done” means physically for a prototype build.
  • Manufacturing/process selection: Chooses an honest output posture (defaulting to manufacture-realistic prototype) and a manufacturing/process stack consistent with the artifact family and operating story.
  • Single master prompt generation: Produces one ready-to-copy prompt that includes assumptions, BOM/validation boundaries, variant-selection policy, and a file-organization requirement for multi-file ForgeCAD projects.

Quick Start

Use the forgecad-prepare-prompt skill when your user request sounds underspecified for a real mechanism or product prototype, and you need a single master prompt for the modeling pass.

Frequently Asked Questions about forgecad-prepare-prompt

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

FAQPage Schema
How do I convert a vague product idea into a manufacturing-ready CAD brief?

To convert a vague product idea into a manufacturing-ready CAD brief, use prompt engineering to normalize the request, define physical completion criteria, and select a manufacture-realistic process stack. This prevents unbuildable or generic toy solutions.

What is the best way to generate a master modeling prompt for multi-file mechanism prototypes?

Generating a master modeling prompt for multi-file mechanism prototypes involves defining an operating story, enforcing joint and assembly readiness, and setting BOM validation boundaries. This ensures parameterized modeling outputs are physically accurate and properly organized.

How do I ensure my mechanical prototype design accounts for BOM and validation boundaries?

To ensure mechanical prototype designs account for BOM and validation boundaries, restate the request in proper artifact terms and apply constraints for manufacturing honesty. This standardizes the prototype template and enforces variant selection policies.

Can I use a single prompt to handle parameterized modeling for different artifact families?

Yes, a single master modeling prompt can handle parameterized modeling across different artifact families by applying a standardized ForgeCAD prototype template. It normalizes underspecified requests into a concrete, build-ready brief regardless of the artifact type.

Why does my mechanism architecture design result in a generic toy solution?

Mechanism architecture designs result in generic toy solutions when key details are missing or lack an operating story. Applying manufacturing-aware design constraints and variant-selection policies during brief normalization prevents these unbuildable outcomes.