skills.rest
SalesforceCommerceCloud
SalesforceCommerceCloudOFFICIAL
Explore all skills by this author →
Website𝕏@commercecloudGitHub

documentation

Update B2C CLI documentation across guides, CLI reference, and API reference.

51|16|Updated Oct 31, 2025
Search Tags:#documentation#writing#markdown#API-docs#guide-update#CLI-reference
One-click install
npx skills add https://github.com/SalesforceCommerceCloud/b2c-developer-tooling --skill documentation-salesforcecommercecloud
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: documentation
Source: https://github.com/SalesforceCommerceCloud/b2c-developer-tooling/tree/main/.claude/skills/documentation
Command: npx skills add https://github.com/SalesforceCommerceCloud/b2c-developer-tooling --skill documentation-salesforcecommercecloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill updates and maintains project documentation for the B2C CLI across guides, CLI reference, and API reference, reducing drift between code and docs.

Core Features & Use Cases

  • Structured documentation updates: Aligns new features and changes with installation, authentication, and configuration guides.
  • Cross-link consistency: Keeps navigation between guides, CLI references, and API docs coherent.
  • Use Case: After a feature release, update the docs to reflect new commands and examples, ensuring users can follow the latest setup steps.

Quick Start

Use the documentation skill to draft a new guide section explaining a recently added CLI command.

Frequently Asked Questions about documentation

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

FAQPage Schema
How do I update B2C CLI documentation after a new feature release?▼

To update B2C CLI documentation after a feature release, draft new guide sections explaining the added CLI commands. This ensures installation, authentication, and configuration guides reflect the latest setup steps and examples.

What is the best way to keep CLI reference and API docs consistent?▼

Maintaining cross-link consistency keeps CLI reference and API docs coherent. This documentation approach enforces structured frontmatter metadata and a three-section Markdown format to align navigation across all content surfaces.

Does B2C CLI documentation require a specific Markdown format?▼

Yes, B2C CLI documentation requires a specific Markdown format. It enforces a structured frontmatter metadata schema and a three-section guidance format to align with repository guidelines and support automated site generation.

How do I prevent documentation drift when new commands are added to the B2C CLI?▼

Preventing documentation drift involves updating guides, CLI references, and API docs simultaneously when new commands are added. This structured documentation update process reduces inconsistencies between the codebase and the content.

Can I use structured Markdown to automate API docs site generation?▼

Yes, you can use structured Markdown to automate API docs site generation. By applying a structured frontmatter metadata schema and repository documentation guidelines, the content aligns to support automated site generation.

Related Skills

Explore More Content & Communication Skills→
rp1-runrp1-run
38

sample-skill

Parse SKILL.md front matter and extract name and description fields.

Official
Basic
lucking7lucking7

init

Generate a standardized AGENTS.md contributor guide for new repositories.

Community
Basic
pradyumnasagarpradyumnasagar
6

agent-handoff

Automate inter-skill data transfer and provenance capture via JSON Material Passports.

Community
Advanced
StarryCodStarryCod
11

llm-wiki

Automate building and maintaining an interlinked Markdown knowledge base.

Community
Advanced