본문으로 건너뛰기
cccskills
무료GitHub에 공개

documentation-guide

Guide documentation structure, README content, and project documentation best practices. Use when: creating README, documentation, docs folder, project setup. Keywords: README, docs, documentation, CONTRIBUTING, CHANGELOG, 文件, 說明文件.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(3)

  • SKILL.md5.3 KB
  • documentation-structure.md6.5 KB
  • readme-template.md6.8 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Documentation Guide

This skill provides guidance on project documentation structure, README content, and documentation best practices.

Quick Reference

Essential Project Files

FileRequiredPurpose
README.md✅Project overview, quick start
CONTRIBUTING.mdRecommendedContribution guidelines
CHANGELOG.mdRecommendedVersion history
LICENSE✅ (OSS)License information

Documentation Completeness Checklist

  • README.md exists with essential sections
  • Installation instructions are clear
  • Usage examples are provided
  • Contributing guidelines documented
  • License specified

Detailed Guidelines

For complete standards, see:

README.md Required Sections

Minimum Viable README

# Project Name

Brief one-liner description.

## Installation

```bash
npm install your-package

Usage

const lib = require('your-package');
lib.doSomething();

License

MIT


### Recommended README Sections

1. **Project Name & Description**
2. **Badges** (CI status, coverage, npm version)
3. **Features** (bullet list)
4. **Installation**
5. **Quick Start / Usage**
6. **Documentation** (link to docs/)
7. **Contributing** (link to CONTRIBUTING.md)
8. **License**

## docs/ Directory Structure

docs/ ├── index.md # Documentation index ├── getting-started.md # Quick start guide ├── architecture.md # System architecture ├── api-reference.md # API documentation ├── deployment.md # Deployment guide └── troubleshooting.md # Common issues


## File Naming Conventions

### Root Directory (UPPERCASE)

README.md # ✅ GitHub auto-displays CONTRIBUTING.md # ✅ GitHub auto-links in PR CHANGELOG.md # ✅ Keep a Changelog convention LICENSE # ✅ GitHub auto-detects


### docs/ Directory (lowercase-kebab-case)

docs/getting-started.md # ✅ URL-friendly docs/api-reference.md # ✅ URL-friendly docs/GettingStarted.md # ❌ Case issues docs/API_Reference.md # ❌ Inconsistent


## Examples

### Good README.md

```markdown
# MyProject

A fast, lightweight JSON parser for Node.js.

[![CI](https://github.com/org/repo/actions/workflows/ci.yml/badge.svg)](https://github.com/org/repo/actions)
[![npm version](https://badge.fury.io/js/myproject.svg)](https://www.npmjs.com/package/myproject)

## Features

- 10x faster than standard JSON.parse
- Streaming support
- Type-safe with TypeScript

## Installation

```bash
npm install myproject

Quick Start

const { parse } = require('myproject');

const data = parse('{"name": "test"}');
console.log(data.name); // "test"

Documentation

See docs/ for full documentation.

Contributing

See CONTRIBUTING.md for contribution guidelines.

License

MIT - see LICENSE


### Good CHANGELOG.md

```markdown
# Changelog

All notable changes to this project will be documented in this file.

## [Unreleased]

### Added
- New feature X

## [1.2.0] - 2025-12-15

### Added
- OAuth2 authentication support
- New API endpoint `/users/profile`

### Changed
- Improved error messages

### Fixed
- Memory leak in session cache

## [1.1.0] - 2025-11-01

### Added
- Initial release

Configuration Detection

This skill supports project-specific documentation configuration.

Detection Order

  1. Check CONTRIBUTING.md for "Disabled Skills" section
    • If this skill is listed, it is disabled for this project
  2. Check CONTRIBUTING.md for "Documentation Language" section
  3. Check existing documentation structure
  4. If not found, default to English

Documentation Audit

When reviewing a project, check for:

ItemHow to Check
README existsFile present at root
README completeHas installation, usage, license sections
CONTRIBUTING existsFile present (for team projects)
CHANGELOG existsFile present (for versioned projects)
docs/ organizedHas index.md, logical structure
Links workingInternal links resolve correctly

First-Time Setup

If documentation is missing:

  1. Ask the user: "This project doesn't have complete documentation. Which language should I use? (English / 中文)"
  2. After user selection, suggest documenting in CONTRIBUTING.md:
## Documentation Language

This project uses **[chosen option]** for documentation.
<!-- Options: English | 中文 -->
  1. Start with README.md (essential)
  2. Add LICENSE (for open source)
  3. Add CONTRIBUTING.md (for team projects)
  4. Create docs/ structure (for complex projects)

Configuration Example

In project's CONTRIBUTING.md:

## Documentation Language

This project uses **English** for documentation.
<!-- Options: English | 中文 -->

License: CC BY 4.0 | Source: universal-dev-standards

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Prevent AI hallucination and ensure evidence-based responses when analyzing code or making suggestions. Use when: analyzing code, making recommendations, providing options, or when user asks about confidence/certainty. Keywords: certainty, assumption, inference, evidence, source, 確定性, 推測, 假設, 來源, 證據.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AsiaOstrich/universal-dev-skills432025년 12월 30일 업데이트

Systematic code review checklist and pre-commit quality gates for PRs. Use when: reviewing pull requests, checking code quality, before committing code. Keywords: review, PR, pull request, checklist, quality, commit, 審查, 檢查, 簽入.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AsiaOstrich/universal-dev-skills432025년 12월 30일 업데이트

Format commit messages following conventional commits standard. Use when: writing commit messages, git commit, reviewing commit history. Keywords: commit, git, message, conventional, 提交, 訊息, feat, fix, refactor.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AsiaOstrich/universal-dev-skills432025년 12월 30일 업데이트

Guide Git branching strategies, branch naming, and merge operations. Use when: creating branches, merging, pull requests, Git workflow questions. Keywords: branch, merge, PR, pull request, GitFlow, GitHub Flow, 分支, 合併, 工作流程.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AsiaOstrich/universal-dev-skills432025년 12월 30일 업데이트

Semantic versioning and changelog formatting for software releases. Use when: preparing releases, updating version numbers, writing changelogs. Keywords: version, release, changelog, semver, major, minor, patch, 版本, 發布, 變更日誌.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AsiaOstrich/universal-dev-skills432025년 12월 30일 업데이트

Guide requirement writing, user story creation, and feature specification. Use when: writing requirements, user stories, issues, feature planning. Keywords: requirement, user story, issue, feature, specification, 需求, 功能規劃, 規格.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AsiaOstrich/universal-dev-skills432025년 12월 30일 업데이트

AsiaOstrich의 스킬 모두 보기

이 스킬의 문제 신고