signup-login-page-generator
When the user wants to create, optimize, or audit signup and login pages. Also use when the user mentions "signup page," "login page," "registration page," "auth page," "sign up form," "create account," "student discount at signup," or "auth subdomain." For indexing/auth URLs, use indexing.
Best use case
signup-login-page-generator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
When the user wants to create, optimize, or audit signup and login pages. Also use when the user mentions "signup page," "login page," "registration page," "auth page," "sign up form," "create account," "student discount at signup," or "auth subdomain." For indexing/auth URLs, use indexing.
Teams using signup-login-page-generator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/signup-login/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How signup-login-page-generator Compares
| Feature / Agent | signup-login-page-generator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
When the user wants to create, optimize, or audit signup and login pages. Also use when the user mentions "signup page," "login page," "registration page," "auth page," "sign up form," "create account," "student discount at signup," or "auth subdomain." For indexing/auth URLs, use indexing.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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), SheerID/UNiDAYS (broader); see **education-program** - **Progressive**: Collect email first; verify student; then complete profile if needed ## SEO | Page | Meta | Reason | |------|------|--------| | **Login** | `noindex, nofollow` | No search value; security risk; indexed login pages can confuse users | | **Signup** | `noindex, follow` | Block from SERP; allow crawl of links (Privacy, Terms) | **Implementation**: Use `<meta name="robots" content="noindex">` or `X-Robots-Tag` header. robots.txt does not prevent indexing—crawlers must access the page to read the directive. See **indexing** for full noindex page-type list. ## Output Format - **Domain** and URL choice - **Modal vs page** recommendation - **Structure** (headline, trust, media, form, discount block) - **Discount** integration (student, annual, promo) - **SEO** meta tags - **Related** skills for execution ## Related Skills - **indexing**: Full noindex page-type list; noindex,follow vs noindex,nofollow - **education-program**: Student discount at signup (P0); verification; placement - **landing-page-generator**: Signup is CTA destination; landing page structure applies to signup when signup is conversion endpoint - **popup-generator**: Modal option for lightweight capture; signup as full form → dedicated page - **newsletter-signup-generator**: Form design; minimal fields; trust signals - **trust-badges-generator**: Trust signals on signup - **pricing-page-generator**: Pricing CTA → signup; annual discount flows to signup - **website-structure**: /login, /signup in Standalone paths
Related Skills
page-metadata
When the user wants to optimize meta tags other than title, description, Open Graph, or Twitter Cards. Also use when the user mentions "hreflang," "meta robots," "viewport," "charset," "canonical meta," "other meta tags," "meta robots noindex," "meta robots nofollow," "hreflang tags," "viewport meta," or "meta charset." For title tags, use title-tag. For meta descriptions, use meta-description. For Facebook/LinkedIn previews, use open-graph. For X previews, use twitter-cards.
status-page-generator
When the user wants to create, optimize, or structure a status page. Also use when the user mentions "status page," "status.yourdomain.com," "uptime," "service health," "incident page," or "system status." For incident comms, use public-relations.
feedback-page-generator
When the user wants to create, optimize, or audit a feedback or roadmap page. Also use when the user mentions "feedback page," "roadmap," "feature requests," "vote on features," "Canny," "UserVoice," or "product feedback." For sitewide page planning, use website-structure.
disclosure-page-generator
When the user wants to create, optimize, or audit an affiliate, sponsor, or paid partnership disclosure page. Also use when the user mentions "disclosure," "affiliate disclosure," "sponsored content," "FTC disclosure," or "paid partnership." For sitewide page planning, use website-structure.
changelog-page-generator
When the user wants to create, optimize, or structure a changelog or release notes page. Also use when the user mentions "changelog," "release notes," "what's new," "updates," "product updates," "version history," or "changelog.yourdomain.com." For sitewide page planning, use website-structure.
use-cases-page-generator
When the user wants to create, optimize, or audit use case pages. Also use when the user mentions "use cases," "use case page," "for [role]," "by persona," "by scenario," "by business goal," "ICP pages," or "audience-specific pages." For sitewide page planning, use website-structure.
startups-page-generator
When the user wants to create, optimize, or audit a startups, education, or special program page. Also use when the user mentions "startups program," "for startups," "education discount," "student plan," "for students," or "special pricing." For education discounts, use education-program.
solutions-page-generator
When the user wants to create, optimize, or audit solutions pages. Also use when the user mentions "solutions," "solutions page," "by industry," "industry solutions," "by company size," "SMB," "enterprise," "by outcome," "business outcomes," or "how we solve X." For sitewide page planning, use website-structure.
showcase-page-generator
When the user wants to create, optimize, or audit a showcase or gallery page for user-generated content. Also use when the user mentions "showcase," "gallery," "user work," "UGC," "creator showcase," "examples," or "made with [product]." For social proof components, use testimonials-generator.
services-page-generator
When the user wants to create, optimize, or audit a services page. Also use when the user mentions "services page," "what we offer," "service offerings," "consulting services," "service page," "offerings page," "service catalog," or "professional services." For sitewide page planning, use website-structure.
products-page-generator
When the user wants to create, optimize, or audit a product listing or category page. Also use when the user mentions "product page," "product listing," "shop," "e-commerce products," "product catalog," "product grid," "product cards," or "product overview." For category SEO, use category-page-generator.
pricing-page-generator
When the user wants to create, optimize, or audit pricing page content and structure. Also use when the user mentions "pricing page," "pricing table," "plans," "subscription," "pricing plans," "pricing tiers," "pricing comparison," "SaaS pricing," "enterprise pricing," "API pricing," "contact sales," "pricing in nav," "public pricing," "hide pricing," or "pricing objection handling." For pricing strategy, use pricing-strategy.