blast-studio 0.0.0-stage → 0.1.0
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.
- package/LICENSE +202 -0
- package/README.md +138 -2
- package/bin/bstudio.mjs +13 -0
- package/dist/agent-env.js +152 -0
- package/dist/brief.js +53 -0
- package/dist/budget/ledger.js +153 -0
- package/dist/campaign-zip.js +93 -0
- package/dist/cli.js +118 -0
- package/dist/commands/accept.js +64 -0
- package/dist/commands/auth.js +77 -0
- package/dist/commands/brief.js +117 -0
- package/dist/commands/budget.js +22 -0
- package/dist/commands/dashboard.js +9 -0
- package/dist/commands/doctor.js +57 -0
- package/dist/commands/export.js +42 -0
- package/dist/commands/init.js +24 -0
- package/dist/commands/install-skills.js +52 -0
- package/dist/commands/library.js +12 -0
- package/dist/commands/make.js +71 -0
- package/dist/commands/mark.js +44 -0
- package/dist/commands/new.js +25 -0
- package/dist/commands/plan.js +57 -0
- package/dist/commands/render-preview.js +43 -0
- package/dist/commands/render.js +243 -0
- package/dist/commands/review.js +119 -0
- package/dist/commands/revise.js +73 -0
- package/dist/commands/sources.js +33 -0
- package/dist/commands/status.js +34 -0
- package/dist/config.js +141 -0
- package/dist/dashboard/server.js +171 -0
- package/dist/dashboard/static/app.css +1 -0
- package/dist/dashboard/static/app.js +52 -0
- package/dist/dashboard/static/index.html +8 -0
- package/dist/env.js +47 -0
- package/dist/export.js +110 -0
- package/dist/fetch-text.js +64 -0
- package/dist/io.js +1 -0
- package/dist/keychain.js +41 -0
- package/dist/library.js +49 -0
- package/dist/packs.js +91 -0
- package/dist/plan.js +75 -0
- package/dist/posts.js +40 -0
- package/dist/providers/images.js +116 -0
- package/dist/providers/voice.js +55 -0
- package/dist/render/ffmpeg.js +96 -0
- package/dist/render/metrics.js +109 -0
- package/dist/render/stills.js +172 -0
- package/dist/render/template.js +20 -0
- package/dist/render/video.js +173 -0
- package/dist/review/gates.js +201 -0
- package/dist/review/reviewer.js +79 -0
- package/dist/review/score.js +21 -0
- package/dist/review/slop.js +17 -0
- package/dist/review-hash.js +21 -0
- package/dist/types.js +29 -0
- package/dist/updater/check.js +140 -0
- package/dist/updater/propose.js +144 -0
- package/dist/workspace.js +142 -0
- package/package.json +45 -4
- package/platforms/bluesky/guide.md +94 -0
- package/platforms/bluesky/pack.yml +150 -0
- package/platforms/dailydev/guide.md +82 -0
- package/platforms/dailydev/pack.yml +152 -0
- package/platforms/devto/guide.md +93 -0
- package/platforms/devto/pack.yml +119 -0
- package/platforms/gist/guide.md +92 -0
- package/platforms/gist/pack.yml +119 -0
- package/platforms/github-discussion/guide.md +92 -0
- package/platforms/github-discussion/pack.yml +122 -0
- package/platforms/hashnode/guide.md +93 -0
- package/platforms/hashnode/pack.yml +124 -0
- package/platforms/hn/guide.md +48 -0
- package/platforms/hn/pack.yml +59 -0
- package/platforms/instagram/guide.md +95 -0
- package/platforms/instagram/pack.yml +136 -0
- package/platforms/lemmy/guide.md +88 -0
- package/platforms/lemmy/pack.yml +141 -0
- package/platforms/linkedin/guide.md +93 -0
- package/platforms/linkedin/pack.yml +145 -0
- package/platforms/mastodon/guide.md +92 -0
- package/platforms/mastodon/pack.yml +138 -0
- package/platforms/medium/guide.md +92 -0
- package/platforms/medium/pack.yml +119 -0
- package/platforms/newsletter/guide.md +94 -0
- package/platforms/newsletter/pack.yml +144 -0
- package/platforms/producthunt/guide.md +92 -0
- package/platforms/producthunt/pack.yml +166 -0
- package/platforms/reddit/guide.md +92 -0
- package/platforms/reddit/pack.yml +151 -0
- package/platforms/snapshots/.gitkeep +0 -0
- package/platforms/snapshots/bluesky-10.sha256 +1 -0
- package/platforms/snapshots/bluesky-10.txt +1 -0
- package/platforms/snapshots/bluesky-11.sha256 +1 -0
- package/platforms/snapshots/bluesky-11.txt +1 -0
- package/platforms/snapshots/bluesky-12.sha256 +1 -0
- package/platforms/snapshots/bluesky-12.txt +1 -0
- package/platforms/snapshots/bluesky-13.sha256 +1 -0
- package/platforms/snapshots/bluesky-13.txt +1 -0
- package/platforms/snapshots/bluesky-14.sha256 +1 -0
- package/platforms/snapshots/bluesky-14.txt +1 -0
- package/platforms/snapshots/cross-platform-63.sha256 +1 -0
- package/platforms/snapshots/cross-platform-63.txt +1 -0
- package/platforms/snapshots/cross-platform-64.sha256 +1 -0
- package/platforms/snapshots/cross-platform-64.txt +1 -0
- package/platforms/snapshots/dailydev-55.sha256 +1 -0
- package/platforms/snapshots/dailydev-55.txt +1 -0
- package/platforms/snapshots/dailydev-56.sha256 +1 -0
- package/platforms/snapshots/dailydev-56.txt +1 -0
- package/platforms/snapshots/dailydev-57.sha256 +1 -0
- package/platforms/snapshots/dailydev-57.txt +1 -0
- package/platforms/snapshots/devto-26.sha256 +1 -0
- package/platforms/snapshots/devto-26.txt +1 -0
- package/platforms/snapshots/devto-27.sha256 +1 -0
- package/platforms/snapshots/devto-27.txt +1 -0
- package/platforms/snapshots/devto-28.sha256 +1 -0
- package/platforms/snapshots/devto-28.txt +1 -0
- package/platforms/snapshots/devto-29.sha256 +1 -0
- package/platforms/snapshots/devto-29.txt +1 -0
- package/platforms/snapshots/gist-52.sha256 +1 -0
- package/platforms/snapshots/gist-52.txt +1 -0
- package/platforms/snapshots/gist-53.sha256 +1 -0
- package/platforms/snapshots/gist-53.txt +1 -0
- package/platforms/snapshots/gist-54.sha256 +1 -0
- package/platforms/snapshots/gist-54.txt +1 -0
- package/platforms/snapshots/github-discussion-policy.sha256 +1 -0
- package/platforms/snapshots/github-discussion-policy.txt +1 -0
- package/platforms/snapshots/hashnode-30.sha256 +1 -0
- package/platforms/snapshots/hashnode-30.txt +1 -0
- package/platforms/snapshots/hashnode-31.sha256 +1 -0
- package/platforms/snapshots/hashnode-31.txt +1 -0
- package/platforms/snapshots/hashnode-32.sha256 +1 -0
- package/platforms/snapshots/hashnode-32.txt +1 -0
- package/platforms/snapshots/hn-23.sha256 +1 -0
- package/platforms/snapshots/hn-23.txt +1 -0
- package/platforms/snapshots/hn-24.sha256 +1 -0
- package/platforms/snapshots/hn-24.txt +1 -0
- package/platforms/snapshots/hn-25.sha256 +1 -0
- package/platforms/snapshots/hn-25.txt +1 -0
- package/platforms/snapshots/hyperframes-releases.sha256 +1 -0
- package/platforms/snapshots/hyperframes-releases.txt +1 -0
- package/platforms/snapshots/instagram-43.sha256 +1 -0
- package/platforms/snapshots/instagram-43.txt +1 -0
- package/platforms/snapshots/instagram-47.sha256 +1 -0
- package/platforms/snapshots/instagram-47.txt +1 -0
- package/platforms/snapshots/lemmy-policy.sha256 +1 -0
- package/platforms/snapshots/lemmy-policy.txt +1 -0
- package/platforms/snapshots/linkedin-1.sha256 +1 -0
- package/platforms/snapshots/linkedin-1.txt +1 -0
- package/platforms/snapshots/linkedin-2.sha256 +1 -0
- package/platforms/snapshots/linkedin-2.txt +1 -0
- package/platforms/snapshots/linkedin-3.sha256 +1 -0
- package/platforms/snapshots/linkedin-3.txt +1 -0
- package/platforms/snapshots/linkedin-4.sha256 +1 -0
- package/platforms/snapshots/linkedin-4.txt +1 -0
- package/platforms/snapshots/mastodon-15.sha256 +1 -0
- package/platforms/snapshots/mastodon-15.txt +1 -0
- package/platforms/snapshots/mastodon-16.sha256 +1 -0
- package/platforms/snapshots/mastodon-16.txt +1 -0
- package/platforms/snapshots/mastodon-17.sha256 +1 -0
- package/platforms/snapshots/mastodon-17.txt +1 -0
- package/platforms/snapshots/medium-34.sha256 +1 -0
- package/platforms/snapshots/medium-34.txt +1 -0
- package/platforms/snapshots/medium-35.sha256 +1 -0
- package/platforms/snapshots/medium-35.txt +1 -0
- package/platforms/snapshots/medium-36.sha256 +1 -0
- package/platforms/snapshots/medium-36.txt +1 -0
- package/platforms/snapshots/newsletter-58.sha256 +1 -0
- package/platforms/snapshots/newsletter-58.txt +1 -0
- package/platforms/snapshots/newsletter-59.sha256 +1 -0
- package/platforms/snapshots/newsletter-59.txt +1 -0
- package/platforms/snapshots/newsletter-60.sha256 +1 -0
- package/platforms/snapshots/newsletter-60.txt +1 -0
- package/platforms/snapshots/newsletter-61.sha256 +1 -0
- package/platforms/snapshots/newsletter-61.txt +1 -0
- package/platforms/snapshots/newsletter-62.sha256 +1 -0
- package/platforms/snapshots/newsletter-62.txt +1 -0
- package/platforms/snapshots/openai-image-pricing.sha256 +1 -0
- package/platforms/snapshots/openai-image-pricing.txt +1 -0
- package/platforms/snapshots/playwright-releases.sha256 +1 -0
- package/platforms/snapshots/playwright-releases.txt +1 -0
- package/platforms/snapshots/producthunt-37.sha256 +1 -0
- package/platforms/snapshots/producthunt-37.txt +1 -0
- package/platforms/snapshots/producthunt-38.sha256 +1 -0
- package/platforms/snapshots/producthunt-38.txt +1 -0
- package/platforms/snapshots/producthunt-39.sha256 +1 -0
- package/platforms/snapshots/producthunt-39.txt +1 -0
- package/platforms/snapshots/reddit-20.sha256 +1 -0
- package/platforms/snapshots/reddit-20.txt +1 -0
- package/platforms/snapshots/reddit-21.sha256 +1 -0
- package/platforms/snapshots/reddit-21.txt +1 -0
- package/platforms/snapshots/reddit-22.sha256 +1 -0
- package/platforms/snapshots/reddit-22.txt +1 -0
- package/platforms/snapshots/substack-policy.sha256 +1 -0
- package/platforms/snapshots/substack-policy.txt +1 -0
- package/platforms/snapshots/threads-18.sha256 +1 -0
- package/platforms/snapshots/threads-18.txt +1 -0
- package/platforms/snapshots/threads-19.sha256 +1 -0
- package/platforms/snapshots/threads-19.txt +1 -0
- package/platforms/snapshots/tiktok-50.sha256 +1 -0
- package/platforms/snapshots/tiktok-50.txt +1 -0
- package/platforms/snapshots/tiktok-51.sha256 +1 -0
- package/platforms/snapshots/tiktok-51.txt +1 -0
- package/platforms/snapshots/x-5.sha256 +1 -0
- package/platforms/snapshots/x-5.txt +1 -0
- package/platforms/snapshots/x-6.sha256 +1 -0
- package/platforms/snapshots/x-6.txt +1 -0
- package/platforms/snapshots/x-7.sha256 +1 -0
- package/platforms/snapshots/x-7.txt +1 -0
- package/platforms/snapshots/x-8.sha256 +1 -0
- package/platforms/snapshots/x-8.txt +1 -0
- package/platforms/snapshots/x-9.sha256 +1 -0
- package/platforms/snapshots/x-9.txt +1 -0
- package/platforms/snapshots/youtube-shorts-40.sha256 +1 -0
- package/platforms/snapshots/youtube-shorts-40.txt +1 -0
- package/platforms/snapshots/youtube-shorts-41.sha256 +1 -0
- package/platforms/snapshots/youtube-shorts-41.txt +1 -0
- package/platforms/snapshots/youtube-shorts-42.sha256 +1 -0
- package/platforms/snapshots/youtube-shorts-42.txt +1 -0
- package/platforms/sources.yml +947 -0
- package/platforms/substack/guide.md +94 -0
- package/platforms/substack/pack.yml +116 -0
- package/platforms/threads/guide.md +93 -0
- package/platforms/threads/pack.yml +148 -0
- package/platforms/tiktok/guide.md +92 -0
- package/platforms/tiktok/pack.yml +129 -0
- package/platforms/x/guide.md +94 -0
- package/platforms/x/pack.yml +130 -0
- package/platforms/youtube-shorts/guide.md +92 -0
- package/platforms/youtube-shorts/pack.yml +138 -0
- package/providers/prices.yml +31 -0
- package/schemas/campaign.v2.json +26 -0
- package/schemas/manifest.v1.json +37 -0
- package/schemas/pack.schema.json +601 -0
- package/schemas/review.schema.json +31 -0
- package/skills/studio-reviewer/SKILL.md +13 -0
- package/skills/studio-updater/SKILL.md +8 -0
- package/skills/studio-video/SKILL.md +20 -0
- package/skills/studio-visual/SKILL.md +12 -0
- package/skills/studio-writer/SKILL.md +14 -0
- package/templates/README.md +7 -0
- package/templates/card.html +1 -0
- package/templates/carousel-closing.html +1 -0
- package/templates/carousel-content.html +1 -0
- package/templates/carousel-title.html +1 -0
- package/templates/code.html +1 -0
- package/templates/fonts/IBM-Plex-OFL.txt +93 -0
- package/templates/fonts/IBMPlexMono.woff2 +0 -0
- package/templates/fonts/IBMPlexSans.woff2 +0 -0
- package/templates/fonts/Space-Grotesk-OFL.txt +93 -0
- package/templates/fonts/SpaceGrotesk.woff2 +0 -0
- package/templates/poster.html +1 -0
- package/templates/quote.html +1 -0
- package/templates/thumbnail.html +1 -0
- package/test/fixtures/reviews/calibration.json +22 -0
- package/test/fixtures/reviews/grounding/cases.json +17 -0
|
@@ -0,0 +1,119 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "devto",
|
|
3
|
+
"name": "DEV",
|
|
4
|
+
"marketBlaster": "devto",
|
|
5
|
+
"ai": "draft",
|
|
6
|
+
"aiSource": "devto-28",
|
|
7
|
+
"formats": [
|
|
8
|
+
"article",
|
|
9
|
+
"image"
|
|
10
|
+
],
|
|
11
|
+
"textLimit": "unknown",
|
|
12
|
+
"titleLimit": "unknown",
|
|
13
|
+
"media": [],
|
|
14
|
+
"disclosure": {
|
|
15
|
+
"text": {
|
|
16
|
+
"rule": "Select the applicable Hand Written, AI-Assisted or Fully Autonomous disclosure tier.",
|
|
17
|
+
"source": "devto-28",
|
|
18
|
+
"accepts": ["Hand Written (No AI)", "AI-Assisted (Some AI)", "Fully Autonomous"],
|
|
19
|
+
"acceptsWhenGenerated": ["AI-Assisted (Some AI)", "Fully Autonomous"]
|
|
20
|
+
},
|
|
21
|
+
"media": "unknown",
|
|
22
|
+
"voice": "unknown"
|
|
23
|
+
},
|
|
24
|
+
"rubric": [
|
|
25
|
+
{
|
|
26
|
+
"id": "hook",
|
|
27
|
+
"question": "Does the title name a developer outcome or problem?",
|
|
28
|
+
"anchors": {
|
|
29
|
+
"0": "The opening has no identifiable subject or result.",
|
|
30
|
+
"1": "A subject appears, but the problem or outcome is vague or delayed.",
|
|
31
|
+
"2": "The opening identifies the subject and a concrete problem or outcome."
|
|
32
|
+
}
|
|
33
|
+
},
|
|
34
|
+
{
|
|
35
|
+
"id": "audience-fit",
|
|
36
|
+
"question": "Does the introduction identify the environment and reader who can use the tutorial?",
|
|
37
|
+
"anchors": {
|
|
38
|
+
"0": "No intended reader or relevant situation is identifiable.",
|
|
39
|
+
"1": "A reader group or situation is hinted at but not connected to the content.",
|
|
40
|
+
"2": "The intended reader and relevant situation are explicit."
|
|
41
|
+
}
|
|
42
|
+
},
|
|
43
|
+
{
|
|
44
|
+
"id": "simplicity",
|
|
45
|
+
"question": "Are prerequisites and steps ordered so a developer can follow them?",
|
|
46
|
+
"anchors": {
|
|
47
|
+
"0": "The reader cannot reconstruct the main point or sequence.",
|
|
48
|
+
"1": "The main point is present but key context or ordering is missing.",
|
|
49
|
+
"2": "The main point and necessary steps are clear and ordered."
|
|
50
|
+
}
|
|
51
|
+
},
|
|
52
|
+
{
|
|
53
|
+
"id": "anti-slop",
|
|
54
|
+
"question": "Are generic AI-sounding transitions and unsupported claims absent?",
|
|
55
|
+
"anchors": {
|
|
56
|
+
"0": "The candidate relies on hype, fabricated urgency or unsupported claims.",
|
|
57
|
+
"1": "Some concrete substance is present but generic or inflated language remains.",
|
|
58
|
+
"2": "Concrete language replaces hype and claims are supported."
|
|
59
|
+
}
|
|
60
|
+
},
|
|
61
|
+
{
|
|
62
|
+
"id": "platform-fit",
|
|
63
|
+
"question": "Are the tags, headings, canonical URL and AI disclosure tier appropriate?",
|
|
64
|
+
"anchors": {
|
|
65
|
+
"0": "The candidate ignores the destination’s format or community rules.",
|
|
66
|
+
"1": "The format or community is identified but a relevant rule or constraint remains unchecked.",
|
|
67
|
+
"2": "The format and relevant destination rules are checked and followed."
|
|
68
|
+
}
|
|
69
|
+
},
|
|
70
|
+
{
|
|
71
|
+
"id": "visual-quality",
|
|
72
|
+
"question": "Are code screenshots avoidable, images described and diagrams legible?",
|
|
73
|
+
"anchors": {
|
|
74
|
+
"0": "The visual is unreadable or lacks its relevant alternative or captions.",
|
|
75
|
+
"1": "The visual is partly readable or an alternative or caption is incomplete.",
|
|
76
|
+
"2": "Key content is readable and relevant alternatives or accurate captions are present."
|
|
77
|
+
},
|
|
78
|
+
"appliesTo": [
|
|
79
|
+
"image",
|
|
80
|
+
"carousel",
|
|
81
|
+
"poster",
|
|
82
|
+
"video",
|
|
83
|
+
"diagram",
|
|
84
|
+
"logo",
|
|
85
|
+
"terminal-demo"
|
|
86
|
+
]
|
|
87
|
+
},
|
|
88
|
+
{
|
|
89
|
+
"id": "value",
|
|
90
|
+
"question": "Does a runnable example or concrete reproduction support the lesson?",
|
|
91
|
+
"anchors": {
|
|
92
|
+
"0": "No supported takeaway or useful example is identifiable.",
|
|
93
|
+
"1": "A takeaway is present but its evidence or practical detail is incomplete.",
|
|
94
|
+
"2": "A specific takeaway is supported by a concrete example or source."
|
|
95
|
+
}
|
|
96
|
+
},
|
|
97
|
+
{
|
|
98
|
+
"id": "canonical-url",
|
|
99
|
+
"question": "Is the original canonical URL set for a cross-post?",
|
|
100
|
+
"anchors": {
|
|
101
|
+
"0": "A cross-post has no canonical URL or points to the wrong source.",
|
|
102
|
+
"1": "The original source is identified but the canonical field remains unchecked.",
|
|
103
|
+
"2": "The canonical field identifies the original source, or the article is original."
|
|
104
|
+
}
|
|
105
|
+
}
|
|
106
|
+
],
|
|
107
|
+
"sources": [
|
|
108
|
+
"devto-26",
|
|
109
|
+
"devto-27",
|
|
110
|
+
"devto-28",
|
|
111
|
+
"devto-29",
|
|
112
|
+
"cross-platform-63",
|
|
113
|
+
"cross-platform-64"
|
|
114
|
+
],
|
|
115
|
+
"notes": [
|
|
116
|
+
"[JUDGEMENT] Rubric scores are editorial aids, not predictions of reach.",
|
|
117
|
+
"Check actual account, route, community and current requirements before publication."
|
|
118
|
+
]
|
|
119
|
+
}
|
|
@@ -0,0 +1,92 @@
|
|
|
1
|
+
# GitHub: README, Discussions and Releases
|
|
2
|
+
|
|
3
|
+
## Who reads it
|
|
4
|
+
|
|
5
|
+
[JUDGEMENT] Write for developers reading a reusable code example. Identify the actual reader and their situation, not a generic “everyone”.
|
|
6
|
+
|
|
7
|
+
## How distribution works
|
|
8
|
+
|
|
9
|
+
Explore may show popular or relevant projects personalized from activity; an exact Trending formula is **[UNVERIFIED]**. [Discovery](https://docs.github.com/en/get-started/exploring-projects-on-github/discovering-projects-on-github). README is the durable project entry point, Discussions are community conversations, and Releases describe versions; GitHub supports Markdown. Project-related promotion in a README is allowed when advertising is not its primary focus; bulk promotional activity and artificial stars/follows are prohibited. [Acceptable use](https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies). Universal AI disclosure rule **[UNVERIFIED]**.
|
|
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
|
+
- Code Gist: introduce the problem and runtime, provide minimal code and give a reproducible example.
|
|
18
|
+
|
|
19
|
+
- Add setup, expected output and a caveat in Markdown; do not bury the example under a product pitch.
|
|
20
|
+
|
|
21
|
+
- Embedded image limits are unknown; repository social-preview limits do not automatically apply to a Gist.
|
|
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 minimal API client.
|
|
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 minimal API client, 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 minimal API client 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 minimal API client.
|
|
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 minimal API client.
|
|
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 use the Gist primarily as an advertisement or fabricate runnable output.
|
|
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
|
+
Check applicable project and community rules; a universal 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 / Explore](https://docs.github.com/en/get-started/exploring-projects-on-github/discovering-projects-on-github)
|
|
91
|
+
- [specs / social preview](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)
|
|
92
|
+
- [community rules / promotion and manipulation](https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies)
|
|
@@ -0,0 +1,119 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "gist",
|
|
3
|
+
"name": "GitHub: README, Discussions and Releases",
|
|
4
|
+
"marketBlaster": "gist",
|
|
5
|
+
"ai": "draft",
|
|
6
|
+
"aiSource": "gist-54",
|
|
7
|
+
"formats": [
|
|
8
|
+
"article",
|
|
9
|
+
"diagram"
|
|
10
|
+
],
|
|
11
|
+
"textLimit": "unknown",
|
|
12
|
+
"titleLimit": "unknown",
|
|
13
|
+
"media": [
|
|
14
|
+
{
|
|
15
|
+
"kind": "image",
|
|
16
|
+
"maxBytes": "unknown"
|
|
17
|
+
}
|
|
18
|
+
],
|
|
19
|
+
"disclosure": {
|
|
20
|
+
"text": "unknown",
|
|
21
|
+
"media": "unknown",
|
|
22
|
+
"voice": "unknown"
|
|
23
|
+
},
|
|
24
|
+
"rubric": [
|
|
25
|
+
{
|
|
26
|
+
"id": "hook",
|
|
27
|
+
"question": "Does the opening identify what the code demonstrates?",
|
|
28
|
+
"anchors": {
|
|
29
|
+
"0": "The opening has no identifiable subject or result.",
|
|
30
|
+
"1": "A subject appears, but the problem or outcome is vague or delayed.",
|
|
31
|
+
"2": "The opening identifies the subject and a concrete problem or outcome."
|
|
32
|
+
}
|
|
33
|
+
},
|
|
34
|
+
{
|
|
35
|
+
"id": "audience-fit",
|
|
36
|
+
"question": "Are the runtime and intended developer clear?",
|
|
37
|
+
"anchors": {
|
|
38
|
+
"0": "No intended reader or relevant situation is identifiable.",
|
|
39
|
+
"1": "A reader group or situation is hinted at but not connected to the content.",
|
|
40
|
+
"2": "The intended reader and relevant situation are explicit."
|
|
41
|
+
}
|
|
42
|
+
},
|
|
43
|
+
{
|
|
44
|
+
"id": "simplicity",
|
|
45
|
+
"question": "Can a reader locate setup, example and expected result without searching?",
|
|
46
|
+
"anchors": {
|
|
47
|
+
"0": "The reader cannot reconstruct the main point or sequence.",
|
|
48
|
+
"1": "The main point is present but key context or ordering is missing.",
|
|
49
|
+
"2": "The main point and necessary steps are clear and ordered."
|
|
50
|
+
}
|
|
51
|
+
},
|
|
52
|
+
{
|
|
53
|
+
"id": "anti-slop",
|
|
54
|
+
"question": "Are inflated claims and boilerplate marketing absent?",
|
|
55
|
+
"anchors": {
|
|
56
|
+
"0": "The candidate relies on hype, fabricated urgency or unsupported claims.",
|
|
57
|
+
"1": "Some concrete substance is present but generic or inflated language remains.",
|
|
58
|
+
"2": "Concrete language replaces hype and claims are supported."
|
|
59
|
+
}
|
|
60
|
+
},
|
|
61
|
+
{
|
|
62
|
+
"id": "platform-fit",
|
|
63
|
+
"question": "Is the Gist focused on the code rather than bulk promotion?",
|
|
64
|
+
"anchors": {
|
|
65
|
+
"0": "The candidate ignores the destination’s format or community rules.",
|
|
66
|
+
"1": "The format or community is identified but a relevant rule or constraint remains unchecked.",
|
|
67
|
+
"2": "The format and relevant destination rules are checked and followed."
|
|
68
|
+
}
|
|
69
|
+
},
|
|
70
|
+
{
|
|
71
|
+
"id": "visual-quality",
|
|
72
|
+
"question": "Are diagrams or screenshots legible and described when present?",
|
|
73
|
+
"anchors": {
|
|
74
|
+
"0": "The visual is unreadable or lacks its relevant alternative or captions.",
|
|
75
|
+
"1": "The visual is partly readable or an alternative or caption is incomplete.",
|
|
76
|
+
"2": "Key content is readable and relevant alternatives or accurate captions are present."
|
|
77
|
+
},
|
|
78
|
+
"appliesTo": [
|
|
79
|
+
"image",
|
|
80
|
+
"carousel",
|
|
81
|
+
"poster",
|
|
82
|
+
"video",
|
|
83
|
+
"diagram",
|
|
84
|
+
"logo",
|
|
85
|
+
"terminal-demo"
|
|
86
|
+
]
|
|
87
|
+
},
|
|
88
|
+
{
|
|
89
|
+
"id": "value",
|
|
90
|
+
"question": "Can the reader run or adapt a concrete example?",
|
|
91
|
+
"anchors": {
|
|
92
|
+
"0": "No supported takeaway or useful example is identifiable.",
|
|
93
|
+
"1": "A takeaway is present but its evidence or practical detail is incomplete.",
|
|
94
|
+
"2": "A specific takeaway is supported by a concrete example or source."
|
|
95
|
+
}
|
|
96
|
+
},
|
|
97
|
+
{
|
|
98
|
+
"id": "runnable-example",
|
|
99
|
+
"question": "Are dependencies and commands sufficient to reproduce the example?",
|
|
100
|
+
"anchors": {
|
|
101
|
+
"0": "The example cannot run and has no dependency or command information.",
|
|
102
|
+
"1": "Code and some setup are present but a dependency, command or expected result is missing.",
|
|
103
|
+
"2": "Dependencies, commands and expected output support reproduction."
|
|
104
|
+
}
|
|
105
|
+
}
|
|
106
|
+
],
|
|
107
|
+
"sources": [
|
|
108
|
+
"gist-52",
|
|
109
|
+
"gist-53",
|
|
110
|
+
"gist-54",
|
|
111
|
+
"cross-platform-63",
|
|
112
|
+
"cross-platform-64"
|
|
113
|
+
],
|
|
114
|
+
"notes": [
|
|
115
|
+
"[JUDGEMENT] Rubric scores are editorial aids, not predictions of reach.",
|
|
116
|
+
"Check actual account, route, community and current requirements before publication.",
|
|
117
|
+
"Image limit applies to repository social previews, not arbitrary embedded images."
|
|
118
|
+
]
|
|
119
|
+
}
|
|
@@ -0,0 +1,92 @@
|
|
|
1
|
+
# GitHub: README, Discussions and Releases
|
|
2
|
+
|
|
3
|
+
## Who reads it
|
|
4
|
+
|
|
5
|
+
[JUDGEMENT] Write for repository contributors joining a project discussion. Identify the actual reader and their situation, not a generic “everyone”.
|
|
6
|
+
|
|
7
|
+
## How distribution works
|
|
8
|
+
|
|
9
|
+
Explore may show popular or relevant projects personalized from activity; an exact Trending formula is **[UNVERIFIED]**. [Discovery](https://docs.github.com/en/get-started/exploring-projects-on-github/discovering-projects-on-github). README is the durable project entry point, Discussions are community conversations, and Releases describe versions; GitHub supports Markdown. Project-related promotion in a README is allowed when advertising is not its primary focus; bulk promotional activity and artificial stars/follows are prohibited. [Acceptable use](https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies). Universal AI disclosure rule **[UNVERIFIED]**.
|
|
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
|
+
- Discussion: choose the correct category; state the context, proposal or question, evidence and alternatives.
|
|
18
|
+
|
|
19
|
+
- Link relevant issues, commits or documentation and name the specific decision or feedback sought.
|
|
20
|
+
|
|
21
|
+
- Embedded media limits are unknown; describe diagrams and do not substitute social-preview rules for discussion limits.
|
|
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 proposed configuration change.
|
|
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 proposed configuration change, 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 proposed configuration change 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 proposed configuration change.
|
|
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 proposed configuration change.
|
|
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 post bulk promotions, request artificial stars or put a proposal in an unrelated category.
|
|
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
|
+
Check applicable project and community rules; a universal 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 / Explore](https://docs.github.com/en/get-started/exploring-projects-on-github/discovering-projects-on-github)
|
|
91
|
+
- [specs / social preview](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)
|
|
92
|
+
- [community rules / promotion and manipulation](https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies)
|
|
@@ -0,0 +1,122 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "github-discussion",
|
|
3
|
+
"name": "GitHub: README, Discussions and Releases",
|
|
4
|
+
"marketBlaster": "github-discussion",
|
|
5
|
+
"ai": "draft",
|
|
6
|
+
"aiSource": "github-discussion-policy",
|
|
7
|
+
"formats": [
|
|
8
|
+
"article",
|
|
9
|
+
"image"
|
|
10
|
+
],
|
|
11
|
+
"textLimit": "unknown",
|
|
12
|
+
"titleLimit": "unknown",
|
|
13
|
+
"marketBlasterMedia": { "source": "mb-check", "allowedKinds": [] },
|
|
14
|
+
"media": [
|
|
15
|
+
{
|
|
16
|
+
"kind": "image",
|
|
17
|
+
"maxBytes": "unknown"
|
|
18
|
+
}
|
|
19
|
+
],
|
|
20
|
+
"disclosure": {
|
|
21
|
+
"text": "unknown",
|
|
22
|
+
"media": "unknown",
|
|
23
|
+
"voice": "unknown"
|
|
24
|
+
},
|
|
25
|
+
"rubric": [
|
|
26
|
+
{
|
|
27
|
+
"id": "hook",
|
|
28
|
+
"question": "Does the title identify the decision or problem?",
|
|
29
|
+
"anchors": {
|
|
30
|
+
"0": "The opening has no identifiable subject or result.",
|
|
31
|
+
"1": "A subject appears, but the problem or outcome is vague or delayed.",
|
|
32
|
+
"2": "The opening identifies the subject and a concrete problem or outcome."
|
|
33
|
+
}
|
|
34
|
+
},
|
|
35
|
+
{
|
|
36
|
+
"id": "audience-fit",
|
|
37
|
+
"question": "Does the opening tell contributors which project and users are affected?",
|
|
38
|
+
"anchors": {
|
|
39
|
+
"0": "No intended reader or relevant situation is identifiable.",
|
|
40
|
+
"1": "A reader group or situation is hinted at but not connected to the content.",
|
|
41
|
+
"2": "The intended reader and relevant situation are explicit."
|
|
42
|
+
}
|
|
43
|
+
},
|
|
44
|
+
{
|
|
45
|
+
"id": "simplicity",
|
|
46
|
+
"question": "Are context, proposal and open questions separated clearly?",
|
|
47
|
+
"anchors": {
|
|
48
|
+
"0": "The reader cannot reconstruct the main point or sequence.",
|
|
49
|
+
"1": "The main point is present but key context or ordering is missing.",
|
|
50
|
+
"2": "The main point and necessary steps are clear and ordered."
|
|
51
|
+
}
|
|
52
|
+
},
|
|
53
|
+
{
|
|
54
|
+
"id": "anti-slop",
|
|
55
|
+
"question": "Are vague announcements and requests for artificial engagement absent?",
|
|
56
|
+
"anchors": {
|
|
57
|
+
"0": "The candidate relies on hype, fabricated urgency or unsupported claims.",
|
|
58
|
+
"1": "Some concrete substance is present but generic or inflated language remains.",
|
|
59
|
+
"2": "Concrete language replaces hype and claims are supported."
|
|
60
|
+
}
|
|
61
|
+
},
|
|
62
|
+
{
|
|
63
|
+
"id": "platform-fit",
|
|
64
|
+
"question": "Is the discussion in the right category and relevant to the repository?",
|
|
65
|
+
"anchors": {
|
|
66
|
+
"0": "The candidate ignores the destination’s format or community rules.",
|
|
67
|
+
"1": "The format or community is identified but a relevant rule or constraint remains unchecked.",
|
|
68
|
+
"2": "The format and relevant destination rules are checked and followed."
|
|
69
|
+
}
|
|
70
|
+
},
|
|
71
|
+
{
|
|
72
|
+
"id": "visual-quality",
|
|
73
|
+
"question": "Are any diagrams legible and described for readers who cannot see them?",
|
|
74
|
+
"anchors": {
|
|
75
|
+
"0": "The visual is unreadable or lacks its relevant alternative or captions.",
|
|
76
|
+
"1": "The visual is partly readable or an alternative or caption is incomplete.",
|
|
77
|
+
"2": "Key content is readable and relevant alternatives or accurate captions are present."
|
|
78
|
+
},
|
|
79
|
+
"appliesTo": [
|
|
80
|
+
"image",
|
|
81
|
+
"carousel",
|
|
82
|
+
"poster",
|
|
83
|
+
"video",
|
|
84
|
+
"diagram",
|
|
85
|
+
"logo",
|
|
86
|
+
"terminal-demo"
|
|
87
|
+
]
|
|
88
|
+
},
|
|
89
|
+
{
|
|
90
|
+
"id": "value",
|
|
91
|
+
"question": "Does the discussion link to evidence or a concrete reproduction?",
|
|
92
|
+
"anchors": {
|
|
93
|
+
"0": "No supported takeaway or useful example is identifiable.",
|
|
94
|
+
"1": "A takeaway is present but its evidence or practical detail is incomplete.",
|
|
95
|
+
"2": "A specific takeaway is supported by a concrete example or source."
|
|
96
|
+
}
|
|
97
|
+
},
|
|
98
|
+
{
|
|
99
|
+
"id": "discussion-category",
|
|
100
|
+
"question": "Does the selected category match the question or proposal?",
|
|
101
|
+
"anchors": {
|
|
102
|
+
"0": "The category is unrelated to the topic.",
|
|
103
|
+
"1": "A plausible category is selected but its fit is unresolved.",
|
|
104
|
+
"2": "The selected category matches the project question or proposal."
|
|
105
|
+
}
|
|
106
|
+
}
|
|
107
|
+
],
|
|
108
|
+
"sources": [
|
|
109
|
+
"mb-check",
|
|
110
|
+
"github-discussion-policy",
|
|
111
|
+
"gist-52",
|
|
112
|
+
"gist-53",
|
|
113
|
+
"gist-54",
|
|
114
|
+
"cross-platform-63",
|
|
115
|
+
"cross-platform-64"
|
|
116
|
+
],
|
|
117
|
+
"notes": [
|
|
118
|
+
"[JUDGEMENT] Rubric scores are editorial aids, not predictions of reach.",
|
|
119
|
+
"Check actual account, route, community and current requirements before publication.",
|
|
120
|
+
"Image limit applies to repository social previews, not arbitrary embedded images."
|
|
121
|
+
]
|
|
122
|
+
}
|
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
# Hashnode
|
|
2
|
+
|
|
3
|
+
## Who reads it
|
|
4
|
+
|
|
5
|
+
[JUDGEMENT] Write for developers reading technical tutorials and syndicated articles. Identify the actual reader and their situation, not a generic “everyone”.
|
|
6
|
+
|
|
7
|
+
## How distribution works
|
|
8
|
+
|
|
9
|
+
A [historical feed description](https://townhall.hashnode.com/revamped-personalized-feed) cites followed tags/authors, engagement and quality signals; it does not establish today's weights. Articles support Markdown and syndicated original URLs. [Syndication](https://townhall.hashnode.com/why-you-should-republish-your-devblog-posts-and-how-to-do-it). [Terms](https://hashnode.com/terms) require review/edit/approval of AI-generated editor suggestions and prohibit unsolicited promotion and generation intended to manipulate search or engagement. General disclosure mandate **[UNVERIFIED]**.
|
|
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: state the problem, environment, reproducible steps, outcome and limitations.
|
|
18
|
+
|
|
19
|
+
- Syndication: set the original URL and review the imported text; article length is unknown.
|
|
20
|
+
|
|
21
|
+
- Cover image: use a relevant illustration and alt text; the sourced 8 MB limit is specific to the upload API.
|
|
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 database migration.
|
|
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 database migration, 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 database migration 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 database migration.
|
|
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 database migration.
|
|
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 submit unreviewed AI editor suggestions or manipulative promotion.
|
|
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
|
+
Review, edit and approve AI editor suggestions. A general disclosure mandate 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 / historical feed](https://townhall.hashnode.com/revamped-personalized-feed)
|
|
91
|
+
- [specs / syndication](https://townhall.hashnode.com/why-you-should-republish-your-devblog-posts-and-how-to-do-it)
|
|
92
|
+
- [specs / image upload API](https://github.com/Hashnode/gql-skill/blob/main/skills/gql-api/references/mutations.md)
|
|
93
|
+
- [AI policy / community rules](https://hashnode.com/terms)
|