Skip to main content
skill CX Codex

generic-static-feature-developer — Claude Code skill: what it does

generic-static-feature-developer guides feature work on plain HTML, CSS and JS sites: vanilla patterns, a GitHub Actions deploy and checks before you commit.

MIT 139 installs ★ 114 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add travisjneuman/.claude --skill generic-static-feature-developer -a claude-code
Open on GitHub

What generic-static-feature-developer does

The skill keeps a static site static. Pages stay plain HTML, styles stay plain CSS, scripts stay plain JS, and nothing gets bundled or transpiled. What you get instead is a set of patterns for the small stuff: one click listener on body that dispatches by selector, DOMContentLoaded for setup, classList toggles for state.

Progressive enhancement runs through the whole thing: content first, then CSS, then JS. A deploy workflow for GitHub Pages is included, built on peaceiris/actions-gh-pages, plus shell lines for pngquant, jpegoptim and cwebp to shrink images before they land in the repo. There is a budget too — page weight under 50KB, First Contentful Paint under 1s, Lighthouse Performance at 95 or above.

It builds on generic-feature-developer, so the workflow, scope calls and the build-or-integrate decision come from that base skill; on its own it is only the static-site layer. Browser runs, Lighthouse and screenshots happen when you ask, not on every change.

What it helps with

  • add a feature to a static site with no build step
  • ship a repo to GitHub Pages with one workflow
  • shrink PNG and JPEG files and convert them to WebP
  • check layout at 375px, 768px and 1024px
  • keep the page under 50KB with a 95+ Lighthouse score

Example prompts for the agent

  • Add a testimonials section to the static site using plain HTML, CSS and JS.
  • Set up a GitHub Actions workflow that deploys this repo to GitHub Pages.
  • Run the pre-commit checklist: browser support and the three breakpoints.

How to install generic-static-feature-developer

1Skills CLI (Vercel)

npx skills add travisjneuman/.claude --skill generic-static-feature-developer -a claude-code

2Manually: put the files in place

~/.claude/skills/generic-static-feature-developer/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/generic-static-feature-developer/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about generic-static-feature-developer

How do I install generic-static-feature-developer in Claude Code?

Run npx skills add travisjneuman/.claude --skill generic-static-feature-developer -a claude-code. The skill file lands at ~/.claude/skills/generic-static-feature-developer/SKILL.md.

What does generic-static-feature-developer do?

It guides feature development on minimalist static sites: vanilla JS patterns, progressive enhancement, a GitHub Pages deploy workflow and targets for page weight and paint time.

Does it replace generic-feature-developer?

No. It extends that skill and adds the static-site specifics; development workflow and scope assessment still come from the base skill.

Source text

SKILL.md · MIT
---
name: generic-static-feature-developer
description: Guide feature development for static HTML/CSS/JS sites. Covers patterns, automation workflows, and content validation. Use when adding features, modifying automation, or planning changes.
---

# Static Site Feature Developer

Guide feature development for minimalist static sites.

**Extends:** [Generic Feature Developer](../generic-feature-developer/SKILL.md) - Read base skill for development workflow, scope assessment, and build vs integrate decisions.

## Static Site Architecture

### Typical Structure

```
project/
├── index.html          # Main page
├── style.css           # All styles
├── script.js           # All interactions
├── assets/             # Images, icons
├── .github/workflows/  # Automation (optional)
└── docs/               # Documentation
```

### No Build Tools Philosophy

