Full product launch kit spanning engineering, design, QA, product, marketing, and operations. Scaffolds a Next.js app with auth and analytics and a Platform tenant chart whose ModelGateway is the app's model path, alongside a design system, design tokens, test plan, acceptance criteria, PRD, campaign brief, and operational runbook.
Render it
# CLI
npx @nanohype/sdk render-composite product-launch --out ./my-app
# SDK
import { LocalSource, renderComposite } from "@nanohype/sdk";
const result = await renderComposite(source, "product-launch", variables);
# MCP — from an agent
get_composite({ name: "product-launch" })
What it draws together
Variables
Required
ProjectName string- Project name used across all templates Must be lowercase kebab-case.
ProductName string- Human-readable product name
Optional
LlmProvider string — defaults to gateway- LLM provider the packages deployed on the substrate call: gateway, the Platform ModelGateway, which holds the Bedrock role there, so none of them holds a model credential
IncludeMarketing bool — defaults to true- Include marketing campaign brief
Tenant string — defaults to ${ProjectName}- Owning team: the tenants-<team> namespace the Platform, BudgetPolicy and ModelGateway CRs are applied in, the Platform's spec.tenant, and the team label on the tenant chart's resources and telemetry
Image string — defaults to ${ProjectName}- Container image repository the tenant chart deploys, without a tag; each values-<env>.yaml pins one
AppMetric string — defaults to http- Prefix of the RED series the tenant chart's Grafana dashboard reads: <prefix>_requests_total, <prefix>_errors_total and <prefix>_request_duration_seconds. The default, http, is the prefix a ts-service emits them under; set it to the prefix the deployed service emits