[Slice 7] translate-content skill

[wab]

Parent

#21

What to build

Ship the translate-content skill. Once landed, an Ocobo team member can take an existing French blog post (or story, or job, or team member) and produce its other-language version with one command.

Concretely:

• Create .claude/skills/translate-content/SKILL.md.
• Input: path to an existing content file.
• Skill detects content type and current language.
• For path-based types (blog, story, job): duplicate the file to the sibling <type>/<other-lang>/<slug>.md. Translate title, description, subtitle (story), quotes (story), and the markdown body. Preserve all other frontmatter fields verbatim (slugs, URLs, dates).
• For dict-based type (team): edit the existing file's frontmatter to fill the missing language in role and bio. Do not duplicate the file.
• For tool (monolingual): refuse with a clear message.
• Preview the diff before writing. Asks for confirmation.
• pnpm validate runs after write and must pass.

Acceptance criteria

• /translate-content blog/fr/some-post.md produces blog/en/some-post.md with translated title, description, body; other fields preserved.
• /translate-content team/some-member.md adds the missing language to role and bio in the same file.
• /translate-content tools/some-tool.md refuses with a clear "tools are monolingual" message.
• The translated file passes pnpm validate.
• A preview is shown before any write happens.

Blocked by

• [Slice 4] new-blog-post end-to-end (multimode) #25 (need at least one path-based type fully shipped to demo end-to-end)