Dev.to WebDev 🛠 Dev 👁 0 📖 4 min read

Frontend Developers Are Going to Be Fine... Right?

As a frontend or full-stack software developer, what skills really matter today? We know that AI is writing 90% of our projects, so what should we specialize in? Let's take a look. I really feel like some skills will se

Frontend Developers Are Going to Be Fine... Right?

As a frontend or full-stack software developer, what skills really matter today? We know that AI is writing 90% of our projects, so what should we specialize in? Let's take a look.

I really feel like some skills will set you apart today. Here are five skills you should pay attention to today, if you want to stay ahead of the curve.

1. Architecture

Mission 01 slide: Architecture, with tiles for where state lives and how the page renders

You don't need to memorize every API anymore, but you do need to know what a good architecture looks like before the agent starts. Adam Jacob said on Syntax that if you don't pick an architecture, the agent picks whatever feels right in the moment, and that's why a vibe-coded app gets worse with every feature you add.

For example, where does state live? I use Pinia in Vue, so I tell the agent that up front and save it in a steering file. Also, how does the page load? A static site, server-side rendering, and a single page app all suit different projects. If you don't say, the agent guesses. I don't like that.

2. Debugging

Mission 02 slide: Debugging, with a big 66% stat and three steps

In the 2025 Stack Overflow survey, the top frustration with AI tools was code that's almost right. It compiles, looks fine in review, and breaks on an edge case. 45% said debugging AI-generated code takes longer than debugging their own.

You can paste the error back into the agent, and sometimes that's enough. When the agent tries the same fix twice, stop it and look yourself. Read the stack trace in the console. Check the network tab for a 401 or a CORS error. Open Vue DevTools or React DevTools and see what the component is doing.

3. Verification

Mission 03 slide: Verification, a pipeline from agent edit through types, lint, black-box tests, and rule review to you review

I was just at the AI Engineer Summit in San Francisco, and software factories and verification came up in talk after talk. How do you know the code the agent wrote does what you expect?

My answer is deterministic guardrails. Add the right linters. Write black-box tests with Playwright that use the app the way a user would. Keep your rules in steering files or AGENTS.md. Every check runs on every change and gives the same answer each time, so the agent can't talk its way past it.

Then review the code yourself. Some projects push hundreds of commits a day through a fully automated factory. If you're a web developer at a company like most of us, you're still doing code reviews, and you should be.

4. Accessibility

Mission 04 slide: Accessibility, with an encode, automate, improve loop around every UI change

I'm a big accessibility fan, and I think you should be too. WebAIM scanned the top million home pages and found detectable WCAG failures on about 96% of them.

Start by writing your rules into a review skill. You can download WCAG skills, but I'd write your own with rules specific to your app.

Then automate it. I use a Kiro hook that runs an accessibility review skill every time the agent finishes a task. I went further with Kiro Crew and set up a bot that checks my site in the middle of the night, then sends me a report or opens a PR with fixes. When it misses something, add that case to the skill so it catches it next time.

Then test it with a screen reader yourself. Not every day, but every time you ship a new feature.

5. Taste and product sense

Mission 05 slide: Taste and product sense, build it better than the default

I can usually tell when a site came straight out of one prompt with no changes. So can a lot of people, so be careful.

Use the tools to build and design, but stay critical of what they give you. To be transparent, I made the slides (and some of this blog post) with Kiro. I wanted the video to have a sunset beach look inspired by open-world games, and the first versions looked like every other AI deck. It took a lot of rounds to get there.

Peter Steinberger said in an interview with Amigoscode that high agency is the most important skill now. When you pitch a feature, bring something working so people can react to a real thing. A rough prototype is enough, even one drawn in Windows Paint.

The big picture

Build the machine that builds the machine, with automated checks, automated review, and human review

Adam Jacob described this as building the machine that builds the machine. Matt Pocock compared it to learning to drive, where you learn the brakes before the accelerator. Automated checks, automated review, and human review are the brakes, and humans are still part of that list.

Thanks! Let me know in the comments what you think!

Credits

A lot of these ideas came from other people, and they're worth your time.

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.