kami
# Kami
What this skill does
# Kami ## Purpose Typeset professional documents with the Kami editorial design system only when the user explicitly asks for Kami, the Kami skill, or the Kami editorial design system by name. Generic presentation, document, report, resume, PDF, and PowerPoint requests should use the native artifact tools instead. This CoWork bundle ports the upstream [Kami](https://github.com/tw93/Kami) skill into a bundled skill with a workspace-local scaffold flow. The goal is to keep the strong visual system available on request while avoiding edits to bundled templates under `resources/skills/`. ## Licensing Note - Upstream Kami is MIT licensed. - This bundled port includes the open English font assets used by the upstream project. - This bundled port does **not** ship the proprietary Chinese serif font `TsangerJinKai02-W04.ttf`. - Chinese HTML templates in this port are patched to rely on system serif fallbacks by default. - If a user has a licensed copy of that font and wants to use it, they can add it to the scaffolded project intentionally. ## Supported Outputs - `one-pager` - `long-doc` - `letter` - `portfolio` - `resume` - `slides` - `diagram-architecture` - `diagram-flowchart` - `diagram-quadrant` ## Project Layout The CoWork wrapper scaffolds a workspace-local project with a stable shape: - `templates/` for document or slide source files - `diagrams/` for standalone diagram HTML - `fonts/` for bundled open fonts and optional user-supplied licensed fonts - `outputs/` for rendered PDF and PPTX files - `manifest.json` for scaffold metadata Edit only the scaffolded project files. Do not edit bundled files under this skill directory. ## Workflow 1. Resolve document type and language before creating files. 2. Run `scripts/setup.sh` to detect local render support. 3. Run `scripts/bootstrap_project.py` to scaffold a workspace-local project. 4. Read the smallest useful reference set: - `CHEATSHEET.md` or `CHEATSHEET.en.md` for light edits - `references/design*.md` for new documents or larger layout work - `references/writing*.md` for section structure and editorial tone - `references/production*.md` for rendering issues - `references/diagrams*.md` for standalone diagram work 5. If the user gives raw notes, distill them before styling: - extract facts and metrics - classify them into the target section structure - identify what is missing - ask once instead of inventing missing claims 6. Keep the visual system intact. Favor content edits and small layout adjustments over broad CSS reinvention. 7. Render HTML-based outputs with `scripts/render_html.py`. 8. Render slides with `scripts/render_slides.mjs`, pointing it at the scaffolded `slides.mjs` or `slides-en.mjs` source file and the project's `outputs/` directory. ## Design Constraints - Parchment background, never pure white - Ink-blue as the only accent color - Warm neutrals, no cool gray UI defaults - Serif carries the hierarchy - Tight editorial spacing, not loose slideware spacing - Avoid glossy UI flourishes, hard shadows, and loud gradients ## Chinese Font Rule When upstream references mention `TsangerJinKai02`, treat that as an optional licensed upgrade, not a bundled requirement in this CoWork port. Default to the patched fallbacks already present in the scaffolded Chinese HTML templates unless the user explicitly provides a licensed font file. ## Reference Map - `CHEATSHEET.md` / `CHEATSHEET.en.md`: quick style and template reference - `references/design.md` / `design.en.md`: visual rules and layout tokens - `references/writing.md` / `writing.en.md`: section structure and editorial guidance - `references/production.md` / `production.en.md`: rendering and export troubleshooting - `references/diagrams.md` / `diagrams.en.md`: standalone diagram guidance - `scripts/bootstrap_project.py`: scaffold workspace-local source files - `scripts/render_html.py`: render a source HTML file to PDF with placeholder checks - `scripts/render_slides.mjs`: render slide source to `output.pptx` and optionally `output.pdf` - `scripts/setup.sh`: preflight local document-render dependencies - `scripts/build.py`: upstream bundle build/verification helper retained for reference ## Runtime Prompt - Runtime prompt is defined directly in `../kami.json`.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.