create-schematic

Create PCB schematic plans with requirements.md and todo.md artifacts.

43|2|Updated Jan 25, 2024
One-click install
npx skills add https://github.com/glowingkitty/OpenMates --skill create-schematic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-schematic
Source: https://github.com/glowingkitty/OpenMates/tree/main/backend/apps/pcb_design/focus_modes/create-schematic
Command: npx skills add https://github.com/glowingkitty/OpenMates --skill create-schematic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn a PCB design idea into a coherent electrical schematic by asking for missing requirements and then guiding the generation of the schematic artifact.

Core Features & Use Cases

  • Requirements clarification: Collects and structures what’s needed by creating a requirements.md file based on user answers.
  • Step-by-step task tracking: For more complex builds, creates and maintains todo.md to track progress and remaining work.
  • Schematic creation guidance: Guides you through producing atopile code for a PCB schematic or alternatively explains how to create the schematic in KiCad.
  • Use Case: You describe the intended circuitry at a high level and want a correct schematic plan without knowing exactly how to translate it into an implementable schematic workflow.

Quick Start

Ask it to create a PCB schematic for your project by prompting for the requirements and generating atopile code, or explain the KiCad steps if you prefer manual editing.

Frequently Asked Questions about create-schematic

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

FAQPage Schema
How do I generate a PCB schematic from high-level circuit requirements?

To generate a PCB schematic from circuit requirements, you can use a structured planning approach that translates your high-level descriptions into actionable steps, producing either atopile code or manual KiCad build instructions.

What is the best way to plan electronics design before creating a schematic in KiCad?

The best way to plan electronics design for a KiCad schematic is to first clarify missing requirements and document them in a structured markdown file, ensuring the circuitry constraints are fully mapped before implementation.

Can I use atopile code instead of manually drawing a schematic in KiCad?

Yes, you can use atopile code as an alternative to manually drawing a schematic in KiCad, allowing you to generate the electrical connections programmatically based on a structured requirements plan.

How do you track progress for complex PCB design planning workflows?

To track progress for complex PCB design planning, you can create and maintain a markdown todo file that monitors step-by-step task completion and outlines remaining work for the schematic generation.

Do I need to provide detailed component specifications to start schematic creation?

No, you do not need to provide detailed component specifications upfront to start schematic creation; the workflow will actively ask clarifying questions to gather missing requirements and structure your design planning artifacts.