-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
Both. The repo root is a runnable React + Firebase app (Step 02 of the
playbook). The .SYSTEMX/Template/ directory is the full ordered system that
takes you all the way to production. Use the fast start when you just want a
running app; use the playbook when you need provisioning, payments, Functions,
local verification, and monitoring.
src/config/firebase.ts only calls initializeApp when an API key + project ID
are present. Until then, auth, db, and storage are null and the app boots
normally (with a dev-only console warning). This lets you develop UI before
provisioning Firebase. See Environment Variables.
No. A Firebase web API key identifies your project; it does not grant privileged access. It's protected by Security Rules + App Check, not by secrecy. It's expected to ship in the client bundle. Real secrets (payment provider secret keys, webhook secrets, email API keys) belong on the server. See Security.
gh repo create my-app --template WayneTechLab/SFWA-WTL-TEMPLATE --private --clone…or click “Use this template” on the repo page. See Quick Start.
npm run build
bash .SYSTEMX/scripts/deploy.sh hosting --dry-run
bash .SYSTEMX/scripts/deploy.sh hosting --project your-firebase-project-idFull details in Deployment.
No — those are optional modules toggled during the Interview (Step 01). The baseline app has none of them; enable only what your project needs.
Yes — that's a first-class mode. Start with .SYSTEMX, fill the intake packet
under .SYSTEMX/Unified-Setup-Process/intake/, then re-inject
06-AI-REINJECTION-PROMPT.md. Use .SYSTEMX/Template/WEBAPP-STACK-G1.0.md
and the steps/ files for detailed gates. See Setup Playbook.
The SYSTEMX local tooling baseline is Node 24 LTS. A selected Firebase Cloud Functions module may use its own supported runtime; do not infer that module runtime from the local workstation baseline.
Add a page component under src/pages/, then register it in src/router.tsx. All
routes render inside the shared Layout (Navbar + Footer). See
Project Structure.
Generation 1.0. Bump the generation for a breaking change to the step order or baseline stack (e.g. swapping the build tool); patch individual step files freely.
.SYSTEMX/Template/WEBAPP-STACK-G1.0.md
is the master playbook. This wiki summarizes and links into it.
S.F.W.A. Template · .SYSTEMX Forever WebApp · WayneTechLab.com · Repo · Update Log
Start
- Home
- Quick Start
- One-Line Install
- WTL Standard Setup Guide
- Setup Playbook
- User Ingest & Production Setup
- Production Kit
- Brand Guide Kit
- WTL Site Shell G1
Platform setup
SYSTEMX
- The SYSTEMX Standard
- SYSTEMX Executive Summary
- SYSTEMX Security Overview
- SYSTEMX Menu Operations
- SYSTEMX Setup and Deployment
- SYSTEMX Webportal
- SYSTEMX LAN Builder
- SYSTEMX LAN Operations Manual
- SYSTEMX LAN API Reference
- Unified Login and Admin Operations
- SYSTEMX LAN Webflow Master Plan
- SYSTEMX Logs and Evidence
- SYSTEMX Root and Folder Standard
- SYSTEMX Environment Solutions
- SYSTEMX Operating Rhythm
- SYSTEMX Sync and Controlled Updates
- SYSTEMX Long-Term Warnings
- SYSTEMX Third-Party Responsibility
Agents and tooling
- Agent Mesh & Tooling Standard
- MCP and Agents
- Agent 0 Operating Model
- Agent 0 and Subagents
- How Subagents Work
- Starter Prompts and Smart Routing
Reference
- Architecture & Stack
- Project Structure
- Environment Variables
- Security
- Deployment
- Testing & QA
- GitHub Authors & Contribution Notes
- Update Log
- FAQ