logseq-format
此技能使用shadcn/ui、TypeScript和Tailwind CSS将UI规范和组件需求转换为生产就绪的React组件。当用户用自然语言描述UI元素、布局或交互组件,并需要将它们实现为可重用的React组件时使用。针对ScaffAI项目的技术栈进行了优化,具有自动辅助功能支持。
📖 中文导读:此技能使用shadcn/ui、TypeScript和Tailwind CSS将UI规范和组件需求转换为生产就绪的React组件。当用户用自然语言描述UI元素、布局或交互组件,并需要将它们实现为可重用的React组件时使用。针对ScaffAI项目的技术栈进行了优化,具有自动辅助功能支持。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: logseq-format description: Use ONLY when user mentions converting/using/writing in "logseq format" or similar (must mention "logseq")
logseq Format
Format content for logseq, an outliner-based knowledge management tool.
Core Principles
- Everything is a bullet: logseq is outliner-first. All content lives in bullet points.
- Hierarchy matters: Use indentation (2 spaces or 1 tab per level) to create structure.
- Top-level = main ideas: Start with high-level concepts as top-level bullets (no indentation).
Formatting Rules
Top-Level List Structure
- First main topic
- Sub-point with details
- Another sub-point
- Deeper nesting for specifics
- Second main topic
- Related details
- Third main topic
Markup Syntax
- Bold:
**text**or__text__ - Italic:
*text*or_text_ - Highlight:
^^highlighted^^ - Code inline:
`code` - Code block: Triple backticks with language
- Links to pages:
[[Page Name]] - Tags:
#tagor#[[multi word tag]] - Block references:
((block-id)) - TODO markers:
TODO,DOING,DONE,LATER,NOW
Properties (metadata)
- Main topic
property-name:: value
another-property:: another value
- Content continues here
Example Output
- Project Planning #project
status:: active
priority:: high
- Define **scope** and objectives
- List all deliverables
- Set clear timeline with [[Q1 Goals]]
- Identify stakeholders
- TODO Schedule kickoff meeting
- Gather requirements from [[Product Team]]
- Risk assessment
- Document potential blockers
- Create mitigation strategies
Best Practices
- Start broad, go deep: Top-level bullets = chapters, nested bullets = details
- One idea per bullet: Keep bullets focused and atomic
- Use properties sparingly: Add metadata only when it adds value for queries
- Link liberally: Connect related concepts with
[[page links]] - Indent consistently: Use 2 spaces per indentation level
- Frontload importance: Put most important info at the top of each branch