Loading...
Loading...
Found 36 Skills
Generate a README introduction following the Diataxis 4-paragraph structure for product documentation.
Optimize content structure and framing for AI citation. Covers trust formats, extractability, and fact-density.
Realign a listing whose order has gone arbitrary — a list, table, catalog, sections, an enum — into a logical sequence under one stated principle. Move items only: nothing is reworded, added, or removed. Use when the order no longer helps a reader follow the set.
Create comprehensive marketing content for themes, plugins, and web products. Generates organized folder structure with product descriptions, feature highlights, social media posts, email campaigns, video scripts, sales materials, and brand assets. Use when creating promotional content, announcements, or sales copy.
Content: Use when writing technical blog posts from scattered notes or ideas. NOT for documentation, specs, or talks.
Searches across your Notion workspace, synthesizes findings from multiple pages, and creates comprehensive research documentation saved as new Notion pages. Turns scattered information into structured reports with proper citations and actionable insights.
Use when writing or editing markdown files. Covers headings, text formatting, lists, links, images, code blocks, and blockquotes.
Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.
Put the answer first, then context and details follow. Use when writing documentation, tutorials, error messages, or any communication where readers need to decide quickly if something is relevant to them.
Book Teardown. Calm, concise, sharp, and straightforward. Explain five key points clearly: What question is the author answering? What unproven assumptions does the author base their argument on? What framework do they use to analyze the topic? What conclusions do they reach? Finally, a few sentences of God's-eye view compression of the entire book. Use this when the user says '拆书', '拆这本', '分析这本书', '这本书在讲什么', '上帝之眼看这本书', '压缩一本书', 'book', or shares a book name requesting structural analysis. DO NOT use for chapter summaries (use Fabric extract_wisdom), papers (use ljg-paper), deep dives into a single viewpoint (use ljg-think), or ranking within a field (use ljg-rank).
Core technical documentation writing principles for voice, tone, structure, and LLM-friendly patterns. Use when writing or reviewing any documentation.
Generate visual mindmaps from natural language descriptions or content using the MCP mindmap tool. Use when users request to visualize structures, workflows, knowledge hierarchies, requirements, meeting notes, or any content as a mindmap. Automatically opens in browser after generation. Supports converting processes, architectures, learning paths, or any structured information into visual diagrams.