Loading...
Loading...
Found 51 Skills
Writing, explore — mine raw fragments, no structure yet.
Transform high-level ideas or briefs into fully structured presentation scripts saved as Markdown files, describing presentations slide by slide with exhaustive detail. Use this skill when users request: (1) Creating presentation blueprints or scripts, (2) Structuring slide decks from concepts, (3) Designing presentation narratives with detailed specifications for content, layout, typography, and visuals, or (4) Creating presentation documentation for designers or presenters.
Validate ASCII diagram alignment in markdown. TRIGGERS - diagram alignment, ASCII art, box-drawing diagrams.
This skill should be used when the user asks to "format markdown", "write markdown documentation", "follow markdown style guide", "apply markdown conventions", or needs guidance on markdown best practices.
Full Lifecycle Management of Issue Pool (Development Paradigm v1 Planning Phase). The core is an issue-driven process: users throw in ideas casually, and you turn vague issues into actionable tasks—what you deliver is "problem definition", not "solution implementation"; the carrier is a single markdown file named ISSUES.md at the root of the repository, without introducing kanban or new formats. Five actions: Record (add original content to the pool + relevance check), Merge (merge homogeneous requirements), Break Down (discuss and decompose, guide users to reveal the real needs behind the proposed solutions), Transfer (deliver outputs), Pending (if the issue is still vague after two rounds of discussion, record the bottlenecks and put it back into the pool, and avoid making fake plans to wrap up). The only criterion for judging during Transfer is "whether it can be delivered in one version": If yes → simple task, write a paragraph plus 3~5 acceptance criteria under the pool entry; If no → complex plan, place it in docs/plan/ and write the framework plan content following the seven steps in references/plan-writing.md (explain "why to do it / what constitutes completion / what steps to take", without involving fields or interfaces), the end must remain vague, and break down the next batch only after delivering one batch. When users say "record an issue", "add/summarize issues", "break down an issue / decompose"
This skill should be used when generating lesson summaries for educational content. It extracts key concepts, mental models, patterns, and common mistakes from lesson markdown files using a Socratic extraction process. Use this skill when a lesson file needs a `.summary.md` companion file, or when reviewing/refreshing existing summaries.
Extract any website's design system into an agent-ready DESIGN.md using Firecrawl scrape evidence. Use when the user wants colors, fonts, spacing, components, layout patterns, or brand/UI guidance from a website so AI agents can create new websites, clone a look, or build pages inspired by that design.
Build full-text bilingual, figure-aware, source-grounded Markdown reading files for journal or conference papers from PDF, DOI, arXiv, publisher HTML, or pasted text. Use whenever the user asks to translate an entire paper, make a complete markdown reader, preserve figure or table placement near the relevant prose, or keep exact source anchors for every block. Do not use this for summaries, bullet-keyword notes, or citation-only tasks.
Use when you need to generate an onboarding guide for new team members joining a project
This skill should be used when the user asks to "create a location", "add a location", "magic system", "political system", "build the world", "add culture", "world history", "technology system", "religion", "economy", or wants to develop any aspect of a story's world and setting.
When the user wants to create or update their startup context document. Also use when the user mentions "set up context", "tell you about my startup", or any other skill needs context that doesn't exist yet.
Installs a live docs.page site from a public GitHub repository by following Quickstart. Use when the user wants to add docs.page, install docs.page, scaffold docs.json, or host markdown documentation at docs.page/{owner}/{repo}.