b2c-app-builder 0.221.39

package/agents/skills/b2c-design-onboarding/references/workflow.experience.onboarding-system.onb-09-evidence-join.md

@@ -0,0 +1,37 @@
+# Onboarding ONB-09: evidence join
+
+<!-- Generated task skill. Edit catalog owners, then run render:task-skills. -->
+
+Canonical workflow: `workflow.experience.onboarding-system.onb-09-evidence-join`. This is a reference contract, not an executable plan. Managed eligibility, ordering, authority, and acceptance remain with the installed business runtime.
+
+## Method
+
+Join the current guidance, competitor reviews, Onbo Hub atlas, internal guidance audit, provider/policy landscape, and motion research into explicit, evidence-and-complaint-traceable decisions (adopt/adapt/test/reject/investigate), each naming the affected screen, control, architecture, or product work, its analytics implication, its test, and remaining risk; also run the seven-principle activation audit against the joined evidence. Write the join to product/onboarding/graph/ONB-09-evidence-join.md. Write the research Foundation contract from reference.experience.onboarding-foundations, pinning applied knowledge, resolved observations, and the decisions each changes. check:onboarding-evidence-onb-09 rejects a stub packet, and ONB-10 through ONB-14 all branch from this decision set.
+
+## Inputs and outputs
+
+For advisory work, use the evidence supplied and return findings. Do not create runtime state, prerequisite artifacts, or a whole business to satisfy these managed-workspace paths. Missing evidence remains explicit.
+
+Managed inputs: `product/onboarding/graph/ONB-03-current-guidance.md`, `product/onboarding/graph/ONB-04-competitor-reviews.md`, `product/onboarding/graph/ONB-05-onbo-hub-atlas.md`, `product/onboarding/graph/ONB-06-internal-guidance-audit.md`, `product/onboarding/graph/ONB-07-provider-policy-landscape.md`, `product/onboarding/graph/ONB-08-motion-research.md`
+
+Consult when relevant: None declared.
+
+Managed outputs: `product/onboarding/graph/ONB-09-evidence-join.md`
+
+## Verification and authority
+
+Declared checks: `check:onboarding-evidence-onb-09`, `check:onboarding-foundations-research`
+
+Additional founder decisions: None specific to this workflow; host permission boundaries still apply.
+
+Run applicable checks with the installed builder's documented target arguments. Report unavailable or unrun checks honestly. A review report, generated file, or successful command does not by itself establish accepted runtime or provider evidence. Do not mark reducer state by hand.
+
+## Select supporting knowledge
+
+Load only the sections needed for the current task. Broad load-when wording does not override accepted scope or an explicit provider binding. Provider procedures are current only at the corresponding selected-provider action. Stop and report an unresolved required source rather than treating its title as delivered guidance.
+
+| Reference | Load when | Stable identity |
+| --- | --- | --- |
+| [Analytics And Attribution](../../../../knowledge/data/analytics-attribution.md) | before onboarding, paywalls, funnels, store CTAs, referrals, lifecycle email, UGC/Fastlane campaigns, paid UA, or any builder prompt that names events; before PostHog setup, dashboards, deep links, feature flags, experiments, or session replay | `reference.data.analytics-attribution` |
+| [Onboarding Conversion](../../../../knowledge/experience/onboarding-conversion.md) | before onboarding quizzes, welcome/splash screens, personalization, attribution questions, demo videos, App Review popups, paywall timing, closing offers, trials, or first-session activation | `reference.experience.onboarding-conversion` |
+| [Research-backed onboarding with identity and measurement](../../../../knowledge/experience/onboarding-foundations.md) | Before onboarding research acceptance, identity and analytics decisions, design lock, prototype acceptance or final onboarding verification. | `reference.experience.onboarding-foundations` |

package/agents/skills/b2c-design-onboarding/references/workflow.experience.onboarding-system.onb-10-first-value-activation.md

@@ -0,0 +1,35 @@
+# Onboarding ONB-10: first value and activation
+
+<!-- Generated task skill. Edit catalog owners, then run render:task-skills. -->
+
+Canonical workflow: `workflow.experience.onboarding-system.onb-10-first-value-activation`. This is a reference contract, not an executable plan. Managed eligibility, ordering, authority, and acceptance remain with the installed business runtime.
+
+## Method
+
+Separately define first value rendered (the real, personalized result the user sees), first value engaged (the meaningful action they take on it), activation (the retention hypothesis and its derived condition), habit signal, monetization, review eligibility, and onboarding completion — first value must be real, actionable, persistent, recoverable, and visible inside the populated normal product experience, not a canned demo. Write the milestones to product/onboarding/graph/ONB-10-first-value-activation.md; check:onboarding-evidence-onb-10 rejects a stub packet, and ONB-15's architecture decision depends on these being real, distinct milestones.
+
+## Inputs and outputs
+
+For advisory work, use the evidence supplied and return findings. Do not create runtime state, prerequisite artifacts, or a whole business to satisfy these managed-workspace paths. Missing evidence remains explicit.
+
+Managed inputs: `product/onboarding/graph/ONB-09-evidence-join.md`
+
+Consult when relevant: None declared.
+
+Managed outputs: `product/onboarding/graph/ONB-10-first-value-activation.md`
+
+## Verification and authority
+
+Declared checks: `check:onboarding-evidence-onb-10`
+
+Additional founder decisions: None specific to this workflow; host permission boundaries still apply.
+
+Run applicable checks with the installed builder's documented target arguments. Report unavailable or unrun checks honestly. A review report, generated file, or successful command does not by itself establish accepted runtime or provider evidence. Do not mark reducer state by hand.
+
+## Select supporting knowledge
+
+Load only the sections needed for the current task. Broad load-when wording does not override accepted scope or an explicit provider binding. Provider procedures are current only at the corresponding selected-provider action. Stop and report an unresolved required source rather than treating its title as delivered guidance.
+
+| Reference | Load when | Stable identity |
+| --- | --- | --- |
+| [Onboarding Conversion](../../../../knowledge/experience/onboarding-conversion.md) | before onboarding quizzes, welcome/splash screens, personalization, attribution questions, demo videos, App Review popups, paywall timing, closing offers, trials, or first-session activation | `reference.experience.onboarding-conversion` |

package/agents/skills/b2c-design-onboarding/references/workflow.experience.onboarding-system.onb-11-effort-question-audit.md

