-
Notifications
You must be signed in to change notification settings - Fork 0
Project Structure
Lucas YourLastName edited this page Jul 17, 2026
·
3 revisions
The repository serves a dual role: the root is a runnable app; .SYSTEMX/
holds the full setup playbook.
.
├── index.html # Vite entry HTML
├── package.json # scripts + dependencies
├── package-lock.json
├── vite.config.ts # Vite + React + Tailwind + @ alias + chunking
├── tsconfig.json # strict TypeScript config
├── eslint.config.js # ESLint flat config
├── firebase.json # Hosting + rules + security headers
├── firestore.rules # Firestore security rules
├── firestore.indexes.json # Composite indexes
├── storage.rules # Storage security rules
├── .firebaserc # Firebase project alias (set your project id)
├── .env.example # VITE_FIREBASE_* client config template
├── public/
│ ├── robots.txt
│ └── favicon.svg
└── src/
├── main.tsx # entry + RouterProvider
├── router.tsx # route table
├── index.css # Tailwind entry
├── vite-env.d.ts # Vite types
├── config/
│ └── firebase.ts # Firebase client init (lazy/guarded)
├── components/
│ └── layout/
│ ├── Layout.tsx # Navbar + <Outlet/> + Footer
│ ├── Navbar.tsx
│ └── Footer.tsx
└── pages/
├── HomePage.tsx
├── ServicesPage.tsx
├── DocsPage.tsx
├── LoginPage.tsx
├── AboutPage.tsx
├── ContactPage.tsx
└── NotFoundPage.tsx # catch-all 404
.SYSTEMX/Template/
├── README.md # index + how-to for the template
├── WEBAPP-STACK-G1.0.md # master playbook: use cases + stack reference
├── setup.sh # interactive orchestrator (walks steps in order)
├── steps/
│ ├── 00-prerequisites.md # install + verify all CLIs
│ ├── 01-project-interview.md # capture project identity & choices
│ ├── 02-scaffold.md # TS + React + Vite + Tailwind skeleton
│ ├── 03-firebase-provision.md # create/convert Firebase project, web config
│ ├── 04-env-and-secrets.md # .env / secrets wiring
│ ├── 05-stripe.md # products, prices, webhooks (optional)
│ ├── 06-cloud-functions.md # Cloud Functions backend
│ ├── 07-security-rules.md # Firestore / Storage rules + tests
│ ├── 08-mcp-servers.md # Chrome DevTools MCP (optional)
│ ├── 09-ci-cd.md # GitHub Actions, branch protection, secrets
│ ├── 10-testing-qa.md # Vitest + Playwright + a11y/security gates
│ ├── 11-build-deploy.md # build, deploy, smoke test
│ └── 12-post-launch.md # monitoring, runbook, backups, cost guardrails
├── templates/
│ ├── env.template # client VITE_* variables
│ ├── secrets.env.template # server-side secrets (never commit)
│ └── interview.answers.template # captured answers from step 01 (git-ignored)
└── starter/ # a self-contained copy of the runnable app
When you run the full playbook, the project grows to include functions, tests, and scripts:
<repo-root>/
├── src/
│ ├── main.tsx / App.tsx
│ ├── config/ # firebase.ts, seo.ts, navigation.ts
│ ├── components/ hooks/ lib/ pages/ data/ types/ styles/
│ └── __tests__/
├── functions/
│ ├── package.json / tsconfig.json
│ └── src/ # index.ts, payments, email, scheduled jobs
├── tests/ # Playwright specs
├── scripts/ # deploy, security, seed helpers
├── vitest.config.ts / vitest.setup.ts
├── playwright.config.ts
└── .github/workflows/ci.yml
-
Path alias: import from
@/…(maps tosrc/…) — configured in bothtsconfig.jsonandvite.config.ts. -
Pages live in
src/pages/and are registered insrc/router.tsx. -
Layout wraps all routes via
createBrowserRouterwith a parentelement. -
Firebase is initialized once in
src/config/firebase.tsand guarded so the app boots without credentials.
SFWA-WTL-G1 · Standard Firebase Web App, Wayne Tech Lab Generation 1 · Provided by Wayne Tech Lab LLC under MIT · Use at your own risk · Subject to daily change · Repository
- Home
- Quick Start
- WTL Standard Setup Guide
- One-Line Install
- Platform Matrix
- Linux Setup
- Windows Setup
- Architecture and Stack
- Project Structure
- SYSTEMX Root and Folder Standard
- Setup Playbook
- Environment Variables
- Security
- Deployment
- Testing and QA
- MCP and Agents
- GitHub Authors and Contribution Notes
- SYSTEMX WEBPORTAL
- White Paper
- Executive Summary
- CISO Note From the Founder
- Wayne Tech Lab Purpose
- Security Overview
- Long-Term Warnings
- .ENV Solutions
- Menu Operations
- Setup and Deployment
- Start and End of Day
- SYSTEMX Sync and Controlled Updates
- Agent 0 and Subagents
- Agent 0 Operating Model
- How Subagents Work
- Starter Prompts and Smart Routing
- Third-Party Responsibility
- User Ingest and Production Setup
- FAQ