Offer And Pricing
CoveredPackages, price points, first paid unit, margins, and the smallest sellable promise.
TBD
Style / Component Library
Component Library
One surface for the reusable UI layer. Start with the standard primitives, then graduate to domain components only when the page job needs them.
19
standard primitives
11
component families
0
new local primitives
/style
audit first route
AI-native business plan
The operating-model artifacts this business idea needs.
PrettyMint is not just a pitch. A venture folder should show the idea, the economics, the go-to-market path, the AI leverage, the delivery loop, and the proof gates needed to run it. Missing artifacts stay visible until they are authored.
Artifacts
6
Covered
3
Needed
0
Cash Flow Model
ArtifactRevenue, delivery cost, burn, runway, scenarios, break-even, and kill thresholds.
Dedicated planning artifact exists.
Open cash flow model
Go-To-Market Plan
ArtifactIdeal customer profile, wedge, channels, acquisition loop, 90-day plan, and conversion proof.
Dedicated planning artifact exists.
Open go-to-market plan
AI-Native Strategy
ArtifactWhere AI creates leverage, what remains human judgment, and what data compounds.
Dedicated planning artifact exists.
Open ai-native strategy
Lead Magnet
ArtifactThe diagnostic or proof asset that turns interest into a named prospect.
Dedicated planning artifact exists.
Open lead magnet
Validation Checklist
ArtifactFounder readiness, pain evidence, demand signals, risk gates, and next experiment.
Dedicated planning artifact exists.
Open validation checklist
Principles Audit
ArtifactBusiness principles, constraints, leverage, distribution, and what not to optimize.
Dedicated planning artifact exists.
Open principles audit
Operating Loop
CoveredHow the business runs week to week: learn, sell, deliver, measure, improve, teach.
Run one Loyalty Audit on a friendly creator. Track actual hours vs value delivered.
Proof And Kill Signals
CoveredMetrics, evidence state, proof gaps, reactivation conditions, and kill criteria.
No pilot creator yet
Planning standard: cash flow model, go-to-market plan, AI strategy, offer/pricing, lead magnet, validation checklist, principles audit, operating loop, and proof/kill signals. Business instruments hold the reusable templates; venture folders hold the business-specific plan.
Playbook backing
The pitch explains this business. The playbook explains the operating system.
FLOW source trail: venture navigation, venture traction instruments, and the leverage-model notes all point to the same standard. Compare the bet, prove the economics, redesign the workflow, map the apps and tech stack, then route the Stackmates overlap into buildable capability.
Business model
How to choose and run the business model after the workflow is redesigned.
Cash flow
Model revenue, burn, runway, break-even, scenarios, and kill thresholds.
Go-to-market
Define the ideal customer profile, wedge, channels, acquisition loop, and 90-day conversion plan.
Operations
How to run the business: process, owners, platforms, gauges, and cadence.
Tech stack
Architecture and stack choices, including what Stackmates has built or must build.
Apps
What app surfaces and software categories the business model needs.
AI work map
Separate human judgment, agent work, data loops, and automation leverage.
Instruments
Use the reusable blueprint library; keep venture folders business-specific.
Use Order
Import the standard layer before making page-local UI
The style page is proof and inventory, not a pattern mine. Production pages should compose primitives, then domain components, then page-private components only when reuse is not real yet.
- NeedPage structureStart withSection, Container, SectionHeaderRuleUse before local section wrappers.
- NeedActionStart withButton, EyebrowLink, InlineLink, CopyablePromptRuleOne action pattern per job.
- NeedGroupingStart withCard, Rhythm, Divider, TightFiveRuleTokenized spacing and bounded density.
- NeedMeaningStart withBadge, Chip, Pill, Callout, StatRuleStatus and labels with semantic color roles.
- NeedDataStart withDataListTable, ScoreBar, HealthBarRuleMobile-first tables and measured progress.
| Need | Start with | Rule |
|---|---|---|
| Page structure | Section, Container, SectionHeader | Use before local section wrappers. |
| Action | Button, EyebrowLink, InlineLink, CopyablePrompt | One action pattern per job. |
| Grouping | Card, Rhythm, Divider, TightFive | Tokenized spacing and bounded density. |
| Meaning | Badge, Chip, Pill, Callout, Stat | Status and labels with semantic color roles. |
| Data | DataListTable, ScoreBar, HealthBar | Mobile-first tables and measured progress. |
Design Decisions
The house style is instrument-grade, not generic-clean
Dreamineering surfaces should feel like charts, gauges, ledgers, and field notes: distinctive enough to remember, restrained enough to trust, and legible before anything else.
- GateContextDecisionPurpose and reader job firstWhat to checkState the user, page job, and memorable differentiator before styling.
- GateTypographyDecisionDisplay voice plus readable bodyWhat to checkHeadlines can carry character; body copy stays 16px+, plain, and scannable.
- GateColorDecisionSemantic accents onlyWhat to checkBrand, status, risk, and action are distinct roles. Color never does the whole job alone.
- GateLayoutDecisionStable density and no collisionsWhat to checkUse grids, overflow guards, and min/max widths so long text cannot overlap.
- GateCopyDecisionSpecific nouns and verbsWhat to checkNo generic CTA or AI-startup phrasing. Labels name the destination or object.
| Gate | Decision | What to check |
|---|---|---|
| Context | Purpose and reader job first | State the user, page job, and memorable differentiator before styling. |
| Typography | Display voice plus readable body | Headlines can carry character; body copy stays 16px+, plain, and scannable. |
| Color | Semantic accents only | Brand, status, risk, and action are distinct roles. Color never does the whole job alone. |
| Layout | Stable density and no collisions | Use grids, overflow guards, and min/max widths so long text cannot overlap. |
| Copy | Specific nouns and verbs | No generic CTA or AI-startup phrasing. Labels name the destination or object. |
Live Specimens
Tokenized primitives rendered side by side
These are the components agents should copy by import. If a page duplicates one of these with raw JSX, fix the page before adding another component.
standard
Buttons and links
Inline action copy uses InlineLink and structural CTAs use EyebrowLink →.
standard
Labels and status
brand chipsuccesswarningdangerinfo badgeneutral badgepainjobsignal
Words are design
Labels must name the state. Color is reinforcement, not the only signal.
standard
Cards, rhythm, and density
Claim
Reader
Action
Proof
Next
bounded density
Use Rhythm and TightFive when a section starts to sprawl.
domain
Metrics and progress
4.8:1
Minimum contrast sample
AA body
7/10
Clarity
4
Coverage72% / 100%
domain
Checklist and principle rows
Mobile reflow checked
No horizontal scroll at 375px.
Rendered contrast measured
Compute ratios before shipping.
5
Can a tired reader scan the state in three seconds?
Use this row pattern when a principle needs score, question, and evidence.
domain
Commissioning state
01
Token audit3/5
L4: 2
L3: 3
L2: 5
L1: 6
24 totalL0L1L2L3L4
domain
Feature matrix controls
2 features
| ID | Feature | State | Demand score |
|---|---|---|---|
| CAP-01 | Evidence intake | L3 | 3 |
| MEA-02 | Reality scorecard | L1 | 1 |
| Category | Traditional SaaS | AI Agents | RaaS Providers |
|---|---|---|---|
| Capture | Forms, CRM | Research agent | Evidence API |
| Measure | BI dashboard | Metric critic | Score ledger |
domain
Image artifacts
Image wrappers are evidence, not decoration
Use these when the picture carries a named model, source board, or domain artifact. Alt text names the artifact; captions add source or interpretation.
domain
Venture and conviction atoms
HIGHMEDIUMLOWVALIDATEDPROJECTED
72%
Full Inventory
Every live component family
This inventory makes component reuse visible. A component listed as domain or specialist is reusable, but it is not the default primitive layer.
standard
Design System
Primitive layer. Import these first for page structure, type, links, labels, cards, stats, tables, and prompts.
Design decision
The primitive layer stays quiet and exact: semantic colors, 8px-or-less radius on cards, measured spacing, and plain labels before ornament.
Audit gate: Every primitive must pass contrast, 44px action targets, keyboard focus, mobile reflow, and a copy label that names the object.
SectionContainerSectionHeaderButtonCardChipBadgePillCalloutProseEyebrowEyebrowLinkInlineLinkRhythmTightFiveStatDividerDataListTableCopyablePrompt
domain
Data Display
Small evidence widgets used by business-plan and checklist pages.
Design decision
Data widgets are compact instruments, not decorative cards. Numbers lead, labels explain the unit, and status must not depend on color alone.
Audit gate: No text below 12px for labels, no unlabelled progress state, and every metric needs a visible denominator or context line.
StatCardCheckItemStageHeaderScoreBarPrincipleRow
domain
Feature Matrix
Commissioning and health displays for matrix-style product surfaces.
Design decision
Matrix components prioritize comparison speed: repeated row structure, predictable filters, visible counts, and compact status labels.
Audit gate: Filters need result counts, reset/empty behavior when interactive, and labels that describe the filtered object.
CategorySummaryFeatureTableFilterBarHealthBarLevelBadgeMarketLandscape
domain
Venture
Venture scorecards, metric kits, pricing, positioning, and operating surfaces.
Design decision
Venture components use strong evidence hierarchy: proposition first, proof state second, action third. Sticky navigation must survive long venture names.
Audit gate: No overlapping nav text at 375px or desktop widths; proof/status copy must state reality, dream, projected, validated, or risk.
VentureHeroVentureDreamCardVentureOperatingKitProposalNavigationConvictionBadgeStatusBadgeScoreRingMetricBarScoreCardCriticalMetricsPricingCardsPositioningMapCompetitorTableKillCriteriaScenarioTableTightFiveStripCollapsibleSection
domain
Journey
AI-transformation journey shells, subpage panels, shared charts, tables, and plan instruments.
Design decision
Journey components are work instruments for repeated scanning. They choose density on purpose and keep tables/charts horizontally resilient.
Audit gate: Tables need mobile alternatives or horizontal overflow; timeline/chart labels must remain readable without hover.
JourneyLandingInstrumentPageLensSubPageSectionPanelAITransformationOnePagePlanBreakevenChartCostInputsTableDecisionsBlockEvidenceCardGanttTimelineKillSwitchListMetricStripPipelineDiagramScenarioBarChartScenarioCashflowTableSiblingPagerStageRoadmapTableTightFiveCardTransformationPlanWeekByWeekTableWorkflowInventoryTable
domain
Landing Page
Homepage sections composed from primitives; use as page sections, not new primitives.
Design decision
Landing sections carry story rhythm. They can be more expressive than primitives, but headlines still answer what the reader gets.
Audit gate: Five-second scan must reveal what Dreamineering is, who it helps, and the next action without reading body copy.
HomeHeroHomeBeliefHomeCtaHomeDreamEngineeringBridgeHomeFaqHomeProofHomeThreeDoorsHomeWhyNow
specialist
Navigation
Route and menu instruments. First Mate is the intentional navigation cockpit.
Design decision
Navigation is an opinionated route spine, not an atlas dump. Labels choose the next useful course and preserve public/private boundaries.
Audit gate: Desktop and mobile routes must match, active states must be visible, and labels must not wrap into collisions.
LoopNavFirstMateNavGlossFlyoutNavbarItemMatterFlyoutNavbarItem
specialist
Prompt Deck
Interactive deck runtime with its own scoped token namespace and DNA gate.
Design decision
The prompt deck is allowed a stronger DNA than the house system because it is a distinct interaction artifact with its own runtime lint.
Audit gate: Prompt-deck tokens stay in the pd-* namespace and scoreGenericTest must pass before reuse.
PromptDeckPromptDeckShowcaseSlideSlideDepthDesignDnaPreviewDeckArrowsDeckHeroDeckHintsDeckNavDeckPillsFaceToggleMantraRevealSlideStageSpeechControlSpeechButton
domain
Industry
Domain analysis diagrams for value chains, competitive dynamics, KPI change, and opportunity mapping.
Design decision
Industry diagrams expose structure and tradeoffs. They should feel like analysis instruments, not generic illustration panels.
Audit gate: Diagram labels must be readable on mobile, color must carry a semantic role, and every axis/legend needs text backup.
ValueChainAnalysisCompetitiveDynamicsFiveIndustryLayersIndustryMatrixKPITransformationNavigationConvergenceMapOpportunityMatrixPillarCoverageVVFLDiagram
domain
Image Components
Reusable visual artifacts and bitmap wrappers used by MDX and story pages.
Design decision
Images are treated as evidence artifacts. The wrapper must preserve alt text, captions, source links, and mobile containment instead of acting like decorative stock media.
Audit gate: Every exported image wrapper needs meaningful alt text, a bounded max width, lazy loading, and a caption when the image needs source or context.
BaseImageDreamineeringLogoDreamineeringEvolutionLogoLoopCompassValidatedVirtuousFeedbackLoopTheHeroesJourneyEvolutionSalesPitchProcessImprovementInnerOuterVoiceTightFiveRugbyFlowOfProgressProgressJourneyDigitalMyceliumPlatformBusinessFactoryStackmatesStackmatesDreamEngineeringBusinessFactoryMeetingTemplateAlgorithmIDDTradeBusinessFirstPrinciplesAlignedPrioritiesPricingAlgorithmBerleytrails
specialist
Other Instruments
Special-purpose canvases, wiki projections, shell helpers, and one-off shared instruments.
Design decision
Specialist instruments stay shared only while they have multiple consumers or a clear cross-page contract; otherwise they move page-local.
Audit gate: If a specialist component has no live imports, delete it or co-locate it with its single page before closing the audit.
ActionsAndConsequencesFunctionCatalogBrowserExcalidrawDiagramThinkingLoopCalloutWikiProjectionPlaybookPageContextDreamNamerHorizonBannerVesselNavConvictionBarBusinessFlowDiagramIntentionAttentionHingeLoopIntentionRibbon
Audit Path
This page is the design system self-test
Run rendered audit against /style before trusting changes to primitives, tokens, or component recipes.
Build
eng-run-frontend
Owns component and style-page implementation under token, semantic HTML, and design-system constraints.
Orchestrate
ux-orchestrate-page
Owns the UX blend gate for material src/pages work: route, research, create, audit, improve, dogfood, and delegate.
Verify
ux-audit-interface
Owns rendered verification: rendering, visual, responsive, and interaction checks.
Measure
ux-audit-legibility
Computes contrast, type-size, color-role, mobile reflow, and hierarchy gates.
Put this to work
Audit this component library
Design curatorCopy this prompt. Paste into Claude, ChatGPT, or any AI assistant. The page context is already loaded — send it and get analysis tailored to your role.
Run the rendered design audit against /style. Check contrast, type size, focus visibility, touch targets, mobile reflow at 375px, and whether page code imports the standard design-system primitives before local UI.