Agent skill

Design

by static-web-server in static-web-server/static-web-server

Design or review software architecture, API contracts, data models, and module boundaries for the Static Web Server (SWS) project

Apache-2.0Auto-check passedDevelopment

Install Design

skills CLI

$ npx skills add static-web-server/static-web-server --skill design -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install static-web-server/static-web-server design --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/design .claude/skills/design && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "design" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/design into .claude/skills/design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/design

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add static-web-server/static-web-server --skill design -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install static-web-server/static-web-server design --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/design .agents/skills/design && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "design" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/design into .agents/skills/design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add static-web-server/static-web-server --skill design -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install static-web-server/static-web-server design --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/design .cursor/skills/design && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "design" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/design into .cursor/skills/design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/static-web-server/static-web-server.git --path .agents/skills/design

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add static-web-server/static-web-server --skill design -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install static-web-server/static-web-server design --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/design .gemini/skills/design && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "design" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/design into .gemini/skills/design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install static-web-server/static-web-server design

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add static-web-server/static-web-server --skill design -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/design .github/skills/design && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "design" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/design into .github/skills/design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add static-web-server/static-web-server --skill design -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install static-web-server/static-web-server design --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/design .opencode/skills/design && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "design" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/design into .opencode/skills/design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: design
GitHub stars: 2.4k
Token cost: ~1.8k tokens
SKILL.md length: 830 words
Files: 1
Skills in repo: 9
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Design or review software architecture, API contracts, data models, and module boundaries for the Static Web Server (SWS) project

Works in 3 steps: Pre-processing steps return early when… → Post-processing steps are additive —… → Order matters: static compression runs…
Tasks that involve Software architecture
SKILL.md covers Principles, Module Architecture, Request Pipeline Design and Configuration Design, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Design is an agent skill from static-web-server/static-web-server. Design or review software architecture, API contracts, data models, and module boundaries for the Static Web Server (SWS) project

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Software architecture and API design. It works with Linux. The repository describes itself as: A cross-platform, high-performance and asynchronous web server for static files-serving. ⚡. The licence is Apache-2.0.

When your agent uses it

Tasks that involve Software architecture
Tasks that involve API design

Example prompts

“/design”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Pre-processing steps return early when they handle the request (CORS preflight, redirect, health check)
Post-processing steps are additive — they append or modify headers. No step removes headers set by prior steps
Order matters: static compression runs before dynamic compression (pre-compressed files avoid CPU cost), cache-control runs before…

What it can do on your machine

Read from SKILL.md and the folder at commit 32ec4aa. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Design loads about 1.8k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 830 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~34
When it runs · the whole SKILL.md, loaded when a task matches: ~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from static-web-server/static-web-server at commit 32ec4aa, republished under its Apache-2.0 licence (© static-web-server). 830 words, ~1,842 tokens.

