Standardize semantic markup and quality checks for Markdown and XML documentation.
npx skills add https://github.com/nq-rdl/agent-extensions --skill writerside
Please help me install this Agent Skill. Skill: writerside Source: https://github.com/nq-rdl/agent-extensions/tree/main/skills/writerside Command: npx skills add https://github.com/nq-rdl/agent-extensions --skill writerside
Writerside standardizes semantic markup, topic structure, and quality checks to help teams deliver well-structured documentation across Markdown and semantic XML topics, with consistent navigation, diagrams, and templates.
Open a Writerside project in JetBrains IDE and start modeling topics and navigation, then run the Docker-based builder to generate the HTML output.
High-intent search queries and answers about installing and using this skill.
Semantic markup consistency across Markdown and XML topics is enforced through built-in inspections and validation rules. These quality tooling checks standardize topic structure, cross-topic references, and style-guide compliance across all documentation instances.
Technical documentation navigation is structured using a hierarchical topic model with TOC integration and cross-topic references. This ensures predictable builds and consistent output across mixed Markdown and semantic XML content instances.
Documentation projects are built for predictable HTML output using a Docker-based builder. After modeling topics and navigation in a JetBrains IDE, running the Docker builder generates consistent HTML output across all instances.
Yes, built-in inspections and documentation quality tooling validate content directly within a JetBrains IDE. Linting checks enforce style-guide support, semantic markup rules, and cross-topic reference integrity for both Markdown and XML topics.
Semantic XML topics are needed when technical documentation requires strict semantic markup, complex diagrams, and structured topic hierarchy beyond standard Markdown. Mixing both formats allows predictable builds with consistent navigation and quality checks.
Documentation builds fail during cross-topic reference validation when built-in inspections detect broken links or inconsistent semantic markup. Enforcing a structured topic hierarchy and style-guide compliance resolves these reference and markup errors.
buyuk-devIndex and search markdown notes with semantic retrieval via LiteLLM embeddings.
EdgeHuntGenerate visual explanations, slides, or diagrams from Markdown or HTML.
Thanh-aperoAnalyze code semantics via AST parsing and KuzuDB graph database.
zzafergokConvert Markdown documents to HTML using marked.js, pandoc, gomarkdown, or static site generators.
