hardware-spec

Generates a measured hardware and performance specification HTML document for Air Force infrastructure procurement.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/levori119/skyboard --skill hardware-spec-levori119
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hardware-spec
Source: https://github.com/levori119/skyboard/tree/main/.claude/skills/hardware-spec
Command: npx skills add https://github.com/levori119/skyboard --skill hardware-spec-levori119

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pg.

What problem does it solve? Procurement committees reject vague or inflated hardware requests, and under-specified requests result in delivered equipment that cannot run the system. This Skill produces a defensible hardware specification document (HARDWARE_SPEC.html) for the SKY-KING air traffic control system, where every number is either measured from the live system or explicitly flagged as a planning assumption. ## Core Features & Use Cases - Mandatory measurement phase: Runs shell and PostgreSQL scripts to measure client polling load, API surface size, database size, table breakdown, and query round-trip latency before any number is written. - Deployment-scale sizing: Applies fixed sizing formulas (requests/sec per workstation, DB queries per request, bandwidth) across locked deployment scopes (VMP, routine security, wartime) for 10 sites and 192 workstations. - Procurement-ready HTML output: Generates a standalone RTL Hebrew document with executive summary, critical requirements (DB co-location RTT < 1ms, physical workstations not VDI, wartime-sized servers), a "what is not required" section, and a pre-purchase validation section. - Use Case: Before submitting an infrastructure request to the Air Force, run this Skill to measure the current system, compute per-site server and workstation specs, and produce the submission document that survives procurement review. ## Quick Start Generate the hardware specification document for the SKY-KING infrastructure request using the hardware-spec skill.

Frequently Asked Questions about hardware-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a hardware specification for a procurement committee?▼

Measure the real system first: client request rates, database size, and query latency. Then derive server and workstation specs from fixed sizing formulas, classify every line as mandatory, recommended, or optional, and include a section listing what is explicitly not required.

How do I measure server load before sizing hardware?▼

Extract client polling intervals from source code to compute requests per second per workstation, count API endpoints, and query PostgreSQL for database size, largest tables, and round-trip latency. Multiply per-workstation load by the workstation count per site.

Why must the database server be co-located with the application server?▼

The initDb startup sequence performs roughly 300 serial round trips, so 70ms latency means a 36-second startup versus 2 seconds at 0.5ms. Each workstation request also runs 2-3 queries, multiplying every millisecond of latency across all users.

Can the workstation run as a thin client or VDI?▼

No. Local audio transcription runs on the workstation CPU so audio never leaves the machine, and pen input latency cannot survive a remote desktop. The spec mandates a physical Windows 11 x64 workstation with a defined processor model.

What are the limitations of the sizing numbers in this specification?▼

Server instance capacity of 400 requests per second per 8 vCPU is a planning assumption not yet measured, and must be flagged as such in the document. A real load test with the LOADRUNNER project is required to convert it into a measured value before large purchases.