scaffold-server-system-wiring

Name: scaffold-server-system-wiring
Availability: InStock
Author: buchananwill

Enforce agent roles and review gates for server-subtree orchestration.

2|Updated Mar 17, 2026

Search Tags:#typescript #scaffold #orchestration #docker #review #server #roles

Ready to run

npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill scaffold-server-system-wiring

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scaffold-server-system-wiring
Source: https://github.com/buchananwill/ue-claude-scaffold/tree/main/skills/scaffold-server-system-wiring
Command: npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill scaffold-server-system-wiring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The scaffold server wiring skill formalizes and enforces governance for server-subtree work in ue-claude-scaffold, ensuring roles, track boundaries, and mandatory review gates are consistently applied.

Core Features & Use Cases

Defines explicit agent roles (implementer, safety-reviewer, reviewer, decomp-reviewer, style-sweep) and ownership for server/** tasks.
Enforces strict track scope so changes outside the server subtree are blocked and clearly flagged.
Provides a reproducible protocol for decomposing work, reviewing changes, and executing terminal style sweeps in a Docker-based scaffold.

Quick Start

Describe your server-scaffold wiring plan and assign agents to the scaffold-server roles, then initiate the orchestration workflow for the server subtree.

Frequently Asked Questions about scaffold-server-system-wiring

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

FAQPage Schema

How do I enforce agent roles and review gates for TypeScript server orchestration in Docker?▼

Server orchestration in Docker enforces agent roles and task boundaries by assigning explicit ownership for implementer, safety-reviewer, reviewer, decomp-reviewer, and style-sweep. It defines mandatory review gates to coordinate TypeScript server-subtree work consistently.

What is the best way to scope server-subtree changes and block modifications outside the server directory?▼

Scoping server-subtree changes requires enforcing strict track boundaries that block and clearly flag any modifications outside the server/** directory. This ensures orchestration remains isolated to the designated server subtree throughout the workflow.

How do I set up a reproducible protocol for decomposing server tasks and executing style sweeps?▼

A reproducible protocol for server task decomposition defines sequential stages for work breakdown, change review, and terminal style sweeps. It assigns specific agent roles to each stage within a Docker-based scaffold to maintain execution consistency.

Can I use this orchestration approach to enforce SQL-injection safety reviews and API contract checks?▼

Server orchestration specifies functional requirements including SQL-injection safety, API contracts, and TypeScript plugin work. The safety-reviewer and reviewer roles are mandated to enforce these specific checks before changes pass the designated review gates.

Why do I need defined agent roles like decomp-reviewer and style-sweep for scaffold server wiring?▼

Defined agent roles like decomp-reviewer and style-sweep are needed for scaffold server wiring to separate task decomposition validation from code style enforcement. This separation prevents scope creep and ensures consistent governance across server-subtree changes.