@@ -0,0 +1,35 @@
+# Onboarding ONB-11: effort and question audit
+
+<!-- Generated task skill. Edit catalog owners, then run render:task-skills. -->
+
+Canonical workflow: `workflow.experience.onboarding-system.onb-11-effort-question-audit`. This is a reference contract, not an executable plan. Managed eligibility, ordering, authority, and acceptance remain with the installed business runtime.
+
+## Method
+
+Audit every step for effort placed before value is shown (class each passive/low/moderate/high/sensitive/permission/account/financial, and decide keep/defer/infer/delete) and every question for whether it is required, changes downstream logic, and produces visible personalization proof the user actually sees — including the total interruption budget across the flow. Write the audit to product/onboarding/graph/ONB-11-effort-question-audit.md; check:onboarding-evidence-onb-11 rejects a stub packet.
+
+## Inputs and outputs
+
+For advisory work, use the evidence supplied and return findings. Do not create runtime state, prerequisite artifacts, or a whole business to satisfy these managed-workspace paths. Missing evidence remains explicit.
+
+Managed inputs: `product/onboarding/graph/ONB-09-evidence-join.md`
+
+Consult when relevant: None declared.
+
+Managed outputs: `product/onboarding/graph/ONB-11-effort-question-audit.md`
+
+## Verification and authority
+
+Declared checks: `check:onboarding-evidence-onb-11`
+
+Additional founder decisions: None specific to this workflow; host permission boundaries still apply.
+
+Run applicable checks with the installed builder's documented target arguments. Report unavailable or unrun checks honestly. A review report, generated file, or successful command does not by itself establish accepted runtime or provider evidence. Do not mark reducer state by hand.
+
+## Select supporting knowledge
+
+Load only the sections needed for the current task. Broad load-when wording does not override accepted scope or an explicit provider binding. Provider procedures are current only at the corresponding selected-provider action. Stop and report an unresolved required source rather than treating its title as delivered guidance.
+
+| Reference | Load when | Stable identity |
+| --- | --- | --- |
+| [Onboarding Conversion](../../../../knowledge/experience/onboarding-conversion.md) | before onboarding quizzes, welcome/splash screens, personalization, attribution questions, demo videos, App Review popups, paywall timing, closing offers, trials, or first-session activation | `reference.experience.onboarding-conversion` |

package/agents/skills/b2c-design-onboarding/references/workflow.experience.onboarding-system.onb-12-state-identity-contract.md

@@ -0,0 +1,38 @@
+# Onboarding ONB-12: state and identity contract
+
+<!-- Generated task skill. Edit catalog owners, then run render:task-skills. -->
+
+Canonical workflow: `workflow.experience.onboarding-system.onb-12-state-identity-contract`. This is a reference contract, not an executable plan. Managed eligibility, ordering, authority, and acceptance remain with the installed business runtime.
+
+## Method
+
+Define the canonical state model keeping identity, onboarding journey, profile completeness, activation, entitlement, experiment assignment/exposure, review eligibility, permission/consent, and lifecycle state as distinct machines, each with its authoritative owner, persistence/event contract, and idempotency/retry/recovery behavior — grounded in the current RevenueCat entitlement and identity model from ONB-07. Write the contract to product/onboarding/graph/ONB-12-state-identity-contract.md. Write its Foundation contract with explicit auth timing, verified-session rules, anonymous continuity, secure credential storage, account isolation, logout, deletion, and restore. Auth success never grants an entitlement. check:onboarding-evidence-onb-12 rejects a stub packet.
+
+## Inputs and outputs
+
+For advisory work, use the evidence supplied and return findings. Do not create runtime state, prerequisite artifacts, or a whole business to satisfy these managed-workspace paths. Missing evidence remains explicit.
+
+Managed inputs: `product/onboarding/graph/ONB-09-evidence-join.md`
+
+Consult when relevant: None declared.
+
+Managed outputs: `product/onboarding/graph/ONB-12-state-identity-contract.md`
+
+## Verification and authority
+
+Declared checks: `check:onboarding-evidence-onb-12`, `check:onboarding-foundations-identity`
+
+Additional founder decisions: None specific to this workflow; host permission boundaries still apply.
+
+Run applicable checks with the installed builder's documented target arguments. Report unavailable or unrun checks honestly. A review report, generated file, or successful command does not by itself establish accepted runtime or provider evidence. Do not mark reducer state by hand.
+
+## Select supporting knowledge
+
+Load only the sections needed for the current task. Broad load-when wording does not override accepted scope or an explicit provider binding. Provider procedures are current only at the corresponding selected-provider action. Stop and report an unresolved required source rather than treating its title as delivered guidance.
+
+| Reference | Load when | Stable identity |
+| --- | --- | --- |
+| [Analytics And Attribution](../../../../knowledge/data/analytics-attribution.md) | before onboarding, paywalls, funnels, store CTAs, referrals, lifecycle email, UGC/Fastlane campaigns, paid UA, or any builder prompt that names events; before PostHog setup, dashboards, deep links, feature flags, experiments, or session replay | `reference.data.analytics-attribution` |
+| [Onboarding Conversion](../../../../knowledge/experience/onboarding-conversion.md) | before onboarding quizzes, welcome/splash screens, personalization, attribution questions, demo videos, App Review popups, paywall timing, closing offers, trials, or first-session activation | `reference.experience.onboarding-conversion` |
+| [Research-backed onboarding with identity and measurement](../../../../knowledge/experience/onboarding-foundations.md) | Before onboarding research acceptance, identity and analytics decisions, design lock, prototype acceptance or final onboarding verification. | `reference.experience.onboarding-foundations` |
+| [RevenueCat Agent Tooling](../../../../knowledge/money/revenuecat-agent-tooling.md) | when the selected RevenueCat operation needs official agent setup, identity, instrumentation, or verification procedures | `reference.money.revenuecat-agent-tooling` |

package/agents/skills/b2c-design-onboarding/references/workflow.experience.onboarding-system.onb-13-analytics-experiments.md

