doc-create

Generates sequenced, formatted filenames for new documentation entries.

Updated May 1, 2026
One-click install
npx skills add https://github.com/42hz-ai/42hz-hardware-sbc-config --skill doc-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-create
Source: https://github.com/42hz-ai/42hz-hardware-sbc-config/tree/main/.cursor/skills/doc-create
Command: npx skills add https://github.com/42hz-ai/42hz-hardware-sbc-config --skill doc-create

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation and consistent naming of documentation files following a strict convention, reducing manual errors and saving time.

Core Features & Use Cases

  • Naming Automation: Generate filenames based on repository identifier, prefix, sequential numbers, and descriptive slugs.
  • Versioning with Sequence: Ensure unique and ordered documentation identifiers for projects.
  • Use Case: Adding a new infrastructure document by auto-generating the filename IDCTR-INFRA-0003-aws-identity-center.md aligned with existing files.

Quick Start

Use the doc-create skill to generate a new documentation filename with the correct sequence number for the INFRA prefix.

Frequently Asked Questions about doc-create

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

FAQPage Schema
How do I automate documentation file naming conventions across projects?

Automate documentation file naming by generating filenames based on repository identifier, prefix, sequential numbers, and descriptive slugs. This ensures filenames adhere to defined formats and sequences without manual input.

How do I add sequential versioning to infrastructure documentation filenames?

Add sequential versioning to infrastructure documentation by auto-generating filenames with ordered identifiers. This ensures unique and ordered documentation identifiers for projects, such as appending sequence numbers to an INFRA prefix.

What is the best way to maintain consistent naming standards for software engineering documentation?

The best way to maintain consistent naming standards is using automated conventions to generate filenames. This reduces manual errors and saves time by enforcing a strict format across all documentation files in software engineering workflows.

Can I generate descriptive slugs for new documentation files automatically?

Yes, you can generate descriptive slugs automatically when creating new documentation files. The automation combines the repository identifier, prefix, sequential number, and slug into a standardized filename without requiring manual input.

Does automated file naming work for infrastructure documentation workflows?

Automated file naming works for infrastructure documentation workflows needing structured file conventions. It generates correctly sequenced filenames like IDCTR-INFRA-0003-aws-identity-center.md, aligning new files with existing documentation standards.