Ops Command Lite

Ops Command Lite is a public portfolio mockup for a small-business operations dashboard. It presents the first screen of an internal command center: KPIs, revenue and lead movement, risk signals, pipeline status, module readiness, and a clear access boundary.

The project is intentionally lightweight. It uses synthetic TypeScript data, ships without a backend, and is designed to be understandable from a clean GitHub clone in a few minutes.

Preview

The app opens directly into the dashboard. There is no marketing landing page, login wall, private data, hosted database, API key, AI provider, or tracking script.

Visual direction:

• Accessible soft-neumorphic interface.
• Dense operational layout, not a generic SaaS landing page.
• High-contrast text and restrained shadows.
• Responsive desktop and mobile dashboard structure.

What It Shows

• Executive KPI cards for revenue, leads, conversion, overdue tasks, and active clients.
• A compact revenue and lead-flow chart for the active operating period.
• Risk items that affect follow-up, revenue timing, and client health.
• Sales pipeline value by stage and owner.
• Module readiness for future product areas.
• Access-boundary panel that makes the mock/demo scope explicit.

Stack

• Next.js App Router.
• React Server Components.
• TypeScript.
• Tailwind CSS.
• Vitest.
• Optional SQLite reference schema in sqlite/schema.sql.

Data And Runtime Scope

Runtime dashboard data lives in lib/demo/ops-snapshot.ts. The SQLite schema is a reference artifact only; it is not connected to the app at runtime.

This repository should stay portfolio-safe:

• Use synthetic data only.
• Do not commit .env.local.
• Do not add private customer data.
• Do not add real cloud credentials, service-role keys, API keys, or tokens.
• Keep client components limited to real interaction needs.

Local Setup

Requirements:

• Node.js 20 or newer.
• npm.

Install dependencies:

npm install

Run the development server:

npm run dev

Open http://localhost:3000. The root route redirects to /dashboard.

Quality Checks

Run the same checks used for the GitHub workflow:

npm run lint
npm run typecheck
npm test
npm run build

The production build prerenders /dashboard as static content.

Project Map

app/                         Next.js App Router pages and global CSS
components/layout/           Dashboard shell and navigation
components/dashboard/        KPI and operations dashboard components
lib/demo/ops-snapshot.ts     Synthetic portfolio data
lib/formatters.ts            Number, currency, and percent formatting helpers
sqlite/schema.sql            Optional local schema reference
docs/                        Product, architecture, data, and implementation docs
tests/                       Vitest unit tests

Documentation

• Documentation Index
• Product Spec
• Architecture
• Data Model
• Permissions Mock
• Executive Brief Mock
• Implementation Plan

Deployment Notes

The app is ready for a static-friendly Vercel deployment. No environment variables are required for the public demo. The checked-in .env.example is only a placeholder for a public app URL.

License

No open-source license has been selected yet. Add a license before positioning the repository as open source.