// Understand and change support-markdown build logic, Markwon/commonmark-java dependency wiring, module dependencies, version catalog entries, Dokka setup, and shared Gradle conventions. Use for buildSrc edits, new dependencies, parser or renderer dependency changes, or documentation pipeline work.
| name | support-markdown-build-dependencies |
| description | Understand and change support-markdown build logic, Markwon/commonmark-java dependency wiring, module dependencies, version catalog entries, Dokka setup, and shared Gradle conventions. Use for buildSrc edits, new dependencies, parser or renderer dependency changes, or documentation pipeline work. |
| argument-hint | Describe the dependency, Gradle change, or build pipeline task you need to make |
buildSrc.:markdown dependency surface before adding anything new, especially for Markwon parser and renderer features.gradle/libs.versions.toml first.markdown/build.gradle.kts before adding a new artifact.buildSrc instead of duplicating it in individual module build files.buildSrc.support-markdown-plugin-workflow skill.jenv-gradle-low-ram skill if Java selection or memory pressure becomes an issue.Deep reference for Markwon plugin internals, commonmark-java AST extension points, Android Spanned rendering, and AniList-Flavored Markdown syntax. Use when implementing new plugins, debugging rendering pipelines, choosing the correct hook layer (processMarkdown vs configureParser vs configureVisitor vs beforeSetText), or understanding how commonmark nodes become Android spans.
Implement or debug support-markdown plugins using real AniList feed fixtures, FeedList.graphql curl validation, and Markwon/commonmark-java extension points. Use for new plugin work, parser or rendering bugs, markdown test design, and deciding whether behavior belongs in processMarkdown, configureParser, configureVisitor, HtmlPlugin handlers, or beforeSetText.
Write or improve KDoc for public APIs in support-markdown. Use for Dokka updates, plugin class docs, controller docs, listener docs, span docs, and explaining how downstream apps should use or configure Markwon and commonmark-java backed library behavior.
Reference map for support-markdown modules, plugin packages, dependency layers, Markwon/commonmark-java ownership boundaries, consumer entry points, and Dokka navigation. Use for questions like which package should own this code, where a class should live, or how the library is organized.
Align jenv with .java-version and run Gradle reliably on low-RAM machines. Use for Java mismatch errors, Gradle OOMs, daemon memory pressure, and selecting safe build flags.