refactor(linkedin-studio): S29e terminology-scrub — rename thought-leadership-angles.md -> content-angles.md + all pointers
Final sub-pass of the S29 plugin-wide terminology scrub. The canonical reference file is renamed and every functional pointer updated atomically in one commit. The file's in-file title/headers were already FORM A-scrubbed in S29c (H1 reads "Content Angles"), so S29e is a pure rename + pointer update — no FORM A remained in the file. Rename: references/thought-leadership-angles.md -> references/content-angles.md (git mv). Pointers updated (17 files, 29 occurrences) — token "thought-leadership-angles" -> "content-angles": - references/ (2): ai-content-framework, glossary - agents/ (7): content-repurposer, strategy-advisor, network-builder, content-planner, trend-spotter, video-scripter, differentiation-checker - commands/ (6): pipeline, video, post, competitive, react, batch - skills/ (1): linkedin-content-creation/SKILL - docs/ (1, forward-looking): integration-test-guide Left URØRT per the standing S29 decision (history = honest record of a past state, not a runtime load): CHANGELOG.md, docs/hardening/log.md, docs/hardening/plan.md. STATE.md untouched here (rewritten at session end). Verify: no thought-leadership-angles* file remains; references/content-angles.md present; zero residual "thought-leadership-angles" in commands/agents/references/skills/integration-test-guide; structure gate scripts/test-runner.sh 81/0/0 exit 0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016qgzo6rxthw7KuxHjn5vyE
This commit is contained in:
parent
a534edf4fc
commit
9e5695286d
18 changed files with 29 additions and 29 deletions
|
|
@ -63,9 +63,9 @@ If they provide a URL, use WebFetch to extract the content first.
|
|||
|
||||
## Step 2: Select Content Angle
|
||||
|
||||
Read `references/thought-leadership-angles.md` for the 8 universal angles.
|
||||
Read `references/content-angles.md` for the 8 universal angles.
|
||||
|
||||
**Industry-specific angles:** If `${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/profile/user-profile.md` exists and has an `industry` field, check the "Industry Angle Variants" section in `thought-leadership-angles.md` for the matching industry table. Use the industry-specific starter questions and example hooks to generate more targeted angle suggestions.
|
||||
**Industry-specific angles:** If `${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/profile/user-profile.md` exists and has an `industry` field, check the "Industry Angle Variants" section in `content-angles.md` for the matching industry table. Use the industry-specific starter questions and example hooks to generate more targeted angle suggestions.
|
||||
|
||||
Select the strongest angle based on the content and user's expertise areas. Present ONE recommended angle with brief reasoning:
|
||||
|
||||
|
|
@ -200,7 +200,7 @@ Replace placeholders with actual post data. This replaces manual YAML editing.
|
|||
|
||||
## Reference Files
|
||||
|
||||
- `references/thought-leadership-angles.md` - 8 universal angles
|
||||
- `references/content-angles.md` - 8 universal angles
|
||||
- `references/engagement-frameworks.md` - Hooks, structure, CTAs
|
||||
- `references/linkedin-formats.md` - Format specifications
|
||||
- `references/algorithm-signals-reference.md` - Algorithm mechanics
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue