quantabridges-solutions/qbs-dev-kit

Manage AWS infrastructure for a QBS SaaS project using Terraform. Covers first-time setup, adding resources (Lambda, CloudFront, RDS, ElastiCache/Redis, S3), deployments, and troubleshooting. Use when the user mentions Terraform, AWS, Lambda, CloudFront, RDS, Redis, ElastiCache, infra setup, or deployment infrastructure.

Add new features to a .NET API using CQRS/MediatR — commands, queries, handlers, entities, validators, and EF migrations. Use when the user asks to add an endpoint, create a new feature, add a new entity, or implement CQRS in a .NET project.

Add new features to a .NET API using traditional services architecture — entities, DTOs, service interface + implementation, controller, and EF migrations. Use when the user asks to add an endpoint, create a new feature, add a new entity, or build a service in a .NET project.

Build and submit QBS Expo apps with EAS for iOS and Android, including eas.json profiles, GitHub Actions, and required secrets. Use when the user asks for EAS, App Store, Play Store, Android build, iOS submit, or mobile release.

Review a PR or local diff against QBS SaaS conventions — OTP-only auth, OrganizationId filters, thin controllers, EF CLI migrations, single API client, no secrets. Use when the user asks for a code review, PR review, review my changes, or a pre-merge checklist (not a full security audit — use saas-security-review for that).

Add production observability to a QBS .NET/AWS service using OpenTelemetry, structured logs, traces, metrics, correlation IDs, deployment metadata, CloudWatch-compatible export and agent audit events. Use when the user asks for logging, observability, tracing, metrics, CloudWatch, OpenTelemetry, correlation IDs, alarms, or production diagnostics.

QBS spec-driven development for brownfield features: constitution, spec, clarify, plan, checklist, tasks, analyze, implement, converge, and optional GitHub issues. Use when the user wants SDD, spec-kit style workflow, feature specs, plan before code, artifact consistency, or closing spec-to-code gaps. Artifacts live under specs/NNN-slug/ and docs/qbs-constitution.md.

Add or extend tests for a QBS SaaS feature — xUnit + WebApplicationFactory with OrganizationId isolation on the API, and Playwright (or Vitest) on the React app. Use when the user asks for tests, unit tests, integration tests, tenant isolation tests, Playwright, or coverage for a new endpoint or page.

Add new screens or features to a React Native Expo app. Covers screen creation, navigation, API integration, and UI patterns. Use when the user asks to add a screen, mobile page, React Native component, Expo screen, or mobile feature.

Add new pages, features, or API integrations to a React (Vite + TypeScript + Tailwind) web app. Use when the user asks to add a page, React component, web UI feature, form, table, or dashboard section.

Run a security review on a new feature, endpoint, or entity in a QBS SaaS project. Covers auth, tenant isolation, data encryption, input validation, secrets, logging, and infrastructure hardening. Use when the user asks for a security review, security checklist, "is this secure", or when completing a new feature that handles sensitive data.

Scaffold a governed QBS SaaS project (API + React + Expo + Terraform + agentic delivery controls). Ask ONE question (which components?) unless the user already specified them, then run scripts/scaffold.sh, apply the agentic foundation, and run language toolchains with no further questions. Defaults: .NET 8, React+Vite, Expo, Postgres, eu-west-1, Traditional Services. Use when the user says new project, scaffold, bootstrap, or start a new app.