How do I install the Developer Workflow skill?

Run npx skillmds@latest add kevoyuan/developer-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Developer Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Developer Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Developer Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Developer Workflow?

Kevoyuan (@kevoyuan) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Developer Workflow by kevoyuan — Agent Skill

Name: Developer Workflow
Author: Kevoyuan

Developer Workflow

Work safely on the AgentSCAD codebase, especially skill/docs changes around the CAD pipeline. Use when editing AgentSCAD skills, docs, resolver guidance, or orchestration-adjacent notes while preserving runtime contracts and avoiding unrelated code changes.

Kevoyuan 666fd07 2.7 KB Updated Sep 17, 2026

File contents

AgentSCAD Developer Workflow

Use this workflow for codebase work that touches AgentSCAD skills or documentation.

First Read

Inspect git status --short.
Read the relevant skill or doc before editing.
If runtime behavior matters, read the route or helper that owns the contract, but do not edit it unless explicitly requested.

Protected Contracts

Preserve these exactly unless the user explicitly requests a coordinated runtime change:

SSE data frames: data: ${JSON.stringify(payload)}\n\n.
State strings: NEW, SCAD_GENERATED, RENDERED, VALIDATED, DELIVERED, DEBUGGING, REPAIRING, VALIDATION_FAILED, GEOMETRY_FAILED, RENDER_FAILED, HUMAN_REVIEW, CANCELLED.
Step strings: starting, generating_llm, generating_mock, scad_generated, scad_applied, rendering, render_failed, rendered, validating, validation_failed, validated, delivering, delivered.
Artifact paths: /artifacts/{jobId}/model.scad, /artifacts/{jobId}/model.stl, /artifacts/{jobId}/preview.png, optional /artifacts/{jobId}/report.
Generation JSON: summary, parameters, scad_source.
Parameter fields: key, label, kind, unit, value, min, max, step, source, editable, description, group.
Validation fields: rule_id, rule_name, level, passed, is_critical, message.
Provider fallback: MiMo when configured, then ZAI SDK. Product generation fails visibly when no model succeeds; legacy templates are available only through the explicit demo-only switch.
Rendering and validation: OpenSCAD CLI renders artifacts; Python/trimesh validates STL with mock fallback.
Keep deterministic behavior in TypeScript/Python tools, not prompts.

Skill Writing

Keep SKILL.md concise and task-oriented.
Include YAML frontmatter with name and description.
Put trigger guidance in the description.
Prefer imperative workflow instructions over broad background.
Do not duplicate large source snippets when a short contract summary is enough.

Editing Rules

Do not revert other people's edits.
Keep changes scoped to requested files.
Avoid touching src/, package files, Prisma files, or existing CAD skills unless explicitly authorized.
Use deterministic tests and wrapper tools instead of guessing about runtime behavior.
After edits, verify with git diff --stat and inspect the changed files.

---name: developer-workflowdescription: Work safely on the AgentSCAD codebase, especially skill/docs changes around the CAD pipeline. Use when editing AgentSCAD skills, docs, resolver guidance, or orchestration-adjacent notes while preserving runtime contracts and avoiding unrelated code changes.---# AgentSCAD Developer WorkflowUse this workflow for codebase work that touches AgentSCAD skills or documentation.## First Read1. Inspect `git status --short`.2. Read the relevant skill or doc before editing.3. If runtime behavior matters, read the route or helper that owns the contract, but do not edit it unless explicitly requested.## Protected ContractsPreserve these exactly unless the user explicitly requests a coordinated runtime change:- SSE data frames: `data: ${JSON.stringify(payload)}\n\n`.- State strings: `NEW`, `SCAD_GENERATED`, `RENDERED`, `VALIDATED`, `DELIVERED`, `DEBUGGING`, `REPAIRING`, `VALIDATION_FAILED`, `GEOMETRY_FAILED`, `RENDER_FAILED`, `HUMAN_REVIEW`, `CANCELLED`.- Step strings: `starting`, `generating_llm`, `generating_mock`, `scad_generated`, `scad_applied`, `rendering`, `render_failed`, `rendered`, `validating`, `validation_failed`, `validated`, `delivering`, `delivered`.- Artifact paths: `/artifacts/{jobId}/model.scad`, `/artifacts/{jobId}/model.stl`, `/artifacts/{jobId}/preview.png`, optional `/artifacts/{jobId}/report`.- Generation JSON: `summary`, `parameters`, `scad_source`.- Parameter fields: `key`, `label`, `kind`, `unit`, `value`, `min`, `max`, `step`, `source`, `editable`, `description`, `group`.- Validation fields: `rule_id`, `rule_name`, `level`, `passed`, `is_critical`, `message`.- Provider fallback: MiMo when configured, then ZAI SDK. Product generation fails visibly when no model succeeds; legacy templates are available only through the explicit demo-only switch.- Rendering and validation: OpenSCAD CLI renders artifacts; Python/trimesh validates STL with mock fallback.- Keep deterministic behavior in TypeScript/Python tools, not prompts.## Skill Writing- Keep `SKILL.md` concise and task-oriented.- Include YAML frontmatter with `name` and `description`.- Put trigger guidance in the description.- Prefer imperative workflow instructions over broad background.- Do not duplicate large source snippets when a short contract summary is enough.## Editing Rules- Do not revert other people's edits.- Keep changes scoped to requested files.- Avoid touching `src/`, package files, Prisma files, or existing CAD skills unless explicitly authorized.- Use deterministic tests and wrapper tools instead of guessing about runtime behavior.- After edits, verify with `git diff --stat` and inspect the changed files.

Frequently asked questions