blast-studio 0.0.0-stage → 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (256) hide show
  1. package/LICENSE +202 -0
  2. package/README.md +138 -2
  3. package/bin/bstudio.mjs +13 -0
  4. package/dist/agent-env.js +177 -0
  5. package/dist/brief.js +53 -0
  6. package/dist/budget/ledger.js +153 -0
  7. package/dist/campaign-zip.js +93 -0
  8. package/dist/cli.js +118 -0
  9. package/dist/commands/accept.js +64 -0
  10. package/dist/commands/auth.js +77 -0
  11. package/dist/commands/brief.js +117 -0
  12. package/dist/commands/budget.js +22 -0
  13. package/dist/commands/dashboard.js +9 -0
  14. package/dist/commands/doctor.js +57 -0
  15. package/dist/commands/export.js +42 -0
  16. package/dist/commands/init.js +24 -0
  17. package/dist/commands/install-skills.js +52 -0
  18. package/dist/commands/library.js +12 -0
  19. package/dist/commands/make.js +71 -0
  20. package/dist/commands/mark.js +44 -0
  21. package/dist/commands/new.js +25 -0
  22. package/dist/commands/plan.js +57 -0
  23. package/dist/commands/render-preview.js +43 -0
  24. package/dist/commands/render.js +243 -0
  25. package/dist/commands/review.js +119 -0
  26. package/dist/commands/revise.js +73 -0
  27. package/dist/commands/sources.js +33 -0
  28. package/dist/commands/status.js +34 -0
  29. package/dist/config.js +141 -0
  30. package/dist/dashboard/server.js +171 -0
  31. package/dist/dashboard/static/app.css +1 -0
  32. package/dist/dashboard/static/app.js +52 -0
  33. package/dist/dashboard/static/index.html +8 -0
  34. package/dist/env.js +47 -0
  35. package/dist/export.js +110 -0
  36. package/dist/fetch-text.js +64 -0
  37. package/dist/io.js +1 -0
  38. package/dist/keychain.js +41 -0
  39. package/dist/library.js +49 -0
  40. package/dist/packs.js +91 -0
  41. package/dist/plan.js +75 -0
  42. package/dist/posts.js +40 -0
  43. package/dist/providers/images.js +116 -0
  44. package/dist/providers/voice.js +55 -0
  45. package/dist/render/bins.js +21 -0
  46. package/dist/render/ffmpeg.js +102 -0
  47. package/dist/render/metrics.js +109 -0
  48. package/dist/render/stills.js +175 -0
  49. package/dist/render/template.js +20 -0
  50. package/dist/render/video.js +175 -0
  51. package/dist/review/gates.js +201 -0
  52. package/dist/review/reviewer.js +79 -0
  53. package/dist/review/score.js +21 -0
  54. package/dist/review/slop.js +17 -0
  55. package/dist/review-hash.js +21 -0
  56. package/dist/types.js +29 -0
  57. package/dist/updater/check.js +140 -0
  58. package/dist/updater/propose.js +144 -0
  59. package/dist/workspace.js +142 -0
  60. package/package.json +45 -4
  61. package/platforms/bluesky/guide.md +94 -0
  62. package/platforms/bluesky/pack.yml +150 -0
  63. package/platforms/dailydev/guide.md +82 -0
  64. package/platforms/dailydev/pack.yml +152 -0
  65. package/platforms/devto/guide.md +93 -0
  66. package/platforms/devto/pack.yml +119 -0
  67. package/platforms/gist/guide.md +92 -0
  68. package/platforms/gist/pack.yml +119 -0
  69. package/platforms/github-discussion/guide.md +92 -0
  70. package/platforms/github-discussion/pack.yml +122 -0
  71. package/platforms/hashnode/guide.md +93 -0
  72. package/platforms/hashnode/pack.yml +124 -0
  73. package/platforms/hn/guide.md +48 -0
  74. package/platforms/hn/pack.yml +59 -0
  75. package/platforms/instagram/guide.md +95 -0
  76. package/platforms/instagram/pack.yml +136 -0
  77. package/platforms/lemmy/guide.md +88 -0
  78. package/platforms/lemmy/pack.yml +141 -0
  79. package/platforms/linkedin/guide.md +93 -0
  80. package/platforms/linkedin/pack.yml +145 -0
  81. package/platforms/mastodon/guide.md +92 -0
  82. package/platforms/mastodon/pack.yml +138 -0
  83. package/platforms/medium/guide.md +92 -0
  84. package/platforms/medium/pack.yml +119 -0
  85. package/platforms/newsletter/guide.md +94 -0
  86. package/platforms/newsletter/pack.yml +144 -0
  87. package/platforms/producthunt/guide.md +92 -0
  88. package/platforms/producthunt/pack.yml +166 -0
  89. package/platforms/reddit/guide.md +92 -0
  90. package/platforms/reddit/pack.yml +151 -0
  91. package/platforms/snapshots/.gitkeep +0 -0
  92. package/platforms/snapshots/bluesky-10.sha256 +1 -0
  93. package/platforms/snapshots/bluesky-10.txt +1 -0
  94. package/platforms/snapshots/bluesky-11.sha256 +1 -0
  95. package/platforms/snapshots/bluesky-11.txt +1 -0
  96. package/platforms/snapshots/bluesky-12.sha256 +1 -0
  97. package/platforms/snapshots/bluesky-12.txt +1 -0
  98. package/platforms/snapshots/bluesky-13.sha256 +1 -0
  99. package/platforms/snapshots/bluesky-13.txt +1 -0
  100. package/platforms/snapshots/bluesky-14.sha256 +1 -0
  101. package/platforms/snapshots/bluesky-14.txt +1 -0
  102. package/platforms/snapshots/cross-platform-63.sha256 +1 -0
  103. package/platforms/snapshots/cross-platform-63.txt +1 -0
  104. package/platforms/snapshots/cross-platform-64.sha256 +1 -0
  105. package/platforms/snapshots/cross-platform-64.txt +1 -0
  106. package/platforms/snapshots/dailydev-55.sha256 +1 -0
  107. package/platforms/snapshots/dailydev-55.txt +1 -0
  108. package/platforms/snapshots/dailydev-56.sha256 +1 -0
  109. package/platforms/snapshots/dailydev-56.txt +1 -0
  110. package/platforms/snapshots/dailydev-57.sha256 +1 -0
  111. package/platforms/snapshots/dailydev-57.txt +1 -0
  112. package/platforms/snapshots/devto-26.sha256 +1 -0
  113. package/platforms/snapshots/devto-26.txt +1 -0
  114. package/platforms/snapshots/devto-27.sha256 +1 -0
  115. package/platforms/snapshots/devto-27.txt +1 -0
  116. package/platforms/snapshots/devto-28.sha256 +1 -0
  117. package/platforms/snapshots/devto-28.txt +1 -0
  118. package/platforms/snapshots/devto-29.sha256 +1 -0
  119. package/platforms/snapshots/devto-29.txt +1 -0
  120. package/platforms/snapshots/gist-52.sha256 +1 -0
  121. package/platforms/snapshots/gist-52.txt +1 -0
  122. package/platforms/snapshots/gist-53.sha256 +1 -0
  123. package/platforms/snapshots/gist-53.txt +1 -0
  124. package/platforms/snapshots/gist-54.sha256 +1 -0
  125. package/platforms/snapshots/gist-54.txt +1 -0
  126. package/platforms/snapshots/github-discussion-policy.sha256 +1 -0
  127. package/platforms/snapshots/github-discussion-policy.txt +1 -0
  128. package/platforms/snapshots/hashnode-30.sha256 +1 -0
  129. package/platforms/snapshots/hashnode-30.txt +1 -0
  130. package/platforms/snapshots/hashnode-31.sha256 +1 -0
  131. package/platforms/snapshots/hashnode-31.txt +1 -0
  132. package/platforms/snapshots/hashnode-32.sha256 +1 -0
  133. package/platforms/snapshots/hashnode-32.txt +1 -0
  134. package/platforms/snapshots/hn-23.sha256 +1 -0
  135. package/platforms/snapshots/hn-23.txt +1 -0
  136. package/platforms/snapshots/hn-24.sha256 +1 -0
  137. package/platforms/snapshots/hn-24.txt +1 -0
  138. package/platforms/snapshots/hn-25.sha256 +1 -0
  139. package/platforms/snapshots/hn-25.txt +1 -0
  140. package/platforms/snapshots/hyperframes-releases.sha256 +1 -0
  141. package/platforms/snapshots/hyperframes-releases.txt +1 -0
  142. package/platforms/snapshots/instagram-43.sha256 +1 -0
  143. package/platforms/snapshots/instagram-43.txt +1 -0
  144. package/platforms/snapshots/instagram-47.sha256 +1 -0
  145. package/platforms/snapshots/instagram-47.txt +1 -0
  146. package/platforms/snapshots/lemmy-policy.sha256 +1 -0
  147. package/platforms/snapshots/lemmy-policy.txt +1 -0
  148. package/platforms/snapshots/linkedin-1.sha256 +1 -0
  149. package/platforms/snapshots/linkedin-1.txt +1 -0
  150. package/platforms/snapshots/linkedin-2.sha256 +1 -0
  151. package/platforms/snapshots/linkedin-2.txt +1 -0
  152. package/platforms/snapshots/linkedin-3.sha256 +1 -0
  153. package/platforms/snapshots/linkedin-3.txt +1 -0
  154. package/platforms/snapshots/linkedin-4.sha256 +1 -0
  155. package/platforms/snapshots/linkedin-4.txt +1 -0
  156. package/platforms/snapshots/mastodon-15.sha256 +1 -0
  157. package/platforms/snapshots/mastodon-15.txt +1 -0
  158. package/platforms/snapshots/mastodon-16.sha256 +1 -0
  159. package/platforms/snapshots/mastodon-16.txt +1 -0
  160. package/platforms/snapshots/mastodon-17.sha256 +1 -0
  161. package/platforms/snapshots/mastodon-17.txt +1 -0
  162. package/platforms/snapshots/medium-34.sha256 +1 -0
  163. package/platforms/snapshots/medium-34.txt +1 -0
  164. package/platforms/snapshots/medium-35.sha256 +1 -0
  165. package/platforms/snapshots/medium-35.txt +1 -0
  166. package/platforms/snapshots/medium-36.sha256 +1 -0
  167. package/platforms/snapshots/medium-36.txt +1 -0
  168. package/platforms/snapshots/newsletter-58.sha256 +1 -0
  169. package/platforms/snapshots/newsletter-58.txt +1 -0
  170. package/platforms/snapshots/newsletter-59.sha256 +1 -0
  171. package/platforms/snapshots/newsletter-59.txt +1 -0
  172. package/platforms/snapshots/newsletter-60.sha256 +1 -0
  173. package/platforms/snapshots/newsletter-60.txt +1 -0
  174. package/platforms/snapshots/newsletter-61.sha256 +1 -0
  175. package/platforms/snapshots/newsletter-61.txt +1 -0
  176. package/platforms/snapshots/newsletter-62.sha256 +1 -0
  177. package/platforms/snapshots/newsletter-62.txt +1 -0
  178. package/platforms/snapshots/openai-image-pricing.sha256 +1 -0
  179. package/platforms/snapshots/openai-image-pricing.txt +1 -0
  180. package/platforms/snapshots/playwright-releases.sha256 +1 -0
  181. package/platforms/snapshots/playwright-releases.txt +1 -0
  182. package/platforms/snapshots/producthunt-37.sha256 +1 -0
  183. package/platforms/snapshots/producthunt-37.txt +1 -0
  184. package/platforms/snapshots/producthunt-38.sha256 +1 -0
  185. package/platforms/snapshots/producthunt-38.txt +1 -0
  186. package/platforms/snapshots/producthunt-39.sha256 +1 -0
  187. package/platforms/snapshots/producthunt-39.txt +1 -0
  188. package/platforms/snapshots/reddit-20.sha256 +1 -0
  189. package/platforms/snapshots/reddit-20.txt +1 -0
  190. package/platforms/snapshots/reddit-21.sha256 +1 -0
  191. package/platforms/snapshots/reddit-21.txt +1 -0
  192. package/platforms/snapshots/reddit-22.sha256 +1 -0
  193. package/platforms/snapshots/reddit-22.txt +1 -0
  194. package/platforms/snapshots/substack-policy.sha256 +1 -0
  195. package/platforms/snapshots/substack-policy.txt +1 -0
  196. package/platforms/snapshots/threads-18.sha256 +1 -0
  197. package/platforms/snapshots/threads-18.txt +1 -0
  198. package/platforms/snapshots/threads-19.sha256 +1 -0
  199. package/platforms/snapshots/threads-19.txt +1 -0
  200. package/platforms/snapshots/tiktok-50.sha256 +1 -0
  201. package/platforms/snapshots/tiktok-50.txt +1 -0
  202. package/platforms/snapshots/tiktok-51.sha256 +1 -0
  203. package/platforms/snapshots/tiktok-51.txt +1 -0
  204. package/platforms/snapshots/x-5.sha256 +1 -0
  205. package/platforms/snapshots/x-5.txt +1 -0
  206. package/platforms/snapshots/x-6.sha256 +1 -0
  207. package/platforms/snapshots/x-6.txt +1 -0
  208. package/platforms/snapshots/x-7.sha256 +1 -0
  209. package/platforms/snapshots/x-7.txt +1 -0
  210. package/platforms/snapshots/x-8.sha256 +1 -0
  211. package/platforms/snapshots/x-8.txt +1 -0
  212. package/platforms/snapshots/x-9.sha256 +1 -0
  213. package/platforms/snapshots/x-9.txt +1 -0
  214. package/platforms/snapshots/youtube-shorts-40.sha256 +1 -0
  215. package/platforms/snapshots/youtube-shorts-40.txt +1 -0
  216. package/platforms/snapshots/youtube-shorts-41.sha256 +1 -0
  217. package/platforms/snapshots/youtube-shorts-41.txt +1 -0
  218. package/platforms/snapshots/youtube-shorts-42.sha256 +1 -0
  219. package/platforms/snapshots/youtube-shorts-42.txt +1 -0
  220. package/platforms/sources.yml +947 -0
  221. package/platforms/substack/guide.md +94 -0
  222. package/platforms/substack/pack.yml +116 -0
  223. package/platforms/threads/guide.md +93 -0
  224. package/platforms/threads/pack.yml +148 -0
  225. package/platforms/tiktok/guide.md +92 -0
  226. package/platforms/tiktok/pack.yml +129 -0
  227. package/platforms/x/guide.md +94 -0
  228. package/platforms/x/pack.yml +130 -0
  229. package/platforms/youtube-shorts/guide.md +92 -0
  230. package/platforms/youtube-shorts/pack.yml +138 -0
  231. package/providers/prices.yml +31 -0
  232. package/schemas/campaign.v2.json +26 -0
  233. package/schemas/manifest.v1.json +37 -0
  234. package/schemas/pack.schema.json +601 -0
  235. package/schemas/review.schema.json +31 -0
  236. package/skills/studio-reviewer/SKILL.md +13 -0
  237. package/skills/studio-updater/SKILL.md +8 -0
  238. package/skills/studio-video/SKILL.md +20 -0
  239. package/skills/studio-visual/SKILL.md +12 -0
  240. package/skills/studio-writer/SKILL.md +14 -0
  241. package/templates/README.md +7 -0
  242. package/templates/card.html +1 -0
  243. package/templates/carousel-closing.html +1 -0
  244. package/templates/carousel-content.html +1 -0
  245. package/templates/carousel-title.html +1 -0
  246. package/templates/code.html +1 -0
  247. package/templates/fonts/IBM-Plex-OFL.txt +93 -0
  248. package/templates/fonts/IBMPlexMono.woff2 +0 -0
  249. package/templates/fonts/IBMPlexSans.woff2 +0 -0
  250. package/templates/fonts/Space-Grotesk-OFL.txt +93 -0
  251. package/templates/fonts/SpaceGrotesk.woff2 +0 -0
  252. package/templates/poster.html +1 -0
  253. package/templates/quote.html +1 -0
  254. package/templates/thumbnail.html +1 -0
  255. package/test/fixtures/reviews/calibration.json +22 -0
  256. package/test/fixtures/reviews/grounding/cases.json +17 -0
