What is the primary focus of the md-style skill?

It focuses on creating concise, technical README files that prioritize engineering specifications over marketing language, opinions, or project history.

Does this skill help with Markdown syntax?

This skill focuses specifically on language and writing style. It is designed to be used in conjunction with the /md-writer skill, which handles Markdown syntax and formatting rules.

Why does this skill exclude roadmaps and tables of contents?

The philosophy behind this skill is to treat a README as an engineering specification. To maximize efficiency for experienced developers, it removes navigational 'fluff' and future plans to focus on the current implementation.

Is the md-style skill user-invocable?

No, this skill is typically configured to run automatically when Claude is tasked with creating or updating README.md files to ensure consistent documentation standards.

Engineering README Style Guide

Name: Engineering README Style Guide
Author: jimweller

byjimweller

0•

학습 및 문서화

Enforces a concise, direct, and fluff-free writing style for technical README documentation tailored for experienced engineers.

The md-style skill provides a strict framework for creating high-quality engineering documentation. It eliminates marketing hyperbole, repetitive information, and unnecessary roadmaps, focusing instead on technical specifications, architecture diagrams, and essential configuration data. By prioritizing brevity and factual accuracy, it ensures that README files serve as efficient tools for developers rather than promotional materials or project plans.

주요 기능

01Enforces a 'No Fluff' policy by removing tables of contents and verbose explanations.

02Strips marketing language and hyperbole for a purely technical, direct tone.

03Standardizes README structure with specific sections for Architecture, Usage, and Configuration.

04Implements factual, direct-voice writing patterns to improve information density.

05Automates the exclusion of roadmaps and development history in favor of documentation of the current state.

060 GitHub stars

사용 사례

01Standardizing documentation across a large engineering organization's repositories.

02Refactoring verbose legacy READMEs into concise, professional technical specifications.

03Generating new project documentation that assumes a competent, experienced developer audience.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jimweller/davit-dataops-dotfiles md-style

For use in Claude.ai and ChatGPT

주요 기능

01Enforces a 'No Fluff' policy by removing tables of contents and verbose explanations.

02Strips marketing language and hyperbole for a purely technical, direct tone.

03Standardizes README structure with specific sections for Architecture, Usage, and Configuration.

04Implements factual, direct-voice writing patterns to improve information density.

05Automates the exclusion of roadmaps and development history in favor of documentation of the current state.

060 GitHub stars

사용 사례

01Standardizing documentation across a large engineering organization's repositories.

02Refactoring verbose legacy READMEs into concise, professional technical specifications.

03Generating new project documentation that assumes a competent, experienced developer audience.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jimweller/davit-dataops-dotfiles md-style

For use in Claude.ai and ChatGPT