wtf-p 0.1.0

package/write-the-f-paper/venues/acm-cs.yaml

@@ -0,0 +1,102 @@
+# ACM Computer Science Conference/Journal Template
+# Standard structure for ACM SIGMOD, SOSP, OSDI, EuroSys, etc.
+
+name: ACM Computer Science
+short: acm-cs
+description: Standard ACM CS conference structure (systems, databases, architecture)
+
+structure:
+  - number: 1
+    name: Introduction
+    slug: introduction
+    word_ratio: 0.15
+    purpose: |
+      Hook the reader with the problem. State contributions clearly.
+      End with paper organization paragraph.
+    subsections:
+      - Motivation and Problem Statement
+      - Contributions
+      - Paper Organization
+    citation_density: medium
+
+  - number: 2
+    name: Background and Motivation
+    slug: background
+    word_ratio: 0.12
+    purpose: |
+      Establish technical context. Define key concepts.
+      Motivate why existing solutions fall short.
+    subsections:
+      - Technical Background
+      - Motivating Example
+      - Problem Definition
+    citation_density: high
+
+  - number: 3
+    name: Approach and Methodology
+    slug: approach
+    word_ratio: 0.25
+    purpose: |
+      Core technical contribution. System design, algorithms, architecture.
+      This is the meat of the paper.
+    subsections:
+      - Overview
+      - Design/Architecture
+      - Key Techniques
+      - Implementation Details
+    citation_density: low
+
+  - number: 4
+    name: Evaluation and Experimental Results
+    slug: evaluation
+    word_ratio: 0.25
+    purpose: |
+      Prove it works. Benchmarks, comparisons, ablations.
+      Answer: Is it faster? More accurate? More scalable?
+    subsections:
+      - Experimental Setup
+      - Baseline Comparisons
+      - Performance Analysis
+      - Ablation Studies
+    citation_density: medium
+
+  - number: 5
+    name: Related Work
+    slug: related-work
+    word_ratio: 0.12
+    purpose: |
+      Position contribution in literature. Show you know the field.
+      Differentiate from similar work.
+    subsections:
+      - Category 1 (e.g., Systems approaches)
+      - Category 2 (e.g., ML-based approaches)
+      - Category 3 (e.g., Hybrid approaches)
+    citation_density: very_high
+
+  - number: 6
+    name: Conclusion and Future Work
+    slug: conclusion
+    word_ratio: 0.08
+    purpose: |
+      Summarize contributions. Acknowledge limitations.
+      Point to future directions.
+    subsections:
+      - Summary
+      - Limitations
+      - Future Directions
+    citation_density: none
+
+optional_sections:
+  - name: Acknowledgments
+    position: after_conclusion
+  - name: Appendix
+    position: end
+
+citation_style: acm
+page_limit_hint: "12-14 pages (double column)"
+
+notes: |
+  - Related Work typically comes AFTER evaluation in systems papers
+  - Contributions should be bulleted and specific
+  - Evaluation needs quantitative comparisons with baselines
+  - ACM venues expect reproducibility (artifact evaluation)

package/write-the-f-paper/venues/arxiv-ml.yaml

@@ -0,0 +1,103 @@
+# arXiv ML/AI Conference Template
+# Standard structure for NeurIPS, ICML, ICLR, AAAI, etc.
+
+name: arXiv ML/AI
+short: arxiv-ml
+description: Standard ML conference structure (NeurIPS, ICML, ICLR style)
+
+structure:
+  - number: 1
+    name: Introduction
+    slug: introduction
+    word_ratio: 0.12
+    purpose: |
+      Problem setup. Why this matters. Contribution summary.
+      ML papers are dense - get to the point fast.
+    subsections:
+      - Problem and Motivation
+      - Contributions
+    citation_density: medium
+
+  - number: 2
+    name: Related Work
+    slug: related-work
+    word_ratio: 0.10
+    purpose: |
+      Position in literature. ML moves fast - cite recent work.
+      Often brief, sometimes moved to appendix.
+    subsections:
+      - Prior Approaches
+      - Concurrent Work
+    citation_density: very_high
+
+  - number: 3
+    name: Preliminaries
+    slug: preliminaries
+    word_ratio: 0.08
+    purpose: |
+      Notation, problem formulation, background concepts.
+      Keep it tight - reviewers know the basics.
+    subsections:
+      - Notation
+      - Problem Setup
+      - Background
+    citation_density: medium
+
+  - number: 4
+    name: Method
+    slug: method
+    word_ratio: 0.25
+    purpose: |
+      Your algorithm/model. Math-heavy. Clear notation.
+      Pseudocode welcome. Theoretical analysis if applicable.
+    subsections:
+      - Overview
+      - Core Algorithm
+      - Theoretical Analysis
+    citation_density: low
+
+  - number: 5
+    name: Experiments
+    slug: experiments
+    word_ratio: 0.30
+    purpose: |
+      Empirical validation. Standard benchmarks required.
+      Ablations show each component matters.
+    subsections:
+      - Setup and Baselines
+      - Main Results
+      - Ablation Studies
+      - Analysis
+    citation_density: medium
+
+  - number: 6
+    name: Conclusion
+    slug: conclusion
+    word_ratio: 0.05
+    purpose: |
+      Brief wrap-up. Limitations often required section.
+    subsections:
+      - Summary
+      - Limitations
+      - Future Work
+    citation_density: none
+
+optional_sections:
+  - name: Abstract
+    position: before_introduction
+    word_limit: 200
+  - name: Broader Impact
+    position: after_conclusion
+  - name: Appendix
+    position: end
+    notes: Proofs, additional experiments, hyperparameters
+
+citation_style: neurips
+page_limit_hint: "8-9 pages + references + appendix"
+
+notes: |
+  - ML reviewers skim - make contributions crystal clear
+  - Notation consistency is critical
+  - Standard benchmarks expected (ImageNet, GLUE, etc.)
+  - Ablations are mandatory, not optional
+  - Broader Impact/Ethics statement increasingly required

