Frontend Engineering

Q: Why use Frontend Engineering on TypingMind?

Because you install it once and use it with any model. Frontend Engineering 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.

Q: How do I install Frontend Engineering in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/DevelopersGlobal/ai-agent-skills/tree/main/skills/frontend-engineering. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Q: Which AI models can use Frontend Engineering?

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.

Q: How many AI models can I use with Frontend Engineering?

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

Q: Is the Frontend Engineering AI skill free?

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

Q: 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.

Q: 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.

Organization

DevelopersGlobal

frontend-engineering

Accessible, performant, responsive UI patterns. Component design, state management discipline, and Core Web Vitals compliance.

Overview

Publisher	DevelopersGlobal
Repository	`ai-agent-skills`
Skill name	`frontend-engineering`
Stars	212
Forks	33
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

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.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by DevelopersGlobal on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/DevelopersGlobal/ai-agent-skills/tree/main/skills/frontend-engineering
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/DevelopersGlobal/ai-agent-skills/tree/main/skills/frontend-engineering

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

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/DevelopersGlobal/ai-agent-skills.git /tmp/ai-agent-skills
mkdir -p .claude/skills
cp -r /tmp/ai-agent-skills/skills/frontend-engineering .claude/skills/frontend-engineering

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Frontend Engineering 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 Frontend Engineering 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 Frontend Engineering 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.

Overview

Frontend code touches every user. Poor UI engineering causes accessibility barriers, performance degradation, and broken experiences on non-standard devices. This skill enforces the discipline of building UI that works for everyone.

When to Use

Building any user-facing UI component
Reviewing frontend PRs
Before any UI ships to production

Process

Step 1: Accessibility First

Every interactive element has a visible focus state.
All images have meaningful alt text (or alt="" for decorative).
Color contrast ratio ≥ 4.5:1 for normal text.
All functionality operable by keyboard alone.
Use semantic HTML: <button> not <div onclick>, <nav> not <div class="nav">.

Verify: Run axe DevTools or Lighthouse accessibility audit. Score ≥ 90.

Step 2: Performance (Core Web Vitals)

LCP (Largest Contentful Paint) < 2.5s: Optimize images, preload critical resources.
FID/INP < 100ms: Avoid long tasks on the main thread.
CLS (Cumulative Layout Shift) < 0.1: Reserve space for dynamic content.
Lazy load below-the-fold images and non-critical JS.
Bundle size: measure before and after. No unneeded dependencies.

Verify: Lighthouse performance score ≥ 80. CWV within targets.

Step 3: Responsive Design

Test at 320px, 768px, 1024px, 1440px viewports.
No horizontal scrolling at any standard viewport.
Touch targets ≥ 44px × 44px.

Step 4: State Management Discipline

Server state vs. client state are separate concerns — don't mix.
No prop drilling more than 2 levels — use context or state management.
Loading, error, and empty states handled for every async operation.

Verify: Loading, error, and empty states all visible in Storybook/dev environment.

Common Rationalizations (and Rebuttals)

Excuse	Rebuttal
"Accessibility is for edge cases"	1 in 4 adults has a disability. It's not an edge case.
"We'll optimize performance later"	Users leave after 3 seconds. "Later" is too late.

Verification

Accessibility audit score ≥ 90
Core Web Vitals within targets
Responsive at 320px/768px/1024px/1440px
Loading, error, empty states handled
All interactive elements keyboard-operable

Frequently asked questions

What does the Frontend Engineering AI skill do?

Accessible, performant, responsive UI patterns. Component design, state management discipline, and Core Web Vitals compliance.

Why use Frontend Engineering on TypingMind?

Because you install it once and use it with any model. Frontend Engineering 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 Frontend Engineering in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/DevelopersGlobal/ai-agent-skills/tree/main/skills/frontend-engineering. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Frontend Engineering?

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 Frontend Engineering?

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

Is the Frontend Engineering AI skill free?

Yes. It is published on GitHub by DevelopersGlobal 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

Diagram Maker

openclaw

OrganizationPopular

Create SVG/HTML or Excalidraw diagrams for concepts, architecture, flows, and whiteboards.

Grill With Docs

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Grill Me

A relentless interview to sharpen a plan or design.

Brand Discovery

Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Overview

When to Use

Process

Step 1: Accessibility First

Step 2: Performance (Core Web Vitals)

Step 3: Responsive Design

Step 4: State Management Discipline

Common Rationalizations (and Rebuttals)

Verification

References

Frequently asked questions

Related AI Skills

Set up your own AI workspace now