Signup Login Page Generator
Structure, optimize, or audit dedicated signup and login pages—including domains, modals, discounts at registration, and auth SEO—for your solo SaaS funnel.
Overview
signup-login-page-generator is an agent skill most often used in Build (also Validate landing funnels and Launch SEO for auth URLs) that guides signup and login page structure, domains, discounts, and SEO.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill signup-login-page-generatorWhat is this skill?
- Initial assessment: goals (trial vs paid), discounts at signup, self-built vs Clerk/Auth0, and audience segments
- Domain and URL matrix for main domain vs auth subdomain choices
- Guidance on modal vs dedicated signup page and tie-in to landing and pricing conversion
- Student discount and promo-at-registration called out as P0 placement on signup
- Reads .claude/project-context.md or .cursor/project-context.md when present for product and offer context
- metadata version 1.0.1
Adoption & trust: 691 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are adding accounts to your app but unsure whether auth lives on a subdomain, a modal, or a dedicated page—and how discounts and SEO should work at registration.
Who is it for?
Indie SaaS founders implementing or refactoring registration after landing and pricing pages are live.
Skip if: Pure email newsletter capture or full landing-page copy strategy—use newsletter-signup-generator or landing-page-generator instead.
When should I use this skill?
When the user wants to create, optimize, or audit signup and login pages, or mentions signup page, login page, registration page, auth page, student discount at signup, or auth subdomain.
What do I get? / Deliverables
You get a structured signup/login plan covering URLs, page type, discount placement, provider choice, and SEO notes aligned with your landing and pricing funnel.
- Signup/login structure recommendation
- Domain and URL strategy table
- Discount and SEO checklist for auth pages
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Signup and login are core product surfaces built in the Build phase, even though they convert traffic from earlier marketing pages. Frontend subphase covers auth UI, routing, and registration flows that agents implement or refactor.
Where it fits
Choose dedicated /signup route versus modal after picking Clerk and annual billing.
Ensure landing CTAs match the registration URL and discount rules before you code the page.
Decide indexing policy for login versus signup URLs without blocking legitimate discovery pages.
How it compares
Pair with landing-page-generator for acquisition copy; this skill owns the auth conversion page and registration discounts, not the hero landing narrative.
Common Questions / FAQ
Who is signup-login-page-generator for?
It is for solo builders and small teams using agentic coding tools who need disciplined signup/login architecture tied to marketing funnels and optional student or promo discounts.
When should I use signup-login-page-generator?
Use it when creating or auditing signup pages, login pages, auth subdomains, or registration discounts—typically while building frontend auth, after a validate-phase landing draft, or when tuning launch-time indexing for auth URLs.
Is signup-login-page-generator safe to install?
Check the Security Audits panel on this catalog entry and review the skill sources locally; do not assume pass/fail counts or star ratings beyond what Prism lists.
SKILL.md
READMESKILL.md - Signup Login Page Generator
# Pages: Signup / Login Guides signup and login page structure, domain choice, modal vs dedicated page, discount integration, and SEO. Signup is the conversion endpoint from landing pages and pricing; when discounts apply at registration (e.g., student discount), signup is the P0 placement. Distinct from **landing-page-generator** (acquisition); **newsletter-signup-generator** (email capture only). **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and offers. Identify: 1. **Goal**: Account creation, trial, paid signup 2. **Discounts**: Student, annual, promo code—apply at signup? 3. **Auth**: Self-built vs third-party (Auth0, Clerk, etc.) 4. **Audience**: General vs segmented (students, startups) ## Domain & URL | Option | Use | |--------|-----| | **Main domain** | /signup, /login, /auth; simple; common for SaaS | | **Subdomain** | auth.example.com; Universal Login pattern; credentials not cross-origin; requires Cookie domain config for cross-subdomain session | | **Third-party** | Redirect to Auth0, Clerk, etc.; provider hosts auth | **Paths**: /signup, /login, /register, /auth; keep short and consistent. ## Modal vs Dedicated Page | Approach | Use | |----------|-----| | **Dedicated page** | Account creation; discount verification; student verification; higher-quality leads; fewer fake emails | | **Modal / popup** | Lightweight lead capture; newsletter; quick demo request; lower quality, higher volume | **When discount applies at signup** (e.g., student 30% off): Use **dedicated page**—user needs space for verification, discount display, and form. Modal can work for simple email-only capture; avoid for full account + verification flows. **Mobile**: Google penalizes intrusive interstitials; dedicated page avoids penalty. ## Page Structure | Section | Purpose | |---------|---------| | **Headline** | Value-focused; "Start free" or "Students: 30% off today, 15% off ongoing" | | **Trust signals** | SSL, payment logos, privacy, customer logos; see **trust-badges-generator** | | **Media** | Product screenshot, short video, or demo GIF above fold; reinforces value | | **Form** | Minimal fields; email first; social login (Google, GitHub) reduces friction | | **Discount block** | Student discount, annual discount, promo code; verification entry when applicable | | **Privacy / Terms** | Links; compliance | ## Discount Integration ### Student / Education (education-program) | Element | Placement | |---------|-----------| | **Headline or subhead** | "Students: 30% off today, 15% off ongoing" | | **Verification** | .edu, SheerID, UNiDAYS; verify at signup to apply discount | | **Eligibility** | Brief eligibility; link to full terms | **P0 placement**: When student discount applies at registration, signup page is primary; pricing page and homepage banner are P1. ### Other Discounts - **Annual discount**: Show when user selected annual plan from pricing; confirm before submit - **Promo code**: "Have a code?" link or inline field; validate before or after submit ## Form & Verification - **Minimal fields**: Email only when possible; add name only if needed; see **newsletter-signup-generator** - **Social login**: Google, GitHub; reduces friction; faster than email form - **Verification entry**: .edu (instant), Sheer