agentleFS
Sign inStart free
podopodo/design-agent-skills/skills/kami/SKILL.md

kami

Skill32 starsChanged 6 months agoMITView on GitHub

Document typesetting skill: resumes, one-pagers, white papers, letters, portfolios, and slide decks laid out on warm paper-like pages with serif type and ink-blue accents. Template and layout rules that produce print-ready output.

  • Deletes or force-pushes

6 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-browser.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    agent-browser

    Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    If an earlier attempt left /tmp/kami-skill behind, delete it first (rm -rf /tmp/kami-skill): git clone refuses a non-empty directory.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

kami

Catalogue stub — full skill: tw93/Kami

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->

Decision tree

  1. Is the full skill already installed?
    • Global: f=~/.agents/skills/kami/CHEATSHEET.md; [ -e "$f" ] && ! grep -qs "^das:" "$f" && echo "installed" || echo "pointer"
    • Project: f=.agents/skills/kami/CHEATSHEET.md; [ -e "$f" ] && ! grep -qs "^das:" "$f" && echo "installed" || echo "pointer"
    • installed → invoke it and proceed
    • pointer → go to step 2

  2. Install (the skills CLI cannot install this one):

    The repo is ~180 MB (fonts, site assets) and a plain npx skills add tw93/Kami clone takes minutes and can hit the CLI's 300 s clone timeout. Cloning only skills/kami (about 3 MB) takes seconds, then the skills CLI installs it from that local path.

    If an earlier attempt left /tmp/kami-skill behind, delete it first (rm -rf /tmp/kami-skill): git clone refuses a non-empty directory.

    [ -e ~/.agents/skills/kami ] && echo "global" || echo "project"

    Global:

    git clone --depth=1 --filter=blob:none --sparse https://github.com/tw93/Kami.git /tmp/kami-skill
git -C /tmp/kami-skill sparse-checkout set skills/kami
npx skills add /tmp/kami-skill/skills/kami -g -y

    Project:

    git clone --depth=1 --filter=blob:none --sparse https://github.com/tw93/Kami.git /tmp/kami-skill
git -C /tmp/kami-skill sparse-checkout set skills/kami
npx skills add /tmp/kami-skill/skills/kami -y

Claude Code plugin route:

/plugin marketplace add tw93/kami
/plugin install kami@kami

Heads-up

  • Requires: Python 3 with WeasyPrint to build PDFs (python-pptx for editable PPTX); the commercial TsangerJinKai02 CJK font is not bundled
  • License: MIT
<!-- das:install:end -->

Invoke after install

  • Skill name: kami (also available as the /kami command; the Claude Code plugin route namespaces it as /kami:kami)
  • Trigger phrases: "Kami document typesetting", "Kami templates", "typeset a resume", "white paper layout"

What it does

"Good content deserves good paper." Kami ships a set of templates and layout rules for documents that should look designed rather than generated: resumes, one-pagers, white papers, letters, portfolios, slide decks, and a landing-page template. Output is PDF, PNG, or editable PowerPoint. The workflow starts by locking a contract (language, template, output formats, page or length target, visual acceptance, verification command), then builds through scripts and verifies the output. English and Chinese have the most complete support; Japanese and Korean use language-specific font fallbacks. An optional brand profile can override defaults.

When NOT to use

  • Auditing or restyling an existing product site or app UI → use hallmark or impeccable
  • Interactive, animated HTML slide decks → use frontend-slides or html-ppt
  • Markdown-driven developer decks → use slidev-skill or marp-slides
  • AI-generated slide imagery from a document → use nanobanan-ppt

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