Visual and interface quality
Design System Skills: Visual, UX, and Interface Quality
A public design engine for typography, colour, layout, UX, interfaces, content design, accessibility, visual assets, presentations, documents, and anti-AI-slop quality.
Inspect on GitHub Design System SkillsRepository facts verified locally on 22 August 2026
Direct answer
Design System Skills owns the visual and interaction layer: choosing type, colour, composition, UI patterns, UX research, accessibility, design tokens, visual assets, and presentation quality. It helps teams make deliberate visual decisions instead of allowing generic AI defaults to determine the result.
Who it serves
Designers, developers, product teams, document and presentation authors, and organisations that need coherent, accessible, human-reviewed visual systems.
89
Active skills in latest repository note
Visual quality
Primary domain
Accessibility
Cross-cutting gate
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.
- Typography, colour, brand identity, layout, grid, composition, motion, responsive interface, and design tokens.
- UX research, psychology, sector-specific interface patterns, conversion, content design, and user flows.
- Web, app, mobile, game, dashboard, document, presentation, and spreadsheet visual quality routes.
- Accessibility, visual QA, ethics, performance, imagery, illustration, and anti-AI-slop design doctrine.
How to use it
A repeatable route from request to evidence
Read the context
Understand the audience, sector, content, brand, device reality, accessibility needs, and product constraints.
Choose the system
Set type, colour, spacing, composition, components, imagery, interaction, and responsive rules before polishing screens.
Design the experience
Apply the system to the actual page, product, document, or deck while preserving content hierarchy and user goals.
Inspect and improve
Run visual, accessibility, responsive, motion, content, and anti-slop checks, then record what should be standardised.
Good fit
When to use this engine
- A website, application, dashboard, document, or deck looks generic, inconsistent, inaccessible, or difficult to use.
- A delivery needs a design system, tokens, responsive rules, typography, imagery, or interface quality gate.
- AI-assisted visual output needs a human visual direction and anti-slop review.
- A technical engine needs a deliberate presentation layer without copying design doctrine into the engineering repository.
Boundaries
What it does not replace
- It owns visual and presentation decisions, not the underlying software architecture or formal requirements structure.
- Content truth, research evidence, and professional claims remain with the relevant content, research, finance, or domain engine.
- It does not make a product usable by styling alone; content, IA, implementation, accessibility, and testing still matter.
- 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
Website Skills
Join visual decisions to website strategy, content, SEO, performance, deployment, and handover.
SRS Skills
Keep the structure and acceptance logic of formal software documentation in the SDLC documentation engine.
Design System Skills on GitHub
Inspect the public visual and interface skill engine.
Frequently asked
Questions about Design System Skills
What does Design System Skills control?
It controls typography, colour, layout, composition, UX, UI, design tokens, imagery, accessibility, visual quality, and presentation-layer decisions.
What does anti-AI-slop mean here?
It means reviewing whether a visual result is generic, templated, incoherent, inaccessible, or disconnected from the real audience and product context.
Does it replace a frontend engineer?
No. It defines and reviews the visual and interaction system; implementation belongs to the appropriate engineering or website engine.
Ready to discuss your project?
Every engagement begins with a conversation. Book a consultation to explore how Peter's experience can serve your organisation.