@@ -0,0 +1,38 @@
+# Onboarding ONB-13: analytics and experiments
+
+<!-- Generated task skill. Edit catalog owners, then run render:task-skills. -->
+
+Canonical workflow: `workflow.experience.onboarding-system.onb-13-analytics-experiments`. This is a reference contract, not an executable plan. Managed eligibility, ordering, authority, and acceptance remain with the installed business runtime.
+
+## Method
+
+Define a machine-readable, typed analytics schema — every event carrying event_id, version, time, source, platform, journey, identity, session, correlation, acquisition, consent, and deduplication semantics — naming the authoritative emitter (client, backend-confirmed, or provider-confirmed) per event, plus experiment assignment, exposure, and expected event sequences for the happy path and each major failure/edge case. Write the contract to product/onboarding/graph/ONB-13-analytics-experiments.md. Write the measurement Foundation contract: consent-aware initialization before the first event, typed event/schema and implementation/test paths, first/last-touch attribution, deep links and unknown joins, identity stitching, deduplication, exposure rules and negative scenarios. check:onboarding-evidence-onb-13 rejects a stub packet, and analytics failure must never block first value.
+
+## Inputs and outputs
+
+For advisory work, use the evidence supplied and return findings. Do not create runtime state, prerequisite artifacts, or a whole business to satisfy these managed-workspace paths. Missing evidence remains explicit.
+
+Managed inputs: `product/onboarding/graph/ONB-09-evidence-join.md`, `product/onboarding/graph/ONB-10-first-value-activation.md`, `product/onboarding/graph/ONB-12-state-identity-contract.md`, `product/onboarding/graph/ONB-14-trust-lifecycle-policy.md`, `analytics/ANALYTICS.md`
+
+Consult when relevant: None declared.
+
+Managed outputs: `product/onboarding/graph/ONB-13-analytics-experiments.md`
+
+## Verification and authority
+
+Declared checks: `check:onboarding-evidence-onb-13`, `check:onboarding-foundations-measurement`
+
+Additional founder decisions: None specific to this workflow; host permission boundaries still apply.
+
+Run applicable checks with the installed builder's documented target arguments. Report unavailable or unrun checks honestly. A review report, generated file, or successful command does not by itself establish accepted runtime or provider evidence. Do not mark reducer state by hand.
+
+## Select supporting knowledge
+
+Load only the sections needed for the current task. Broad load-when wording does not override accepted scope or an explicit provider binding. Provider procedures are current only at the corresponding selected-provider action. Stop and report an unresolved required source rather than treating its title as delivered guidance.
+
+| Reference | Load when | Stable identity |
+| --- | --- | --- |
+| [Analytics And Attribution](../../../../knowledge/data/analytics-attribution.md) | before onboarding, paywalls, funnels, store CTAs, referrals, lifecycle email, UGC/Fastlane campaigns, paid UA, or any builder prompt that names events; before PostHog setup, dashboards, deep links, feature flags, experiments, or session replay | `reference.data.analytics-attribution` |
+| [PostHog Agent Tooling](../../../../knowledge/data/posthog-agent-tooling.md) | when the selected PostHog operation needs official agent setup, identity, instrumentation, or verification procedures | `reference.data.posthog-agent-tooling` |
+| [Onboarding Conversion](../../../../knowledge/experience/onboarding-conversion.md) | before onboarding quizzes, welcome/splash screens, personalization, attribution questions, demo videos, App Review popups, paywall timing, closing offers, trials, or first-session activation | `reference.experience.onboarding-conversion` |
+| [Research-backed onboarding with identity and measurement](../../../../knowledge/experience/onboarding-foundations.md) | Before onboarding research acceptance, identity and analytics decisions, design lock, prototype acceptance or final onboarding verification. | `reference.experience.onboarding-foundations` |

package/agents/skills/b2c-design-onboarding/references/workflow.experience.onboarding-system.onb-14-trust-lifecycle-policy.md

@@ -0,0 +1,35 @@
+# Onboarding ONB-14: trust, lifecycle, and policy
+
+<!-- Generated task skill. Edit catalog owners, then run render:task-skills. -->
+
+Canonical workflow: `workflow.experience.onboarding-system.onb-14-trust-lifecycle-policy`. This is a reference contract, not an executable plan. Managed eligibility, ordering, authority, and acceptance remain with the installed business runtime.
+
+## Method
+
+Define native-only review-request timing (eligibility may be earned early, but the request happens outside first-run onboarding, ungated by sentiment, with a remote kill switch), the permission-request and lifecycle orchestration strategy (request only after a user action with visible benefit; one strategy spanning onboarding recovery through win-back), and the privacy/security/accessibility policy behavior this flow must honor. Write the contract to product/onboarding/graph/ONB-14-trust-lifecycle-policy.md; check:onboarding-evidence-onb-14 rejects a stub packet.
+
+## Inputs and outputs
+
+For advisory work, use the evidence supplied and return findings. Do not create runtime state, prerequisite artifacts, or a whole business to satisfy these managed-workspace paths. Missing evidence remains explicit.
+
+Managed inputs: `product/onboarding/graph/ONB-09-evidence-join.md`
+
+Consult when relevant: None declared.
+
+Managed outputs: `product/onboarding/graph/ONB-14-trust-lifecycle-policy.md`
+
+## Verification and authority
+
+Declared checks: `check:onboarding-evidence-onb-14`
+
+Additional founder decisions: None specific to this workflow; host permission boundaries still apply.
+
+Run applicable checks with the installed builder's documented target arguments. Report unavailable or unrun checks honestly. A review report, generated file, or successful command does not by itself establish accepted runtime or provider evidence. Do not mark reducer state by hand.
+
+## Select supporting knowledge
+
+Load only the sections needed for the current task. Broad load-when wording does not override accepted scope or an explicit provider binding. Provider procedures are current only at the corresponding selected-provider action. Stop and report an unresolved required source rather than treating its title as delivered guidance.
+
+| Reference | Load when | Stable identity |
+| --- | --- | --- |
+| [Onboarding Conversion](../../../../knowledge/experience/onboarding-conversion.md) | before onboarding quizzes, welcome/splash screens, personalization, attribution questions, demo videos, App Review popups, paywall timing, closing offers, trials, or first-session activation | `reference.experience.onboarding-conversion` |

package/agents/skills/b2c-design-onboarding/references/workflow.experience.onboarding-system.onb-15-architecture-decision.md

