메뉴
Capsem marketing website (capsem.org). Use when editing marketing copy, adding sections, working with components, or changing the site theme. Covers site structure, data-driven content, component library, Tailwind theme, and dev workflow.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | site-marketing |
| description | Capsem marketing website (capsem.org). Use when editing marketing copy, adding sections, working with components, or changing the site theme. Covers site structure, data-driven content, component library, Tailwind theme, and dev workflow. |
The marketing site (capsem.org) is a single-page landing built with Astro 6 + Svelte 5 + Tailwind v4. Source lives in site/.
cd site && pnpm run dev # localhost:4321
cd site && pnpm run build # Production build
cd site && pnpm run preview # Preview production build
ci.yaml runs the merge-blocking site-build job under pr-gate. site.yaml
deploys only on every push to main and smokes https://capsem.org/. This
deploy rail is independent from binary releases, manual VM asset releases, and
the release.capsem.org asset-channel workflow.
Single page (site/src/pages/index.astro) composed of Svelte components. All marketing copy is centralized in site/src/lib/data.ts -- edit that file to change text, not the components.
site/
astro.config.mjs Astro config (site: capsem.org, Svelte + Tailwind)
package.json capsem-marketing package
src/
pages/index.astro Single landing page, composes all sections
layouts/Base.astro HTML shell (meta, fonts, skip-to-content)
lib/data.ts All copy: site metadata, nav, features, FAQ, footer
lib/icons.ts Icon SVG paths
styles/global.css Tailwind theme tokens, base styles, button utilities
components/
Nav.svelte Top navigation (client:load)
Hero.svelte Hero section with install command
Features.svelte Feature cards grid
ProductOverview.svelte Architecture diagram (host/guest/vsock)
HowItWorks.svelte Step-by-step explanation
FAQ.svelte Accordion FAQ (client:visible)
CTA.svelte Call-to-action (client:visible)
Footer.svelte Footer with link columns
Section.svelte Reusable section wrapper
SectionHeader.svelte Reusable heading + subtitle
Card.svelte Reusable card component
Badge.svelte Reusable badge component
Icon.svelte SVG icon component
InstallCommand.svelte Copy-to-clipboard install snippet
All text lives in site/src/lib/data.ts as typed const exports:
| Export | Content |
|---|---|
SITE | Name, tagline, description, URLs (GitHub, docs, releases) |
NAV_LINKS | Top nav items |
AGENTS | Supported AI agents list |
SECURITY_BLOCKS | Three security pillars (isolation, inspection, control) |
HOST_COMPONENTS | Host-side architecture diagram items |
GUEST_COMPONENTS | Guest-side architecture diagram items |
VSOCK_CHANNELS | Vsock port labels for architecture diagram |
FAQS | FAQ question/answer pairs |
FOOTER_COLUMNS | Footer link groups |
MCP_TOOLS | MCP tool examples |
PACKAGES | Pre-installed packages list |
ROADMAP | Roadmap items |
Defined in site/src/styles/global.css using Tailwind v4 @theme tokens:
--color-accent (blue), --color-accent-secondary (purple), gradient between them--color-surface) and dark (--color-surface-dark) variants@utility classes: btn-primary (gradient), btn-dark, btn-outline, btn-outline-darksection-dark utility classSection.svelte and SectionHeader.svelte provide consistent spacing and headingsclient:load (Nav) or client:visible (FAQ, CTA)gradient-text utility for accent-colored headingsIcons use inline SVG paths from site/src/lib/icons.ts, rendered via Icon.svelte. Favicons in site/public/ are generated from graphics/icon/1024w/capsem-logo-color.png.
Capsem benchmarking with capsem-bench and capsem-bench-rs. Use when running benchmarks, adding new benchmark categories, interpreting results, or investigating performance regressions. Covers benchmark categories (disk, rootfs, storage, startup, protocol/http, snapshot, all), the JSON output format, and how to add new benchmarks.
Capsem development toolchain -- all just recipes, what they do, when to use which, and dependency chains. Use when you need to know how to build, run, test, or ship Capsem, or when deciding which just command to run for a given change. This is the toolchain reference.
Asset building, manifest format, hash verification, and boot-time resolution for Capsem VM images. Use when debugging boot failures, manifest issues, hash mismatches, or understanding how assets flow from build to boot.
Capsem native package installer -- package install, service registration, self-update, manifest-driven asset download, corp config provisioning, and the install test harness. Use when working on package install/update/uninstall commands, service install/uninstall, asset management, corp config, install test infrastructure, or the installed layout (~/.capsem/).
Capsem release process, CI pipeline, Apple code signing, notarization, documentation site, and post-release verification. Use when preparing a release, debugging CI failures, working with Apple certificates, updating the documentation site, or cutting a new version. Covers the full release lifecycle from pre-release checklist through post-release verification.
Capsem system architecture -- service daemon, per-VM processes, CLI, MCP server, guest agent, vsock, network proxy. Use when you need to understand the system design to write code, review changes, write documentation, or debug cross-component issues. Covers the service architecture, IPC protocols, vsock ports, storage modes, network policy, MITM proxy, and key source files.