Download SKILL.mdSave it as .claude/skills/design/SKILL.md (or your agent's skills folder).

name: design
description: Design or review software architecture, API contracts, data models, and module boundaries for the Static Web Server (SWS) project

Software Design

Load this skill when designing new features, refactoring modules, defining configuration interfaces, or reviewing architecture decisions for SWS.

When to load: a new feature spans more than one module, a config option is being added or changed, a new step is needed in the request pipeline, a Cargo feature flag is being introduced, or an architecture decision needs review.

Principles

Static file server first: Every design decision starts from "how does this improve serving static files securely and efficiently?"
Small, static binary: Release binary is ~4MB (uncompressed, musl). New dependencies must not increase it by more than 100KB unless they replace existing functionality or gate behind a feature flag
Feature-gate optional functionality: Every non-core feature lives behind a Cargo feature flag AND a #[cfg(feature = "...")] gate. Users compile only what they need
Three channels, one source of truth: CLI args, env vars, and TOML config all map to the same General struct. Precedence (highest→lowest): CLI args → env vars → TOML config → compiled defaults
Pre-compute at startup, serve at speed: Resolve, canonicalize, and validate everything possible at server startup. The request hot path is allocation-light and syscall-minimal

Module Architecture

Core Pipeline

settings/     →  server/opts.rs  →  handler.rs  →  static_files.rs
  (parse)         (init)              (pipeline)      (serve file)

Module Responsibilities

Module	Responsibility
`settings/`	Parse CLI/env/TOML, merge, validate
`server/`	Bind listener, start HTTP/1 or HTTP/2+TLS, graceful shutdown
`handler.rs`	Orchestrate request pre/post processing pipeline
`static_files.rs`	Path resolution, index files, directory listing, byte-range, pre-compressed variants
`compression.rs`	On-the-fly gzip/deflate/brotli/zstd compression
`compression_static.rs`	Serve pre-compressed `.br`/`.gz`/`.zst` files from disk
`security_headers.rs`	Append HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy
`control_headers.rs`	Append Cache-Control based on file extension
`cors.rs`	CORS pre-flight and header injection
`fs/`	File system utilities: path sanitization (`fs/path.rs`), metadata (`fs/meta.rs`), streaming (`fs/stream.rs`)
`exts/`	HTTP extensions: `Accept-Encoding` parsing, content-coding negotiation (`exts/http.rs`, `exts/headers/`, `exts/mime.rs`)
`directory_listing/`	HTML/JSON directory index generation
`body.rs`	Unified response body type — `pub type Body = BoxBody<Bytes, io::Error>` (alias, not a struct)
`service.rs`	Hyper `Service` bridge: `RouterService` → `RequestService` → `RequestHandler`

Feature Flags as Module Boundaries

Every optional feature is both a Cargo feature AND a #[cfg(feature = "...")] gate:

compression → compression.rs + compression_static.rs (meta-feature: compression-brotli/-deflate/-gzip/-zstd)
directory-listing → directory_listing/
http2 → server/http2.rs (requires tls)
tls (base plumbing, no crypto provider) → tls.rs + server/http1_tls.rs. tls-ring (default) or tls-fips selects the provider
basic-auth → basic_auth.rs
fallback-page → fallback_page.rs
metrics → metrics.rs. experimental adds tokio-metrics-collector and requires RUSTFLAGS="--cfg tokio_unstable"
mem-cache → mem_cache/ (LFU admission + LRU eviction via mini-moka, CompactString keys)

Request Pipeline Design

The handler's handle() method is the single entry point. The pipeline is linear with three phases:

#	Step	Phase	Can Short-Circuit?
1	Method check	Pre	Yes (405)
2	Health/metrics	Pre	Yes
3	CORS validation	Pre	Yes (preflight 204)
4	Basic auth	Pre	Yes (401)
5	Maintenance mode	Pre	Yes (503)
6	Redirects	Pre	Yes (301/302)
7	Rewrites	Pre	No (modifies URI, continues)
8	Virtual hosts	Pre	No (selects config, continues)
9	Markdown negotiation	Pre	No (sets content-type hint, continues)
10	`static_files::handle()`	Core	No (always produces a response)
11	Fallback page	Post	No
12	CORS headers	Post	No
13	Markdown content-type	Post	No
14	Text charset	Post	No
15	Static compression vary	Post	No
16	Dynamic compression	Post	No
17	Cache-Control	Post	No
18	Security headers	Post	No
19	Custom headers	Post	No

When adding a new step, specify its position relative to an existing step by number.

Show full SKILL.md (313 more words)Show less

Design Rules for the Pipeline

Pre-processing steps return early when they handle the request (CORS preflight, redirect, health check)
Post-processing steps are additive — they append or modify headers. No step removes headers set by prior steps
Order matters: static compression runs before dynamic compression (pre-compressed files avoid CPU cost), cache-control runs before security headers (custom headers — applied last — take final precedence)

Configuration Design

The `General` struct

CLI arguments, environment variables, and TOML keys all resolve to the same General struct:

--port 8787  ↔  SERVER_PORT=8787  ↔  [general] port = 8787

TOML Config File

Advanced features (custom headers, rewrites, redirects, virtual hosts) are TOML-only. They live in a separate Advanced struct and require glob/regex patterns.

Default Values Philosophy

Secure by default: Hidden files ignored, symlinks disabled, security headers enabled when TLS is active
Performant by default: Compression, cache-control, and HTTP/2 are default-on Cargo features (opt-out via --no-default-features). Disable them to reduce binary size if not needed
Conservative where it matters: Grace period at 0 (explicit opt-in), directory listing off, CORS off

File Serving Design

Index File Resolution

Request for / or /dir/ → directory detected via metadata
Try each index file in the user-configured order (default: ["index.html", "index.htm"])
For each index candidate: check pre-compressed variant, then regular file, then .html suffix fallback
If no index found → directory listing (if enabled) or 404

Pre-compressed Variant Priority

Static (on-disk) compression is tried before dynamic (on-the-fly). The client's Accept-Encoding header determines variant selection. SWS honors quality values.

Byte-Range Serving

static_files.rs supports Range: bytes= for partial content delivery. Multi-range responses use multipart/byteranges.

Review Checklist

Is the new code behind an appropriate feature flag if optional?
Does the request pipeline order make sense (pre → core → post)?
Are paths canonicalized once, not per-request?
Can every public function be tested with the existing fixture infrastructure?
Are error states mapped to appropriate HTTP status codes?
Does the config change work across all three channels (CLI, env, TOML)?

Files

Just SKILL.md in .agents/skills/design of static-web-server/static-web-server.

Open the folder on GitHubat commit 32ec4aa

Compare with similar skills

Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Design compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Design this skillstatic-web-server/static-web-server	2.4k	—	~1.8k	Automated safety check: Pass	Apache-2.0	yesterday
Architecture Decisions and ADRsfirst-fluke/oh-my-agent	1.3k	—	~2.6k	Automated safety check: Pass	MIT	yesterday
Light System DesignLight0305/Light-skills	640	—	~3.6k	Automated safety check: Pass	MIT	3 mo ago
System Designopenxlings/xlings	615	1 repos	~328	Automated safety check: Pass	Apache-2.0	yesterday
Quarkus Patternsaffaan-m/ECC	274k	1 repos	~5.4k	Automated safety check: Pass	MIT	2 days ago
Quarkus Patternsaffaan-m/ECC	274k	—	~6.1k	Automated safety check: Pass	MIT	2 days ago

Similar skills

Architecture Decisions and ADRs
first-fluke/oh-my-agent
Evaluates system boundaries and tradeoffs and writes architecture recommendations, option comparisons or ADRs, with a Mermaid diagram when structure changes.
1.3k GitHub stars~2.6k tokensUpdated yesterday
DevelopmentAuto-check passed
Light System Design
Light0305/Light-skills
Evidence-based workflow for designing or modernizing a software system: current-state inventory, options, API and schema contracts, migration plans, ADRs and verification.
640 GitHub stars~3.6k tokensUpdated 3 mo ago
DevelopmentAuto-check passed
System Design
openxlings/xlings
Design systems, services, and architectures. An agent skill from openxlings/xlings.
615 GitHub starsUsed in 1 repo~328 tokens
Backend & APIsAuto-check passed
Quarkus Patterns
affaan-m/ECC
Quarkus 3.x LTS architecture patterns with Camel for messaging, RESTful API design, CDI services, data access with Panache, and async processing.
274k GitHub starsUsed in 1 repo~5.4k tokens
Backend & APIsAuto-check passed
Quarkus Patterns
affaan-m/ECC
Quarkus 3.x LTS architecture patterns with Camel for messaging, RESTful API design, CDI services, data access with Panache, and async processing.
274k GitHub stars~6.1k tokensUpdated 2 days ago
Backend & APIsAuto-check passed
URL Shortener Interviewer
PrepLabsAI/InterviewMentor
A Senior Engineer interviewer providing the classic URL Shortener system design scenario.
112 GitHub stars~2.6k tokensUpdated today
Backend & APIsAuto-check passed

More from static-web-server/static-web-server

All 9 skills in this repo

Issue Tracking
static-web-server/static-web-server
Triage, debug, fix, and document issues for the Static Web Server (SWS) project — bug reports, root cause analysis, fix implementation, and regression prevention
2.4k GitHub stars~1.5k tokensUpdated yesterday
Auto-check passed
Performance
static-web-server/static-web-server
Optimize or review performance for the Static Web Server (SWS) project — profiling, bottlenecks, resource usage, compression, and caching
2.4k GitHub stars~3.1k tokensUpdated yesterday
Auto-check passed
Prose
static-web-server/static-web-server
Author or edit any prose for the Static Web Server (SWS) project — documentation, design docs, READMEs, PR descriptions, issue bodies, commit message bodies, or other human-readable text — following…
2.4k GitHub stars~971 tokensUpdated yesterday
Auto-check passed
Rust Backend
static-web-server/static-web-server
Write or review Rust backend code for the Static Web Server (SWS) project — crates, modules, functions, types, error handling, and async code
2.4k GitHub stars~1.7k tokensUpdated yesterday
Auto-check passed
Static File Serving
static-web-server/static-web-server
Serve static files and web assets with optimal headers, MIME types, compression, and caching for the Static Web Server (SWS) project
2.4k GitHub stars~1.8k tokensUpdated yesterday
Auto-check passed
Testing
static-web-server/static-web-server
Write or review tests for the Static Web Server (SWS) project — unit tests, integration tests, test fixtures, and mocking strategies
2.4k GitHub stars~1.5k tokensUpdated yesterday
Auto-check passed

Works with

Linux

Questions about Design

What does Design do?

Design or review software architecture, API contracts, data models, and module boundaries for the Static Web Server (SWS) project. Design is an agent skill from static-web-server/static-web-server.

When should I use Design?

Design fits situations like: tasks that involve Software architecture; tasks that involve API design.

How do I install Design in Claude Code?

Run `npx skills add static-web-server/static-web-server --skill design -a claude-code`. Or copy the skill folder (.agents/skills/design in static-web-server/static-web-server) into .claude/skills/design in your project. Claude Code loads it when a task matches its description.

How do I install Design in Codex?

Run `npx skills add static-web-server/static-web-server --skill design -a codex`. Or copy the skill folder (.agents/skills/design in static-web-server/static-web-server) into .agents/skills/design in your project. Codex loads it when a task matches its description.

Can I use Design in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add static-web-server/static-web-server --skill design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design, .gemini/skills/design, .github/skills/design and .opencode/skills/design in your project.

What does Design need to run?

SKILL.md names no scripts, command-line tools or credentials: Design is instructions for the agent only.

Does Design access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Design safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Design use?

Design is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Design use?

About 1.8k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Design?

Skills that share tags, products or a category with Design: Architecture Decisions and ADRs (first-fluke/oh-my-agent, 1.3k stars), Light System Design (Light0305/Light-skills, 640 stars), System Design (openxlings/xlings, 615 stars) and Quarkus Patterns (affaan-m/ECC, 274k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Design?

static-web-server (a GitHub organization) maintains it in static-web-server/static-web-server, which has 2,373 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 5, 2026.

Source: static-web-server/static-web-server on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Design

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Software Design

Principles

Module Architecture

Core Pipeline

Module Responsibilities

Feature Flags as Module Boundaries

Request Pipeline Design

Design Rules for the Pipeline

Configuration Design

The General struct

TOML Config File

Default Values Philosophy

File Serving Design

Index File Resolution

Pre-compressed Variant Priority

Byte-Range Serving

Review Checklist

Files

Compare with similar skills

Similar skills

More from static-web-server/static-web-server

Related

Questions about Design

The `General` struct