@@ -0,0 +1,35 @@
+# Onboarding ONB-15: architecture decision
+
+<!-- Generated task skill. Edit catalog owners, then run render:task-skills. -->
+
+Canonical workflow: `workflow.experience.onboarding-system.onb-15-architecture-decision`. This is a reference contract, not an executable plan. Managed eligibility, ordering, authority, and acceptance remain with the installed business runtime.
+
+## Method
+
+Compare native-first, hosted-funnel-first, hybrid, web-first, and any other evidence-backed architecture against first value, conversion/retention, identity/analytics, policy/economics, and operations, using the first-value, effort, state, analytics, and trust decisions from ONB-10 through ONB-14, then select exactly one target architecture with a stated reason. Write the decision to product/onboarding/graph/ONB-15-architecture-decision.md; check:onboarding-evidence-onb-15 rejects a stub packet, and every node from ONB-16 onward builds on this one selected model.
+
+## Inputs and outputs
+
+For advisory work, use the evidence supplied and return findings. Do not create runtime state, prerequisite artifacts, or a whole business to satisfy these managed-workspace paths. Missing evidence remains explicit.
+
+Managed inputs: `product/onboarding/graph/ONB-10-first-value-activation.md`, `product/onboarding/graph/ONB-11-effort-question-audit.md`, `product/onboarding/graph/ONB-12-state-identity-contract.md`, `product/onboarding/graph/ONB-13-analytics-experiments.md`, `product/onboarding/graph/ONB-14-trust-lifecycle-policy.md`
+
+Consult when relevant: None declared.
+
+Managed outputs: `product/onboarding/graph/ONB-15-architecture-decision.md`
+
+## Verification and authority
+
+Declared checks: `check:onboarding-evidence-onb-15`
+
+Additional founder decisions: None specific to this workflow; host permission boundaries still apply.
+
+Run applicable checks with the installed builder's documented target arguments. Report unavailable or unrun checks honestly. A review report, generated file, or successful command does not by itself establish accepted runtime or provider evidence. Do not mark reducer state by hand.
+
+## Select supporting knowledge
+
+Load only the sections needed for the current task. Broad load-when wording does not override accepted scope or an explicit provider binding. Provider procedures are current only at the corresponding selected-provider action. Stop and report an unresolved required source rather than treating its title as delivered guidance.
+
+| Reference | Load when | Stable identity |
+| --- | --- | --- |
+| [Onboarding Conversion](../../../../knowledge/experience/onboarding-conversion.md) | before onboarding quizzes, welcome/splash screens, personalization, attribution questions, demo videos, App Review popups, paywall timing, closing offers, trials, or first-session activation | `reference.experience.onboarding-conversion` |

package/agents/skills/b2c-design-onboarding/references/workflow.experience.onboarding-system.onb-16-journey-graph.md

@@ -0,0 +1,37 @@
+# Onboarding ONB-16: canonical journey graph
+
+<!-- Generated task skill. Edit catalog owners, then run render:task-skills. -->
+
+Canonical workflow: `workflow.experience.onboarding-system.onb-16-journey-graph`. This is a reference contract, not an executable plan. Managed eligibility, ordering, authority, and acceptance remain with the installed business runtime.
+
+## Method
+
+Draw the acquisition-specific journeys and converge them into one semantic onboarding state graph, marking each step's entry condition, owner/renderer, input/transition, canonical event, back/skip/close/resume behavior, and failure/next-step path — and mark where the acquisition promise, first effort, first value, engagement, account creation, paywall, purchase, activation, review eligibility, normal-product entry, and interruption budget each land on the graph. Resolve applicability from accepted product.yaml feature scopes and declared b2c.yaml monetization bindings when present: not selected, selected but unavailable, and unresolved stay different. Record first value, navigation/recovery, identity, accessibility, and the monetization boundary actually selected. When feature.commitment-funnel is required, record the Commitment Funnel in first-session order (welcome, quiz or goals, micro-commitment with a skip path, personalized insight, hard paywall) and Funnel Quality Metrics; when that feature is excluded or a non-goal, do not add a quiz or hard paywall to satisfy a gate; when the instance is absent, hold rather than treating the funnel as free or as selected. Keep that funnel in its recipe and reference.experience.commitment-funnel; do not silently select RevenueCat. Write the graph to product/onboarding/graph/ONB-16-journey-graph.md; check:onboarding-evidence-onb-16 rejects a stub packet.
+
+## Inputs and outputs
+
+For advisory work, use the evidence supplied and return findings. Do not create runtime state, prerequisite artifacts, or a whole business to satisfy these managed-workspace paths. Missing evidence remains explicit.
+
+Managed inputs: `product/onboarding/graph/ONB-15-architecture-decision.md`, `product.yaml`, `b2c.yaml`, `b2c.json`
+
+Consult when relevant: None declared.
+
+Managed outputs: `product/onboarding/graph/ONB-16-journey-graph.md`
+
+## Verification and authority
+
+Declared checks: `check:onboarding-evidence-onb-16`
+
+Additional founder decisions: None specific to this workflow; host permission boundaries still apply.
+
+Run applicable checks with the installed builder's documented target arguments. Report unavailable or unrun checks honestly. A review report, generated file, or successful command does not by itself establish accepted runtime or provider evidence. Do not mark reducer state by hand.
+
+## Select supporting knowledge
+
+Load only the sections needed for the current task. Broad load-when wording does not override accepted scope or an explicit provider binding. Provider procedures are current only at the corresponding selected-provider action. Stop and report an unresolved required source rather than treating its title as delivered guidance.
+
+| Reference | Load when | Stable identity |
+| --- | --- | --- |
+| [Design Evidence Stack](../../../../knowledge/design/design-evidence-stack.md) | before planning, creating, revising, auditing, or implementing any user-facing surface, component, interaction, onboarding flow, paywall, store frame, or marketing design; use it to classify the decision, select evidence sources, and record the evidence pass before mutation | `reference.design.design-evidence-stack` |
+| [Commitment Funnel](../../../../knowledge/experience/commitment-funnel.md) | before first-session screen order; when product.yaml records feature.commitment-funnel as required and onboarding needs welcome, quiz, micro-commitment, personalized insight, hard paywall, and install-to-trial quality metrics | `reference.experience.commitment-funnel` |
+| [Onboarding Conversion](../../../../knowledge/experience/onboarding-conversion.md) | before onboarding quizzes, welcome/splash screens, personalization, attribution questions, demo videos, App Review popups, paywall timing, closing offers, trials, or first-session activation | `reference.experience.onboarding-conversion` |

