Website strategy and delivery
Website Skills: From Brief to Search-Ready Website Delivery
A public website engine for strategy, information architecture, content, UX, accessibility, performance, SEO, analytics, deployment, launch, handover, and post-launch improvement.
Inspect on GitHub Website SkillsRepository facts verified locally on 22 August 2026
Direct answer
Website Skills gives a team a reviewable route from a website brief to a maintainable, measurable product. It joins qualification, information architecture, content production, accessibility, performance, SEO, analytics, security, deployment, launch operations, and handover.
Who it serves
Website practitioners, agency delivery teams, organisations improving discovery and conversion, and teams that need explicit launch and recovery gates.
60
Active skills reported
Maintainable websites
Primary output
SEO · A11y · Speed
Core quality gates
main
Repository branch
Non-negotiable operating rule
Human in the middle. Every time.
Nothing is considered finished merely because an AI tool or skills engine produced it. A responsible person reviews the facts, logic, sources, calculations, code, security, privacy, context, and quality of the output before it is published, deployed, submitted, or used to make a decision. For some actions, the engine must stop until the user explicitly types that they approve the action; approval must never be inferred from silence or a vague request.
Human responsibility: approve, correct, escalate, reject, stop, or roll back the work.
Engine responsibility: make the method, evidence, limits, review points, and approval pauses visible.
In practice
A second view of the work this engine supports
The visuals illustrate the domain; they do not replace evidence, controls, or the human review required before a consequential decision or action.
Capability map
What this engine covers
The list below is a plain-language summary of the repository's verified capability surface. It is not a promise that every project needs every skill.
- Qualification, intake, positioning, information architecture, content planning, page production, and conversion journeys.
- Accessibility, performance, security, analytics, SEO, structured data, content quality, and search discovery.
- Photo and visual asset handling, deployment, launch operations, rollback, onboarding, maintenance, and handover.
- Evidence-backed post-launch improvement using the Observe → Baseline → Select → Experiment → Check → Standardise → Re-measure loop.
How to use it
A repeatable route from request to evidence
Qualify and research
Confirm the audience, offer, content truth, market, source evidence, permissions, success measure, and delivery constraints.
Shape the experience
Build the information architecture, page intents, content system, visual direction, responsive behaviour, and conversion path.
Build and verify
Implement the pages, optimise imagery, check accessibility, performance, SEO, security, analytics, and mobile behaviour.
Launch and improve
Release with evidence, hand over ownership and recovery steps, then use real data to prioritise improvements.
Good fit
When to use this engine
- You need a search-ready website that is fast, accessible, multilingual, and built from verified content.
- A marketing or service site needs stronger information architecture, conversion paths, internal links, or SEO.
- A team needs photo, content, analytics, launch, rollback, or handoff discipline rather than just page mockups.
- A website project crosses into application engineering or visual design and needs clean specialist boundaries.
Boundaries
What it does not replace
- Custom application engineering, APIs, databases, and production software belong with Chwezi Dev Engine.
- Typography, visual identity, UI craft, and visual anti-slop doctrine belong with Design System Skills.
- Current external claims, market evidence, laws, and standards need research and source verification.
- It does not create evidence merely by writing confidently; source claims and project facts still need verification.
- It does not remove accountable human review, specialist judgement, approval authority, or professional sign-off.
- It does not authorise live account changes, client communications, production changes, or submissions without explicit permission.
Continue the route
Related first-party guidance
East Africa website delivery
See the site's existing service page for multilingual and affordable website delivery in East Africa.
Design System Skills
Use the visual engine when the work needs deliberate typography, layout, UI, or brand decisions.
Website Skills on GitHub
Inspect the public website delivery engine and its quality gates.
Frequently asked
Questions about Website Skills
What does Website Skills cover?
It covers website strategy, information architecture, content, UX, accessibility, performance, security, SEO, analytics, deployment, launch operations, handover, and improvement.
Is Website Skills the same as a page generator?
No. It is a delivery and operating system for turning a brief and verified assets into a maintainable website with quality and recovery gates.
Which engine handles visual design?
Design System Skills owns typography, visual identity, UI/UX, interface craft, visual assets, and anti-visual-slop decisions.
Ready to discuss your project?
Every engagement begins with a conversation. Book a consultation to explore how Peter's experience can serve your organisation.