content-to-code-brief

name	content-to-code-brief
description	Code-generation bridge skill. Use only when a vague business or content request must be translated into a concrete coding plan for this repo.
metadata	{"family":"orchestrators","owner":"engineering + content","last_reviewed":"2026-04-30T00:00:00.000Z","version":"1.0.0"}

Content To Code Brief

This is a code-generation skill. Use it only to prepare implementation work, not editorial research.

Use When

• the request is vague
• a non-technical person describes an outcome, not an implementation
• the agent must convert business/content intent into exact code changes

Convert The Request Into

Produce a brief with these fields before coding:

1. goal
2. route impact
3. feature owner folder
4. data source or new data location
5. page shell to reuse
6. metadata helper to use
7. schema components to use
8. verification commands

Mapping Rules

New page

• route: src/app/.../page.tsx
• composition: src/features/...

New content data

• place in src/features/<feature>/data/...

New tool

• check src/features/tools/shared/data/tool-registry/*
• prefer ToolPageShell

New editorial/career-hub page

Check:

• StandardPageLayout
• ContentPageShell
• IndustryPageShell
• SeasonalPageShell

Output Style

When converting the request, be explicit about:

• exact file paths likely to change
• which existing abstraction should be reused
• which old patterns must be avoided

Forbidden Outcome

Do not turn a vague request into generic boilerplate that ignores the repo structure.