pmos-fullstack-builder

Generate React and Ant Design fullstack packages from PMOS requirements.

Updated May 9, 2026
One-click install
npx skills add https://github.com/RhyTsui/PMOS --skill pmos-fullstack-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmos-fullstack-builder
Source: https://github.com/RhyTsui/PMOS/tree/main/skills/pmos-fullstack-builder
Command: npx skills add https://github.com/RhyTsui/PMOS --skill pmos-fullstack-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the gap between governed PMOS requirements/design outputs and production-ready implementation by generating the real frontend and backend hookup scaffolding needed to complete delivery.

Core Features & Use Cases

  • Frontend mother-repo scaffolding & CRUD package generation: Creates runnable React (Ant Design / Ant Design X) feature packages aligned to the UI/schema contract.
  • API client wiring with mock fallback: Integrates explicit API boundaries through client/config seams so implementation can progress safely even when backend details are incomplete.
  • Delivery-closure readiness: Prepares backend hookup seams and includes GitLab CI/delivery closure with verification readiness before calling the work “complete.”

What problem does it solve?

This skill ensures implementation isn’t “just docs” by producing runnable code and verification evidence aligned to PMOS governance.

Quick Start

Tell the AI to run the PMOS fullstack builder to implement the required frontend packages and backend integration seam for the current governed requirement and UI/schema contract, then close the build only after the strongest available verification checks pass.

Frequently Asked Questions about pmos-fullstack-builder

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

FAQPage Schema
How do I generate runnable React and Ant Design code from governed requirement specs?

To generate runnable React and Ant Design code from governed requirement specs, use a fullstack builder to convert PMOS design outputs into frontend mother-repo scaffolding and CRUD feature packages. This produces implementation packages with stable scripts and verification evidence.

How do I wire API client integration with mock fallback for frontend development?

Wiring API client integration with mock fallback requires configuring explicit API boundary seams through client/config integration. This allows your frontend implementation to progress safely with mock data even when backend API details remain incomplete.

What is the best way to scaffold a fullstack CRUD application aligned to a UI schema contract?

Scaffolding a fullstack CRUD application aligned to a UI schema contract involves generating runnable React feature packages using Ant Design and Ant Design X. This approach ensures the frontend implementation matches the governed schema contract exactly.

Can I use GitLab CI for delivery closure verification before marking a requirement as solved?

Yes, you can use GitLab CI for delivery closure verification by preparing backend hookup seams and running verification commands. This ensures explicit unresolved blockers are identified and the strongest available checks pass before reporting a requirement solved status.

Does fullstack scaffolding work when backend API endpoints are not fully defined?

Fullstack scaffolding works when backend API endpoints are incomplete by integrating explicit API boundaries with mock fallback. This allows the React and Ant Design frontend implementation to proceed independently while maintaining safe client/config seams.

Why does my requirement solved status fail PMOS delivery rules without runnable verification code?

Your requirement solved status fails PMOS delivery rules without runnable verification code because governed delivery requires stable scripts, explicit verification commands, and backend hookup seams. Producing only documentation without runnable code violates PMOS governance constraints.