Code Pasting - Markdown¶
Markdown as the foundation for AI-readable requirements and documentation.
Why Markdown?¶
Markdown is the standard format for:
- Documentation - READMEs, guides, and specifications
- AI Communication - Clear structure that AI tools parse perfectly
- Version Control - Plain text integrates seamlessly with git
- Knowledge Sharing - Renders beautifully on GitHub and documentation sites
- Cross-Platform - Works everywhere without special tools
Markdown Fundamentals¶
Headings¶
Structure your content with headings:
1 2 3 4 | |
Rule: Use one H1 per document. AI tools use heading hierarchy to understand structure.
Lists¶
Organize information clearly:
1 2 3 4 5 6 7 8 9 10 | |
Code Blocks¶
Always use fenced code blocks for AI clarity:
1 2 3 4 5 6 7 8 | |
Important: Always specify the language for syntax highlighting and AI understanding.
Emphasis¶
1 2 3 4 | |
Links and Images¶
1 2 3 | |
Writing AI-Friendly Specifications¶
When writing requirements for AI tools, follow these patterns:
Clear Structure¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | |
Specify Edge Cases¶
1 2 3 4 5 6 7 8 9 10 11 | |
Show Examples¶
1 2 3 4 5 6 7 8 9 10 11 12 13 | |
Documentation Patterns for Code Pasting¶
API Documentation¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 | |
Function Specification¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 | |
Best Practices for AI Communication¶
✅ Do This¶
- Use clear, simple language
- Break complex ideas into sections
- Provide concrete examples
- Specify all constraints upfront
- Use code blocks for all code
- Include success criteria
❌ Don't Do This¶
- Vague descriptions without examples
- Mixing code with prose without block formatting
- Missing edge cases
- Assuming implicit knowledge
- Using complex sentences when simple ones work
- Forgetting to specify language in code blocks
Markdown Files in Git¶
Structure Your Documentation¶
1 2 3 4 5 6 7 8 9 | |
.claude.md for Code Pasting¶
Create a .claude.md file in your project root:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 | |
Markdown Resources¶
Writing Markdown in Microsoft Word¶
Writage Plugin¶
For users who prefer writing in Microsoft Word, the Writage plugin provides seamless markdown support:
What is Writage?
Writage is a plugin for Microsoft Word that allows you to: - Write and edit markdown directly in Word - Export Word documents to markdown - Import markdown files and edit in Word - Maintain markdown formatting and structure - Use Word's familiar interface for markdown writing
Installation
- Download Writage from writage.com
- Install the plugin (available for Windows)
- Restart Microsoft Word
- Writage appears in the Word ribbon
How to Use Writage
Opening Markdown Files¶
1 2 | |
Creating New Markdown Documents¶
- Create new Word document
- Go to Writage ribbon
- Click Markdown mode
- Write in familiar Word interface
- Markdown formatting is applied automatically
Writing with Markdown Awareness¶
- Use Heading Styles for
# ## ### - Use Lists for bullets and numbering
- Use Bold/Italic for
**bold**and*italic* - Use Code style for inline code
- Insert Tables naturally - Writage handles markdown conversion
Exporting to Markdown¶
1 2 3 | |
Benefits of Writage
- ✅ Use Word's familiar interface
- ✅ Real-time spell check
- ✅ Grammar checking
- ✅ Track changes for collaboration
- ✅ Export clean markdown for AI tools
- ✅ No need to learn markdown syntax
- ✅ Professional document formatting
Workflow with Writage
- Write Requirements in Word using Writage
- Use heading styles naturally
- Create lists and tables visually
-
Spell/grammar check built-in
-
Export to Markdown from Writage
- Automatic conversion to
.mdformat -
All formatting preserved
-
Commit to GitHub
- Pure markdown files in version control
-
Easy for AI tools to parse
-
Paste into Claude Code
- Perfectly formatted requirements
- Claude understands structure exactly
Tips for Best Results¶
- Use consistent Heading Styles (Heading 1, 2, 3)
- Use Bullet Lists instead of typing dashes
- Create Tables using Word's table tools
- Use Code style for snippets
- Avoid complex formatting (colors, custom fonts)
- Keep structure simple and hierarchical
Limitations¶
- ⚠️ Available for Windows only (not macOS)
- ⚠️ Some complex Word features don't convert to markdown
- ⚠️ Keep to standard markdown elements for best results
- ⚠️ Test export before committing to GitHub
Alternative: Direct Markdown Editing¶
If Writage isn't suitable, other options include:
- VS Code - Lightweight, free, excellent markdown support
- Typora - Markdown-first editor with live preview
- Obsidian - Knowledge management with markdown
- Notion - Cloud-based with markdown support
- GitHub Web Editor - Edit directly in browser
Rendering and Sharing¶
GitHub¶
Markdown files render automatically on GitHub:
1 2 3 | |
Documentation Sites¶
Use tools to create documentation sites:
- MkDocs - This documentation uses MkDocs
- Sphinx - Python documentation standard
- Hugo - Static site generator
The Markdown-First Workflow¶
- Write Requirements in markdown (Word with Writage or your preferred editor)
- Commit to GitHub for version history
- Paste into Claude Code for code generation
- Review Output and iterate
- Commit Code with markdown specifications
- Share Documentation in markdown format
This workflow makes development reproducible, collaborative, and AI-friendly, whether you're writing in Word or a dedicated markdown editor.