Forgecad Project Sync Agent Skill

Manage hosted ForgeCAD project sync from the CLI: init, clone, pull, push, file operations, members, publishing, and shares.

539 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

912

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/ForgeCAD/forgecad-public-kit --skill forgecad-project-sync

The instruction itself

1 sections, as written by the author

Project Sync

forgecad.io is the hosted ForgeCAD platform; a project is a local folder linked to the server by forgecad.json. The full command inventory (project, file, member, share, token commands and flags) lives in forgecad project --help and the forgecad skill's docs/CLI.md — do not relearn it here.

One studio process. Run a single long-running forgecad studio <folder> [<folder> ...] naming every active project folder. The user opens the one printed localhost port once; create and edit files only under those folders so the browser live-updates. Never spawn extra servers per project.
studio vs dev. forgecad studio is for users and agents; forgecad dev is only for developing ForgeCAD itself.
Login only for hosted commands. forgecad login before any project/publish command; local work (run, render, studio) needs no auth.
init creates, push syncs. project init "Name" creates the remote project, writes forgecad.json, and pushes existing local files. push only syncs an already-initialized project. clone <slug> is the inverse: remote → new local folder.
Sync is content-hash based. status/push/pull compare file content hashes — no timestamps, no git; a file is "modified" purely by content difference. Loop: edit → project status → project push.
Sync vs single-file ops. Use status/pull/push for normal sync; use project file <read|save|delete|...> only for one hosted-file operation without a full push/pull cycle.
Project context required. All project file * and publish commands must run inside a folder containing forgecad.json.
Shares are live references. A published model always shows the current project file, never a snapshot — pushing changes silently updates published models. publish prints the share URL.
Non-interactive runs. Pass --force to skip confirmation prompts (push, pull, delete) in agent automation.

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take forgecad/forgecad-project-sync from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.