メニュー
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
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when working on a Python task and unsure which specialist to load - routes to type-system, mypy-resolution, project-tooling, delinting, testing, async, scientific-computing, ML-workflows, debugging-and-profiling, or Textual-TUI specialists based on symptoms
Use when starting any UX/UI design task — visual design, IA, interaction, accessibility (WCAG 2.2), user research across mobile, web, desktop, game, and AI surfaces, plus first-principles audience-derived needs analysis. Routes to 11 specialist sheets.
Use when a Claude is taking **standing ownership** of a software product across many sessions — discovery, strategy, specs, and value validation — deciding *what to build, why, for whom,* and *whether it worked*, with continuity, decision provenance, and an authority boundary that escalates irreversible or outward-facing actions to the human owner. Owns the product disciplines: opportunity assessment (JTBD, problem validation, business case), vision/strategy/positioning and intent-roadmapping, PRDs with falsifiable acceptance criteria, delivery orchestration and acceptance, product-value metrics and experimentation, and the product anti-pattern catalog. Orchestrates rather than reimplements: routes sequencing/flow/WSJF to `/axiom-program-management`, plans to `/axiom-planning`, solution/architecture to `/axiom-solution-architect`, research method to `/lyra-ux-designer`. Do **not** load to build one feature, choose an architecture, or manage delivery flow for already-decided work.
This skill should be used when the user asks to "track work", "create an issue", "find something to work on", "what should I work on next", "triage bugs", "close an issue", "check what's blocked", "plan a milestone", "review sprint progress", "coordinate agents", or when working in a project that uses filigree for issue tracking. Provides workflow patterns, team coordination protocols, and operational guidance for the filigree issue tracker.
Use when designing a system that spans more than one process, machine, or failure domain and a partition, crash, or duplicate must not silently corrupt state. Use when you see split-brain, lost writes under partition, duplicate processing, stuck or half-applied sagas, retry storms, dual writes drifting apart, or "works in staging, melts under load." Architecture-level — how to design correctness under partial failure, not how to deploy it. Single-service API internals → `axiom-web-backend`; CI/CD and ops → `axiom-devops-engineering`; replay/seed determinism → `axiom-determinism-and-replay`; broker/event-sourcing mechanics → the event-driven pack.
Use when designing a system whose past behaviour must be recoverable as a fact — RL training substrates, multi-agent simulations, deterministic game engines, replay-debuggable services, multiplayer lockstep, or any pipeline where "I cannot reproduce that bug" is unacceptable. Use when teams disagree about what "snapshot", "seed", or "replay" mean across modules. Use when cross-machine or cross-process determinism is required, or a regulator will ask "what was the input at tick T?". Architecture-level — how to design a deterministic system. For verifying an existing simulation against known patterns, use `/check-determinism` from yzmir-simulation-foundations instead.
| 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 |
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.
Load this skill when:
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).
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 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).
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"
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.
| 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.