/design-docs:user-docs-badges

Normalize standard project badges in README files while preserving custom status indicators.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/spencerbeggs/design-docs-plugin --skill design-docs-user-docs-badges
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: /design-docs:user-docs-badges
Source: https://github.com/spencerbeggs/design-docs-plugin/tree/main/plugin/skills/user-docs-badges
Command: npx skills add https://github.com/spencerbeggs/design-docs-plugin --skill design-docs-user-docs-badges

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort of maintaining consistent, up-to-date badge blocks in project README files, ensuring that metadata like license, runtime, and TypeScript support is always accurate.

Core Features & Use Cases

  • Automated Normalization: Automatically detects and updates the four standard badges (npm, License, Runtime, TypeScript) while preserving custom badges like CI status or code coverage.
  • Smart Detection: Intelligently distinguishes between package-level READMEs and monorepo root documentation to apply the correct badge strategy.
  • Use Case: When updating a project's Node.js version or license, run this skill to instantly refresh the badge block without manually editing Markdown image links.

Quick Start

Use the user-docs-badges skill to normalize the badge block in the current README.md file.

Frequently Asked Questions about /design-docs:user-docs-badges

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically update README badges when project metadata changes?

You can automatically update README badges by running a skill that detects package metadata and surgically updates standard badge blocks for npm, License, Runtime, and TypeScript while preserving custom status indicators.

How do I standardize badge blocks in a monorepo root README without losing custom CI status badges?

Standardizing badge blocks in monorepo documentation involves smart detection that distinguishes root READMEs from package-level READMEs, applying correct badge strategies while leaving custom badges untouched.

What is the best way to maintain consistent license and runtime badges across multiple README files?

Maintaining consistent README badges is best handled by automated normalization, which identifies package metadata and updates the four standard badges without requiring manual Markdown image link edits.

Do I need a specific subagent to normalize documentation badges in my project?

Normalizing documentation badges requires integration with the user-docs subagent to perform structural analysis and file modification of the README.md file.

Why does my badge block not update when I change my project's Node.js version?

Your badge block may not update because standard badges require automated normalization to detect package metadata changes and refresh the image links in the README file.

Can I preserve custom code coverage badges while normalizing standard npm badges?

You can preserve custom code coverage badges during normalization because the process intelligently distinguishes between standard metadata badges and custom status indicators, updating only the four standard badges.