agentleFS
KevoyuanKevoyuan/AgentSCAD/skills/scad-planning/SKILL.md

scad-planning

Skill26 starsChanged 5 months agoMITView on GitHub

Choose a CAD modeling approach from the user's request and the persisted evidence contract before writing OpenSCAD.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before writing code, decide how to construct the requested object.

    line 14
  2. Distinctive:

    Keep requested features and acceptance criteria visible in the resulting geometry.

    line 20
  3. Distinctive:

    If a requirement cannot be represented confidently, preserve the uncertainty in a comment or editable parameter instead of silently …

    line 21

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

SCAD Planning

The supplied generation plan is an evidence checkpoint, not an approved geometry design. Its features, dimensions, explicit constraints, assumptions, and acceptance criteria describe the request. Empty modeling and design fields mean no approach has been chosen yet.

Before writing code, decide how to construct the requested object. Keep that reasoning internal and return the artifact in the coding skill's required format.

  1. Preserve explicit user constraints and required features. Treat suggested family parameters as editable defaults, not facts supplied by the user.
  2. Decide whether the request calls for one printable body, multiple parts, an assembly, or a display model. Do not assume FDM printability or a single connected body for every request.
  3. Choose a coordinate system, construction sequence, openings, mating clearances, and library modules appropriate to the object. Use the available library guidance; do not invent includes.
  4. Apply printable feature and wall guidance only when the intended use supports printing. Expose uncertain dimensions as editable parameters rather than presenting them as verified product measurements.
  5. Keep requested features and acceptance criteria visible in the resulting geometry. Never describe a feature as validated merely because code was generated.
  6. If a requirement cannot be represented confidently, preserve the uncertainty in a comment or editable parameter instead of silently choosing a materially different artifact.
  7. For a functional, independently manufacturable, or removable assembly, account for each required part instance, local frame, mating connection, specified motion, clearance, and assembly or removal path. Do not replace required instances with representative blocks or merge separate mating bodies. Display-only simplification applies only to optional detail and must preserve explicitly requested features.

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.