Conversation
…body
Third attempt at the same post. Two prior attempts both wrong:
v1 (for-the-ones-who-lose-things): drifted into marketing —
benefits lists, audience segmentation, CTA verbs.
v2 (what-we-hand-to-machines): overcorrected into a beige
philosophy essay — Cormorant Garamond italic paragraphs,
no code, no diagrams, no opinions.
What this version (another-notes-app) actually does:
- Body font is now Kalam (handwritten but readable for prose).
Caveat is reserved for short accents only (1-3 word emphasis).
Cormorant Garamond is removed from body usage; only the inode
wordmark still uses it.
- Inter sans-serif used for big page titles and stack-card names
to give visual variety against the Kalam paragraphs.
- Visual variety on every page: 2 terminal blocks (demo + install),
1 sketchy embedding scatter visualisation, 1 architecture
diagram with adapter pattern boxes + arrows, 1 stack-card grid,
hand-drawn ✗ marks for the pain pages.
- Voice is dry-witted developer talking to developer. Real opinions,
real takes on Notion / Obsidian / 1Password without punching down.
"please don't ask me to add a kanban board." kind of energy.
- Real terminal output for `inode add` / `inode ask` (page 4) and
real install commands you can copy-paste (page 10).
SKILL.md updated to reflect both lessons:
- Type discipline section now mandates Kalam for body, Caveat
accent-only, Cormorant banned for body. Includes the Google
Fonts <link> string to copy.
- New "Visual variety" section requires at least 3 of: terminal
block, architecture diagram, stack-card grid, comparison page,
embedding scatter, hand-drawn pain list.
- Voice rules section lists banned phrases and the dry-wit register.
- Counter-examples section points at both v1 and v2 by name with
a one-line diagnosis of each, so future invocations of the skill
know what to avoid.
chore(social): rewrite — developer-blog voice, visual variety, Kalam body
shahid-io
enabled auto-merge
June 14, 2026 09:38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Briefly describe what this PR does and why.
Fixes #
Type of Change
feat— new featurefix— bug fixrefactor— refactoring, no behaviour changedocs— documentation onlychore— dependencies, tooling, configtest— adding or fixing testsci— CI/CD pipelineChanges
Testing
Describe how you tested this. What cases did you verify?
# commands you ranChecklist
develop(ormainfor hotfix)go test ./...passesgo vet ./...passesBreaking Change?