package/agents/skills/b2c-design-onboarding/references/workflow.experience.onboarding-system.onb-17-screen-control-paywall-contract.md

@@ -0,0 +1,40 @@
+# Onboarding ONB-17: screen, control, and paywall contract
+
+<!-- Generated task skill. Edit catalog owners, then run render:task-skills. -->
+
+Canonical workflow: `workflow.experience.onboarding-system.onb-17-screen-control-paywall-contract`. This is a reference contract, not an executable plan. Managed eligibility, ordering, authority, and acceptance remain with the installed business runtime.
+
+## Method
+
+Specify every onboarding screen with a stable ID and exactly one dominant action, pulling on-screen copy by key from product/copy/COPY_DECK.md rather than inventing strings, and define every control's enable/validation rule, state mutation, and exact idempotent provider action, plus failure/recovery and accessibility/localization behavior per screen. Resolve applicability from accepted product.yaml feature scopes and declared b2c.yaml monetization bindings when present; a producer sentence that a bind is not applicable cannot override a required feature. Specify the paywall contract for the selected purchase and presentation owners, including restore, pending, expiry, cancellation, offline, truthful-offer, and entitlement behavior those owners declare — do not invent RevenueCat offerings or customVariables for an unselected presenter. When feature.paywall-goal-headline is required and the presenter can bind it, record the Paywall Goal Headline contract: quiz writes paywall_headline_key, templates live in RevenueCat offering metadata, customVariables bind the selected key, and a skipped goal uses the fallback template with no invented outcome; when that feature is excluded or a non-goal, omit that bind; when the instance is absent, hold. Write the contract to product/onboarding/graph/ONB-17-screen-control-paywall-contract.md; check:onboarding-evidence-onb-17 rejects a stub packet, and ONB-20's adversarial QA runs directly against this contract.
+
+## Inputs and outputs
+
+For advisory work, use the evidence supplied and return findings. Do not create runtime state, prerequisite artifacts, or a whole business to satisfy these managed-workspace paths. Missing evidence remains explicit.
+
+Managed inputs: `product/onboarding/graph/ONB-16-journey-graph.md`, `product/copy/COPY_DECK.md`, `product.yaml`, `b2c.yaml`, `b2c.json`
+
+Consult when relevant: None declared.
+
+Managed outputs: `product/onboarding/graph/ONB-17-screen-control-paywall-contract.md`
+
+## Verification and authority
+
+Declared checks: `check:onboarding-evidence-onb-17`
+
+Additional founder decisions: None specific to this workflow; host permission boundaries still apply.
+
+Run applicable checks with the installed builder's documented target arguments. Report unavailable or unrun checks honestly. A review report, generated file, or successful command does not by itself establish accepted runtime or provider evidence. Do not mark reducer state by hand.
+
+## Select supporting knowledge
+
+Load only the sections needed for the current task. Broad load-when wording does not override accepted scope or an explicit provider binding. Provider procedures are current only at the corresponding selected-provider action. Stop and report an unresolved required source rather than treating its title as delivered guidance.
+
+| Reference | Load when | Stable identity |
+| --- | --- | --- |
+| [Design Evidence Stack](../../../../knowledge/design/design-evidence-stack.md) | before planning, creating, revising, auditing, or implementing any user-facing surface, component, interaction, onboarding flow, paywall, store frame, or marketing design; use it to classify the decision, select evidence sources, and record the evidence pass before mutation | `reference.design.design-evidence-stack` |
+| [Design Worthiness](../../../../knowledge/design/design-worthiness.md) | when DESIGN.md authoring or its generated Design Room review needs the mechanical worthiness floor or its independent audit must record the delegated taste decision before engineering harden, including native flow semantics and mechanical anti-generic consistency, with no beauty score | `reference.design.design-worthiness` |
+| [Mobile Flow Craft](../../../../knowledge/design/mobile-flow-craft.md) | designing, implementing, or auditing a native mobile screen or flow; deciding navigation and presentation semantics; hardening native fidelity; defining motion; or preparing runtime design acceptance | `reference.design.mobile-flow-craft` |
+| [Commitment Funnel](../../../../knowledge/experience/commitment-funnel.md) | before first-session screen order; when product.yaml records feature.commitment-funnel as required and onboarding needs welcome, quiz, micro-commitment, personalized insight, hard paywall, and install-to-trial quality metrics | `reference.experience.commitment-funnel` |
+| [Onboarding Conversion](../../../../knowledge/experience/onboarding-conversion.md) | before onboarding quizzes, welcome/splash screens, personalization, attribution questions, demo videos, App Review popups, paywall timing, closing offers, trials, or first-session activation | `reference.experience.onboarding-conversion` |
+| [Paywall Goal Headline](../../../../knowledge/experience/paywall-goal-headline.md) | before paywall copy lock; when product.yaml records feature.paywall-goal-headline as required and the declared present-paywall owner can bind RevenueCat offering metadata | `reference.experience.paywall-goal-headline` |

package/agents/skills/b2c-design-onboarding/references/workflow.experience.onboarding-system.onb-18-visual-design-prototype.md

