cuyamaca-project-manifest

Create and manage Cuyamaca project manifests with hardware configuration.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/yuyanghu06/cuyamaca --skill cuyamaca-project-manifest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cuyamaca-project-manifest
Source: https://github.com/yuyanghu06/cuyamaca/tree/main/.claude/skills/cuyamaca-project-manifest
Command: npx skills add https://github.com/yuyanghu06/cuyamaca --skill cuyamaca-project-manifest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cuyamaca projects often require consistent manifests and hardware definitions; this skill provides a dedicated project system and manifest editor to reduce setup errors and accelerate configuration.

Core Features & Use Cases

  • Project CRUD: create, open, list, and delete projects with manifest.json and related files.
  • Manifest modeling: define board, serial port, baud rate, and component list in a structured manifest.
  • UI scaffolding: parts panel, component picker, and pin assignment editor for interactive hardware configuration.
  • Phase 3 workflows: supports building and editing the manifest, with references to manifest schema and hardware workflow.
  • Reference coverage: aligns with "phase 3", "manifest", "parts editor", "component picker" and "pin assignment" terminology.
  • Use Case: Create a new project named "my-robot" with board "arduino:avr:uno" and add two components with pins.

Quick Start

Run this skill to scaffold the project system and manifest editor for a new Cuyamaca project.

Frequently Asked Questions about cuyamaca-project-manifest

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

FAQPage Schema
How do I create a Tauri project manifest for hardware configuration?

To create a Tauri project manifest, define the board, serial port, baud rate, and component list in a structured manifest.json file. This provides a dedicated project system and manifest editor to reduce hardware setup errors.

What is a Cuyamaca project manifest and when do I need one?

A Cuyamaca project manifest is a structured file defining board type, serial port, baud rate, and component list. You need it when configuring consistent hardware definitions and reducing setup errors in Tauri projects.

How do I manage pin assignments and components in a Tauri hardware editor?

Manage pin assignments and components using the parts panel, component picker, and pin assignment editor. This UI scaffolding enables interactive hardware configuration within your Tauri frontend.

Can I use Rust and TypeScript together to scaffold a manifest editor?

Yes, you can use Rust and TypeScript together to scaffold a manifest editor. Rust defines backend models for Manifest, Project, and Component, while TypeScript handles frontend types and CRUD commands.

What's the best way to structure CRUD commands for project management in Tauri?

Structure CRUD commands for project management by creating Rust backend models that handle create, open, list, and delete operations. This persists manifest.json and related files while exposing a static component library to the frontend.

Why does my hardware definition need a specific component library in the frontend?

Your hardware definition needs a specific component library in the frontend to enable the parts editor UI and component picker. This static library allows interactive selection and pin assignment for accurate hardware configuration.