mp-netcore

Add modules and commands to the mp_Net-Core Slave project.

Updated May 1, 2026
One-click install
npx skills add https://github.com/itdogwowo/mp_Net-Core --skill mp-netcore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mp-netcore
Source: https://github.com/itdogwowo/mp_Net-Core/tree/main/.trae/skills/mp-netcore
Command: npx skills add https://github.com/itdogwowo/mp_Net-Core --skill mp-netcore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

mp_Net-Core Slave 開發技能 provides a complete specification for adding feature modules under mp_Net-Core/slave, including project structure, core design principles, and standards for commands, actions, tasks, and config management.

Core Features & Use Cases

It codifies the repository structure (app, boot, action, schema, tasks), the SysBus three-tier storage model, and dual-core task division to streamline development, testing, and maintenance across hardware and software boundaries.

Quick Start

Read the mp_Net-Core slave project structure and follow the 4-step process to add a new command or module according to the guidelines in this skill.

Frequently Asked Questions about mp-netcore

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

FAQPage Schema
How do I add a new command to an embedded dual-core project?

To add a new command in an embedded dual-core project, follow the standardized 4-step process to wire actions, define protocol schemas, and register modules within the fixed file structure.

What is the SysBus three-tier storage model in dual-core environments?

The SysBus three-tier storage model is a core design principle that codifies data management across hardware and software boundaries to streamline dual-core task division and maintenance.

How do I structure background tasks and action modules for hardware control?

Structure hardware control modules by enforcing a fixed repository layout with separate directories for app, boot, action, schema, and tasks, ensuring standardized registry wiring.

Do I need specific frontmatter and config management practices for embedded modules?

Yes, extending hardware control modules requires strict frontmatter requirements and standardized config management practices to maintain consistency across the dual-core slave project.

What is the best way to manage protocol schemas in a dual-core slave architecture?

The best way to manage protocol schemas is to place them in the designated schema directory and follow the standardized action wiring guidelines to ensure correct hardware boundary communication.