They fail because all the boring production details get skipped.

Things like:

• SEO metadata

• prerendering

• analytics

• social share images

• CSP headers

• Lighthouse optimization

• mobile polish

• sitemap generation

• robots.txt

• deployment configuration

• IndexNow

• caching

• environment setup

The actual React components are often the easy part now.

The operational infrastructure is what still slows everything down.

After building a few AI-assisted projects with Claude Code, I realized I was repeatedly solving the same problems over and over again. Not just visually, but operationally.

So instead of writing larger prompts, I started building reusable Claude Code skills.

The result became an open source repository of production-oriented workflows:

senternet-site-skills on GitHub

The repository contains reusable production-focused skills for things like SEO, prerendering, mobile optimization, social sharing, CSP configuration, Lighthouse tuning, analytics setup, deployment workflows, and more.

The Problem With “Vibe Coding”

I actually like AI-assisted development.

A lot.

Claude Code is incredibly powerful for:

• rapid iteration

• frontend generation

• restructuring layouts

• writing utility code

• integrating APIs

• content scaffolding

But after the initial excitement wears off, a pattern emerges:

The AI can generate pages faster than you can operationalize them.

You end up spending huge amounts of time fixing:

• SEO issues

• deployment inconsistencies

• broken metadata

• poor mobile behavior

• missing analytics

• performance regressions

• social preview problems

• incomplete production setup

And ironically, these are often the least exciting tasks for humans to repeatedly perform manually.

That made them perfect candidates for reusable skills.

From Giant Prompts to Reusable Workflows

At first, I tried solving this with increasingly large prompts.

Things like:

“Please make sure this page is mobile responsive, optimized for SEO, uses prerendering, has proper metadata, social sharing support, CSP headers, analytics integration, and production-safe deployment settings…”

That approach quickly became unreliable.

Claude would focus heavily on one instruction while quietly ignoring another. Sometimes it would partially implement features. Other times it would regress working functionality while trying to “help.”

The breakthrough came when I stopped treating prompts like conversations and started treating them like infrastructure.

Instead of giant prompts, I created focused reusable skills:

• senternet-site-metatags

• senternet-site-prerender

• senternet-site-mobile-optimize

• senternet-site-share-images

• senternet-site-csp

• senternet-site-lighthouse

• senternet-site-indexnow

• senternet-site-firebase

Each skill had:

• narrowly scoped responsibilities

• deterministic expectations

• operational guardrails

• reusable implementation logic

The outputs became dramatically more stable.

The Most Important Idea: Operational Consistency

One thing I learned very quickly:

AI is surprisingly good at generating components.

It is much worse at consistently maintaining production infrastructure across multiple projects.

Humans naturally remember things like:

• “Did we set OpenGraph tags?”

• “Are we prerendering this route?”

• “Did we configure robots.txt?”

• “Will this social image crop correctly?”

• “Are Lighthouse scores still acceptable?”

• “Did analytics get added to the production layout?”

AI often forgets these details entirely unless explicitly guided.

That’s where reusable skills become powerful.

Instead of depending on memory or repetitive prompting, operational standards become encoded into reusable workflows.

The goal wasn’t full automation.

It was reducing forgotten work.

The “Uber Skill” Concept

One of the most useful patterns ended up being what I started calling “uber-skills.”

Instead of handling a single isolated task, these workflows orchestrate multiple setup steps together.

For example:

• detect what’s already configured

• skip completed setup

• identify missing production features

• apply only incremental improvements

• avoid destructive rewrites

That last point became especially important.

One of the biggest failure modes with AI coding tools is:

asking for one change and getting an accidental full-project refactor.

The skills helped constrain that behavior significantly.

---
name: senternet-create-site
description: Orchestrate the full Senternet site build by running foundation, favicon, SEO, analytics, prerender, image, and performance skills in order.
---

# Create a Complete Optimized Marketing Site

Spin up or upfit a fully optimized marketing site by executing all site skills in sequence.

---

## Mode Detection

Before asking anything, check whether the user provided a path to an existing directory:

- **Existing directory** — run in **upfit mode**: navigate to that directory and detect what's already implemented before each step. Skip steps that are complete, patch steps that are partial.
- **No directory provided** — run in **create mode**: ask the intake questions below and build from scratch. If the user does not have a design zip, directory, or HTML export, default to a barebones Hello World site using the requested project and directory names.

## Upfit Feature Inventory

In upfit mode, surface a visible feature inventory before the optional phases so the user can see what is already enabled and what is still available to add.

- For each optional capability, detect whether the repo already has it.
- Report each one as either `enabled` or `available`.
- If one or more optional capabilities are `available`, present them to the user as a single enablement menu instead of separate yes/no prompts.
- Only offer options for capabilities that are not already enabled.

Optional capabilities to inventory in upfit mode:

- Transactional email via Resend
- Reddit pixel for ad campaigns
- Spanish `/es/` multilingual support
- Ad landing pages for paid campaigns
- SEO blog
- Competitor comparison / alternative pages
- reCAPTCHA Enterprise protection for forms

What Actually Improved

The biggest gains weren’t:

• writing code faster

• generating prettier components

• reducing typing

The biggest gains were:

• fewer regressions

• fewer forgotten deployment details

• fewer SEO mistakes

• fewer repetitive setup tasks

• more consistent production readiness

• reduced decision fatigue

In other words:

The AI became more useful once the workflow became more structured.

Real-World Usage

These workflows eventually became part of the production process behind projects like:

• StockCar

• Bee Ready

Both projects benefited from repeatedly applying the same operational standards:

• metadata handling

• mobile optimization

• share image workflows

• SEO structure

• deployment consistency

• performance optimization

Without reusable skills, I found myself re-solving the same infrastructure problems on every project.

Where AI-Assisted Development Still Struggles

Even with reusable skills, there are still clear limitations.

Claude Code can still:

• over-refactor working code

• hallucinate architecture decisions

• regress responsive layouts

• invent unnecessary abstractions

• partially apply instructions

• miss subtle UX inconsistencies

And frontend polish still requires human judgment.

A lot of human judgment.

But structured workflows dramatically reduce the chaos.

My Current Take

I increasingly think the future of AI-assisted development looks less like prompting and more like operational engineering.

The developers getting the best results probably won’t be:

• the people writing the longest prompts

• the people trying to remove all constraints

• the people chasing fully autonomous agents

It’ll be the people building:

• reusable workflows

• constrained systems

• composable tooling

• deterministic infrastructure

• operational guardrails

The real leverage comes from encoding consistency.

Not just generating code.

Final Thoughts

AI coding tools are already extremely capable.

But there’s still a huge difference between:

generating a demo

and:

repeatedly shipping production-ready websites.

For me, reusable Claude Code skills became a way to bridge that gap.

Not by replacing engineering discipline.

But by making it easier to apply consistently.