dev-setup

Coordinate setup checks and verification gates for ManuAI development workflows.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/J4Joshua/manuaI --skill dev-setup-j4joshua
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-setup
Source: https://github.com/J4Joshua/manuaI/tree/main/.agents/skills/dev-setup
Command: npx skills add https://github.com/J4Joshua/manuaI --skill dev-setup-j4joshua

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent development practices by guiding ManuAI contributors through setup checks, verification gates, and safe code change workflows.

Core Features & Use Cases

  • Development Health Checks: Verify local services and required AI components before starting work.
  • Change Verification Workflow: Match code changes to the correct validation commands for voice, agents, screens, and retrieval systems.
  • Engineering Conventions: Maintain shared contracts for paths, imports, screen state, chunk schemas, and offline operation requirements.

Quick Start

Use the dev-setup skill to prepare a ManuAI development session and identify the correct verification steps before modifying code.

Frequently Asked Questions about dev-setup

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

FAQPage Schema
How do I verify offline AI pipeline components before starting local development?

To verify offline AI pipeline components, you need to run development health checks that validate local services and required AI components before starting work. This prevents inconsistent practices by ensuring your environment matches project conventions.

What is the correct workflow for matching code changes to validation commands?

The correct workflow for matching code changes to validation commands involves using a change verification process that maps specific modifications for voice, agents, screens, and retrieval systems to their corresponding validation gates.

How do I maintain shared engineering contracts for chunk schemas and screen state?

To maintain shared engineering contracts for chunk schemas and screen state, follow established engineering conventions that enforce repository-specific procedures for paths, imports, and offline operation requirements during feature modifications.

Does the ManuAI development workflow require adherence to specific repository conventions?

Yes, the ManuAI development workflow requires strict adherence to project conventions, validation gates, shared contracts, and repository-specific development procedures to coordinate verification and change management practices safely.

What is the best way to prepare a ManuAI development session for feature modifications?

The best way to prepare a ManuAI development session for feature modifications is to execute setup checks that verify local services and identify the correct verification steps before modifying any code.