scaffolding-landing-pages
Skill0 starsChanged 4 months agoMITView on GitHub
Scaffolds responsive landing pages and small web projects - semantic HTML, clean CSS, vanilla JS for forms and interactions, and a deployment-ready file structure. Make sure to use this skill whenever the user wants a landing page, one-pager, marketing site, or basic web project built quickly, or mentions an HTML/CSS starter, hero section, contact form, or "web dev from scratch" - even if they don't explicitly ask for a "landing page".
In this repository19 other files it gives its agents.
- adding-authenticationSkill
- auditing-seoSkill
- automating-git-workflowsSkill
- building-email-sequencesSkill
- building-graphql-apisSkill
- building-wordpress-pluginsSkill
- designing-carouselsSkill
- fine-tuning-ml-modelsSkill
- handling-web-formsSkill
- n8n-automationSkill
- organizing-spreadsheetsSkill
- reviewing-cloudflare-workers-codeSkill
- reviewing-code-for-securitySkill
- setting-up-error-monitoringSkill
- setting-up-firebase-authSkill
- using-nextjs-best-practicesSkill
- working-with-postgres-databasesSkill
- writing-marketing-copySkill
- writing-terraform-codeSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Ask (or infer) what the page needs: hero, features, pricing, testimonials, FAQ, contact form, footer.
- Distinctive: line 30
Default for a single-page site (no framework needed unless the user asks for React/Vue):
- Distinctive: line 39
Don't reach for a build tool or framework unless the user needs multiple routes, a CMS, or component reuse across pages - a single-page …
- Very specific: line 43
Use real semantic elements, not div soup: <header>, <nav>, <main>, <section>, <footer>.
- Distinctive: line 49
Avoid pulling in a CSS framework (Bootstrap/Tailwind CDN) unless the user asks - a hand-written stylesheet for a single page is usually …
- Distinctive: line 53
Use vanilla JS for: mobile nav toggle, smooth scroll to anchors, form validation/submission, FAQ accordion.
- Very specific: line 60
All images have alt text
- Very specific: line 63
No render-blocking large images - suggest loading="lazy" for below-the-fold images
- Very specific: line 67
If the user wants this deployed, mention Netlify/Vercel/GitHub Pages as zero-config static hosts - don't assume which one without asking.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Scaffolding landing pages
Builds a responsive, dependency-light landing page: semantic HTML, clean CSS, and vanilla JS where interactivity is needed.
Workflow
Copy this checklist and track progress:
Progress:
- [ ] Step 1: Clarify sections and goal
- [ ] Step 2: Set up file structure
- [ ] Step 3: Build semantic HTML
- [ ] Step 4: Style responsively
- [ ] Step 5: Add interactions
- [ ] Step 6: Check accessibility and performanceStep 1: Clarify sections and goal
Ask (or infer) what the page needs: hero, features, pricing, testimonials, FAQ, contact form, footer. Confirm the primary call-to-action - a landing page should have exactly one main conversion goal.
Step 2: Set up file structure
Default for a single-page site (no framework needed unless the user asks for React/Vue):
project/
├── index.html
├── styles.css
└── script.jsDon't reach for a build tool or framework unless the user needs multiple routes, a CMS, or component reuse across pages - a single-page marketing site rarely does.
Step 3: Build semantic HTML
Use real semantic elements, not div soup: <header>, <nav>, <main>, <section>, <footer>. Every section needs a heading (h2) even if visually hidden, for accessibility and SEO. Include meta viewport and a real <title>/meta description.
Step 4: Style responsively
Mobile-first: write base styles for small screens, add @media (min-width: ...) for larger. Use CSS Grid/Flexbox for layout, CSS custom properties for the color palette and spacing scale so the whole page can be re-themed by editing a handful of variables at the top of the file.
Avoid pulling in a CSS framework (Bootstrap/Tailwind CDN) unless the user asks - a hand-written stylesheet for a single page is usually smaller and easier to customize.
Step 5: Add interactions
Use vanilla JS for: mobile nav toggle, smooth scroll to anchors, form validation/submission, FAQ accordion. Keep it framework-free unless the page's complexity genuinely requires state management.
For contact forms with no backend, wire to a form endpoint service (e.g. Formspree-style POST) or clearly mark where the user needs to plug in their own backend - never fabricate a working submission endpoint.
Step 6: Check accessibility and performance
Before delivering, verify:
- All images have
alttext - Color contrast is readable (don't rely on light gray text on white)
- Interactive elements are keyboard-reachable (real
<button>/<a>, not<div onclick>) - No render-blocking large images - suggest
loading="lazy"for below-the-fold images
Notes
- If the user wants this deployed, mention Netlify/Vercel/GitHub Pages as zero-config static hosts - don't assume which one without asking.
- For anything beyond a single page (multiple routes, a blog, a CMS-backed site), recommend a framework (Next.js/Astro) instead of hand-rolling more HTML files.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