Edit → Save → Deploy (that's it)

- Pure HTML (no templating engines)
- Pure CSS (no Sass/Less/PostCSS)
- Pure JS (no bundling, no transpilation)
- No `node_modules` in production

## Development Workflow

### Local Testing

```bash
# Start local server (cross-platform options)
python -m http.server 8000   # Windows
python3 -m http.server 8000  # macOS/Linux
npx serve .                  # Node.js (recommended - all platforms)
# Visit http://localhost:8000
```

### Before Committing

1. Review markup and CSS for Chrome, Firefox, and Safari support
2. Review layout at 375px, 768px, and 1024px breakpoints
3. Run browser, Lighthouse, or screenshot checks only when the user asks

## Progressive Enhancement

### Philosophy

1. **Content first** - Works without CSS/JS
2. **Enhance with CSS** - Better styling for capable browsers
3. **Enhance with JS** - Interactivity for JS-enabled browsers

### Example Pattern

```html
<!-- Works without JS -->
<details>
  <summary>Menu</summary>
  <nav>
    <a href="#about">About</a>
    <a href="#contact">Contact</a>
  </nav>
</details>
```

```javascript
// Enhancement: Custom animation when JS available
if ("IntersectionObserver" in window) {
  // Progressive enhancement
}
```

## Vanilla JavaScript Patterns

### Event Delegation

```javascript
// One listener for many elements
document.body.addEventListener("click", (e) => {
  if (e.target.matches(".menu-toggle")) {
    toggleMenu();
  }
  if (e.target.matches(".close-btn")) {
    closeModal();
  }
});
```

### DOM Ready

```javascript
// Modern approach
document.addEventListener("DOMContentLoaded", () => {
  initApp();
});

// Or: script at end of body (no event needed)
```

### Class Toggling

```javascript
// Toggle visibility
element.classList.toggle("visible");

// Add/remove
element.classList.add("active");
element.classList.remove("active");
```

## Automation (GitHub Actions)

### Simple Deploy Workflow

```yaml
# .github/workflows/deploy.yml
name: Deploy
on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Deploy to GitHub Pages
        uses: peaceiris/actions-gh-pages@v3
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          publish_dir: ./
```

### Image Optimization

```bash
# Optimize before committing
# PNG
pngquant --quality=65-80 image.png

# JPEG
jpegoptim --max=80 image.jpg

# WebP conversion
cwebp -q 80 image.png -o image.webp
```

## Feature Checklist

**Before Starting:**

- [ ] Read CLAUDE.md for project constraints
- [ ] Check existing patterns to reuse
- [ ] Understand performance budget

**During Development:**

- [ ] One change at a time
- [ ] Test in multiple browsers
- [ ] Test responsiveness
- [ ] Keep page weight in budget

**Before Completion:**

- [ ] Lighthouse 95+ Performance
- [ ] All breakpoints tested
- [ ] Screenshots for comparison
- [ ] Documentation updated

## Performance Targets

| Metric                 | Target |
| ---------------------- | ------ |
| Total weight           | < 50KB |
| First Contentful Paint | < 1s   |
| Lighthouse Performance | 95+    |

## See Also

- [Generic Feature Developer](../generic-feature-developer/SKILL.md) - Workflow, decisions
- [Code Review Standards](../_shared/CODE_REVIEW_STANDARDS.md) - Quality requirements
- [Design Patterns](../_shared/DESIGN_PATTERNS.md) - UI patterns

© travisjneuman · MIT · travisjneuman/.claude

Similar skills

All skills for Frontend and UI →
stitch::extract-static-html official google-labs-code stitch::extract-static-html is a Claude Code skill that extracts a self-contained static HTML file from a running web app, with CSS and images embedded. CX Codex +1 11,500installs render-static-sites Render render-static-sites walks your agent through shipping a static site or SPA to Render's CDN: build commands, publish paths, SPA routing, headers and PR previews. CX Codex +1 434installs deploy-static-site-with-wrangler drawthingsai deploy-static-site-with-wrangler is a Claude Code skill that uploads static site builds to temporary public Cloudflare URLs. It triggers when someone asks to share or preview built HTML assets. CX Codex +1 ★ 171repo stars stardust adobe stardust — a skill for Claude Code, Codex and Cursor that drives a site redesign through extract, direct, prototype and migrate. Per-page state is saved, so a paused session resumes from the right phase. CX Codex +1 592installs pinme-share glitternetwork pinme-share — a Claude Code skill that packages results into a static HTML page and uploads it with pinme upload. It takes a project, report, or conversation summary and returns a shareable link. CX Codex +1 517installs Tistory Blog Skin UI/UX Enhancement Pipeline inhyoe Tistory Blog Skin UI/UX Enhancement Pipeline is a prompt for ChatGPT, Claude.ai, and Claude Code that upgrades a Tistory Poster skin with a reading progress bar, floating table of contents, and dark sidebar styling. GP ChatGPT ★ 178,201repo stars

From the same set117

The whole set →
svelte-development The svelte-development Claude Code skill covers Svelte 5 and SvelteKit development. It applies to reactive components, SvelteKit routing and server functions, and upgrades from Svelte 4. CX Codex +1 139installs llm-app-development llm-app-development — a skill for Claude Code guides the design of RAG pipelines, autonomous agents, and structured schemas. Triggers when building chatbots, retrieval systems, or LLM-driven tools. CX Codex +1 139installs product-analytics product-analytics architects event tracking, funnels, cohorts, and privacy-compliant instrumentation for PostHog, Amplitude, Mixpanel, and Segment. CX Codex +1 139installs payment-integration The payment-integration skill covers Stripe and RevenueCat integrations, subscription flows, and webhook handling. Use it when building payments or reviewing PCI scope. CX Codex +1 139installs customer-success customer-success guides engineering workflows for customer support systems, knowledge bases, ticketing integrations, and health metrics. CX Codex +1 138installs test-specialist test-specialist — a Claude Code skill that supplies test patterns for JS/TS, Python, Go, and Rust. Activates only when you explicitly ask for tests or coverage targets. CX Codex +1 138installs battle-card-builder battle-card-builder builds sales battle cards, competitive comparisons, and structured objection scripts using an 8-part framework. CX Codex +1 137installs serverless-development serverless-development — a skill for AI coding on serverless compute: AWS Lambda, Vercel Edge, Cloudflare Workers. Useful when an API or webhook has to scale on its own. CX Codex +1 133installs

Project sponsors

Companies that keep this analytics open