markdown-syntax-fundamentals
Markdown Syntax Fundamentals
Core markdown syntax for creating well-structured documents.
Headings
# Heading 1
## Heading 2
### Heading 3
#### Heading 4
##### Heading 5
###### Heading 6
Heading Best Practices
- Use a single H1 (
#) per document as the title - Don't skip heading levels (H2 to H4)
- Keep headings concise and descriptive
- Use sentence case or title case consistently
Text Formatting
Emphasis
*italic* or _italic_
**bold** or __bold__
***bold italic*** or ___bold italic___
~~strikethrough~~
Inline Code
Use `backticks` for inline code like `const x = 1`
Lists
Unordered Lists
- Item one
- Item two
- Nested item
- Another nested item
- Item three
* Alternative marker
+ Also works
Ordered Lists
1. First item
2. Second item
1. Nested numbered
2. Another nested
3. Third item
Task Lists (GitHub Flavored)
- [x] Completed task
- [ ] Incomplete task
- [ ] Another task
Links
Basic Links
[Link text](https://example.com)
[Link with title](https://example.com "Title text")
Reference Links
[Link text][reference-id]
[reference-id]: https://example.com "Optional title"
Automatic Links
<https://example.com>
<email@example.com>
Internal Links (Anchors)
[Jump to section](#section-heading)
Anchor IDs are auto-generated from headings:
- Lowercase
- Spaces become hyphens
- Special characters removed
Images
Basic Images


Reference Images
![Alt text][image-id]
[image-id]: path/to/image.png "Optional title"
Linked Images
[](https://example.com)
Code Blocks
Fenced Code Blocks
```javascript
function hello() {
console.log("Hello, World!");
}
```
Common Language Identifiers
javascript/jstypescript/tspython/pybash/shell/shjson/yamlhtml/csssqlmarkdown/md
Indented Code Blocks
// Four spaces or one tab
function example() {
return true;
}
Blockquotes
Basic Blockquotes
> This is a blockquote.
> It can span multiple lines.
> Blockquotes can contain
>
> Multiple paragraphs.
Nested Blockquotes
> Outer quote
>> Nested quote
>>> Deeply nested
Blockquotes with Other Elements
> ## Heading in blockquote
>
> - List item
> - Another item
>
> ```code block```
Horizontal Rules
---
***
___
Use three or more hyphens, asterisks, or underscores.
Escaping Characters
\* Not italic \*
\# Not a heading
\[Not a link\]
\`Not code\`
Characters that can be escaped: \ ` * _ { } [ ] ( ) # + - . ! |
Line Breaks
Line one with two trailing spaces
Line two (hard break)
Line one
Line two (paragraph break)
Best Practices
- Consistent formatting: Pick a style and stick to it
- Blank lines: Add blank lines before and after:
- Headings
- Code blocks
- Lists
- Blockquotes
- Line length: Consider wrapping at 80-120 characters for readability
- Alt text: Always provide meaningful alt text for images
- Link text: Use descriptive link text, not "click here"
- Code highlighting: Always specify language for fenced code blocks
More from arielperez82/agents-and-skills
algorithmic-art
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
16problem-solving
Apply systematic problem-solving techniques for complexity spirals (simplification
15research
Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.
14brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
14docs-seeker
Search technical documentation using executable scripts to detect query
14mermaid-diagrams
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.
14