@@ -0,0 +1,40 @@
+# Onboarding ONB-18: visual design and prototype
+
+<!-- Generated task skill. Edit catalog owners, then run render:task-skills. -->
+
+Canonical workflow: `workflow.experience.onboarding-system.onb-18-visual-design-prototype`. This is a reference contract, not an executable plan. Managed eligibility, ordering, authority, and acceptance remain with the installed business runtime.
+
+## Method
+
+Author the high-fidelity onboarding design in DESIGN.md — Git owns revisions — then render the generated read-only Design Room for review; the Design Room is not a mutable design store or a second design authority. Produce an interactive prototype covering the happy path and critical branches on the shipping platforms recorded in studio/seed/business.json mobileApp.platforms and DESIGN.md accepted surfaces, plus small viewports, large text, and reduced motion on those selected surfaces, and run design QA against it. Do not fabricate captures for an unselected platform; a selected platform without a supported adapter is an explicit unsupported or missing-implementation hold, not assumed parity from a shared component contract; the host recipe target, including host/agent-cli, is not the consumer app's shipping scope. After DESIGN.md changes, regenerate the review page and renew affected proof — old screenshots do not certify new code. Record the design proof — with the inspectable artifact path, not just adjectives — in product/onboarding/graph/ONB-18-visual-design-prototype.md. Map each ONB-09 decision to rendered design evidence in the Foundation contract. Instrument the prototype now, not after implementation: capture fresh install, consent denial, unknown attribution and analytics-unavailable traces in product/onboarding/prototype-evidence.json; a static mockup or event-name list is insufficient. check:onboarding-evidence-onb-18 rejects a stub packet, and ONB-20's adversarial QA depends on this prototype actually existing.
+
+## Inputs and outputs
+
+For advisory work, use the evidence supplied and return findings. Do not create runtime state, prerequisite artifacts, or a whole business to satisfy these managed-workspace paths. Missing evidence remains explicit.
+
+Managed inputs: `product/onboarding/graph/ONB-16-journey-graph.md`, `product/onboarding/graph/ONB-17-screen-control-paywall-contract.md`, `product/onboarding/graph/ONB-12-state-identity-contract.md`, `product/onboarding/graph/ONB-13-analytics-experiments.md`, `DESIGN.md`, `studio/seed/business.json`
+
+Consult when relevant: None declared.
+
+Managed outputs: `product/onboarding/graph/ONB-18-visual-design-prototype.md`, `product/onboarding/prototype-evidence.json`
+
+## Verification and authority
+
+Declared checks: `check:onboarding-evidence-onb-18`, `check:onboarding-foundations-prototype`
+
+Additional founder decisions: None specific to this workflow; host permission boundaries still apply.
+
+Run applicable checks with the installed builder's documented target arguments. Report unavailable or unrun checks honestly. A review report, generated file, or successful command does not by itself establish accepted runtime or provider evidence. Do not mark reducer state by hand.
+
+## Select supporting knowledge
+
+Load only the sections needed for the current task. Broad load-when wording does not override accepted scope or an explicit provider binding. Provider procedures are current only at the corresponding selected-provider action. Stop and report an unresolved required source rather than treating its title as delivered guidance.
+
+| Reference | Load when | Stable identity |
+| --- | --- | --- |
+| [Analytics And Attribution](../../../../knowledge/data/analytics-attribution.md) | before onboarding, paywalls, funnels, store CTAs, referrals, lifecycle email, UGC/Fastlane campaigns, paid UA, or any builder prompt that names events; before PostHog setup, dashboards, deep links, feature flags, experiments, or session replay | `reference.data.analytics-attribution` |
+| [Design Evidence Stack](../../../../knowledge/design/design-evidence-stack.md) | before planning, creating, revising, auditing, or implementing any user-facing surface, component, interaction, onboarding flow, paywall, store frame, or marketing design; use it to classify the decision, select evidence sources, and record the evidence pass before mutation | `reference.design.design-evidence-stack` |
+| [Design Worthiness](../../../../knowledge/design/design-worthiness.md) | when DESIGN.md authoring or its generated Design Room review needs the mechanical worthiness floor or its independent audit must record the delegated taste decision before engineering harden, including native flow semantics and mechanical anti-generic consistency, with no beauty score | `reference.design.design-worthiness` |
+| [Mobile Flow Craft](../../../../knowledge/design/mobile-flow-craft.md) | designing, implementing, or auditing a native mobile screen or flow; deciding navigation and presentation semantics; hardening native fidelity; defining motion; or preparing runtime design acceptance | `reference.design.mobile-flow-craft` |
+| [Onboarding Conversion](../../../../knowledge/experience/onboarding-conversion.md) | before onboarding quizzes, welcome/splash screens, personalization, attribution questions, demo videos, App Review popups, paywall timing, closing offers, trials, or first-session activation | `reference.experience.onboarding-conversion` |
+| [Research-backed onboarding with identity and measurement](../../../../knowledge/experience/onboarding-foundations.md) | Before onboarding research acceptance, identity and analytics decisions, design lock, prototype acceptance or final onboarding verification. | `reference.experience.onboarding-foundations` |

package/agents/skills/b2c-design-onboarding/references/workflow.experience.onboarding-system.onb-19-implementation-cutover-contract.md

@@ -0,0 +1,37 @@
+# Onboarding ONB-19: implementation and cutover contract
+
+<!-- Generated task skill. Edit catalog owners, then run render:task-skills. -->
+
+Canonical workflow: `workflow.experience.onboarding-system.onb-19-implementation-cutover-contract`. This is a reference contract, not an executable plan. Managed eligibility, ordering, authority, and acceptance remain with the installed business runtime.
+
+## Method
+
+Define the implementation task list plus reliability behavior (pending purchases, restore, entitlement delay, network, generation, analytics-non-blocking, deep link, identity, unsupported-client), performance/observability budgets (P50/P95 and failure budgets for startup, first value, provider init, paywall, checkout, entitlement, handoff), and the hard-cutover Removal Inventory for anything the new graph replaces (replaced code, data, config, provider setup, dashboards, tests, docs, secrets, transformation tooling), each with a disposition and a verification method. Write the contract to product/onboarding/graph/ONB-19-implementation-cutover-contract.md; check:onboarding-evidence-onb-19 rejects a stub packet, and this is the plan ONB-22 later executes and the manifest ONB-22's cutover proves against the real repository.
+
+## Inputs and outputs
+
+For advisory work, use the evidence supplied and return findings. Do not create runtime state, prerequisite artifacts, or a whole business to satisfy these managed-workspace paths. Missing evidence remains explicit.
+
+Managed inputs: `product/onboarding/graph/ONB-16-journey-graph.md`, `product/onboarding/graph/ONB-12-state-identity-contract.md`, `product/onboarding/graph/ONB-13-analytics-experiments.md`, `product/onboarding/prototype-evidence.json`
+
+Consult when relevant: None declared.
+
+Managed outputs: `product/onboarding/graph/ONB-19-implementation-cutover-contract.md`
+
+## Verification and authority
+
+Declared checks: `check:onboarding-evidence-onb-19`
+
+Additional founder decisions: None specific to this workflow; host permission boundaries still apply.
+
+Run applicable checks with the installed builder's documented target arguments. Report unavailable or unrun checks honestly. A review report, generated file, or successful command does not by itself establish accepted runtime or provider evidence. Do not mark reducer state by hand.
+
+## Select supporting knowledge
+
+Load only the sections needed for the current task. Broad load-when wording does not override accepted scope or an explicit provider binding. Provider procedures are current only at the corresponding selected-provider action. Stop and report an unresolved required source rather than treating its title as delivered guidance.
+
+| Reference | Load when | Stable identity |
+| --- | --- | --- |
+| [Analytics And Attribution](../../../../knowledge/data/analytics-attribution.md) | before onboarding, paywalls, funnels, store CTAs, referrals, lifecycle email, UGC/Fastlane campaigns, paid UA, or any builder prompt that names events; before PostHog setup, dashboards, deep links, feature flags, experiments, or session replay | `reference.data.analytics-attribution` |
+| [Onboarding Conversion](../../../../knowledge/experience/onboarding-conversion.md) | before onboarding quizzes, welcome/splash screens, personalization, attribution questions, demo videos, App Review popups, paywall timing, closing offers, trials, or first-session activation | `reference.experience.onboarding-conversion` |
+| [Research-backed onboarding with identity and measurement](../../../../knowledge/experience/onboarding-foundations.md) | Before onboarding research acceptance, identity and analytics decisions, design lock, prototype acceptance or final onboarding verification. | `reference.experience.onboarding-foundations` |

