Two skills ship with NgMd so coding agents already know how to scaffold and author. Mirrors the format angular/skills uses.

Agent Skills

NgMd ships two agent skills in the skills/ directory. A skill is a self-contained instruction file (SKILL.md with YAML frontmatter) that teaches a coding agent how to perform a specific task inside an NgMd project. Agents that support skills (Claude Code, Gemini CLI, Antigravity, and others) load the relevant skill on demand instead of re-deriving conventions from the codebase every time.

The format mirrors angular/skills exactly so any tool that handles one handles the other.

Available skills

Skill	Description
ngmd-new-site	Scaffolds a new NgMd site with create-ngmd. Covers Node prerequisites, package-manager fallback, the post-scaffold layout, and the first edits a new project needs (site config, sidebar nav, first markdown page).
ngmd-authoring	Writes and edits pages in an NgMd project. Covers the prose-vs-component page model, all seventeen authoring components, the markdown affordances (*Keyword autolinks, file="..." code imports, group="..." tabs, {1,3-5} line highlighting), the build-time link guards, and the prose voice the project favours.

Using these skills

Both skills are designed for agentic coding tools like Claude Code, Gemini CLI, Antigravity, and others. Activating a skill loads the specific instructions and resources needed for that task.

If your agent supports the skills.sh community installer, one command and you're done. Otherwise it's a directory copy into wherever your tool looks for skills.

npx skills add https://github.com/erkamyaman/ngmd

Manual install paths

Tool	Skills directory
Claude Code	~/.claude/skills/ (user-wide) or .claude/skills/ (per-project)
Gemini CLI	.agent/skills/ in the project root
Antigravity	Configured via the editor's skills panel
Any other agent	Wherever the tool looks for SKILL.md files

Drop the two folders (ngmd-new-site/, ngmd-authoring/) from this repo's skills/ directory into the location above, and your agent will pick them up on next load.

Versioning

The skills live next to the framework. When the conventions in NgMd change (a new component, a new affordance, a renamed config key), the matching skill files get updated in the same PR. There's no separate release cadence to track.

Skill	Last touched in
ngmd-new-site	Same release as the scaffolder it documents
ngmd-authoring	Same release as the NgmdUi vocabulary it documents

Feedback Beta

If a skill gives a wrong answer or misses a convention:

• File an issue at github.com/erkamyaman/ngmd/issues
• Or open a Discussion if you want to talk through whether the skill should cover the case before you file

The source of truth lives next to the framework, so fixes ship with the next release.