agentleFS
Sign inStart free
GoogleKnown publishergoogle/capsem/skills/site-marketing/SKILL.md

site-marketing

Skill179 starsChanged 13 days agoApache-2.0View on GitHub

The marketing website, capsem.org. Use when editing copy, adding sections, or changing the site theme.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run these commands through the repository's bounded-command wrapper:

    line 14
  2. Very specific:

    Keep all copy, UI labels, reviewed documentation destinations, benchmark disclosures, and fictional hero output in src/lib/data.ts.

    line 43
  3. Very specific:

    Use @capsem/diagrams/Diagram.astro from the shared web/diagrams/ package.

    line 55
  4. Very specific:

    Keep marketing definitions and labels in data.ts.

    line 56
  5. Very specific:

    Use shared semantic tones from web/diagrams/semantics.ts, backed by Tailwind color tokens.

    line 58
  6. Very specific:

    Verify readable labels, zoom/pan/fit controls, the text connection table, and phone layouts in a real browser.

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Marketing Website

The single-page marketing site in web/marketing/ uses Astro 7, Svelte 5, and Tailwind v4. It explains benefits and use cases; precise procedures and contracts belong on the documentation site (see /site-infra).

Development and publication

Run these commands through the repository's bounded-command wrapper:

pnpm --dir web/marketing run dev
pnpm --dir web/marketing run check
pnpm --dir web/marketing run build
pnpm --dir web/marketing run preview

ci.yaml owns the merge-blocking site-build job. Pushes to main trigger site.yaml, which builds, deploys to Cloudflare Pages, and smokes capsem.org. Changes to web/diagrams/ trigger both public-site builds and deployments. This rail is independent from binary and runtime releases. Use /release-process for channel publication at release.capsem.org.

Architecture and content

src/pages/index.astro composes these sections:

ComponentPurpose
Nav.svelteResponsive navigation; hydrated on load.
Hero.svelteDownloads, copyable install command, and animated demo; hydrated on load.
Agents.astroSupported agents and bundled tools.
Performance.astroPerformance claims, methodology, caveats, and sources.
Security.astroShared JointJS security diagram and architecture link.
Control.astroActivity, CEL rule, and detection examples.
Footer.svelteBrand, license, and source link; rendered statically.

Keep all copy, UI labels, reviewed documentation destinations, benchmark disclosures, and fictional hero output in src/lib/data.ts. Its exports are SITE, DOCS, NAV_LINKS, DOWNLOAD, UI, AGENTS, SPEED, SECURITY, SECURITY_DIAGRAM, CONTROL, HERO_DEMO, and HERO_TERMINAL_SCRIPT.

Download.svelte uses lib/download.ts for platform detection and the shared Modal.svelte dialog. Keep focus, Escape, backdrop, and close-button behavior in that dialog. HeroDemo.svelte uses lib/hero-terminal.ts for playback; verify animated, paused, replay, and reduced-motion states when changing it.

Diagrams

Use @capsem/diagrams/Diagram.astro from the shared web/diagrams/ package. Keep marketing definitions and labels in data.ts; do not fork the viewer, add another renderer, or introduce JointJS+ without an explicit decision. Use shared semantic tones from web/diagrams/semantics.ts, backed by Tailwind color tokens. Every used meaning appears in the diagram's Legend, and distinct meanings use distinct color families. Keep host credentials, processing, and VM boundaries separate; permission levels serve the security manual's separate explanation.

Preserve hardware and process boundaries and connection direction when editing. Verify readable labels, zoom/pan/fit controls, the text connection table, and phone layouts in a real browser. Both sites must build after a viewer change.

Theme and assets

src/styles/global.css owns Tailwind @theme tokens and shared layout utilities: content-shell, section-space, panel, button, text-link, and brand-gradient. .section-dark remaps semantic surfaces and text. The hero's scene styling lives in styles/hero-demo.css. Inter is loaded by Base.astro.

The visible logo is public/logo-color.png. Agent logos in public/agents/ retain attribution in SOURCES.md and licensing in LICENSE. Canonical brand graphics live in web/graphics/; favicons derive from web/graphics/icon/1024w/capsem-logo-color.png.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free