package/write-the-f-paper/venues/ieee-cs.yaml

@@ -0,0 +1,100 @@
+# IEEE Computer Science Conference/Journal Template
+# Standard structure for IEEE IPDPS, SC, HPDC, TPDS, etc.
+
+name: IEEE Computer Science
+short: ieee-cs
+description: Standard IEEE CS conference structure (HPC, parallel systems, storage)
+
+structure:
+  - number: 1
+    name: Introduction
+    slug: introduction
+    word_ratio: 0.15
+    purpose: |
+      Problem statement and motivation. Clear contribution list.
+      IEEE style: more formal, less narrative.
+    subsections:
+      - Problem Statement
+      - Motivation
+      - Contributions
+      - Organization
+    citation_density: medium
+
+  - number: 2
+    name: Background and Related Work
+    slug: background
+    word_ratio: 0.15
+    purpose: |
+      IEEE often combines background with related work upfront.
+      Technical foundations + literature positioning.
+    subsections:
+      - Technical Background
+      - Related Work
+      - Positioning
+    citation_density: very_high
+
+  - number: 3
+    name: System Design
+    slug: design
+    word_ratio: 0.22
+    purpose: |
+      Architecture and design decisions.
+      IEEE emphasizes clear diagrams and formal descriptions.
+    subsections:
+      - Architecture Overview
+      - Component Design
+      - Algorithms
+      - Optimizations
+    citation_density: low
+
+  - number: 4
+    name: Implementation
+    slug: implementation
+    word_ratio: 0.10
+    purpose: |
+      Implementation specifics. IEEE values reproducibility details.
+      Hardware/software environment, parameters.
+    subsections:
+      - System Implementation
+      - Experimental Platform
+    citation_density: low
+
+  - number: 5
+    name: Evaluation
+    slug: evaluation
+    word_ratio: 0.25
+    purpose: |
+      Rigorous experimental validation.
+      IEEE expects statistical rigor and scalability analysis.
+    subsections:
+      - Experimental Setup
+      - Performance Evaluation
+      - Scalability Analysis
+      - Comparative Analysis
+    citation_density: medium
+
+  - number: 6
+    name: Conclusion
+    slug: conclusion
+    word_ratio: 0.08
+    purpose: |
+      Brief summary. Future work optional but common.
+    subsections:
+      - Summary
+      - Future Work
+    citation_density: none
+
+optional_sections:
+  - name: Acknowledgments
+    position: after_conclusion
+  - name: References
+    position: end
+
+citation_style: ieee
+page_limit_hint: "10-12 pages (double column)"
+
+notes: |
+  - IEEE often wants Related Work early (Section 2)
+  - Implementation details get their own section
+  - Scalability analysis is expected for systems papers
+  - Figures should be IEEE-compliant (grayscale-friendly)

package/write-the-f-paper/venues/nature.yaml

