new-team-member
Skill0 starsChanged 12 days agoMITView on GitHub
Add a new bilingual team member with proper frontmatter and both DE/EN files.
- Commits and pushes
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- brandSkill
- deploySkill
- new-postSkill
- onboardSkill
- passionfruit-a11ySkill
- passionfruit-contentSkill
- passionfruit-designSkill
- passionfruit-perfSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create a bilingual (DE + EN) team member entry with correct frontmatter, a real bio, and a commit.
- Distinctive: line 12
Ask these ONE AT A TIME using the AskUserQuestion tool:
- Very specific: line 31
Read all existing files in src/content/team/de/ and find the highest displayOrder value.
- Distinctive: line 48
If the user gave the role/specializations in one language, translate for the other.
- Very specific: line 86
If no LinkedIn was provided, omit the socials block entirely.
- Distinctive: line 92
Use a real photo only. Never generate a portrait of a real person.
- Very specific: line 94
Local session: ask for the file path and copy it to src/assets/team/<photo-name>.png.
- Very specific: line 95
Cloud session (
CLAUDE_CODE_REMOTE=true): ask the user to upload it to src/assets/team/ on GitHub (Add file → Upload files), then pull it. - Very specific: line 97
If they don't have one yet, leave photo out.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add a New Team Member
Create a bilingual (DE + EN) team member entry with correct frontmatter, a real bio, and a commit.
Gather info
Ask these ONE AT A TIME using the AskUserQuestion tool:
- "What's their name?"
- "What's their role/title?" (will be translated for both locales)
- "What are their specializations? (e.g., Frontend, TypeScript, UI/UX, Strategy)" (will be translated for both locales)
- "LinkedIn URL? (optional — press enter to skip)"
- "What should their short bio say? A few facts are enough, and I'll write it up."
- "Do you have a photo of them? (optional)"
This is a real person, so use only what the user told you. Don't invent their background, and never commit placeholder text, because it would go live.
Generate identifiers
translationKey: kebab-case from the name, ASCII-only (e.g., "anna-mueller" for "Anna Müller")- DE/EN slug: same as translationKey (team member slugs are identical across locales)
- Photo name: first name, lowercase, ASCII (e.g., "anna")
Determine displayOrder
Read all existing files in src/content/team/de/ and find the highest displayOrder value. Set the new member's displayOrder to that value + 1.
Translate role and specializations
Provide natural translations for both locales. Examples:
| DE | EN |
| Geschäftsführerin | CEO |
| Lead Entwickler | Lead Developer |
| Designerin | Designer |
| Frontend | Frontend |
| Strategie | Strategy |
| Digitale Transformation | Digital Transformation |
| UI/UX | UI/UX |
| Branding | Branding |
If the user gave the role/specializations in one language, translate for the other.
Create the files
src/content/team/de/<slug>.md
---
translationKey: "<translationKey>"
name: "<name>"
role: "<German role>"
displayOrder: <next number>
specializations: ["<DE specializations>"]
photo: "../../../assets/team/<photo-name>.png"
socials:
linkedin: "<url if provided>"
---
<German bio>src/content/team/en/<slug>.md
---
translationKey: "<translationKey>"
name: "<name>"
role: "<English role>"
displayOrder: <next number>
specializations: ["<EN specializations>"]
photo: "../../../assets/team/<photo-name>.png"
socials:
linkedin: "<url if provided>"
---
<English bio>If no LinkedIn was provided, omit the socials block entirely.
Only include photo if the file exists. A path to a missing file fails the whole build. TeamCard works without one.
Team photo
Use a real photo only. Never generate a portrait of a real person.
- Local session: ask for the file path and copy it to
src/assets/team/<photo-name>.png. - Cloud session (
CLAUDE_CODE_REMOTE=true): ask the user to upload it tosrc/assets/team/on GitHub (Add file → Upload files), then pull it.
If they don't have one yet, leave photo out. They can add it later.
Commit
IMPORTANT: Never commit a single-locale entry. Both DE and EN files must exist before committing.
Stage both files (and the photo if generated), then commit:
git add src/content/team/de/<slug>.md src/content/team/en/<slug>.md src/assets/team/<photo-name>.png # photo only if provided
git commit -m "feat: add team member — <name>"In a cloud session, also push: git push -u origin HEAD.
Tell the user the team member is saved in both languages. In a local session, start pnpm dev yourself and give them the link. In a cloud session, tell them it appears on the preview link once the pull request is open, or on the site once it's merged.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

