How this skill is triggered — by the user, by Claude, or both
Slash command
/docs-generator:generating-writeupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Target**: $ARGUMENTS
templates/project-report-IMRaD/00_title_abstract_abbrev.textemplates/project-report-IMRaD/01_build_settings.mdtemplates/project-report-IMRaD/02_project_introduction.mdtemplates/project-report-IMRaD/03_desired_state.mdtemplates/project-report-IMRaD/04_planning_and_solution.mdtemplates/project-report-IMRaD/05_implementation.mdtemplates/project-report-IMRaD/06_control_of_success.mdtemplates/project-report-IMRaD/07_results.mdtemplates/project-report-IMRaD/08_summary_outlook.mdtemplates/project-report-IMRaD/09a_bibliography.bibtemplates/project-report-IMRaD/10_appendices.mdtemplates/project-report-IMRaD/11_index.mdtemplates/technical-doc/01_build_settings.mdtemplates/technical-doc/02_overview.mdtemplates/technical-doc/03_architecture.mdtemplates/technical-doc/04_api.mdtemplates/technical-doc/05_configuration.mdtemplates/technical-doc/06_deployment.mdtemplates/technical-doc/07_troubleshooting.mdtemplates/technical-doc/09a_bibliography.bibTarget: $ARGUMENTS
Generates structured academic/technical writeups as markdown with citation
support. IEEE [1] style by default. PDF export via pandoc is optional.
project-report-IMRaD), and citation styledocs/write-up/<topic>/templates/ to docs/write-up/<topic>/:
project-report-IMRaD — scientific/academic (Introduction, Methods, Results, Discussion)technical-doc — software documentation (Overview, Architecture, API, Config, Deployment)09a_bibliography.bibnpx markdownlint-cli docs/write-up/<topic>/*.mdmake pandoc_runmake -f $CLAUDE_PLUGIN_ROOT/Makefile setup_pdf_converter HELPmake -f $CLAUDE_PLUGIN_ROOT/Makefile pandoc_run HELP=1| Style | CSL File | Notes |
|---|---|---|
| IEEE (default) | Bundled (scripts/writeup/citation-styles/ieee.csl) | Numeric [1] |
| APA | Bundled (scripts/writeup/citation-styles/apa.csl) | Author-date (Smith, 2024) |
| Chicago | Bundled (scripts/writeup/citation-styles/chicago-author-date.csl) | Author-date (Smith 2024) |
Additional CSL files are available from the Zotero Style Repository.
If pandoc and LaTeX are installed, generate PDF using the bundled Makefile:
dir=docs/write-up/<topic> && \
make -f $CLAUDE_PLUGIN_ROOT/Makefile pandoc_run \
INPUT_FILES="$$(printf '%s\036' $$dir/*.md)" \
OUTPUT_FILE="$$dir/output.pdf" \
BIBLIOGRAPHY="$$dir/09a_bibliography.bib"
With custom citation style:
dir=docs/write-up/<topic> && \
make -f $CLAUDE_PLUGIN_ROOT/Makefile pandoc_run \
INPUT_FILES="$$(printf '%s\036' $$dir/*.md)" \
OUTPUT_FILE="$$dir/output.pdf" \
BIBLIOGRAPHY="$$dir/09a_bibliography.bib" \
CSL="$CLAUDE_PLUGIN_ROOT/scripts/writeup/citation-styles/apa.csl"
Full writeup build (content generation + PDF):
make -f $CLAUDE_PLUGIN_ROOT/Makefile writeup \
WRITEUP_DIR=docs/write-up/<topic>
NEVER add manual section numbers to headings. Pandoc --number-sections
handles all numbering automatically.
# 2. Projektvorstellung, ## 2.1 Motivation, ### 2.1.1 Details# Projektvorstellung, ## Motivation, ### DetailsManual numbers in markdown headings conflict with pandoc auto-numbering and produce duplicated numbers in the PDF output.
Before completing:
N., N.N, N.N.N prefixesnpx markdownlint-cli docs/write-up/<topic>/*.md[@key] references exist in .bib filemake pandoc_runnpx claudepluginhub qte77/claude-code-plugins --plugin docs-generatorProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.