NoamanKhalil/WebSkills

WebSkills to build a website with the best development principles.

1

3 commits

updated Sep 20, 2026

See the code

See what people are saying (1)

SourceMessageScoreDate

Skills to Make the Perfect Website

2

Sep 21, 2026

README

WebSkills

WebSkills to build a website with the best development principles.

Most launches don't fail on the feature — they fail on the boring stuff around it: a contact form that dies silently, a sitemap nobody generated, a cookie banner that isn't actually legal, a tests/ folder shipped straight to production. None of it shows up in a demo. All of it shows up the week after launch, as a support ticket, a bounced compliance review, or a domain blocklisted for something a stranger uploaded through your own site.

This skill is the difference between "looks done" and "is done." Point it at any project — static site, SPA, full-stack app, something already live — and it works out what the site actually does, asks you the handful of business facts only you know, then runs a real audit: not a generic checklist ticked from memory, but grep results, curl output, and DNS lookups against your code and your domain. It skips what doesn't apply instead of padding the report, refuses to invent a business address or a tracking ID just to fill a blank, and explains why each item matters in plain language — so whoever reads the report walks away understanding the site better, not just holding a longer to-do list.

Built by Noaman Khalil with over 6 years of experience on building products.

Contributors

NoamanKhalil

3 commits

NoamanKhalil/WebSkills

WebSkills to build a website with the best development principles.

1

3 commits

updated Sep 20, 2026

See the code

See what people are saying (1)

SourceMessageScoreDate

Skills to Make the Perfect Website

2

Sep 21, 2026

README

WebSkills

WebSkills to build a website with the best development principles.

Most launches don't fail on the feature — they fail on the boring stuff around it: a contact form that dies silently, a sitemap nobody generated, a cookie banner that isn't actually legal, a tests/ folder shipped straight to production. None of it shows up in a demo. All of it shows up the week after launch, as a support ticket, a bounced compliance review, or a domain blocklisted for something a stranger uploaded through your own site.

This skill is the difference between "looks done" and "is done." Point it at any project — static site, SPA, full-stack app, something already live — and it works out what the site actually does, asks you the handful of business facts only you know, then runs a real audit: not a generic checklist ticked from memory, but grep results, curl output, and DNS lookups against your code and your domain. It skips what doesn't apply instead of padding the report, refuses to invent a business address or a tracking ID just to fill a blank, and explains why each item matters in plain language — so whoever reads the report walks away understanding the site better, not just holding a longer to-do list.

Built by Noaman Khalil with over 6 years of experience on building products.

Contributors

NoamanKhalil

3 commits