personal-brand-content

name

personal-brand-content

description

Plan, draft, package, and QA Arya Teja Rudraraju's personal brand content for LinkedIn, X, YouTube Shorts, blog posts, social carousels, and brand kit assets. Use when working on daily content creation, agentic engineering thought leadership, open-source project breakdowns, multi-agent orchestration posts, remote-machine/mobile-agent workflows, content calendars, social templates, visual briefs, or Codex/Claude/Gemini content-design coordination for aryateja.com.

Personal Brand Content

Use this skill to turn one source of learning into a daily multi-channel content package for Arya's Agentic Engineer brand.

Source Order

1. Read apps/web/lib/portfolio/brand.ts for identity, links, location, and voice rules.
2. Read PRODUCT.md for audience, positioning, and content product goals.
3. Read DESIGN.md for brand visuals and social asset direction.
4. Read docs/CONTENT.md for the daily content runbook.
5. Read only the specific reference file below that matches the task.

Reference Map

• references/daily-pipeline.md: use for the one-hour daily workflow, post packaging, and publish checklists.
• references/editorial-pillars.md: use to choose topics and turn raw learning into repeatable series.
• references/format-patterns.md: use to adapt one idea into LinkedIn, X, YouTube Shorts, blog, carousel, and deck formats.
• references/source-verification.md: use when current facts, repo capabilities, security claims, or external sources are involved.
• references/toolkit-map.md: use when deciding whether to use Impeccable, Open Design, Beautiful HTML Templates, Browser Harness, Career-Ops, Noustiny, Canva, or browser automation.

Default Workflow

1. Identify the source: repo, newsletter, bug, product lesson, workflow, screenshot, or personal story.
2. Verify factual claims against primary sources when claims may have changed.
3. Extract one clear lesson for builders.
4. Draft the canonical note first.
5. Adapt the note into channel-native outputs.
6. Add one visual brief or screenshot plan.
7. Run the voice check: no em-dashes, no AI PM framing, no aspiring language, no corporate filler.
8. Produce a compact package with copy, visual brief, source links, and next action.

Output Shape

For a daily content request, return:

• Core idea: one sentence.
• Why now: one sentence tied to source or current build context.
• LinkedIn: post draft.
• X: standalone post or short thread.
• YouTube Short: hook, 3 beats, visual, closing line.
• Visual: carousel, screenshot, diagram, or template brief.
• Sources: links or local files used.
• Questions: only the 1 to 3 decisions needed before publishing.

Voice Rules

• Sound like a builder who is learning and shipping in public.
• Prefer concrete claims, commands, screenshots, and workflows.
• Keep humility without undercutting authority.
• Avoid hype claims unless there is proof.
• Do not invent numbers, quotes, benchmarks, product status, or release facts.
• Do not use em-dashes in public copy.