dc/datacontroller.io
6
1
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

fix: feed post git data
publish / Build-and-publish (push) Successful in 13m19s
Details

Browse Source
This commit is contained in:
4gl
2026-08-13 13:28:30 +01:00
parent 244829edf9
commit 729437308a
4 changed files with 67 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.agents/docs/linkedin.md
+1
View File
@@ -60,3 +60,4 @@ LinkedIn posts are plain text - there is no rich-text editor, so **no markdown**
- Feed posts (`content/feed/`) and LinkedIn posts are siblings, not copies: the site version may contain markdown links and omits hashtags; the LinkedIn version uses plain text, `#tag` hashtags, and "link in the comments".
- When converting site → LinkedIn: strip markdown, convert links to a comment-based CTA, append hashtags.
- When converting LinkedIn → site: strip `hashtag#` artefacts and hashtags, add proper markdown links, add front matter per the `add-feed-post` skill.
- **Keep them in sync:** whenever a feed post is modified, update its `Source LinkedIn post:` comment in the same change (same points, same claims, same ordering of lists) - and vice versa. A stale LinkedIn comment means the next social post is drafted from outdated copy.
.agents/skills/add-feed-post/SKILL.md
+2 -2
View File
@@ -53,9 +53,9 @@ Use regular dashes (`-`) in content, not em-dashes.
If the post is adapted from source copy the user provided (e.g. a LinkedIn post), paste the original text into an HTML comment (verbatim, except strip the literal `hashtag` prefix that LinkedIn sometimes adds before `#tags`, e.g. `hashtag#sas` -> `#sas`) (`<!-- ... -->`) at the bottom of the markdown file, labelled (e.g. `Source LinkedIn post:`). This preserves the original - including hashtags and checkmarks that get dropped/adapted in the site version - for future reuse.
When editing an existing feed post that has a `Source LinkedIn post:` comment, update the LinkedIn version too, so the overall message stays consistent (same points, same claims, same ordering of any lists). Wording does not need to be identical, and formatting will differ: the article uses Markdown, while LinkedIn is plain text with `✓`-style bullets, hashtags, and a comment-based CTA (see `.agents/docs/linkedin.md`).
**Important:** when editing an existing feed post that has a `Source LinkedIn post:` comment, ALWAYS update the LinkedIn version too, so the overall message stays consistent (same points, same claims, same ordering of any lists). Wording does not need to be identical, and formatting will differ: the article uses Markdown, while LinkedIn is plain text with `✓`-style bullets, hashtags, and a comment-based CTA (see `.agents/docs/linkedin.md`).
Likewise, if an image was generated for the post (e.g. the `previewImg`), record the full image-generation prompt in the same HTML comment block, labelled (e.g. `Image prompt:`), so it can be tweaked and regenerated later.
Every new feed post should include an image (a `previewImg` cover) - and its full image-generation prompt must be recorded in the same HTML comment block, labelled (e.g. `Image prompt:`), so it can be tweaked and regenerated later. If the user has not provided or asked for an image, propose one (theme, style and a draft prompt) and add the `Image prompt:` comment even if the image itself is not yet generated.
### 3. Add images (optional)