@@ -0,0 +1,94 @@
1
+ # Bluesky
2
+
3
+ ## Who reads it
4
+
5
+ [JUDGEMENT] Write for developers and communities choosing their own feeds. Identify the actual reader and their situation, not a generic “everyone”.
6
+
7
+ ## How distribution works
8
+
9
+ Users select custom feeds, so there is no single Bluesky ranking; Discover is one evolving feed. [Custom feeds](https://bsky.social/about/blog/7-27-2023-custom-feeds), [product update](https://bsky.social/about/blog/01-26-2026-whats-next-at-bluesky). Posts support text, images, video and external cards; links in comments versus posts and hashtag boosts are **[UNVERIFIED]**. Sponsored content must be identified and artificial engagement is prohibited. [Community guidelines](https://bsky.social/about/support/community-guidelines).
10
+
11
+ [JUDGEMENT] Treat distribution as context, not a formula. No hook or format guarantees reach.
12
+
13
+ ## Formats that work here
14
+
15
+ [JUDGEMENT] Choose the smallest format that can carry the evidence:
16
+
17
+ - Text: make one complete point with its evidence link; the pack text limit is graphemes and the record also has a byte limit.
18
+
19
+ - Thread: make the first post standalone, then number or sequence only when it improves comprehension.
20
+
21
+ - Image/video: use up to the sourced image count or sourced video duration in the pack, with alternatives or captions.
22
+
23
+ Check `pack.yml` for sourced limits and explicit unknowns; verify the live route and account.
24
+
25
+ ## Hooks
26
+
27
+ [JUDGEMENT] The examples are hypothetical hook patterns, not claims; use them only when supported by actual evidence.
28
+
29
+ - **Problem first:** identify the recurring problem and who it affects.
30
+ Hypothetical example: “A stale CI cache kept our release pipeline failing after the lockfile changed.”
31
+
32
+ - **Unexpected constraint:** lead with the specific constraint uncovered during a reproducible build failure.
33
+ Hypothetical example: “Our migration had to run while both old and new application versions were live.”
34
+
35
+ - **Before and after:** lead with the observed state before and after a reproducible build failure, if supported.
36
+ Hypothetical example: “The test failed with the old schema; after the migration it passed against the new one.”
37
+
38
+ - **Decision tradeoff:** lead with the alternative considered during a reproducible build failure and its cost.
39
+ Hypothetical example: “We chose a reversible database migration over a shorter but irreversible script.”
40
+
41
+ - **Reproduction:** lead with the smallest reproducible input behind a reproducible build failure.
42
+ Hypothetical example: “This five-line test reproduces the timeout when the connection pool has one slot.”
43
+
44
+ - **Practical lesson:** lead with the action another developer can take after a reproducible build failure.
45
+ Hypothetical example: “Before changing a cache key, include the dependency lockfile in the key inputs.”
46
+
47
+ Banned patterns: clickbait that withholds the subject, fake urgency, and engagement bait asking for votes or empty replies.
48
+
49
+ ## Structure template
50
+
51
+ [JUDGEMENT] Fill in only details supported by the source material:
52
+
53
+ - Audience and situation: [who encounters the problem, where]
54
+ - Specific problem or observation: [what happened]
55
+ - Evidence: [primary link, reproduction or verified example]
56
+ - Action and result: [what changed and what was observed]
57
+ - Takeaway or open question: [useful implication, without hype]
58
+ - Required affiliation, rights and disclosure: [checks]
59
+
60
+ ## Visual and video recipes
61
+
62
+ [JUDGEMENT] Use visuals to make the actual lesson easier to understand, not as decorative proof.
63
+
64
+ - Image or diagram: label the subject and flow; keep mobile text legible and provide meaningful alt text.
65
+ - Carousel where supported: topic → context → one step per slide → observed result → concise takeaway.
66
+ - Video where supported: 0–3 s subject, 3–15 s demonstration, then the result and context; adapt timings to the material, not an alleged platform optimum.
67
+ - Captions: accurately transcribe speech, synchronize with audio and keep text clear of interface overlays.
68
+ - Inspect output, rights and the pack’s route-specific limits; do not infer unknown values.
69
+
70
+ ## Anti-patterns
71
+
72
+ - Do not hide commercial content or assume every custom feed ranks alike.
73
+ - Do not invent metrics, testimonials, first-person experience or a guaranteed reach outcome.
74
+ - Avoid generic superlatives, duplicated points and context-free screenshots.
75
+
76
+ ## AI and disclosure
77
+
78
+ Clearly identify commercial content; a blanket AI disclosure requirement is unverified.
79
+
80
+ ## Checklist
81
+
82
+ - [ ] The intended reader and supported takeaway are identifiable.
83
+ - [ ] Claims link to evidence; uncertainties and limitations remain visible.
84
+ - [ ] Actual route, account, community rules and pack limits were checked.
85
+ - [ ] Images have relevant alternatives and spoken media has accurate captions.
86
+ - [ ] Authorship, affiliation, rights and applicable disclosure were checked.
87
+
88
+ ## Sources
89
+
90
+ - [algorithm / custom feeds](https://bsky.social/about/blog/7-27-2023-custom-feeds)
91
+ - [specs / video and images; product update](https://bsky.social/about/blog/01-26-2026-whats-next-at-bluesky)
92
+ - [specs / post record](https://github.com/bluesky-social/atproto/blob/main/packages/api/lexicons/app/bsky/feed/post.json)
93
+ - [specs / video](https://bsky.network/docs/about-bluesky-content/video)
94
+ - [AI policy / community rules](https://bsky.social/about/support/community-guidelines)
@@ -0,0 +1,150 @@
1
+ {
2
+ "id": "bluesky",
3
+ "name": "Bluesky",
4
+ "marketBlaster": "bluesky",
5
+ "ai": "draft",
6
+ "aiSource": "bluesky-14",
7
+ "formats": [
8
+ "text",
9
+ "thread",
10
+ "image",
11
+ "video"
12
+ ],
13
+ "textLimit": {
14
+ "value": 300,
15
+ "source": "bluesky-12"
16
+ },
17
+ "titleLimit": "unknown",
18
+ "marketBlasterMedia": { "source": "mb-check", "allowedKinds": ["image", "video"], "exclusiveKinds": [["image", "video"]] },
19
+ "media": [
20
+ {
21
+ "kind": "image",
22
+ "maxBytes": { "value": 2000000, "source": "mb-check" },
23
+ "maxCount": {
24
+ "value": 4,
25
+ "source": "bluesky-11"
26
+ }
27
+ },
28
+ {
29
+ "kind": "video",
30
+ "maxCount": { "value": 1, "source": "mb-check" },
31
+ "maxBytes": { "value": 300000000, "source": "mb-check" },
32
+ "maxSeconds": {
33
+ "value": 180,
34
+ "source": "bluesky-11"
35
+ }
36
+ }
37
+ ],
38
+ "disclosure": {
39
+ "text": "unknown",
40
+ "media": "unknown",
41
+ "voice": "unknown"
42
+ },
43
+ "rubric": [
44
+ {
45
+ "id": "hook",
46
+ "question": "Can the first post stand alone with a clear proposition?",
47
+ "anchors": {
48
+ "0": "The opening has no identifiable subject or result.",
49
+ "1": "A subject appears, but the problem or outcome is vague or delayed.",
50
+ "2": "The opening identifies the subject and a concrete problem or outcome."
51
+ }
52
+ },
53
+ {
54
+ "id": "audience-fit",
55
+ "question": "Does the post identify the relevant community or feed without assuming a single algorithm?",
56
+ "anchors": {
57
+ "0": "No intended reader or relevant situation is identifiable.",
58
+ "1": "A reader group or situation is hinted at but not connected to the content.",
59
+ "2": "The intended reader and relevant situation are explicit."
60
+ }
61
+ },
62
+ {
63
+ "id": "simplicity",
64
+ "question": "Does a thread keep each reply intelligible and advance one point?",
65
+ "anchors": {
66
+ "0": "The reader cannot reconstruct the main point or sequence.",
67
+ "1": "The main point is present but key context or ordering is missing.",
68
+ "2": "The main point and necessary steps are clear and ordered."
69
+ }
70
+ },
71
+ {
72
+ "id": "anti-slop",
73
+ "question": "Are generic launch boasts and misleading engagement requests absent?",
74
+ "anchors": {
75
+ "0": "The candidate relies on hype, fabricated urgency or unsupported claims.",
76
+ "1": "Some concrete substance is present but generic or inflated language remains.",
77
+ "2": "Concrete language replaces hype and claims are supported."
78
+ }
79
+ },
80
+ {
81
+ "id": "platform-fit",
82
+ "question": "Does the record respect the actual grapheme and byte limits and identify promotion?",
83
+ "anchors": {
84
+ "0": "The candidate ignores the destination’s format or community rules.",
85
+ "1": "The format or community is identified but a relevant rule or constraint remains unchecked.",
86
+ "2": "The format and relevant destination rules are checked and followed."
87
+ }
88
+ },
89
+ {
90
+ "id": "visual-quality",
91
+ "question": "Are image alternatives meaningful and video captions accurate?",
92
+ "anchors": {
93
+ "0": "The visual is unreadable or lacks its relevant alternative or captions.",
94
+ "1": "The visual is partly readable or an alternative or caption is incomplete.",
95
+ "2": "Key content is readable and relevant alternatives or accurate captions are present."
96
+ },
97
+ "appliesTo": [
98
+ "image",
99
+ "carousel",
100
+ "poster",
101
+ "video",
102
+ "diagram",
103
+ "logo",
104
+ "terminal-demo"
105
+ ]
106
+ },
107
+ {
108
+ "id": "value",
109
+ "question": "Is an evidence link or reproducible detail available to the reader?",
110
+ "anchors": {
111
+ "0": "No supported takeaway or useful example is identifiable.",
112
+ "1": "A takeaway is present but its evidence or practical detail is incomplete.",
113
+ "2": "A specific takeaway is supported by a concrete example or source."
114
+ }
115
+ },
116
+ {
117
+ "id": "promotion-disclosed",
118
+ "question": "Is commercial content clearly identified when applicable?",
119
+ "anchors": {
120
+ "0": "Commercial content is presented without identifying the commercial relationship.",
121
+ "1": "The relationship is hinted at but not clear to readers.",
122
+ "2": "The commercial relationship is clearly identified, or the post is not commercial."
123
+ }
124
+ },
125
+ {
126
+ "id": "record-limits",
127
+ "question": "Does the post fit both the grapheme and byte limits of its actual record?",
128
+ "anchors": {
129
+ "0": "The post exceeds a current record limit.",
130
+ "1": "Only one of the grapheme and byte limits was checked.",
131
+ "2": "Both grapheme and byte limits were checked against the actual record."
132
+ }
133
+ }
134
+ ],
135
+ "sources": [
136
+ "mb-check",
137
+ "bluesky-10",
138
+ "bluesky-11",
139
+ "bluesky-12",
140
+ "bluesky-13",
141
+ "bluesky-14",
142
+ "cross-platform-63",
143
+ "cross-platform-64"
144
+ ],
145
+ "notes": [
146
+ "[JUDGEMENT] Rubric scores are editorial aids, not predictions of reach.",
147
+ "Check actual account, route, community and current requirements before publication.",
148
+ "Text limit is graphemes; the record also has a 3,000-byte limit."
149
+ ]
150
+ }
@@ -0,0 +1,82 @@
1
+ # daily.dev
2
+
3
+ ## Who reads it
4
+
5
+ [JUDGEMENT] Write for developers seeking educational content. Identify the actual reader and their situation, not a generic “everyone”.
6
+
7
+ ## How distribution works
8
+
9
+ Wider feed reach depends on reader response; educational, non-misleading developer content is favored in published guidance. Link previews use page title, description and image. [Feed guidance](https://docs.daily.dev/what-the-feed-recommends/). [Guidelines](https://docs.daily.dev/content-guidelines/) reject generated content, predominantly promotional material, paid placements outside official programs and affiliate links; personal and company blogs cannot become indexed sources, though direct posts and Squads are available. AI editing is described separately as permissible when substance and voice remain the author's; generated article submission is not. [Featuring](https://docs.daily.dev/how-to-get-featured/).
10
+
11
+ [JUDGEMENT] Treat distribution as context, not a formula. No hook or format guarantees reach.
12
+
13
+ ## Formats that work here
14
+
15
+ [JUDGEMENT] Choose the smallest format that can carry the evidence:
16
+
17
+ - Outline a developer lesson as problem, genuine experience, evidence and takeaway; the human authors the substance.
18
+
19
+ - Check the final page title and preview image; this is not permission to submit generated prose.
20
+
21
+ - Direct-post and Squad rules vary; text and image limits are unknown in the pack.
22
+
23
+ Check `pack.yml` for sourced limits and explicit unknowns; verify the live route and account.
24
+
25
+ ## Hooks
26
+
27
+ [JUDGEMENT] These are human-author prompts with hypothetical example evidence, not copy-ready submission text.
28
+
29
+ - **Problem first:** identify the recurring problem and who it affects.
30
+ Example evidence: a CI log showing a stale cache after a lockfile change.
31
+
32
+ - **Unexpected constraint:** lead with the specific constraint uncovered during a debugging lesson.
33
+ Example evidence: a migration plan requiring old and new versions to coexist.
34
+
35
+ - **Before and after:** lead with the observed state before and after a debugging lesson, if supported.
36
+ Example evidence: a test result before and after a schema migration.
37
+
38
+ - **Decision tradeoff:** lead with the alternative considered during a debugging lesson and its cost.
39
+ Example evidence: a decision record comparing reversible and irreversible migrations.
40
+
41
+ - **Reproduction:** lead with the smallest reproducible input behind a debugging lesson.
42
+ Example evidence: a five-line test reproducing a pool timeout.
43
+
44
+ - **Practical lesson:** lead with the action another developer can take after a debugging lesson.
45
+ Example evidence: documentation showing the lockfile as a cache-key input.
46
+
47
+ Banned patterns: clickbait that withholds the subject, fake urgency, and engagement bait asking for votes or empty replies.
48
+
49
+ ## Structure template
50
+
51
+ [JUDGEMENT] Talking-point skeleton for the human author; do not copy it as the final post:
52
+
53
+ - Audience and situation: [who encounters the problem, where]
54
+ - Specific problem or observation: [what happened]
55
+ - Evidence: [primary link, reproduction or verified example]
56
+ - Action and result: [what changed and what was observed]
57
+ - Takeaway or open question: [useful implication, without hype]
58
+ - Required affiliation, rights and disclosure: [checks]
59
+
60
+ ## Anti-patterns
61
+
62
+ - Do not submit generated articles, affiliate links or predominantly promotional content.
63
+ - Do not invent metrics, testimonials, first-person experience or a guaranteed reach outcome.
64
+ - Avoid generic superlatives, duplicated points and context-free screenshots.
65
+
66
+ ## AI and disclosure
67
+
68
+ Outline only; the human authors substance and voice. Generated article submissions are prohibited; separate guidance permits AI editing.
69
+
70
+ ## Checklist
71
+
72
+ - [ ] The intended reader and supported takeaway are identifiable.
73
+ - [ ] Claims link to evidence; uncertainties and limitations remain visible.
74
+ - [ ] Actual route, account, community rules and pack limits were checked.
75
+ - [ ] Images have relevant alternatives and spoken media has accurate captions.
76
+ - [ ] Authorship, affiliation, rights and applicable disclosure were checked.
77
+
78
+ ## Sources
79
+
80
+ - [algorithm / feed guidance and AI editing](https://docs.daily.dev/what-the-feed-recommends/)
81
+ - [AI policy / source and promotion rules](https://docs.daily.dev/content-guidelines/)
82
+ - [specs / submissions](https://docs.daily.dev/how-to-get-featured/)
@@ -0,0 +1,152 @@
1
+ {
2
+ "id": "dailydev",
3
+ "name": "daily.dev",
4
+ "marketBlaster": null,
5
+ "ai": "outline",
6
+ "aiSource": "dailydev-56",
7
+ "formats": [
8
+ "text",
9
+ "article"
10
+ ],
11
+ "textLimit": "unknown",
12
+ "titleLimit": "unknown",
13
+ "media": [],
14
+ "disclosure": {
15
+ "text": "unknown",
16
+ "media": "unknown",
17
+ "voice": "unknown"
18
+ },
19
+ "rubric": [
20
+ {
21
+ "id": "hook",
22
+ "question": "Does the human-authored opening identify a useful developer lesson?",
23
+ "anchors": {
24
+ "0": "The opening has no identifiable subject or result.",
25
+ "1": "A subject appears, but the problem or outcome is vague or delayed.",
26
+ "2": "The opening identifies the subject and a concrete problem or outcome."
27
+ }
28
+ },
29
+ {
30
+ "id": "audience-fit",
31
+ "question": "Does the author identify the developer problem and intended reader?",
32
+ "anchors": {
33
+ "0": "No intended reader or relevant situation is identifiable.",
34
+ "1": "A reader group or situation is hinted at but not connected to the content.",
35
+ "2": "The intended reader and relevant situation are explicit."
36
+ }
37
+ },
38
+ {
39
+ "id": "simplicity",
40
+ "question": "Is the explanation organized around an authentic example rather than a pitch?",
41
+ "anchors": {
42
+ "0": "The reader cannot reconstruct the main point or sequence.",
43
+ "1": "The main point is present but key context or ordering is missing.",
44
+ "2": "The main point and necessary steps are clear and ordered."
45
+ }
46
+ },
47
+ {
48
+ "id": "anti-slop",
49
+ "question": "Does the human-written candidate avoid generic hype and generated article prose?",
50
+ "anchors": {
51
+ "0": "The candidate relies on hype, fabricated urgency or unsupported claims.",
52
+ "1": "Some concrete substance is present but generic or inflated language remains.",
53
+ "2": "Concrete language replaces hype and claims are supported."
54
+ }
55
+ },
56
+ {
57
+ "id": "platform-fit",
58
+ "question": "Does the candidate satisfy daily.dev rules on promotion and generated content?",
59
+ "anchors": {
60
+ "0": "The candidate ignores the destination’s format or community rules.",
61
+ "1": "The format or community is identified but a relevant rule or constraint remains unchecked.",
62
+ "2": "The format and relevant destination rules are checked and followed."
63
+ }
64
+ },
65
+ {
66
+ "id": "visual-quality",
67
+ "question": "Are the preview image and any diagrams relevant, readable and described?",
68
+ "anchors": {
69
+ "0": "The visual is unreadable or lacks its relevant alternative or captions.",
70
+ "1": "The visual is partly readable or an alternative or caption is incomplete.",
71
+ "2": "Key content is readable and relevant alternatives or accurate captions are present."
72
+ },
73
+ "appliesTo": [
74
+ "image",
75
+ "carousel",
76
+ "poster",
77
+ "video",
78
+ "diagram",
79
+ "logo",
80
+ "terminal-demo"
81
+ ]
82
+ },
83
+ {
84
+ "id": "value",
85
+ "question": "Can the lesson be used independently of buying a product?",
86
+ "anchors": {
87
+ "0": "No supported takeaway or useful example is identifiable.",
88
+ "1": "A takeaway is present but its evidence or practical detail is incomplete.",
89
+ "2": "A specific takeaway is supported by a concrete example or source."
90
+ }
91
+ },
92
+ {
93
+ "id": "human-authored-substance",
94
+ "question": "Is the article’s substance and voice human-authored, not generated from the outline?",
95
+ "anchors": {
96
+ "0": "The submitted article’s substance is generated rather than human-authored.",
97
+ "1": "Authorship is asserted but the substance and source of the draft are unclear.",
98
+ "2": "The human authored the substance and voice; AI assistance stayed within policy."
99
+ }
100
+ },
101
+ {
102
+ "id": "preview-metadata",
103
+ "question": "Were the article title and preview image checked against the source page?",
104
+ "anchors": {
105
+ "0": "The title or preview image is missing or misleading.",
106
+ "1": "One of title or preview image remains unchecked.",
107
+ "2": "The title and preview image match the actual source page."
108
+ }
109
+ }
110
+ ],
111
+ "outlineRubric": [
112
+ {
113
+ "id": "coverage",
114
+ "question": "Do the talking points cover the problem, relevant context and useful takeaway for developers seeking educational content?",
115
+ "anchors": {
116
+ "0": "The problem or takeaway is absent.",
117
+ "1": "The problem and takeaway are present but important context is missing.",
118
+ "2": "The problem, relevant context and actionable takeaway are covered as talking points."
119
+ }
120
+ },
121
+ {
122
+ "id": "evidence",
123
+ "question": "Do the talking points identify evidence for the a debugging lesson example without inventing experience?",
124
+ "anchors": {
125
+ "0": "The outline asserts unsupported facts or invented experience.",
126
+ "1": "Some evidence is identified but a material assertion lacks a source.",
127
+ "2": "Material assertions point to evidence and uncertainty is noted."
128
+ }
129
+ },
130
+ {
131
+ "id": "community-rules-checked",
132
+ "question": "Have the rules and authorship policy for the intended dailydev destination been checked before the human writes?",
133
+ "anchors": {
134
+ "0": "The target or its rules are not identified.",
135
+ "1": "The target is named but current rules or authorship restrictions are unchecked.",
136
+ "2": "The named destination’s current rules and authorship restrictions are recorded."
137
+ }
138
+ }
139
+ ],
140
+ "sources": [
141
+ "dailydev-55",
142
+ "dailydev-56",
143
+ "dailydev-57",
144
+ "cross-platform-63",
145
+ "cross-platform-64"
146
+ ],
147
+ "notes": [
148
+ "[JUDGEMENT] Rubric scores are editorial aids, not predictions of reach.",
149
+ "Check actual account, route, community and current requirements before publication.",
150
+ "Only human-authored substance and voice: an outline does not authorize submission of generated prose."
151
+ ]
152
+ }
@@ -0,0 +1,93 @@
1
+ # DEV
2
+
3
+ ## Who reads it
4
+
5
+ [JUDGEMENT] Write for developers looking for practical tutorials. Identify the actual reader and their situation, not a generic “everyone”.
6
+
7
+ ## How distribution works
8
+
9
+ Markdown articles, tags, cover images, scheduling and cross-posts with canonical URL are supported; high-quality cross-posts may be featured. [Writing help](https://dev.to/help/writing-editing-scheduling). DEV's [AI disclosure tiers](https://dev.to/devteam/introducing-ai-disclosure-on-dev-tools-for-nuance-clarity-and-better-feeds-34mk) include Hand Written, AI-Assisted and Fully Autonomous; authors remain responsible for accuracy. Exact feed weights **[UNVERIFIED]**. Ensure substantial developer value and check [community rules](https://dev.to/code-of-conduct).
10
+
11
+ [JUDGEMENT] Treat distribution as context, not a formula. No hook or format guarantees reach.
12
+
13
+ ## Formats that work here
14
+
15
+ [JUDGEMENT] Choose the smallest format that can carry the evidence:
16
+
17
+ - Article: lead with the outcome, list prerequisites, show runnable steps and expected output, then explain tradeoffs.
18
+
19
+ - Cross-post: set the original canonical URL and use relevant tags; article length and media limits are unknown in the pack.
20
+
21
+ - Cover image: illustrate the actual tutorial and provide an alternative rather than a decorative wall of text.
22
+
23
+ Check `pack.yml` for sourced limits and explicit unknowns; verify the live route and account.
24
+
25
+ ## Hooks
26
+
27
+ [JUDGEMENT] The examples are hypothetical hook patterns, not claims; use them only when supported by actual evidence.
28
+
29
+ - **Problem first:** identify the recurring problem and who it affects.
30
+ Hypothetical example: “A stale CI cache kept our release pipeline failing after the lockfile changed.”
31
+
32
+ - **Unexpected constraint:** lead with the specific constraint uncovered during a failing CI pipeline.
33
+ Hypothetical example: “Our migration had to run while both old and new application versions were live.”
34
+
35
+ - **Before and after:** lead with the observed state before and after a failing CI pipeline, if supported.
36
+ Hypothetical example: “The test failed with the old schema; after the migration it passed against the new one.”
37
+
38
+ - **Decision tradeoff:** lead with the alternative considered during a failing CI pipeline and its cost.
39
+ Hypothetical example: “We chose a reversible database migration over a shorter but irreversible script.”
40
+
41
+ - **Reproduction:** lead with the smallest reproducible input behind a failing CI pipeline.
42
+ Hypothetical example: “This five-line test reproduces the timeout when the connection pool has one slot.”
43
+
44
+ - **Practical lesson:** lead with the action another developer can take after a failing CI pipeline.
45
+ Hypothetical example: “Before changing a cache key, include the dependency lockfile in the key inputs.”
46
+
47
+ Banned patterns: clickbait that withholds the subject, fake urgency, and engagement bait asking for votes or empty replies.
48
+
49
+ ## Structure template
50
+
51
+ [JUDGEMENT] Fill in only details supported by the source material:
52
+
53
+ - Audience and situation: [who encounters the problem, where]
54
+ - Specific problem or observation: [what happened]
55
+ - Evidence: [primary link, reproduction or verified example]
56
+ - Action and result: [what changed and what was observed]
57
+ - Takeaway or open question: [useful implication, without hype]
58
+ - Required affiliation, rights and disclosure: [checks]
59
+
60
+ ## Visual and video recipes
61
+
62
+ [JUDGEMENT] Use visuals to make the actual lesson easier to understand, not as decorative proof.
63
+
64
+ - Image or diagram: label the subject and flow; keep mobile text legible and provide meaningful alt text.
65
+ - Carousel where supported: topic → context → one step per slide → observed result → concise takeaway.
66
+ - Video where supported: 0–3 s subject, 3–15 s demonstration, then the result and context; adapt timings to the material, not an alleged platform optimum.
67
+ - Captions: accurately transcribe speech, synchronize with audio and keep text clear of interface overlays.
68
+ - Inspect output, rights and the pack’s route-specific limits; do not infer unknown values.
69
+
70
+ ## Anti-patterns
71
+
72
+ - Do not omit the canonical URL on a cross-post or misstate the AI disclosure tier.
73
+ - Do not invent metrics, testimonials, first-person experience or a guaranteed reach outcome.
74
+ - Avoid generic superlatives, duplicated points and context-free screenshots.
75
+
76
+ ## AI and disclosure
77
+
78
+ Use the applicable Hand Written, AI-Assisted or Fully Autonomous tier and verify accuracy.
79
+
80
+ ## Checklist
81
+
82
+ - [ ] The intended reader and supported takeaway are identifiable.
83
+ - [ ] Claims link to evidence; uncertainties and limitations remain visible.
84
+ - [ ] Actual route, account, community rules and pack limits were checked.
85
+ - [ ] Images have relevant alternatives and spoken media has accurate captions.
86
+ - [ ] Authorship, affiliation, rights and applicable disclosure were checked.
87
+
88
+ ## Sources
89
+
90
+ - [specs / editor and canonical](https://dev.to/help/writing-editing-scheduling)
91
+ - [specs / article API](https://developers.forem.com/api/v1)
92
+ - [AI policy / disclosure tiers](https://dev.to/devteam/introducing-ai-disclosure-on-dev-tools-for-nuance-clarity-and-better-feeds-34mk)
93
+ - [community rules](https://dev.to/code-of-conduct)