luckiest-co 1.0.0 → 1.0.3

package/skills/luckiest-session-handoff/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: luckiest-session-handoff
+description: Use when the user says "session handoff", "wrap up session", "hand off", "handoff summary", "let's wrap up", "summarize before I clear", or is about to /clear context. Produces a chat-only, structured end-of-session summary — decisions, shipped changes, key files, running state, verification steps, deferrals, open questions — so a fresh agent can continue seamlessly.
+license: See ATTRIBUTION.md
+metadata:
+  version: "1.1.0"
+  listing_id: luckiest-session-handoff
+  author: luckiest
+---
+
+# Luckiest Session Handoff
+
+Produce a repeatable end-of-session summary so the user can `/clear` and start a fresh agent without losing continuity. The next agent should be able to pick up by reading this summary alone.
+
+This is a **context-handoff artifact**, not a status report. The audience is a future instance of you, not a stakeholder.
+
+## Staying current
+
+On activation, call the Luckiest MCP `check_updates` tool with
+`{ listingId: "luckiest-session-handoff", installedSemver: "1.1.0" }`.
+If it returns `upToDate: false`, surface the `notice` to the user. Do nothing further if `upToDate: true`.
+
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-session-handoff", skill_version: "1.1.0", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
+
+## When to invoke
+
+User says: "session handoff", "wrap up session", "hand off", "handoff summary", "let's wrap up", "summarize before I clear", or any near-equivalent. Also invoke proactively if the user says they are about to `/clear` without having run it yet.
+
+## How to produce the summary
+
+1. **Review the full conversation**, not just the last few turns. Handoffs miss things when they only summarize recent context.
+2. **Pull state from these sources (in order):**
+   - Any plan file referenced this session (check the agent's plans directory if a plan was mentioned).
+   - Todo state — any in-progress or pending tasks.
+   - Background processes started with `run_in_background` — process/shell IDs are load-bearing for the next agent.
+   - Files created or modified this session — you know what you touched; do not grep to re-discover.
+   - Memory files written or updated this session.
+   - Unresolved questions — things you asked the user that never got a clear answer, or things the user asked that got deflected.
+3. **Do NOT audit the filesystem.** This is synthesis of what happened in THIS session. No `git log`, no broad glob sweeps. If you did not touch it this session, it does not belong here.
+4. **Produce the output in chat.** Do not write a file. Do not update memory. Chat-only.
+
+## Output template — use exactly this structure, every time
+
+```
+# Session Handoff — <one-line title of what this session was about>
+
+## Where it started
+<2-3 sentences: what the user asked for, key framing or constraints that emerged>
+
+## Decisions locked + what shipped
+- <decision or change> — <why, and where it lives (absolute path if a file)>
+- ...
+
+## Key files for next session
+- `<absolute path>` — <why the next agent should read this first>
+- Plan file: `<path>` (if a plan drove the session)
+- Memory files touched: `<paths>` (if any)
+
+## Running state
+- Background processes: <IDs + what they are + how to kill> — or "none"
+- Dev servers / ports: <url + port> — or "none"
+- Open worktrees / branches: <paths> — or "none"
+
+## Verification — how to confirm things still work
+- `<command>` — <expected outcome>
+- ...
+
+## Deferred + open questions
+- Deferred: <item> — <why pushed to later>
+- Open: <question needing the user's input> — <context>
+
+## Pick up here
+<1-2 sentences: the single most likely next action for a fresh agent>
+```
+
+## Hard rules
+
+1. **Chat output only.** Never write the handoff to a file. Never update memory from this skill.
+2. **Never invent state.** If a section has nothing to report, write "none" — do not omit the section. Structure stability is the whole point.
+3. **Absolute paths always.** The next agent may have a different working directory.
+4. **If a plan file drove the session, name it first** in "Key files" so the next agent reads it before anything else.
+5. **No emojis, no hype, no "great job" summaries.** Terse and concrete — paths, commands, process IDs, decisions. Match the tone of a seasoned engineer handing off at end-of-shift.
+6. **Background process IDs are critical.** If you started any `run_in_background` processes, their IDs must appear in "Running state" with the kill command — the next agent cannot find them otherwise.
+
+## Share with your tribe (optional)
+
+After presenting the handoff, if the work was collaborative or someone else may continue it, offer once: surface this handoff to the user's Luckiest tribe so a teammate who raised a related request can pick up where this session left off. This is an offer the user can decline — never post automatically, and never include secrets, tokens, or `.env` values in what you share.
+
+## Anti-patterns — do not do these
+
+- Summarizing the last 3 turns and calling it a handoff.
+- Listing files by relative path.
+- Skipping the "Running state" section because "nothing is running" — write "none" instead.
+- Writing the summary to a file. This is chat-only by design.
+- Adding a "what went well / what went poorly" retrospective. This is not a retro.
+- Recommending next steps beyond the single "Pick up here" line. The next agent decides; you just hand off.

package/skills/luckiest-signup/ATTRIBUTION.md

@@ -0,0 +1,48 @@
+# Attribution
+
+This skill, **luckiest-signup**, is a rebranded and modified edition of the
+original skill **"signup"** from the **marketingskills** project
+(https://github.com/coreyhaines31/marketingskills) by **Corey Haines**
+(https://corey.co), distributed under the MIT License.
+
+The original work is used and modified under the terms of that license, reproduced
+verbatim below. The copyright notice is preserved as required.
+
+## Modifications
+
+- Renamed to `luckiest-signup` and updated all self-references and sibling
+  cross-references (`onboarding` → `luckiest-onboarding`, `cro` → `luckiest-cro`,
+  `ab-testing` → `luckiest-ab-testing`).
+- Rewrote frontmatter to be spec-compliant; converted the body to third-person voice.
+- Added evidence-based flow detection, a legally-required-field guardrail, and a
+  baseline-anchoring rule for impact estimates.
+- Added a Luckiest "Share with your tribe" offer (opt-in, never auto-post, no credentials).
+- Added a "Staying current" update-check block and version metadata.
+
+See CHANGELOG.md for details.
+
+---
+
+## Original License (MIT) — reproduced verbatim
+
+MIT License
+
+Copyright (c) 2025 Corey Haines
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/luckiest-signup/CHANGELOG.md

@@ -0,0 +1,24 @@
+# Changelog — luckiest-signup
+
+## 1.1.0 — 2026-07-06
+Skill updater pass: analytics integration.
+
+### Analytics (report_usage)
+- Updated `report_usage` call to `skill_version: "1.1.0"` and `check_updates`
+  `installedSemver: "1.1.0"`. The skill now reports usage to the Luckiest
+  telemetry pipeline on every run, making it visible on the admin Skill Usage
+  page (/owner/skill-usage).
+
+## 1.0.0 — 2026-07-01
+Rebranded from signup (marketingskills, MIT).
+
+### Improve pass (/refract)
+- Added an evidence-first flow-detection step: inspect any supplied signup URL, form markup, screenshot, or analytics export and infer flow type / fields / steps before asking the user.
+- Added a legally-required-field guardrail to "Minimize Required Fields": never cut consent, age-gate, or compliance-mandated fields; reduce their friction instead.
+- Added a baseline-anchoring rule to Measurement/Output: state the current baseline before estimating lift and never present a fabricated "+X%" as fact.
+
+### Network hook
+- "Share with your tribe" offer after a signup audit/redesign — opt-in only, never auto-posts, excludes credentials and private analytics.
+
+### Trend pass (/newsjack + /luckiest-trends)
+- No actionable signal. The luckiest-trends engine requires interactive first-run setup and live social sources unavailable in this non-interactive environment; per skill policy no WebSearch-only fallback was substituted.

package/skills/luckiest-signup/SKILL.md

@@ -0,0 +1,382 @@
+---
+name: luckiest-signup
+description: Use when the user wants to optimize signup, registration, account creation, or trial activation flows. Reduces form friction, cuts fields, improves social auth and verification, and raises signup completion rates. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see luckiest-onboarding. For lead capture forms (not account creation), see luckiest-cro.
+license: See ATTRIBUTION.md
+metadata:
+  version: "1.1.0"
+  listing_id: luckiest-signup
+  author: luckiest
+---
+
+# Signup Flow CRO
+
+This skill optimizes signup and registration flows. The goal is to reduce friction, increase completion rates, and set users up for successful activation.
+
+## Staying current
+
+On activation, call the Luckiest MCP check_updates tool with { listingId: "luckiest-signup", installedSemver: "1.1.0" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
+
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-signup", skill_version: "1.1.0", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
+
+## Initial Assessment
+
+**Check for product marketing context first:**
+If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+**Detect the flow from evidence before asking:**
+When a signup URL, form markup, screenshot, or analytics export is provided, inspect it first and infer the flow type, field set, and step count directly. Only ask the user for what cannot be observed. Do not ask questions the supplied artifacts already answer.
+
+Before providing recommendations, understand:
+
+1. **Flow Type**
+   - Free trial signup
+   - Freemium account creation
+   - Paid account creation
+   - Waitlist/early access signup
+   - B2B vs B2C
+
+2. **Current State**
+   - How many steps/screens?
+   - What fields are required?
+   - What's the current completion rate?
+   - Where do users drop off?
+
+3. **Business Constraints**
+   - What data is genuinely needed at signup?
+   - Are there compliance requirements?
+   - What happens immediately after signup?
+
+---
+
+## Core Principles
+
+### 1. Minimize Required Fields
+Every field reduces conversion. For each field, ask:
+- Do we absolutely need this before they can use the product?
+- Can we collect this later through progressive profiling?
+- Can we infer this from other data?
+
+**Typical field priority:**
+- Essential: Email (or phone), Password
+- Often needed: Name
+- Usually deferrable: Company, Role, Team size, Phone, Address
+
+**Never cut a legally-required field.** Consent checkboxes, age gates, tax/region fields, and other compliance-mandated inputs stay even when trimming for conversion. When a field is required by law or platform policy, keep it and instead reduce its friction (clear copy, inline help, smart defaults).
+
+### 2. Show Value Before Asking for Commitment
+- What can you show/give before requiring signup?
+- Can they experience the product before creating an account?
+- Reverse the order: value first, signup second
+
+### 3. Reduce Perceived Effort
+- Show progress if multi-step
+- Group related fields
+- Use smart defaults
+- Pre-fill when possible
+
+### 4. Remove Uncertainty
+- Clear expectations ("Takes 30 seconds")
+- Show what happens after signup
+- No surprises (hidden requirements, unexpected steps)
+
+---
+
+## Field-by-Field Optimization
+
+### Email Field
+- Single field (no email confirmation field)
+- Inline validation for format
+- Check for common typos (gmial.com → gmail.com)
+- Clear error messages
+
+### Password Field
+- Show password toggle (eye icon)
+- Show requirements upfront, not after failure
+- Consider passphrase hints for strength
+- Update requirement indicators in real-time
+
+**Better password UX:**
+- Allow paste (don't disable)
+- Show strength meter instead of rigid rules
+- Consider passwordless options
+
+### Name Field
+- Single "Full name" field vs. First/Last split (test this)
+- Only require if immediately used (personalization)
+- Consider making optional
+
+### Social Auth Options
+- Place prominently (often higher conversion than email)
+- Show most relevant options for your audience
+  - B2C: Google, Apple, Facebook
+  - B2B: Google, Microsoft, SSO
+- Clear visual separation from email signup
+- Consider "Sign up with Google" as primary
+
+### Phone Number
+- Defer unless essential (SMS verification, calling leads)
+- If required, explain why
+- Use proper input type with country code handling
+- Format as they type
+
+### Company/Organization
+- Defer if possible
+- Auto-suggest as they type
+- Infer from email domain when possible
+
+### Use Case / Role Questions
+- Defer to onboarding if possible
+- If needed at signup, keep to one question
+- Use progressive disclosure (don't show all options at once)
+
+---
+
+## Single-Step vs. Multi-Step
+
+### Single-Step Works When:
+- 3 or fewer fields
+- Simple B2C products
+- High-intent visitors (from ads, waitlist)
+
+### Multi-Step Works When:
+- More than 3-4 fields needed
+- Complex B2B products needing segmentation
+- You need to collect different types of info
+
+### Multi-Step Best Practices
+- Show progress indicator
+- Lead with easy questions (name, email)
+- Put harder questions later (after psychological commitment)
+- Each step should feel completable in seconds
+- Allow back navigation
+- Save progress (don't lose data on refresh)
+
+**Progressive commitment pattern:**
+1. Email only (lowest barrier)
+2. Password + name
+3. Customization questions (optional)
+
+---
+
+## Trust and Friction Reduction
+
+### At the Form Level
+- "No credit card required" (if true)
+- "Free forever" or "14-day free trial"
+- Privacy note: "We'll never share your email"
+- Security badges if relevant
+- Testimonial near signup form
+
+### Error Handling
+- Inline validation (not just on submit)
+- Specific error messages ("Email already registered" + recovery path)
+- Don't clear the form on error
+- Focus on the problem field
+
+### Microcopy
+- Placeholder text: Use for examples, not labels
+- Labels: Keep visible (not just placeholders) — placeholders disappear when typing, leaving users unsure what they're filling in
+- Help text: Only when needed, placed close to field
+
+---
+
+## Mobile Signup Optimization
+
+- Larger touch targets (44px+ height)
+- Appropriate keyboard types (email, tel, etc.)
+- Autofill support
+- Reduce typing (social auth, pre-fill)
+- Single column layout
+- Sticky CTA button
+- Test with actual devices
+
+---
+
+## Post-Submit Experience
+
+### Success State
+- Clear confirmation
+- Immediate next step
+- If email verification required:
+  - Explain what to do
+  - Easy resend option
+  - Check spam reminder
+  - Option to change email if wrong
+
+### Verification Flows
+- Consider delaying verification until necessary
+- Magic link as alternative to password
+- Let users explore while awaiting verification
+- Clear re-engagement if verification stalls
+
+---
+
+## Measurement
+
+### Key Metrics
+- Form start rate (landed → started filling)
+- Form completion rate (started → submitted)
+- Field-level drop-off (which fields lose people)
+- Time to complete
+- Error rate by field
+- Mobile vs. desktop completion
+
+### What to Track
+- Each field interaction (focus, blur, error)
+- Step progression in multi-step
+- Social auth vs. email signup ratio
+- Time between steps
+
+### Anchor Impact to a Baseline
+Before claiming an expected lift, state the current baseline the estimate is measured against (e.g. "from a 45% completion rate"). If no baseline is known, say the impact is directional and mark it as a hypothesis to validate, not a promised number. Never present a fabricated "+X%" as fact.
+
+---
+
+## Output Format
+
+### Audit Findings
+For each issue found:
+- **Issue**: What's wrong
+- **Impact**: Why it matters (with estimated impact against the stated baseline where possible)
+- **Fix**: Specific recommendation
+- **Priority**: High/Medium/Low
+
+### Recommended Changes
+Organized by:
+1. Quick wins (same-day fixes)
+2. High-impact changes (week-level effort)
+3. Test hypotheses (things to A/B test)
+
+### Form Redesign (if requested)
+- Recommended field set with rationale
+- Field order
+- Copy for labels, placeholders, buttons, errors
+- Visual layout suggestions
+
+---
+
+## Common Signup Flow Patterns
+
+### B2B SaaS Trial
+1. Email + Password (or Google auth)
+2. Name + Company (optional: role)
+3. → Onboarding flow
+
+### B2C App
+1. Google/Apple auth OR Email
+2. → Product experience
+3. Profile completion later
+
+### Waitlist/Early Access
+1. Email only
+2. Optional: Role/use case question
+3. → Waitlist confirmation
+
+### E-commerce Account
+1. Guest checkout as default
+2. Account creation optional post-purchase
+3. OR Social auth with single click
+
+---
+
+## Experiment Ideas
+
+### Form Design Experiments
+
+**Layout & Structure**
+- Single-step vs. multi-step signup flow
+- Multi-step with progress bar vs. without
+- 1-column vs. 2-column field layout
+- Form embedded on page vs. separate signup page
+- Horizontal vs. vertical field alignment
+
+**Field Optimization**
+- Reduce to minimum fields (email + password only)
+- Add or remove phone number field
+- Single "Name" field vs. "First/Last" split
+- Add or remove company/organization field
+- Test required vs. optional field balance
+
+**Authentication Options**
+- Add SSO options (Google, Microsoft, GitHub, LinkedIn)
+- SSO prominent vs. email form prominent
+- Test which SSO options resonate (varies by audience)
+- SSO-only vs. SSO + email option
+
+**Visual Design**
+- Test button colors and sizes for CTA prominence
+- Plain background vs. product-related visuals
+- Test form container styling (card vs. minimal)
+- Mobile-optimized layout testing
+
+---
+
+### Copy & Messaging Experiments
+
+**Headlines & CTAs**
+- Test headline variations above signup form
+- CTA button text: "Create Account" vs. "Start Free Trial" vs. "Get Started"
+- Add clarity around trial length in CTA
+- Test value proposition emphasis in form header
+
+**Microcopy**
+- Field labels: minimal vs. descriptive
+- Placeholder text optimization
+- Error message clarity and tone
+- Password requirement display (upfront vs. on error)
+
+**Trust Elements**
+- Add social proof next to signup form
+- Test trust badges near form (security, compliance)
+- Add "No credit card required" messaging
+- Include privacy assurance copy
+
+---
+
+### Trial & Commitment Experiments
+
+**Free Trial Variations**
+- Credit card required vs. not required for trial
+- Test trial length impact (7 vs. 14 vs. 30 days)
+- Freemium vs. free trial model
+- Trial with limited features vs. full access
+
+**Friction Points**
+- Email verification required vs. delayed vs. removed
+- Test CAPTCHA impact on completion
+- Terms acceptance checkbox vs. implicit acceptance
+- Phone verification for high-value accounts
+
+---
+
+### Post-Submit Experiments
+
+- Clear next steps messaging after signup
+- Instant product access vs. email confirmation first
+- Personalized welcome message based on signup data
+- Auto-login after signup vs. require login
+
+---
+
+## Task-Specific Questions
+
+1. What's your current signup completion rate?
+2. Do you have field-level analytics on drop-off?
+3. What data is absolutely required before they can use the product?
+4. Are there compliance or verification requirements?
+5. What happens immediately after signup?
+
+---
+
+## Share with your tribe
+
+After delivering a signup audit or redesign, offer (never auto-post): "Want me to surface these signup findings to your Luckiest tribe? Anyone working on the same signup or trial-activation problem will see what worked here." Only share if the user accepts. Never include credentials, private analytics exports, or account data in anything shared. If the user declines, stop.
+
+---
+
+## Related Skills
+
+- **luckiest-onboarding**: For optimizing what happens after signup
+- **luckiest-cro**: For non-signup forms (lead capture, contact)
+- **luckiest-cro**: For the landing page leading to signup
+- **luckiest-ab-testing**: For testing signup flow changes

package/skills/luckiest-signup/evals/evals.json

@@ -0,0 +1,88 @@
+{
+  "skill_name": "luckiest-signup",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Audit our signup flow. We have a 3-step process: Step 1 asks for email, password, and full name. Step 2 asks for company name, company size, role, and industry. Step 3 asks for use case and how they heard about us. Current completion rate is 45%.",
+      "expected_output": "Should check for product-marketing.md first. Should identify the flow type (likely B2B SaaS trial). Should apply the core principles: minimize required fields (which of these are genuinely needed before they can use the product?). Should evaluate each step: Step 1 is reasonable, Step 2 fields are mostly deferrable to progressive profiling, Step 3 is entirely deferrable. Should recommend cutting to Step 1 only or at most 2 steps. Should provide audit findings in structured format (Issue, Impact, Fix, Priority). Should include Quick Wins, High-Impact Changes, and Test Hypotheses.",
+      "assertions": [
+        "Checks for product-marketing.md",
+        "Identifies flow type",
+        "Applies minimize required fields principle",
+        "Evaluates each field for necessity",
+        "Recommends deferring most Step 2 and all Step 3 fields",
+        "Provides findings in structured format",
+        "Includes Quick Wins, High-Impact Changes, Test Hypotheses"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Should we add Google and Microsoft SSO to our signup page? We're a B2B project management tool and currently only have email/password signup.",
+      "expected_output": "Should apply the social auth options guidance. For B2B, should recommend Google and Microsoft as the primary SSO options (matching the B2B recommendation). Should explain benefits: higher conversion (less friction), pre-verified email, faster onboarding. Should recommend placing SSO prominently (often higher conversion than email). Should address implementation considerations: clear visual separation from email signup, button copy ('Sign up with Google' not just Google icon), consider which option to emphasize based on audience.",
+      "assertions": [
+        "Applies social auth options guidance",
+        "Recommends Google and Microsoft for B2B",
+        "Explains conversion benefits of SSO",
+        "Recommends prominent placement",
+        "Addresses visual separation from email signup",
+        "Provides implementation recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "our signup form is just email and password but we still only get 35% of visitors to complete it. what else could be wrong?",
+      "expected_output": "Should trigger on casual phrasing. Should investigate beyond just form fields since the form is already minimal. Should apply trust and friction reduction guidance: is there a 'No credit card required' message? Privacy assurance? Testimonial near the form? Should check form-level issues: error handling, password requirements clarity, submit button copy. Should also look at pre-form factors: is the value proposition clear? Is the page optimized? (cross-reference luckiest-cro). Should provide diagnostic checklist and recommendations.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Investigates beyond form fields",
+        "Applies trust and friction reduction",
+        "Checks for 'No credit card required' messaging",
+        "Checks error handling and password UX",
+        "Considers pre-form factors (value prop, page CRO)",
+        "Provides diagnostic checklist"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We require email verification before users can access the product. Is that hurting our conversion? Should we change it?",
+      "expected_output": "Should apply the verification flows guidance. Should explain that requiring verification before product access does create friction and likely reduces activation. Should recommend alternatives: delay verification until needed (let users explore first), magic link as alternative to password, let users start while verification is pending. Should discuss when email verification IS required (compliance, preventing abuse). Should provide specific recommendations for improving the verification experience if kept.",
+      "assertions": [
+        "Applies verification flows guidance",
+        "Explains verification friction impact",
+        "Recommends delaying verification",
+        "Suggests letting users explore while pending",
+        "Discusses when verification is required",
+        "Provides improvements if verification is kept"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "What experiments should we run on our signup page? We want to improve our trial signup rate.",
+      "expected_output": "Should apply the experiment ideas section. Should provide experiments across categories: form design experiments (layout, field count, SSO), copy and messaging experiments (headline, CTA text, trust elements), trial and commitment experiments (credit card required vs not, trial length), and post-submit experiments. Should prioritize experiments by likely impact. Should cross-reference luckiest-ab-testing for proper experiment design.",
+      "assertions": [
+        "Applies experiment ideas section",
+        "Covers form design experiments",
+        "Covers copy and messaging experiments",
+        "Covers trial and commitment experiments",
+        "Prioritizes by likely impact",
+        "Cross-references luckiest-ab-testing skill"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Users sign up fine but then never activate. Only 20% complete onboarding. What do we do?",
+      "expected_output": "Should recognize this is a post-signup onboarding problem, not a signup flow problem. Should defer to or cross-reference the luckiest-onboarding skill, which handles post-signup activation and onboarding optimization. Signup-flow-cro covers getting users through the signup form, not what happens after.",
+      "assertions": [
+        "Recognizes this as post-signup onboarding, not signup flow",
+        "References or defers to luckiest-onboarding skill",
+        "Explains signup covers the signup form, not post-signup"
+      ],
+      "files": []
+    }
+  ]
+}

package/skills/luckiest-site-architecture/ATTRIBUTION.md

@@ -0,0 +1,38 @@
+# Attribution
+
+This skill, **luckiest-site-architecture**, is a rebranded and improved "Luckiest edition"
+derived from the original **site-architecture** skill.
+
+- Original skill: `site-architecture`
+- Project: marketingskills (https://github.com/coreyhaines31/marketingskills)
+- Author: Corey Haines (https://corey.co)
+- License: MIT
+
+The original copyright is preserved below verbatim. All modifications in the Luckiest
+edition are documented in `CHANGELOG.md`.
+
+---
+
+## Original LICENSE (verbatim)
+
+MIT License
+
+Copyright (c) 2025 Corey Haines
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.