package/agents/skills/b2c-design-onboarding/references/workflow.experience.onboarding-system.onb-20-adversarial-qa.md

@@ -0,0 +1,38 @@
+# Onboarding ONB-20: adversarial QA
+
+<!-- Generated task skill. Edit catalog owners, then run render:task-skills. -->
+
+Canonical workflow: `workflow.experience.onboarding-system.onb-20-adversarial-qa`. This is a reference contract, not an executable plan. Managed eligibility, ordering, authority, and acceptance remain with the installed business runtime.
+
+## Method
+
+Run the synthetic one-star pre-mortem (privacy, permission, poor result, slow network, trial, subscriber, restore, web purchase, accessibility, identity, or subscription-aversion scenarios, each with root cause, likelihood/severity, mitigation, test, and remaining risk) plus a policy review, instrumentation QA, accessibility review, and provider-realism review against the actual ONB-17 contract, ONB-18 prototype, and ONB-19 cutover plan — assume the flow fails before crediting that it works. Use a fresh reviewer session, inspect the prototype event traces and source hashes, and reject missing first-session instrumentation or untested identity/consent boundaries. Write findings to product/onboarding/graph/ONB-20-adversarial-qa.md; check:onboarding-evidence-onb-20 rejects a stub packet, and an unresolved high-severity finding must not be waved through to ONB-21's implementation plan.
+
+## Inputs and outputs
+
+For advisory work, use the evidence supplied and return findings. Do not create runtime state, prerequisite artifacts, or a whole business to satisfy these managed-workspace paths. Missing evidence remains explicit.
+
+Managed inputs: `product/onboarding/graph/ONB-17-screen-control-paywall-contract.md`, `product/onboarding/graph/ONB-18-visual-design-prototype.md`, `product/onboarding/graph/ONB-19-implementation-cutover-contract.md`
+
+Consult when relevant: None declared.
+
+Managed outputs: `product/onboarding/graph/ONB-20-adversarial-qa.md`
+
+## Verification and authority
+
+Declared checks: `check:onboarding-evidence-onb-20`
+
+Additional founder decisions: None specific to this workflow; host permission boundaries still apply.
+
+Run applicable checks with the installed builder's documented target arguments. Report unavailable or unrun checks honestly. A review report, generated file, or successful command does not by itself establish accepted runtime or provider evidence. Do not mark reducer state by hand.
+
+## Select supporting knowledge
+
+Load only the sections needed for the current task. Broad load-when wording does not override accepted scope or an explicit provider binding. Provider procedures are current only at the corresponding selected-provider action. Stop and report an unresolved required source rather than treating its title as delivered guidance.
+
+| Reference | Load when | Stable identity |
+| --- | --- | --- |
+| [Analytics And Attribution](../../../../knowledge/data/analytics-attribution.md) | before onboarding, paywalls, funnels, store CTAs, referrals, lifecycle email, UGC/Fastlane campaigns, paid UA, or any builder prompt that names events; before PostHog setup, dashboards, deep links, feature flags, experiments, or session replay | `reference.data.analytics-attribution` |
+| [Onboarding Conversion](../../../../knowledge/experience/onboarding-conversion.md) | before onboarding quizzes, welcome/splash screens, personalization, attribution questions, demo videos, App Review popups, paywall timing, closing offers, trials, or first-session activation | `reference.experience.onboarding-conversion` |
+| [Research-backed onboarding with identity and measurement](../../../../knowledge/experience/onboarding-foundations.md) | Before onboarding research acceptance, identity and analytics decisions, design lock, prototype acceptance or final onboarding verification. | `reference.experience.onboarding-foundations` |
+| [Isolated Review](../../../../knowledge/orchestration/isolated-review.md) | before dispatching any producer whose surface a second agent must accept, before dispatching an auditor node, when writing or checking the review ledger in operations/ORCHESTRATION.md, and when a review, rubric, or fix loop is contested | `reference.orchestration.isolated-review` |

package/agents/skills/b2c-design-onboarding/references/workflow.experience.onboarding-system.onb-21-compound-engineering-plan.md

