God Ui Ux logo

God Ui Ux

Community
cumabozkurt
god-ui-ux

Web and product UI/UX design and implementation - landing pages, marketing sites, SaaS apps, dashboards, e-commerce, forms, navigation, component states, UX laws, information architecture, microcopy, responsive behavior and production HTML/CSS/Tailwind/React output. Use when designing or building any website or web app interface, improving UX, or turning a design into front-end code.

Overview

Publishercumabozkurt
Repositorygod-of-design
Skill namegod-ui-ux
Stars
7
Forks
1
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by cumabozkurt on GitHub. Read the source before you install it.

Installation

Install the God Ui Ux AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/cumabozkurt/god-of-design/tree/main/skills/god-ui-ux
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/cumabozkurt/god-of-design.git /tmp/god-of-design
mkdir -p .claude/skills
cp -r /tmp/god-of-design/skills/god-ui-ux .claude/skills/god-ui-ux
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable God Ui Ux in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads God Ui Ux on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so God Ui Ux is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

God UI/UX

Procedure

  1. Job and flow. Write the primary user job ("compare plans and start a trial in < 60 s"). Sketch the flow: entry → key decision → action → confirmation. Remove steps.
  2. Information architecture. List the content blocks in priority order. Each section answers one question.
  3. Direction + tokens. Use god-styles and god-tokens. Define tokens before writing components.
  4. Build the components with all states: default, hover, focus-visible, active, disabled, loading, empty, error, success. Also skeleton and overflow (long text, long Turkish/German words, RTL).
  5. Responsive pass: 320, 375, 768, 1024, 1440px. Touch targets ≥ 44×44px (WCAG 2.5.8 requires a 24×24 minimum; Apple and Google recommend 44pt/48dp).
  6. Accessibility pass (god-accessibility) and anti-slop pass (god-anti-slop).
  7. Ship. Semantic HTML, no layout shift (reserve image sizes), lazy-load below the fold, prefers-reduced-motion and prefers-color-scheme support.

UX laws that change decisions

LawImplication
Hick's lawFewer choices → faster decisions. One primary CTA per view; group options.
Fitts's lawBig, close targets are faster. Put primary actions near the thumb or cursor path.
Jakob's lawUsers expect conventions: logo top-left → home, cart top-right, underlined links.
Miller / chunkingChunk info (phone numbers, steps, cards of 3–5 items).
Doherty thresholdRespond in < 400ms. Use optimistic UI and skeletons.
Peak-end rulePolish the key moment and the ending (success states, receipts).
Aesthetic-usability effectBeautiful feels easier, but it doesn't excuse broken usability.
Tesler's lawComplexity has to live somewhere. Absorb it in the system, not in the user.
Von RestorffThe different thing gets remembered. Make the CTA distinct, and only the CTA.
Serial positionFirst and last items are remembered. Put key nav at the ends.

Page patterns

Landing page (in order, adapt freely): nav (logo, 3–5 links, 1 CTA) → hero (specific headline ≤ 10 words + subline + primary CTA + product visual or proof) → social proof (logos/metrics) → problem → solution features (varied layouts) → how it works → testimonials (real names, faces, roles) → pricing → FAQ → final CTA → footer. Headline formula: a concrete outcome for a specific audience. Avoid "Unlock the power of…", "Revolutionize…", "Seamless…".

Dashboard: global nav (left rail) → page title + date range + primary action → KPI row (3–5 metrics with delta and sparkline) → main chart → table with filters → secondary panels. Density: 8pt grid, 13–14px tables, tabular numbers, sticky headers.

Forms: single column, labels above fields (never placeholder-only), inline validation on blur, error text that says how to fix, mark optional fields rather than required ones, right input types (email, tel, inputmode="numeric"), autocomplete attributes, a primary button that states the action ("Create account", not "Submit").

E-commerce product page: gallery (zoom, 4–8 images, video) → title, price, rating → variant pickers with real swatches → stock and delivery estimate → add to cart (sticky on mobile) → trust (returns, secure payment) → details accordion → reviews → related items.

Navigation: ≤ 7 top-level items; current page indicated; mobile uses a bottom tab bar (apps) or a full-screen menu with large targets (web); breadcrumbs for deep IA; search for > 50 pages.

Component recipes

See references/components.md for buttons, inputs, cards, modals, toasts, tables, tabs, navbars, pricing tables, empty states and their Tailwind implementations. See references/microcopy.md for writing UI text.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the God Ui Ux AI skill do?

Web and product UI/UX design and implementation - landing pages, marketing sites, SaaS apps, dashboards, e-commerce, forms, navigation, component states, UX laws, information architecture, microcopy, responsive behavior and production HTML/CSS/Tailwind/React output. Use when designing or building any website or web app interface, improving UX, or turning a design into front-end code.

Why use God Ui Ux on TypingMind?

Because you install it once and use it with any model. God Ui Ux is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install God Ui Ux in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cumabozkurt/god-of-design/tree/main/skills/god-ui-ux. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use God Ui Ux?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with God Ui Ux?

As many as you like. As long as a model supports skills, you can use God Ui Ux with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the God Ui Ux AI skill free?

Yes. It is published on GitHub by cumabozkurt under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