Loading...
Loading...
Found 34 Skills
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.
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.
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.
Validate ASCII diagram alignment in markdown. TRIGGERS - diagram alignment, ASCII art, box-drawing diagrams.
Update the project README.md with comprehensive documentation based on the current codebase state. Use when the README needs updating or is outdated.
Research issues against highly credible primary sources and save findings as Markdown files in the repository. Suitable for users who want to research topics, collect documentation or API facts, or delegate reading tasks to background agents.
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"
Common conventions for writing Markdown documents that cite external sources (survey reports, paper explainers, and any deliverable that surfaces facts from outside). Defines mandatory citation, in-text reference format, quotation-versus-prose separation, the ban on fabricated associations, and the source-list format. Referenced by survey, paper-details, and any skill that produces sourced output.
Break a PRD into independently-workable issues and write each as a local markdown file in issues/. Use when the user wants to turn a PRD into a list of concrete tasks.
Research an Elixir/Phoenix topic on the web. Searches ElixirForum, HexDocs, blogs, and GitHub. Uses efficient markdown conversion.