Skill: Content Writing
Generate authentic, compelling copy for portfolios.
Tone Calibration
Based on content.tone in profile.yaml:
| Tone |
Style |
Example |
| professional |
Formal, third-person |
"Jacob Kieser is a software architect specializing in..." |
| conversational |
Casual first-person |
"I build tools that make developers' lives easier." |
| technical |
Detailed, jargon-appropriate |
"Implemented a distributed cache layer using Redis Cluster..." |
| creative |
Storytelling, personality |
"It started with a broken deploy script at 2am..." |
Length Calibration
Based on content.length:
| Length |
Approach |
| concise |
Short sentences, bullet points, scannable |
| balanced |
Mix of short and long, narrative + lists |
| detailed |
Full paragraphs, comprehensive explanations |
Focus Calibration
Based on content.focus:
| Focus |
Emphasis |
| projects |
What they've built, outcomes, tech choices |
| experience |
Roles, companies, career progression |
| skills |
Technical depth, certifications, expertise |
| personality |
Who they are, how they think, what drives them |
Writing the Tagline
Don't Write
- "Passionate about [X]"
- "Building [vague thing] at scale"
- "Full-stack developer who loves clean code"
- "Turning coffee into code"
Do Write
- Specific value: "Built developer tools used by 2M engineers"
- Unique angle: "Former chef who now designs food tech APIs"
- Clear outcome: "I make AI systems that don't hallucinate"
- Honest and specific: "Infrastructure engineer who deletes more code than I write"
Writing the Bio
Structure
- Hook - Something specific and interesting
- Journey - How they got here (briefly)
- Current - What they're doing now
- Approach - How they think about problems
- Human - Something personal but professional
Anti-Patterns
- "I've been passionate about technology since..."
- Lists of technologies
- "Clean code" and "best practices"
- Corporate jargon (synergize, leverage, thought leader)
Good Examples
- "I spent five years making databases faster at Stripe. Now I help startups avoid the performance mistakes I used to fix."
- "Most of my career has been building tools that other engineers use. I'm good at finding the 80/20."
Writing Project Descriptions
Bad
"A web application built with React and Node.js that allows users to manage tasks."
Good
"Built after realizing Asana was overkill for solo devs. 5K+ developers use it daily to track side projects without the enterprise bloat."
Formula
- Why it exists (the problem)
- What it does (the solution)
- Impact (usage, results, or what you learned)
Critical: Don't Assume or Exaggerate
Never Infer
- Scale from company name ("Engineer at Uber" ≠ "billions of rides")
- Impact without verification
- Metrics you can't confirm
Always Ask
- User counts, revenue, scale
- Specific outcomes
- Role responsibilities
- Why they made certain choices
What You CAN Use
- Technologies from GitHub/package.json
- Public commit history
- Documented project existence
- Dates from public sources
If you're writing numbers without a source, STOP and ask.
Copy Creativity
Based on ai.copy_creativity in profile.yaml:
| Level |
Approach |
| 1-3 |
Safe, conventional, straightforward |
| 4-6 |
Some personality, occasional metaphor |
| 7-8 |
Distinctive voice, memorable phrasing |
| 9-10 |
Bold, potentially polarizing, very unique |
Section Headers
Avoid Generic
- "About Me"
- "My Projects"
- "Experience"
- "Skills"
Use Specific
- "What I Do"
- "Things I've Built"
- "Where I've Worked"
- "Background"
- Or archetype-specific: "~/about.txt", "PLAYER STATS", "Chapter One"
1---2name: content-23description: Generate authentic, compelling copy for portfolios. Covers tone calibration, taglines, bios, project descriptions, and avoiding assumptions.4---5
6# Skill: Content Writing
7
8Generate authentic, compelling copy for portfolios.
9
10---
11
12## Tone Calibration
13
14Based on `content.tone` in profile.yaml:
15
16| Tone | Style | Example |
17|------|-------|---------|
18| professional | Formal, third-person | "Jacob Kieser is a software architect specializing in..." |
19| conversational | Casual first-person | "I build tools that make developers' lives easier." |
20| technical | Detailed, jargon-appropriate | "Implemented a distributed cache layer using Redis Cluster..." |
21| creative | Storytelling, personality | "It started with a broken deploy script at 2am..." |
22
23---
24
25## Length Calibration
26
27Based on `content.length`:
28
29| Length | Approach |
30|--------|----------|
31| concise | Short sentences, bullet points, scannable |
32| balanced | Mix of short and long, narrative + lists |
33| detailed | Full paragraphs, comprehensive explanations |
34
35---
36
37## Focus Calibration
38
39Based on `content.focus`:
40
41| Focus | Emphasis |
42|-------|----------|
43| projects | What they've built, outcomes, tech choices |
44| experience | Roles, companies, career progression |
45| skills | Technical depth, certifications, expertise |
46| personality | Who they are, how they think, what drives them |
47
48---
49
50## Writing the Tagline
51
52### Don't Write
53- "Passionate about [X]"
54- "Building [vague thing] at scale"
55- "Full-stack developer who loves clean code"
56- "Turning coffee into code"
57
58### Do Write
59- Specific value: "Built developer tools used by 2M engineers"
60- Unique angle: "Former chef who now designs food tech APIs"
61- Clear outcome: "I make AI systems that don't hallucinate"
62- Honest and specific: "Infrastructure engineer who deletes more code than I write"
63
64---
65
66## Writing the Bio
67
68### Structure
691. **Hook** - Something specific and interesting
702. **Journey** - How they got here (briefly)
713. **Current** - What they're doing now
724. **Approach** - How they think about problems
735. **Human** - Something personal but professional
74
75### Anti-Patterns
76- "I've been passionate about technology since..."
77- Lists of technologies
78- "Clean code" and "best practices"
79- Corporate jargon (synergize, leverage, thought leader)
80
81### Good Examples
82- "I spent five years making databases faster at Stripe. Now I help startups avoid the performance mistakes I used to fix."
83- "Most of my career has been building tools that other engineers use. I'm good at finding the 80/20."
84
85---
86
87## Writing Project Descriptions
88
89### Bad
90"A web application built with React and Node.js that allows users to manage tasks."
91
92### Good
93"Built after realizing Asana was overkill for solo devs. 5K+ developers use it daily to track side projects without the enterprise bloat."
94
95### Formula
961. Why it exists (the problem)
972. What it does (the solution)
983. Impact (usage, results, or what you learned)
99
100---
101
102## Critical: Don't Assume or Exaggerate
103
104### Never Infer
105- Scale from company name ("Engineer at Uber" ≠ "billions of rides")
106- Impact without verification
107- Metrics you can't confirm
108
109### Always Ask
110- User counts, revenue, scale
111- Specific outcomes
112- Role responsibilities
113- Why they made certain choices
114
115### What You CAN Use
116- Technologies from GitHub/package.json
117- Public commit history
118- Documented project existence
119- Dates from public sources
120
121**If you're writing numbers without a source, STOP and ask.**
122
123---
124
125## Copy Creativity
126
127Based on `ai.copy_creativity` in profile.yaml:
128
129| Level | Approach |
130|-------|----------|
131| 1-3 | Safe, conventional, straightforward |
132| 4-6 | Some personality, occasional metaphor |
133| 7-8 | Distinctive voice, memorable phrasing |
134| 9-10 | Bold, potentially polarizing, very unique |
135
136---
137
138## Section Headers
139
140### Avoid Generic
141- "About Me"
142- "My Projects"
143- "Experience"
144- "Skills"
145
146### Use Specific
147- "What I Do"
148- "Things I've Built"
149- "Where I've Worked"
150- "Background"
151- Or archetype-specific: "~/about.txt", "PLAYER STATS", "Chapter One"
majiayu000