builder

Translate feature specs into Rust, UI, MCP, and test code.

5|1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Tristan578/project-forge --skill builder-tristan578
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: builder
Source: https://github.com/Tristan578/project-forge/tree/main/.claude/skills/builder
Command: npx skills add https://github.com/Tristan578/project-forge --skill builder-tristan578

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Builder translates specs into working code across multiple domains (Rust engine, frontend, MCP commands, and testing) by guiding implementation decisions that align with product vision.

Core Features & Use Cases

  • Domain-aware spec-to-code translation that maps requirements to concrete artifacts across layers
  • Coordinated orchestration of Rust, UI, MCP, and tests to deliver end-to-end functionality
  • Validation through linting, tests, and consistency checks to ensure quality and undo/redo readiness
  • Use Case: When asked to "build" or "implement" a feature, it selects the relevant domain skills and crafts a cohesive implementation plan

Quick Start

Provide a feature spec in specs/ and let the Builder translate it into Rust, frontend, MCP commands, and tests.

Frequently Asked Questions about builder

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

FAQPage Schema
How do I translate feature specs into working code across multiple domains?

Spec-to-code translation maps feature requirements into concrete artifacts by coordinating Rust engine, frontend, MCP commands, and testing layers. It guides implementation decisions to deliver cohesive, end-to-end functionality aligned with product vision.

What's the best way to build features that span both frontend and Rust backend?

Cross-domain orchestration coordinates implementation across Rust, UI, MCP, and tests to deliver end-to-end functionality. It selects relevant domain skills and crafts a cohesive implementation plan that touches all necessary layers.

How do I automate validation and testing when implementing new features?

Automated validation runs linting, tests, and consistency checks to ensure code quality during implementation. This process verifies that translated specs produce working features while maintaining undo/redo readiness across all domains.

Do I need to provide specs in a specific format to automate code generation?

Feature specs should be provided in the specs/ directory to automate code generation. The system reads these specifications and translates them into Rust, frontend, MCP commands, and tests without requiring additional manual configuration.

Can I fix bugs across multiple layers using spec-to-code automation?

Spec-to-code automation handles bug fixes and feature implementations across engine, UI, and testing domains. It maps requirements to concrete artifacts and validates fixes through linting and tests to ensure cross-layer consistency.

What are the limitations of multi-domain spec-to-code translation?

Multi-domain spec-to-code translation is designed for implementing features, fixing bugs, and fulfilling build requests across SpawnForge layers. It requires clear feature specs and focuses on coordinated orchestration rather than standalone single-domain tasks.