@@ -0,0 +1,81 @@
+# Nature/Science IMRaD Template
+# Standard structure for life sciences, interdisciplinary research
+
+name: Nature/Science (IMRaD)
+short: nature
+description: Classic IMRaD structure for life sciences and Nature-family journals
+
+structure:
+  - number: 1
+    name: Introduction
+    slug: introduction
+    word_ratio: 0.15
+    purpose: |
+      Funnel structure: broad context → specific gap → your contribution.
+      End with clear statement of what you did and found.
+    subsections:
+      - Context
+      - Gap
+      - Approach
+    citation_density: high
+
+  - number: 2
+    name: Methods
+    slug: methods
+    word_ratio: 0.25
+    purpose: |
+      Reproducibility is paramount. Every detail needed to replicate.
+      Often moved to end or supplementary in Nature-family.
+    subsections:
+      - Experimental Design
+      - Data Collection
+      - Analysis Methods
+      - Statistical Analysis
+    citation_density: medium
+
+  - number: 3
+    name: Results
+    slug: results
+    word_ratio: 0.30
+    purpose: |
+      Present findings objectively. No interpretation yet.
+      Each figure/table gets narrative explanation.
+    subsections:
+      - Finding 1
+      - Finding 2
+      - Finding 3
+    citation_density: low
+
+  - number: 4
+    name: Discussion
+    slug: discussion
+    word_ratio: 0.25
+    purpose: |
+      Interpret results. Connect to literature. Acknowledge limitations.
+      End with implications and future directions.
+    subsections:
+      - Interpretation
+      - Comparison to Literature
+      - Limitations
+      - Implications
+    citation_density: high
+
+optional_sections:
+  - name: Abstract
+    position: before_introduction
+    word_limit: 150-250
+  - name: Acknowledgments
+    position: after_discussion
+  - name: Data Availability
+    position: end
+  - name: Supplementary Materials
+    position: end
+
+citation_style: nature
+page_limit_hint: "3000-5000 words main text"
+
+notes: |
+  - Abstract is crucial - often only part read
+  - Methods may be brief in main text, detailed in supplement
+  - Results and Discussion sometimes combined
+  - Figures are premium real estate - make them count

package/write-the-f-paper/venues/thesis-chapter.yaml

@@ -0,0 +1,101 @@
+# Thesis/Dissertation Chapter Template
+# Flexible structure for PhD thesis chapters
+
+name: Thesis Chapter
+short: thesis
+description: Flexible structure for dissertation chapters
+
+structure:
+  - number: 1
+    name: Introduction
+    slug: introduction
+    word_ratio: 0.10
+    purpose: |
+      Chapter overview. How it fits in thesis narrative.
+      What reader will learn. Chapter roadmap.
+    subsections:
+      - Chapter Overview
+      - Motivation
+      - Chapter Organization
+    citation_density: medium
+
+  - number: 2
+    name: Background
+    slug: background
+    word_ratio: 0.15
+    purpose: |
+      Technical foundations for this chapter.
+      Can reference thesis background chapter for basics.
+    subsections:
+      - Relevant Concepts
+      - Problem Context
+    citation_density: high
+
+  - number: 3
+    name: Approach
+    slug: approach
+    word_ratio: 0.25
+    purpose: |
+      Your contribution. Design, methodology, implementation.
+      More space than conference paper - be thorough.
+    subsections:
+      - Design Overview
+      - Technical Details
+      - Implementation
+    citation_density: low
+
+  - number: 4
+    name: Evaluation
+    slug: evaluation
+    word_ratio: 0.25
+    purpose: |
+      Experimental validation. Can include negative results.
+      Thesis allows more exploration than conference paper.
+    subsections:
+      - Experimental Setup
+      - Results
+      - Analysis
+      - Discussion
+    citation_density: medium
+
+  - number: 5
+    name: Related Work
+    slug: related-work
+    word_ratio: 0.15
+    purpose: |
+      Comprehensive literature review for this chapter's topic.
+      More thorough than conference paper version.
+    subsections:
+      - Category 1
+      - Category 2
+      - Comparison and Positioning
+    citation_density: very_high
+
+  - number: 6
+    name: Summary
+    slug: summary
+    word_ratio: 0.08
+    purpose: |
+      Chapter contributions. Connection to thesis goals.
+      Transition to next chapter.
+    subsections:
+      - Chapter Contributions
+      - Limitations
+      - Transition to Next Chapter
+    citation_density: none
+
+optional_sections:
+  - name: Chapter Abstract
+    position: before_introduction
+  - name: Appendix
+    position: end
+
+citation_style: thesis
+page_limit_hint: "30-50 pages per chapter"
+
+notes: |
+  - Thesis chapters have more space - use it for clarity, not padding
+  - Can include more background than conference paper
+  - Negative results and failed approaches valuable
+  - Each chapter should standalone but connect to thesis narrative
+  - Committee expects comprehensive related work