source-command-audit-prose

Featured

Add descriptive prose to bare sections in whitepapers (FR + EN) using 9 parallel agents

AI & Automation 5,772 stars 755 forks Updated today CC-BY-SA-4.0

Install

View on GitHub

Quality Score: 90/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# source-command-audit-prose Use this skill when the user asks to run the migrated source command `audit-prose`. ## Command Template # Audit Prose — Enrichissement des Sections Bare Ajoute de la prose descriptive (2-4 phrases) devant chaque section "bare" des whitepapers. Une section "bare" = heading suivi directement d'une table, code block, ou liste sans paragraphe d'intro. ## Usage ``` /audit-prose # Tous les WPs (00-08), FR + EN /audit-prose 07 # WP07 seulement (FR + EN) /audit-prose 03 07 # WP03 et WP07 seulement ``` ## Définition "Bare Section" Section (`##` ou `###`) suivie DIRECTEMENT par : - Une table Markdown (`|`) - Un code block (` ``` `) - Une liste à puces (`-`) ou numérotée Sans paragraphe d'introduction (minimum 2 phrases). ## Règles Strictes (non négociables) 1. **NE JAMAIS** terminer un paragraphe par `:` avant une liste à puces → bug Typst qui fusionne les bullets en inline 2. **NE PAS** inventer de chiffres, métriques, ou citations 3. **NE PAS** ajouter de callouts (`:::`), Mermaid, ou scénarios persona 4. **NE PAS** dépasser +15% de lignes par fichier 5. Versions maintenues à **3.27.6** 6. Prose EN = anglais naturel, **pas** de traduction mot-à-mot du FR 7. Chaque ajout = **minimum 2 phrases, maximum 4 phrases** ## Exemple de Transformation ``` AVANT : ### Exit Codes | Code | Signification | |------|---------------| | 0 | Autorisé | APRÈS : ### Exit Codes Les hooks communiquent avec Codex via des codes de sortie standardi...

Details

Author
FlorianBruniaux
Repository
FlorianBruniaux/claude-code-ultimate-guide
Created
7 months ago
Last Updated
today
Language
Python
License
CC-BY-SA-4.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

polish-open-source-prose

Audit, draft, and revise public-facing prose for open-source software so it is specific, credible, and natural without flattening the project's voice. Use for README files, documentation, landing pages, release notes, changelogs, contribution guides, PR or issue text, UI copy, error messages, prompts, Traditional Chinese (Taiwan) localization, and questions about AI-text watermarking or author provenance. Use when the user asks to remove AI-sounding language, marketing fluff, generic wording, or improve editorial quality. Do not use for code-only tasks with no prose work.

8 Updated today
ting-hong-shieh
AI & Automation Featured

copywriting-prose-creator

Codifies how someone or a brand writes — prose mechanics (lexicon, syntax, rhythm, structure, signature moves) independent of emotional tone. Output: PROSE.md. Three modes: BUILD a fresh guide from SOUL.md + TONE.md + discovery interview; ADAPT an existing guide to a new channel; AUDIT a corpus for prose patterns before codification. Use when: writing rules for a content factory, codifying ghostwriting voice for multi-writer consistency, defining banned words and sentence-length targets, building a house style guide, reverse-engineering prose from a corpus, porting style across channels. Trigger on: PROSE.md, writing style guide, prose guide, house style, ghostwriter style, writing playbook, brand writing mechanics, signature moves. NOT for: writing actual content (→ linkedin-ghostwriting, technical-article-writer, press-release-writer), removing AI patterns (→ humanizer), tone decisions (→ copywriting-tone-of-voice), hooks (→ copywriting-hooks), CTAs (→ copywriting-cta).

188 Updated yesterday
samber
AI & Automation Listed

repo-prose

Write clear technical prose for anything that lives in a repository or on a forge: commit messages, PR titles and descriptions, PR and code review comments, issue text, READMEs, documentation, changelogs, ADRs, code comments, error and log messages. Use when composing any of these, and when editing an existing one. Combines Strunk's composition rules with a kill list of AI writing tells tuned for Claude output. Not for prose that needs a personal voice, such as blog posts, essays, or launch announcements.

0 Updated 2 days ago
svyatov