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
npx skills add travisjneuman/.claude --skill generic-static-feature-developer -a claude-codeWhat 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-code2Manually: put the files in place
~/.claude/skills/generic-static-feature-developer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/generic-static-feature-developer/
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill generic-static-feature-developer -a codex2Manually: put the files in place
.agents/skills/generic-static-feature-developer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill generic-static-feature-developer -a cursor2Manually: put the files in place
.cursor/skills/generic-static-feature-developer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install travisjneuman/.claude skills/generic-static-feature-developer2Manually: put the files in place
.github/skills/generic-static-feature-developer/SKILL.md1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill generic-static-feature-developer -a gemini-cli2Platform CLI
gemini skills install https://github.com/travisjneuman/.claude --path skills/generic-static-feature-developerManually: put the files in place
.devin/skills/generic-static-feature-developer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill generic-static-feature-developer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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