Guide · Agent skill
How to use the Kami Landing Page agent skill (kami-landing)
Updated · written with AI from the project's own documentation and checked against our catalogue data
The kami-landing skill is a reusable instruction package for an AI agent that turns a short brand brief into one self-contained HTML page styled like a professional white paper or printed studio one-pager. This guide is for founders, small studios, open-source maintainers and designers who want a clean editorial profile page without building a website. By the end you will know what the skill does, how to install it, how to phrase a request so the agent picks it up, and what to check in the output.
Kami Landing Pagenexu-io/open-design · Apache-2.0 Download the skill Quick start
- 1Download the ZIP. Get the kami-landing ZIP from the directory page.
- 2Unzip into a skills folder. Place the kami-landing folder in ~/.claude/skills/ for personal use or in a project's .claude/skills/ folder.
- 3Or upload it in Claude. In the Claude apps, go to Settings → Capabilities → Skills and upload the skill.
- 4Write a brief. Prepare the headline, manifesto, metrics, chapters and footer details.
- 5Ask with a trigger phrase. Request a kami-style one-pager or white paper page and include your content.
- 6Check the HTML. Open index.html in a browser and run through the colour, font and italic checks.
What is an agent skill, and what does kami-landing make the agent do?
An agent skill is a folder containing a SKILL.md file of instructions that an AI agent can load when a task matches it. kami-landing tells the agent how to produce one page in the kami (紙 / 纸) design system: a warm cream background, a single ink-blue accent colour, one serif font weight and no italics.
You give the agent your brand details: name, headline, a short manifesto, a few key numbers and numbered sections. The agent returns one HTML file with all styling built in. The page is meant to read like a printed document rather than a software app screen.
- Output: one standalone index.html file with inline CSS and zero JavaScript.
- Languages: English, Simplified Chinese (zh-CN) or Japanese (ja), set by the language parameter.
- Layout: hero headline, manifesto with signature, 3 to 6 metric tiles, 3 to 5 numbered chapters, and a footer.
Download and install kami-landing
Download the ZIP for the skill from the directory page. Unzip it so that the kami-landing folder, containing SKILL.md, README.md and example.html, sits in one of the skill locations below. The skill's SKILL.md refers to design-systems/kami/DESIGN.md and example.html from the same repository, so keep those reference files available to the agent as well.
To install for yourself across projects, unzip into ~/.claude/skills/. To install for one project only, unzip into that project's .claude/skills/ folder. You can also upload the skill in the Claude apps under Settings → Capabilities → Skills.
- Personal: ~/.claude/skills/kami-landing/
- Project only: .claude/skills/kami-landing/ inside your project
- Claude apps: Settings → Capabilities → Skills, then upload the skill
How do you trigger the skill with a natural request?
You do not need a special command. The skill lists trigger words such as "kami", "kami landing", "paper one-pager", "white paper", "editorial document" and "print-grade page". Asking for one of these in plain language is usually enough for the agent to load it.
Name the output and give the content directly. Mention the language if it is not English, and say that you want a single HTML page.
- Good: "Build me a kami-style one-pager for Lumen Field, an indie studio. Headline: Soundscapes for focused work. Three metric tiles: 12 soundscapes, 4 presets, 1 daily ritual."
- Good: "Make a white paper style landing page in Japanese for my open-source project."
- Weak: "Make me a website." The skill is not built for interactive sites, so the agent may choose something else.
What information should you prepare first?
The skill asks for its brief in two rounds. Preparing these items in advance makes the first output much closer to what you want.
The identity round covers name, tagline, location, edition or version, primary URL and dominant language. The content round covers the manifesto paragraph and signature, 3 to 6 metric tiles (value, label and sub-line), and 3 to 5 chapters, each with a title, lede and body.
- Headline: one line, six words or fewer at display size (CJK: eight characters or fewer).
- Metrics: 3 to 6 tiles, each with value, label and sub.
- Chapters: 3 to 5, each with title, lede and body text.
- Footer: licence, year, contact and a three-column site index.
Review the output before you publish it
The skill ends with a self-check list. Before you publish, confirm the basics yourself: the background is parchment rather than pure white, the serif weight stays at 500, there is no italic text, and the ink-blue accent is used sparingly.
Open index.html in a browser and view it at a narrow width as well as a wide one. The skill specifies responsive breakpoints at 1280, 980, 768 and 560 pixels.
- Background is #f5f4ed, not #ffffff.
- Ink-blue #1B365D covers no more than about 5% of the visible surface.
- No italic text and no bold weights above 500 on serif text.
- Numeric figures are aligned with tabular numbers.
Safety notes: scripts and network access
According to the skill's listing, kami-landing runs no scripts and uses no network access on its own. Its main requirement is file-write capability, so the agent can create index.html. It also needs the reference design system files from the same repository.
The one external dependency is optional: the page can load Google Fonts for its web font. If you do not want external requests, check the generated HTML and remove the font link, since the stacks fall back to system serif fonts.
- Requires: file-write capability for index.html.
- Requires: design-systems/kami/DESIGN.md and example.html from the same repository.
- Optional: Google Fonts access for web font loading.
- Runs scripts: no. Uses network: no.
What people use it for
- A founder's one-page profile of a product, with a manifesto and three key numbers.
- An open-source maintainer's print-first summary page for a research project.
- A studio's quick editorial one-pager for a client pitch, generated from a brief.
- A Japanese or Simplified Chinese company profile page using the matching language stack.
Frequently asked questions
Is the kami-landing skill free to use?
The skill is published under the Apache-2.0 licence, as listed on the directory page. Check the licence file in the repository for the full terms before reusing it in a commercial project.
What do I need to run kami-landing?
You need an agent that has file-write capability so it can create index.html. You also need the reference files design-systems/kami/DESIGN.md and example.html from the same repository, and optionally Google Fonts access.
Where do I install the kami-landing skill?
Unzip the downloaded folder into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. You can also upload it in the Claude apps under Settings → Capabilities → Skills.
Can kami-landing build an interactive website or web app?
No. The output is deliberately zero-JavaScript static HTML, so it does not support forms, dynamic data or interactive features. Use a different tool for those pages.
Which languages does the skill support?
It supports English, Simplified Chinese (zh-CN) and Japanese (ja). The language parameter selects the serif font stack, and mixed-language text is allowed inline.
How is kami-landing different from a typical landing page template?
It enforces a restrained print style: a parchment background, one ink-blue accent, a single serif weight and no italics. If you need modern app-style UI or a colourful brand identity, pick a different skill or template.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
kami-landing suits founders, small studios, open-source maintainers and designers who want a clean, print-style one-page profile generated from a brief. It is a poor fit for interactive pages, forms, or brands that need app-style UI or a non-serif, colourful look, so choose another skill for those.
Download the skill