How do I install the Framework Parsers skill?

Run npx skillmds@latest add markuplint/framework-parsers in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Framework Parsers safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Framework Parsers?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Framework Parsers free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Framework Parsers?

markuplint (@markuplint) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Framework Parsers by markuplint — Agent Skill

Name: Framework Parsers
Author: markuplint

Framework Parsers

Create and maintain framework parser and spec packages for markuplint — package types, naming, and the architectural constraints that break the build or runtime contracts when violated. Use when adding or modifying any @markuplint/*-parser or @markuplint/*-spec package. Trigger keywords: new parser, template engine parser, framework parser, spec package, ExtendedSpec, ignoreTags, component-scanner.

markuplint 1aefdde 2.5 KB Updated Sep 17, 2026

File contents

framework-parsers

Create and maintain framework parser and spec packages for markuplint.

Architecture

The parser hierarchy, extension points, and design rationale are documented in the Parser class JSDoc in packages/@markuplint/parser-utils/src/parser.ts. Read it before extending. For concrete patterns, read an existing sibling package (template engine: ejs-parser; full framework: astro-parser; spec: react-spec) — new packages follow the sibling's structure.

Package types and naming

@markuplint/<lang>-parser — parser package. Two kinds:
- Template engine parsers extend HtmlParser and configure only ignoreTags.
- Full framework parsers extend Parser and implement tokenize(), nodeize(), visitAttr(), detectElementType(), delegating tokenization to the framework's own parser library.
@markuplint/<lang>-spec — spec package exporting an ExtendedSpec object (global attributes + per-element overrides).

Rules (constraints — violations break the build or runtime contracts)

Template parsers must only configure ignoreTags — never override tokenize() or nodeize().
Full parsers must delegate tokenization to an external parser library — never implement framework parsing from scratch.
Spec packages must only export an ExtendedSpec object — no parsing logic.
Use potentialName for attribute mapping — it tells markuplint which standard HTML attribute a framework attribute corresponds to.
Test with nodeListToDebugMaps — the standard assertion pattern across all parsers.
Full framework parsers must ship a component-scanner subpath export ("./component-scanner" in package.json exports) — @markuplint/pretenders dynamically imports it at runtime for auto scan. Without it, the framework's components are not detected.
Never import from @markuplint/pretenders inside component-scanner — define local types structurally compatible with its ComponentScanner interface. Importing pretenders creates a circular dependency in the lerna build graph.

---name: framework-parsersdescription: Create and maintain framework parser and spec packages for markuplint — package types, naming, and the architectural constraints that break the build or runtime contracts when violated. Use when adding or modifying any @markuplint/*-parser or @markuplint/*-spec package. Trigger keywords: new parser, template engine parser, framework parser, spec package, ExtendedSpec, ignoreTags, component-scanner.---# framework-parsersCreate and maintain framework parser and spec packages for markuplint.## ArchitectureThe parser hierarchy, extension points, and design rationale are documented in the `Parser` class JSDoc in `packages/@markuplint/parser-utils/src/parser.ts`. Read it before extending. For concrete patterns, read an existing sibling package (template engine: `ejs-parser`; full framework: `astro-parser`; spec: `react-spec`) — new packages follow the sibling's structure.## Package types and naming- `@markuplint/<lang>-parser` — parser package. Two kinds: - **Template engine parsers** extend `HtmlParser` and configure only `ignoreTags`. - **Full framework parsers** extend `Parser` and implement `tokenize()`, `nodeize()`, `visitAttr()`, `detectElementType()`, delegating tokenization to the framework's own parser library.- `@markuplint/<lang>-spec` — spec package exporting an `ExtendedSpec` object (global attributes + per-element overrides).## Rules (constraints — violations break the build or runtime contracts)1. **Template parsers must only configure `ignoreTags`** — never override `tokenize()` or `nodeize()`.2. **Full parsers must delegate tokenization to an external parser library** — never implement framework parsing from scratch.3. **Spec packages must only export an `ExtendedSpec` object** — no parsing logic.4. **Use `potentialName` for attribute mapping** — it tells markuplint which standard HTML attribute a framework attribute corresponds to.5. **Test with `nodeListToDebugMaps`** — the standard assertion pattern across all parsers.6. **Full framework parsers must ship a `component-scanner` subpath export** (`"./component-scanner"` in `package.json` `exports`) — `@markuplint/pretenders` dynamically imports it at runtime for auto scan. Without it, the framework's components are not detected.7. **Never import from `@markuplint/pretenders` inside component-scanner** — define local types structurally compatible with its `ComponentScanner` interface. Importing pretenders creates a circular dependency in the lerna build graph.

Frequently asked questions