Define cross-layer feature architecture patterns for SpawnForge systems.
npx skills add https://github.com/Tristan578/project-forge --skill design-tristan578
Please help me install this Agent Skill. Skill: design Source: https://github.com/Tristan578/project-forge/tree/main/.claude/skills/design Command: npx skills add https://github.com/Tristan578/project-forge --skill design-tristan578
SpawnForge teams require a coherent, scalable blueprint to evaluate and plan cross-layer feature work across the Rust engine, React UI, and MCP command surfaces. This design skill provides a consistent framework to reason about architecture, constraints, and trade-offs so features integrate cleanly without violating the sandwich architecture.
Outline a high-level design spec for a new SpawnForge feature, mapping Rust components, bridge interfaces, and runtime implications.
High-intent search queries and answers about installing and using this skill.
To plan a scalable architecture across Rust, React, and MCP, use a design framework enforcing sandwich architecture with core/bridge isolation. This ensures UI actions route through JSON commands and engine updates flow through events to JS/React cleanly.
Sandwich architecture is a design pattern enforcing core and bridge isolation. It requires UI actions to route through JSON commands to the engine, with engine updates flowing back through events to JS/React, ensuring clear interaction boundaries.
Ensure undo support and AI parity by enforcing undoable actions, standardized MCP commands, chat handlers, and structured data. This provides the structured reasoning required for AI to process and reverse engine state changes accurately.
Yes, you can evaluate ECS components and render backends like WebGPU or WebGL2 using this framework. It ensures components, render backends, and export gating stay coherent across Rust, JS, and TypeScript interaction boundaries.
A limitation of bridge interfaces is the strict requirement for continuous spec validation and performance budgets. You must rigorously map interaction boundaries to prevent JSON command routing and event flow bottlenecks between Rust and React.
The best way to document feature architecture is outlining a high-level design spec that maps Rust components, bridge interfaces, and runtime implications. This codifies decision criteria, EntitySnapshot patterns, and feature-gating rules for review.
1molchuanVerify MCP, Codex, and Gemini endpoints and initialize RPI state.
JBonfimOrchestrate tmux-based Codex and Claude pairing to generate Compozy PRD, TechSpec, and tasks.
nolantaitDocument Bevy ECS Commands for spawning, modifying, and removing entities.
alsmadi99Design high-level software architectures and document decisions with Architecture Decision Records.
