agentleFS
Sign inStart free
isaacsightisaacsight/kernel/design-system/SKILL.md

kernel-chat-design

Skill16 starsChanged 4 months agoMITView on GitHub

Use this skill to generate well-branded editorial interfaces and assets for kernel.chat ("Magazine for City Coders" — an independent magazine that is an unnamed homage to POPEYE), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and editorial UI components for prototyping.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the readme.md file within this skill, and explore the other available files.

    line 7
  2. Distinctive:

    If creating visual artifacts (slides, mocks, throwaway prototypes, etc), copy assets out and create static HTML files for the user to view.

    line 9
  3. Distinctive:

    Never name the design inspiration on any user-visible surface.

    line 31
  4. Very specific:

    Never pure #ffffff — use warm ivory/cream/butter/kraft/ledger stocks.

    line 34
  5. Distinctive:

    Every release is an "ISSUE N · MONTH YEAR".

    line 36
  6. Distinctive:

    If the user invokes this skill without any other guidance, ask them what they want to build or design, ask some questions, and act as an …

    line 38

≈ “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

Read the readme.md file within this skill, and explore the other available files.

If creating visual artifacts (slides, mocks, throwaway prototypes, etc), copy assets out and create static HTML files for the user to view. If working on production code, you can copy assets and read the rules here to become an expert in designing with this brand.

Quick start

  • Entry point: styles.css — link it (or its @imported tokens/ + primitives/editorial.css) to get every token, the two webfonts, and the pop-* editorial utility classes.
  • The register — warm paper stocks, tomato (#E24E1B) as the only spot colour, EB Garamond display + Courier Prime meta, bilingual JP/EN, bracketed kickers, numbered catalogs, issue monuments. Type-first, square, hairline rules. The terminal "quiet utility core" carries a hard tomato block shadow.
  • Components (React): components/editorial/ — Kicker, Banner, Monument, CatalogRow, Terminal. Each has a .prompt.md with usage; mount from the compiled bundle namespace.
  • Whole surface: copy ui_kits/magazine/ (cover → contents → essay spread → colophon) and adapt.
  • Icons: the one system glyph is the asterisk ★ (inline 3-line SVG); <PopIcon> editorial pictograms (1.75px stroke) for sparing accents. No emoji.

Hard rules

  1. Never name the design inspiration on any user-visible surface.
  2. Tomato is the only spot colour. (Purple #6B5B95 is the logo mark only.)
  3. EB Garamond + Courier Prime for Latin; Noto Serif JP for Japanese.
  4. Never pure #ffffff — use warm ivory/cream/butter/kraft/ledger stocks.
  5. Bilingual everywhere it fits. One system glyph (★). No emoji.
  6. Every release is an "ISSUE N · MONTH YEAR".

If the user invokes this skill without any other guidance, ask them what they want to build or design, ask some questions, and act as an expert designer who outputs HTML artifacts or production code, depending on the need.

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