@@ -0,0 +1,35 @@
+# Onboarding ONB-21: Compound Engineering plan
+
+<!-- Generated task skill. Edit catalog owners, then run render:task-skills. -->
+
+Canonical workflow: `workflow.experience.onboarding-system.onb-21-compound-engineering-plan`. This is a reference contract, not an executable plan. Managed eligibility, ordering, authority, and acceptance remain with the installed business runtime.
+
+## Method
+
+Translate the accepted onboarding graph and its adversarial-QA findings into an implementation-ready Compound Engineering plan (ce-plan when available, or this skill's equivalent), breaking work into tasks each with an outcome, exact paths, dependencies/contracts, required analytics/provider work, tests, removal work, and acceptance criteria. Write the plan as ONB-TASK rows in product/onboarding/graph/ONB-21-compound-engineering-plan.md; check:onboarding-evidence-onb-21 rejects a stub packet, and ONB-22 executes exactly this task list rather than improvising new scope.
+
+## Inputs and outputs
+
+For advisory work, use the evidence supplied and return findings. Do not create runtime state, prerequisite artifacts, or a whole business to satisfy these managed-workspace paths. Missing evidence remains explicit.
+
+Managed inputs: `product/onboarding/graph/ONB-20-adversarial-qa.md`
+
+Consult when relevant: None declared.
+
+Managed outputs: `product/onboarding/graph/ONB-21-compound-engineering-plan.md`
+
+## Verification and authority
+
+Declared checks: `check:onboarding-evidence-onb-21`
+
+Additional founder decisions: None specific to this workflow; host permission boundaries still apply.
+
+Run applicable checks with the installed builder's documented target arguments. Report unavailable or unrun checks honestly. A review report, generated file, or successful command does not by itself establish accepted runtime or provider evidence. Do not mark reducer state by hand.
+
+## Select supporting knowledge
+
+Load only the sections needed for the current task. Broad load-when wording does not override accepted scope or an explicit provider binding. Provider procedures are current only at the corresponding selected-provider action. Stop and report an unresolved required source rather than treating its title as delivered guidance.
+
+| Reference | Load when | Stable identity |
+| --- | --- | --- |
+| [Onboarding Conversion](../../../../knowledge/experience/onboarding-conversion.md) | before onboarding quizzes, welcome/splash screens, personalization, attribution questions, demo videos, App Review popups, paywall timing, closing offers, trials, or first-session activation | `reference.experience.onboarding-conversion` |

package/agents/skills/b2c-plan-implementation/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: b2c-plan-implementation
+description: "Produce a bounded implementation plan with ownership, interfaces, dependencies, tests, review, and risks. Planning does not execute app work or declare release readiness."
+compatibility: Markdown and supplied evidence. Provider-backed work needs the corresponding authorized tools. The B2C runtime is optional for focused advisory work.
+metadata:
+  source-workflow: "workflow.engineering.engineering-orchestration-ce-production-readiness"
+  generated-by: b2c-catalog
+---
+
+# Plan implementation
+
+<!-- Generated task skill. Edit catalog owners, then run render:task-skills. -->
+
+## Choose the scope
+
+Use this task directly for focused advice, review, or an authorized change. Do not require setup, install software, create a workspace, or activate a full launch graph merely to use this expertise. A review is read-only unless the user also requests changes.
+
+For an existing managed business, read business-status then business-plan and use its current brief. This skill cannot choose executable next work, bypass prerequisites, change provider bindings, or replace runtime acceptance. Do not inspect raw reducer files merely to start a focused task.
+
+## Method
+
+For a review, assess the existing evidence against this method and return findings; do not execute its authoring or mutation instructions. For requested creation or implementation, follow the method only within the accepted scope and authority.
+
+## Continuous experience principle
+
+Carry the accepted user's intended outcome through the work: make the result meaningfully better for that user, preserve relevant identity, hierarchy, accessibility, and recovery constraints, and verify behavior as well as presence. Apply this only where relevant; a narrow fix stays narrow. This principle does not require an 11-star exercise or a numeric taste score.
+
+Before `ce-work` or a generated builder starts, produce `engineering/ENGINEERING_PLAN.md` through `ce-plan` or an equivalent implementation-plan doc.
+
+The plan must include:
+
+- requirements trace to launch docs and `state/LAUNCH_TRACE.md` IDs
+- 11-star complete product experience, line of feasibility, and magical-moment proof requirements
+- `state/business-state.json` phase, autonomy mode, active blockers, and failure cards that constrain implementation
+- `engineering/TECH_SPEC.md` pointer or inline technical contracts when data/API/state/integration behavior is in scope
+- `product/copy/COPY_DECK.md` coverage for every screen the units build, and the string-externalization mechanism from `engineering/TECH_SPEC.md` §Strings And Localization Readiness
+- [`premium-mobile-craft.md`](../../../knowledge/design/premium-mobile-craft.md) acceptance-criteria coverage for every screen the units build — press states, motion, haptics, loading/empty states — the same per-screen bar the COPY_DECK.md line above already sets for copy
+- implementation units with repo-relative file paths
+- a short decision entry for each non-obvious architecture or data-model choice: the option chosen, the option rejected, and the reason, kept in this plan or a linked `engineering/DECISIONS.md`
+- orchestration strategy, candidate units, safe parallel lanes, serialized lanes, worktree needs, shared resources, and subagent forbidden actions from `operations/ORCHESTRATION.md`
+- frontend, backend, database, analytics, revenue, email, and store-console impacts
+- secret impacts: new secret or env var, secret class, Doppler/provider routing, service token/provider-integration plan, CI/deploy injection, `.env.example` names-only updates, and bundle-safety checks
+- feature flags or rollout controls
+- migration and data-backfill plan when needed
+- auth/session, permission, app integrity, API/RPC/webhook, and state-machine impacts when relevant
+- test scenarios for happy path, edge cases, error paths, and integration paths
+- MobAI/native iOS/device-test scenarios for mobile user journeys, plus XcodeBuildMCP/SnapshotPreviews/serve-sim scenarios when they are the Apple-platform proof route
+- backend verification scenarios showing real test data persisted or projected correctly
+- production-readiness gates and known blockers
+- validator and LaunchBench checks that must pass before done
+
+Do not put unsupported product behavior into `engineering/ENGINEERING_PLAN.md`. Send unresolved product questions back to `ce-brainstorm` or make explicit assumptions.
+
+## Load only what the task needs
+
+[Task inputs, outputs, checks, and knowledge selectors](references/task.md) supplies the canonical details when they are needed. Open the specific referenced sections, not the whole library. In connected knowledge retrieval, follow exact section selectors, revision hashes, and continuation calls. Unresolved guidance remains unresolved.
+
+## Tools and evidence
+
+Keep the method independent of the agent host and business provider. Honor explicit selections. Use already available, authorized tools that implement the required operation; do not infer availability from the agent's name or silently substitute a provider. Load a provider's procedure only when its action is current. Record missing capabilities without inventing provider proof.
+
+Pause for access or secrets, spend, pricing or legal decisions, destructive changes, hosted deployment, store submission, or production release. Guidance is not permission. A proposed price is not an approved price, and a mock is not live evidence.
+
+## Return
+
+Report findings or changes, the evidence inspected, applicable checks actually run, unresolved requirements, and the next decision. Label advisory findings separately from accepted business evidence. Do not record business completion or modify reducer-owned state outside the supported runtime.