tachyon-beep/using-site-designer
plugins/lyra-site-designer/skills/using-site-designer/SKILL.md
Use when designing or implementing static websites for developer tools, open-source projects, or technical documentation — information architecture, HTML/CSS, design tokens, developer UX patterns
$ install --global
skillsauthnpx skillsauth add tachyon-beep/skillpacks using-site-designerInstall 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 6, 2026, 4:41 AM385.9s7 files scanned
SKILL.md
- name:
- using-site-designer
- description:
- Use when designing or implementing static websites for developer tools, open-source projects, or technical documentation — information architecture, HTML/CSS, design tokens, developer UX patterns
Using Site Designer
Overview
This skill routes you to static site design and implementation capabilities. Use it when building websites for developer tools, open-source projects, or documentation-heavy sites where content quality and developer UX matter more than marketing aesthetics.
Core Principle: Developer tool sites succeed on substance — clear docs, working examples, and fast navigation. Not hero images and testimonials.
When to Use
Load this skill when:
- Planning site structure or information architecture for a project
- Implementing HTML/CSS for a developer-facing site
- Setting up design tokens and theming (dark/light mode)
- Building documentation site layouts with sidebars, breadcrumbs, search
- Choosing and configuring a static site generator or docs-first framework (Hugo, Astro, Eleventy, Starlight, VitePress, Docusaurus 3)
- User mentions: "website", "homepage", "landing page", "docs site", "static site"
Don't use for: General UI/UX design principles (use lyra-ux-designer), document formatting/PDF output (use muna-document-designer), or web API backend development (use axiom-web-backend).
How This Pack Works
This pack provides a site-designer agent — a specialist subagent that combines information architecture, CSS craftsmanship, and developer UX expertise. The agent handles:
| Capability | Details | |------------|---------| | Information architecture | Site maps, navigation strategy, audience-specific paths | | HTML/CSS implementation | Semantic markup, CSS custom properties, responsive layouts | | Design tokens | Color palettes, typography, spacing scales, dark/light mode | | Developer UX | Code blocks with copy, anchor links, version selectors, search | | Static site tooling | Hugo, Astro, Eleventy, Starlight, VitePress, Docusaurus 3 — selection and configuration | | Accessibility | WCAG AA compliance, keyboard nav, screen reader support |
Reference Sheets
Reference sheets are located in the same directory as this SKILL.md file. Load them when the user's task matches:
| Reference | When to Load |
|-----------|-------------|
| code-block-patterns.md | Code blocks with copy-to-clipboard, syntax highlighting, language tabs, terminal styling, heading anchors |
| documentation-sites.md | Multi-page documentation with sidebar navigation, versioning, search, API reference layouts |
| landing-pages.md | Project homepages and landing pages — content-first design for open-source and developer tools |
| responsive-patterns.md | Container queries, :has(), native nesting, fluid type, <dialog popover> mobile sidebar, sidebar collapse, responsive tables and code blocks |
| static-site-tooling.md | Choosing and configuring docs-first frameworks (Starlight, VitePress, Docusaurus 3) and general-purpose generators (Hugo, Astro, Eleventy) — build pipelines and deployment with the first-party GitHub Pages flow |
| theming-and-tokens.md | Design token systems with OKLCH primitives, light-dark() semantic tokens, color-mix() derivations, dark/light mode toggle |
To load: Read the reference sheet from this skill's directory and include its guidance when dispatching the site-designer agent. Multiple sheets can be combined (e.g., documentation-sites + theming-and-tokens + responsive-patterns for a themed responsive docs site).
Quick Start
Designing a New Site
Ask for what you need — the site-designer agent will be dispatched:
"Plan the site structure for our open-source CLI tool"
"Create a docs site layout with sidebar navigation"
"Set up design tokens with dark mode for our project site"
"Build a landing page for our Python library"
Common Workflows
New project site: Start with information architecture (who are the audiences, what content exists), then design tokens, then implement pages incrementally.
Documentation site: Load the documentation-sites reference sheet. Focus on navigation patterns, content hierarchy, and cross-linking before any visual design.
Adding theming: Load the theming-and-tokens reference sheet. Define CSS custom properties, implement dark/light toggle, derive the full palette from brand colors.
Relationship to Other Skills
| Need | Use |
|------|-----|
| UI/UX design principles and patterns | lyra-ux-designer |
| Professional PDF/document formatting | muna-document-designer |
| Writing documentation content | muna-technical-writer |
| Web API backend development | axiom-web-backend |
| Building the website itself | lyra-site-designer (this pack) |
The typical flow: design with lyra-ux-designer, write content with muna-technical-writer, build the site with lyra-site-designer.
Related Skills
tachyon-beep/using-program-management
development
VerifiedTrustedCommunity
Use when **managing the delivery of work** rather than building it — running a project or a program, not writing its code. Use when a team is busy but outcomes are not landing, when "when will it be done" has no defensible answer, when status is green every week until it is suddenly red, when dependencies surprise you, when a RAID log is a graveyard, or when several projects must be coordinated toward one outcome (a program). Lean/agile-leaning, honest about where program scale needs predictive structure. Pairs with `/axiom-planning` (turning one workstream into an implementation plan) and `/axiom-sdlc-engineering` (process maturity, requirements traceability, formal governance). Do not load for writing code, picking an architecture, or designing a single feature.
12SKILL.mdUpdated Jun 9, 2026
tachyon-beep/plugins/axiom-product-management/skills/using-product-management
tools
VerifiedTrustedCommunity
--- name: using-product-management description: Use when a Claude is taking **standing ownership** of a software product and driving it end-to-end across many sessions — discovery, strategy, specs, delivery orchestration, and value validation — deciding *what to build, why, for whom,* and *whether it worked*, with continuity, decision provenance, and an authority boundary that escalates anything irreversible or outward-facing to the human owner. Owns the product disciplines: opportunity assessme
12SKILL.mdUpdated Jun 9, 2026
tachyon-beep/using-mcp-engineering
tools
VerifiedTrustedCommunity
Use when designing, implementing, or auditing an MCP (Model Context Protocol) server — tool API design, idempotency under agent retry, structured error envelopes agents can recover from, schema versioning across model drift, transport reliability (stdio / HTTP), output-shape and pagination discipline, and choosing between tools / resources / prompts / sampling. Also use when an MCP server's tools confuse agents, return unstructured errors, deadlock under concurrent calls, double-execute under retry, or lose state across reconnects. Do not use for general REST/GraphQL API design (use `/web-backend`), for client-side prompt engineering or tool-loop design (use `/llm-specialist`), for general in-process plugin architecture (use `/system-architect`), or for cryptographic-provenance audit trails (use `/audit-pipelines`).
12SKILL.mdUpdated May 14, 2026
tachyon-beep/using-embedded-database
development
VerifiedTrustedCommunity
Use when running **SQLite or DuckDB inside an application process** as the durable store — not as a development convenience but as the production database. Use when scaling an SQLite layer that worked at low concurrency and is now hitting SQLITE_BUSY, WAL bloat, lock contention, schema-migration ceremony, or correctness gaps under multi-process writers. Use when introducing DuckDB as an OLAP complement to an OLTP SQLite store, or when picking between the two for a new component. Pairs with `/web-backend` (the API surface above the DB) and `/audit-pipelines` (when the DB is also the audit trail). Do not load for server databases (Postgres, MySQL), key-value stores, or ORM choice in isolation.
12SKILL.mdUpdated May 14, 2026