agentleFS
passion4it-gmbhpassion4it-gmbh/passionfruit-site/.claude/skills/new-team-member/SKILL.md

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

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
  1. Distinctive:

    Create a bilingual (DE + EN) team member entry with correct frontmatter, a real bio, and a commit.

    line 8
  2. Distinctive:

    Ask these ONE AT A TIME using the AskUserQuestion tool:

    line 12
  3. Very specific:

    Read all existing files in src/content/team/de/ and find the highest displayOrder value.

    line 31
  4. Distinctive:

    If the user gave the role/specializations in one language, translate for the other.

    line 48
  5. Very specific:

    If no LinkedIn was provided, omit the socials block entirely.

    line 86
  6. Distinctive:

    Use a real photo only. Never generate a portrait of a real person.

    line 92
  7. Very specific:

    Local session: ask for the file path and copy it to src/assets/team/<photo-name>.png.

    line 94
  8. Very specific:

    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.

    line 95
  9. Very specific:

    If they don't have one yet, leave photo out.

    line 97

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. "What's their name?"
  2. "What's their role/title?" (will be translated for both locales)
  3. "What are their specializations? (e.g., Frontend, TypeScript, UI/UX, Strategy)" (will be translated for both locales)
  4. "LinkedIn URL? (optional — press enter to skip)"
  5. "What should their short bio say? A few facts are enough, and I'll write it up."
  6. "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:

DEEN
GeschäftsführerinCEO
Lead EntwicklerLead Developer
DesignerinDesigner
FrontendFrontend
StrategieStrategy
Digitale TransformationDigital Transformation
UI/UXUI/UX
BrandingBranding

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 to src/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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.