本文へ移動
cccskills
無料GitHub で公開

logo

Kolu, Padi, Kaval, and vendored agent-distro logo assets — favicon, PWA icons, website palette, screenshots, and app identity. Use when changing a logo, an icon, or the website's colour tokens.

日本語の概要は準備中です。原文の説明を表示しています。

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Kolu Logo

  • Treat packages/client/favicon.svg as the source vector. Browser/chrome uses it transparent.
  • Regenerate packages/client/public/icon-192.png, icon-512.png, and icon-512-maskable.png after changing it. These are the PWA/Dock assets and need a rounded-square backing with safe-zone-friendly artwork.
  • Keep the mark readable at 16px: no text, no thin strokes, no crowded prompt glyph.
  • Verify both surfaces: browser tab favicon and macOS Dock/PWA-sized icon.
  • Keep app identity as Kolu [host]; do not reintroduce kolu@host or short_name: "kolu".

Website Palette

  • Keep the website palette in sync with the Kolu logo. When packages/client/favicon.svg changes colour, update the website tokens in website/src/styles/global.css and any non-CSS consumers such as the OG RGB tuple in website/src/site.ts.
  • Treat the logo as three colour roles on the website: the middle step is the primary action/link/hover colour; the top step is the formatting accent for code, prompts, markers, and warnings; the bottom step is the body/detail accent for rules, tips, quotes, diagram streams, and live/success accents.
  • Use the website's palette variables (--color-kolu-logo-*, --color-kolu-primary*, --color-kolu-top*, --color-kolu-bottom*) instead of duplicating raw hex values or reintroducing old amber/purple/violet site tokens.
  • If a website diagram or page represents Kolu, Padi, or Kaval, use the relevant program logo asset from website/public/ rather than drawing an unrelated placeholder mark.

Padi Logo

  • Treat packages/padi/logo.svg as the source vector for Padi. The website copies it to website/public/padi-logo.svg.
  • Keep the Padi SVG background transparent. Let the consuming surface provide any tile or panel behind it.

Kaval Logo

  • Treat packages/kaval/logo.svg as the source vector for Kaval. The website copies it to website/public/kaval-logo.svg, and the app imports it in KavalInfoDialog.
  • Keep the Kaval SVG background transparent. Let the consuming surface provide any tile or panel behind it.
  • Keep it icon-like, not wordmark-like: no long text, no tiny labels, no dense terminal clusters. It must read at 24px in the Kaval dialog and at favicon-adjacent sizes.
  • Preserve the meaning: Kaval is the PTY daemon that guards/watches terminals. A simple prompt, shield/watch shape, and a small session cue are enough.

agent-distro Logo

  • packages/agent-distro/src/solid/agent-distro-logo.svg is vendored verbatim from agent-distro's doc/logo.svg at the npins pin (npins/sources.json → agent-distro). Never edit it here: change it upstream, then re-copy it at the next pin bump and check it is byte-identical (cmp) to the pinned source.
  • Keep it as agent-distro ships it: viewBox="0 0 24 24", strokes currentColor (so it takes the surrounding text colour), the three dots in their own fixed colours.
  • Render it only through AgentDistroLogo (@kolu/agent-distro/solid, packages/agent-distro/src/solid/AgentDistroLogo.tsx, a size prop). It inlines the SVG (?raw) rather than using an <img>, because an <img> cannot inherit currentColor.
  • Show it wherever kolu names agent-distro: the tile header's agents pill, the Settings "Agents" row, the host tab's agents mark (its state treatment around the logo), its host-details section, and the "Coding agents updated" toast. It is decorative (aria-hidden); the text beside it carries the meaning.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

blog-post

無料

Write a kolu blog post grounded in the real build history — mine the Claude Code session logs behind a feature for the actual story (for large efforts, fan out over the transcripts with an ultracode workflow), draft it in the author's voice, and wire it into the Astro site. Use when asked to write a blog post or engineering essay about something that was built, especially one that should read as a narrative of what actually happened rather than invented marketing copy.

日本語の概要は準備中です。原文の説明を表示しています。

juspay/kolu822026年10月21日 更新

ci

無料

Run this repo's CI end-to-end — kolu's policy on top of the odu runner: banned opt-out flags, x86_64-linux pinning, pool upkeep, fail-fast surfacing, e2e timing evidence, and the green-gate. Triggers on "run CI", "drive CI", "re-run the pipeline", "close the red check", "warm the pool". Runner mechanics live in the `/odu` skill.

日本語の概要は準備中です。原文の説明を表示しています。

juspay/kolu822026年10月21日 更新

Launch the kolu dev server on two RANDOM free ports so it never collides with the running production `kolu.service`, remember the ports for the rest of the session, and tear down only the dev instance. Load before running the app locally — for evidence capture, driving a live kolu with the chrome-devtools MCP, or any `just dev` you'd otherwise run by hand. Triggers on "run kolu locally", "launch the dev server", "boot kolu", "drive a live kolu", "start the app to screenshot it", or before pointing chrome-devtools at a local kolu.

日本語の概要は準備中です。原文の説明を表示しています。

juspay/kolu822026年10月21日 更新

diataxis

無料

Classify, write, and audit documentation per Diátaxis (diataxis.fr) — the four-quadrant method (tutorials · how-to guides · reference · explanation). Encodes the compass as a decision procedure, each quadrant's contract as hard rules, and an executable mixed-mode audit. Project-agnostic; the per-repo doc-location mapping lives in a repo rule of the project's own (kolu: the Kolu overlay below). Use when writing any user-facing doc, structuring a docs site, or auditing existing docs for mixed modes.

日本語の概要は準備中です。原文の説明を表示しています。

juspay/kolu822026年10月21日 更新

The Dock's agent-state folds — one fenced source of truth in @kolu/terminal-vocab, the load-bearing order≠colour split, and the one "is something happening" question. Use when editing agentProjection or the canvas dock.

日本語の概要は準備中です。原文の説明を表示しています。

juspay/kolu822026年10月21日 更新

E2E test conventions — semantic selectors, arrange-steps that prove the process started, runtime markers that cannot match the shell echo, and absolute-path tool invocations. Use when writing or changing a .feature scenario under packages/tests.

日本語の概要は準備中です。原文の説明を表示しています。

juspay/kolu822026年10月21日 更新

juspay のスキルをすべて見る

このスキルの問題を報告する