菜单
Use when creating Hebrew or mixed Hebrew/English content, Markdown, HTML, slides, landing pages, PDFs or workshop materials that need correct RTL layout.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create branded Hebrew/RTL contract PDFs for Aviz. Use this whenever the user asks to create, draft, generate, brand, update, or export a contract/agreement/הסכם/חוזה as PDF, especially for workshops, lectures, consulting, AI services, quotes that need contractual terms, or client-facing legal-style documents. The skill gathers missing deal details, applies AVIZ branding, renders HTML to PDF, creates a preview image, and verifies the result before delivery.
Manage Morning (Green Invoice) payment links — create, update, search, deactivate, duplicate. Use for: payment link, לינק לתשלום, דף תשלום, morning payment, create link, update price.
Produce podcast episodes for הצב נחום with script→video→subtitles→Instagram pipeline. Use when: 'פרק חדש של נחום', 'nachum episode', 'פודקאסט נחום', 'היי אתה פרק', or wants to create turtle-character podcast content.
Transform substantial reflections, manifestos or foundational insights into durable workshop concepts, social posts and quote files.
Turn a raw Hebrew idea/draft from Aviz into a publish-ready Facebook post. Restructures into paragraphs (single blank line between each), preserves his voice ("less hype, more practical"), copies the final body to clipboard via pbcopy, and saves to content/posts/YYYY-MM-DD-slug.md as an Obsidian-compatible note with [[wikilinks]] to existing concepts. Triggers on - "פוסט לפייסבוק", "כתוב פוסט", "facebook post", "תסדר את הפוסט", "יש לי רעיון לפוסט", "post idea", "תפרסם", "redact a post".
Clean desktop for live session. Use for: prepare for live, clean desktop, get ready for streaming.
| name | rtl-hebrew |
| description | Use when creating Hebrew or mixed Hebrew/English content, Markdown, HTML, slides, landing pages, PDFs or workshop materials that need correct RTL layout. |
Use this skill whenever the output contains meaningful Hebrew text and will be read as a document, page, slide, PDF, social post or workshop asset.
Hebrew content should be explicitly marked RTL. Do not rely on the viewer to infer direction.
For Markdown files that will be rendered in GitHub, Obsidian or a browser, wrap long Hebrew sections in:
<div dir="rtl" lang="he">
תוכן בעברית...
</div>
For short tables, prefer an HTML table inside the RTL wrapper when normal Markdown table rendering becomes visually confusing.
Set document-level direction:
<html lang="he" dir="rtl">
Set CSS defaults:
body {
direction: rtl;
text-align: right;
}
:where(code, pre, kbd, samp, .ltr) {
direction: ltr;
text-align: left;
}
Use dir="ltr" for code blocks, URLs, commands, emails, file paths and technical identifiers.
Every Hebrew slide should specify:
**Language:** Hebrew
**Direction:** RTL - content flows right to left
Layout rules:
Use HTML/CSS or a renderer that supports Hebrew shaping and RTL. Always render and visually verify the final output.
Minimum CSS:
html {
direction: rtl;
}
body {
font-family: "Arial", "Noto Sans Hebrew", sans-serif;
text-align: right;
}
When replying in Hebrew, write normal Hebrew prose. If providing a copy-paste artifact that may render incorrectly, include RTL wrappers in the artifact itself.
Before finishing a Hebrew visual/document artifact, check: