skillboardUpdated every 6 hours
skillboardWhen the user wants to create, optimize, or audit contact page and forms. Also use when the user mentions "contact page," "contact form," "get in touch," "support form," "contact us," "reach us," "contact information," "support contact," or "inquiry form." For sitewide page planning, use website-structure.
Guides contact page design and form optimization for conversions.
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.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for brand voice.
Identify:
| Principle | Guideline | |-----------|-----------| | Short | 3-5 fields for basic contact; long forms increase abandonment | | Single column | Vertical layout; works better on mobile | | Logical grouping | Name+email together; address fields together | | Required fields | Mark clearly (asterisk); avoid surprises | | Progressive disclosure | Show relevant fields based on selections |
| Element | Guideline | |---------|-----------| | Visibility | "Contact" or "Support" in main nav, not just footer | | Mobile | Appropriate input types (tel for phone), large tap targets | | Proofreading | No typos--credibility at conversion moment | | Alternatives | Email, phone, chat if form isn't right |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/contact · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/contact"
cp -r "skills/pages/brand/contact" ".claude/skills/contact"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.