xplat-docs-platform-block

Guidance for using PlatformBlock in xplat MDX after ApiLink moved to registry-based resolution: the import, case-sensitive platform names, what must not be wrapped, ComponentBlock nesting, tag balance and platform coverage. WHEN TO USE: adding, fixing or auditing a PlatformBlock, or wrapping prose or markup that belongs to some platforms and not others. WHEN NOT TO USE: ApiLink markup or API term resolution (use xplat-docs-api-links), json-snippet blocks (use xplat-docs-json-snippets), or whole-topic structure (use igniteui-doc-topics).

Aller à l'installation Vérifier les fichiers

Dépôt: IgniteUI/igniteui-documentation
Dernière activité de la source: 20 octobre 2026 à 14:01
Langue détectée de SKILL.md: anglais
Étoiles: 6
Forks: 1

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec un assistant IA

Copiez ce prompt dans l’assistant IA que vous utilisez.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/IgniteUI/igniteui-documentation/tree/vnext/.claude/skills/xplat-docs-platform-block.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/IgniteUI/igniteui-documentation --skill xplat-docs-platform-block

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

SKILL.md

Instructions source · Aperçu en lecture seule

name: xplat-docs-platform-block
description: Guidance for using PlatformBlock in xplat MDX after ApiLink moved to registry-based resolution: the import, case-sensitive platform names, what must not be wrapped, ComponentBlock nesting, tag balance and platform coverage. WHEN TO USE: adding, fixing or auditing a PlatformBlock, or wrapping prose or markup that belongs to some platforms and not others. WHEN NOT TO USE: ApiLink markup or API term resolution (use xplat-docs-api-links), json-snippet blocks (use xplat-docs-json-snippets), or whole-topic structure (use igniteui-doc-topics).

# xplat-docs-platform-block (pointer) Generated by `scripts/sync-agent-skills.mjs`. Do not edit. Claude Code discovers project skills only from `.claude/skills/`, so this file exposes the skill there. The source of truth is [`.github/skills/xplat-docs-platform-block/SKILL.md`](../../../.github/skills/xplat-docs-platform-block/SKILL.md) — read it and follow it as your complete instructions before taking any action. Resolve every reference path in the canonical skill relative to its own directory, `.github/skills/xplat-docs-platform-block/`. This pointer carries no rules. If it ever disagrees with the canonical skill, the canonical skill wins.

Voir sur GitHub

Retour à la recherche Retour à l’installation

igniteui-doc-topics

Authors and audits Ignite UI documentation topics - component pages, how-to guides, conceptual overviews and category indexes - across the Angular and cross-platform (React / Web Components / Blazor / WinUI / Uno) doc sets. Applies the Diataxis framework mapped onto Ignite UI house templates: canonical section order, fixed heading names, frontmatter, .mdx sample embeds, and per-framework token and PlatformBlock mechanics. WHEN TO USE: writing, reviewing, auditing, fixing or standardizing a topic, tutorial, guide, reference page or concept overview, including when the request is only "write docs for the X component"; deciding what kind of documentation a page should be; or separating a topic that mixes tutorial, how-to, reference and explanation content. WHEN NOT TO USE: frontmatter-only audits (use igniteui-topic-frontmatter), ApiLink markup (use xplat-docs-api-links), PlatformBlock alone (use xplat-docs-platform-block), or authoring a SKILL.md (use skill-authoring).

2026-10-23

igniteui-topic-frontmatter

Audits and normalizes YAML frontmatter metadata on Ignite UI MDX documentation topics: SEO titles, meta descriptions, llms.description, keywords, canonical links, relatedComponents, mentionedTypes, license and the AI-readable page identity, across the Angular and xplat doc sets. It is strictly frontmatter-only, audit-first: it reports findings and offers suggestions for the user to choose from before changing anything, and never edits topic body content, headings, prose, samples, code snippets, links, tables or section structure. WHEN TO USE: a task mentions frontmatter, SEO titles, meta descriptions, llms.description, keywords, canonical links, relatedComponents, mentionedTypes, metadata uniformity, or AI-readable page identity on a documentation topic. WHEN NOT TO USE: anything touching body content, structure, headings, prose or samples (use igniteui-doc-topics), or frontmatter on a SKILL.md rather than on a topic (use skill-authoring).

2026-10-23

xplat-docs-api-links

Reference guide for authoring and auditing API terms in the multi-platform docs tree. Strict-xplat topics require canonical backticked terms; other populations may use raw ApiLink components. Covers the platformType populations, the apiTerms modes, raw ApiLink props, and pkg/kind disambiguation. WHEN TO USE: adding, fixing or auditing an ApiLink or a backticked API term in xplat MDX, deciding how a page's platformType or apiTerms affects its names, or resolving a check-mdx-links ambiguity report. WHEN NOT TO USE: PlatformBlock on its own (use xplat-docs-platform-block), json-snippet blocks (use xplat-docs-json-snippets), whole-topic structure (use igniteui-doc-topics), or MDX topic frontmatter (use igniteui-topic-frontmatter).

2026-10-22

Tout voir dans ce dépôt

xplat-docs-platform-block

Informations de source

Options d'installation

Installer avec un assistant IA

Vérifiez les fichiers source

Plus depuis ce dépôt

Installer avec un assistant IA

Plus depuis ce dépôt