adambien/web-static
web/web-static/SKILL.md
Build modern static websites using semantic HTML and CSS without external dependencies or build systems
$ install --global
skillsauthnpx skillsauth add adambien/airails web-staticInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 11, 2026, 3:55 AM287.0s2 files scanned
SKILL.md
- name:
- web-static
- description:
- Build modern static websites using semantic HTML and CSS without external dependencies or build systems
- argument-hint:
- [description of the website or page to build]
Build or maintain a static website using $ARGUMENTS. Apply all rules below strictly.
Hard Constraints
- No JavaScript — no
<script>tags, no inline event handlers, no.jsfiles - No external dependencies — no frameworks, libraries, CDNs, or package managers
- No build systems — no transpilation, bundling, preprocessing, Sass, Less, or Tailwind
- No inline styles — all CSS in separate
.cssfiles - Baseline 2025 — only use CSS features widely available across modern browsers
HTML Rules
- Semantic elements over generic
<div>/<span>— use<header>,<nav>,<main>,<article>,<section>,<aside>,<footer>,<figure>,<time>,<address> - One
<main>per page - Proper heading hierarchy (h1 → h2 → h3, no skipping)
langattribute on<html>alton all images (emptyalt=""for decorative)aria-labelon<nav>when multiple navs exist<label>associated with every form input- Skip link for keyboard users
- Use
<a>for navigation, not buttons - Use
<br>only for line breaks in content, never for spacing
CSS Rules
- Use CSS custom properties for theming (
--color-primary,--spacing-unit, etc.) - Use logical properties (
margin-block,padding-inline,inline-size,block-size) - Mobile-first responsive design with
min-widthbreakpoints - Use modern features: CSS nesting, container queries, cascade layers, subgrid,
oklch()colors - Use
clamp()for fluid typography - Prefer
gapover margins for spacing in flex/grid layouts - Include
prefers-reduced-motion: reduceandprefers-color-scheme: darkmedia queries - Use
content-visibility: autofor off-screen sections - WCAG AA color contrast minimum (4.5:1)
- Always maintain visible
:focus-visibleindicators - Use
@supportsfor feature detection when applying Baseline Newly Available features, providing a graceful fallback for older browsers - When recommending a newer CSS feature, cite its Baseline status (Widely Available, Newly Available, or Limited) so the reader can judge browser support
CSS Reset Baseline
Every project starts with:
* { box-sizing: border-box; margin: 0; padding: 0; }
body { font-family: system-ui, -apple-system, sans-serif; line-height: 1.5; }
Interactive Patterns (CSS-Only)
When interactivity is needed, use these approaches — never JavaScript:
- Accordion:
<details>/<summary> - Modal:
:targetpseudo-class with anchor links - Tabs: hidden radio buttons with
:checked+ sibling selectors - Dropdown menu:
:hover+:focus-within - Mobile hamburger: hidden checkbox with
:checked+ sibling selectors - Form styling:
appearance: noneto customize native controls
Performance
loading="lazy"on below-fold images<picture>with WebP sources for responsive images- Preload critical CSS and fonts
contain: layout style painton repeated components
Project Structure
project/
├── index.html
├── css/
│ └── style.css
├── images/
├── fonts/
└── icons/
For small sites, a flat structure (HTML + single style.css + images/) is acceptable.
What NOT to Do
- Do not use tables for layout
- Do not use
<br>for spacing - Do not use non-semantic
<div>when a semantic element exists - Do not use
onclickor any inline event handlers - Do not add JavaScript for interactions achievable with CSS
- Do not use CSS frameworks or preprocessors
Related Skills
adambien/java-conventions
tools
VerifiedTrustedCommunity
Generic, composable Java 25 code conventions — modern syntax, code style, naming, visibility, structure, methods, streams, exceptions, and documentation rules that apply across all Java contexts (single-file scripts, CLI apps, MicroProfile/Jakarta EE servers, libraries). Technology-neutral within the Java world; meant to be composed with context-specific skills (e.g. `java-cli-script`, `java-cli-app`, `microprofile-server`, `bce`). Use when writing, generating, or reviewing Java code anywhere the composed skill does not already specify style. Triggers on "Java conventions", "Java style", "Java code style", "modern Java", "Java 25", "idiomatic Java", or any request to write or review Java code where context-specific skills do not already cover style.
23SKILL.mdUpdated May 25, 2026
adambien/microprofile-server
development
VerifiedTrustedCommunity
Architecture and coding rules for long-running Java MicroProfile / Jakarta EE server applications — BCE layering, business components (BC), JAX-RS resources, CDI, JSON-P, testing (unit/integration/system), and Maven project structure. Use when creating, generating, scaffolding, writing, or reviewing code, resources, entities, boundaries, or business components in MicroProfile server projects. Not for serverless deployments.
23SKILL.mdUpdated Mar 27, 2026
adambien/java-cli-app
tools
VerifiedTrustedCommunity
Create and maintain multi-file Java 25 CLI applications packaged as executable JARs with zb (Zero Dependencies Builder). Use when asked to create a Java CLI application, a CLI project with multiple source files, or an executable JAR. Triggers on "Java CLI app", "CLI application", "multi-file Java", "executable JAR", "zb build", or requests for Java programs that need multiple source files or JAR packaging. Not for single-file scripts — use java-cli-script for those.
23SKILL.mdUpdated Mar 27, 2026
adambien/zb-release-pipeline
development
VerifiedTrustedCommunity
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb project", "add a zb release pipeline", "create a build workflow", "automate the zb build/release", or when a project has a .zb config and needs continuous builds/releases. Trigger even if the user doesn't say "zb" explicitly, as long as the project is a zb project (a .zb file is present and there is no Maven/Gradle build).
22SKILL.mdUpdated May 21, 2026