AI PRACTICE · FUTALK DESIGN DIARY
AI Weekly Skill
Give AI the mechanical work and keep editorial judgement human
A human–AI production system built for the long-running FuTalk Design Diary weekly: AI and automation handle discovery, first-pass filtering, organisation, translation, imagery, layout, audits, and draft creation; editorial value, fact-checking, visual judgement, selection, and publishing remain human decisions.
View project Git ↗
- My role
- Creator, editor-in-chief, final owner, and rule-maker
- Cadence
- Weekly, across production, review, drafts, and maintenance
- Current version
- Workflow v0.6.5, running in real production
01 · STARTING POINT
The goal was never to let AI write the weekly for me
Automate the mechanical work, retain human judgement, and keep every result reviewable and traceable
THREE PROBLEMS WITH MANUAL PRODUCTION
- Browsing, filtering, translation, screenshots, and layout repeat every week.
- Mechanical work crowds out the editorial decisions that require experience and taste.
- A fully manual process is easy to interrupt when the workload grows.
WHAT THIS PROJECT CHANGES
- Reduce repetitive work and sustain a reliable weekly cadence.
- Expand the candidate pool without lowering editorial quality.
- Make results traceable, stop errors, and turn experience into a maintainable system.
02 · WORKFLOW
Six stages, with the final vote kept human
Divide a real SOP into stable, testable stages so every step leaves evidence and every run stays traceable
- 01 · AIRules & state
Read editorial rules and state; set issue number and date window
- 02 · AI + HUMANCandidate review
Owner inbox plus discovery, deduplication, and categories
- 03 · AIImages & cover
Source images, screenshots, audits, and five cover candidates
- 04 · AIBuild outputs
Markdown, HTML, draft package, and audit evidence
- 05 · HUMANDual review
Visual review plus automated quality gates
- 06 · HUMANDraft & archive
Create and read back drafts only after approval
A version exists only after explicit owner acceptance—passing automation and visual review is not acceptance.
AI · AI and automation handle
- Candidate discovery, aggregation, deduplication, and categories
- Faithful translation, summaries, and structured data
- Article images, screenshots, and cover backgrounds
- Markdown, HTML, and WeChat draft packages
- Linting, style checks, completeness checks, and dry-runs
HUMAN · I remain responsible for
- Sources, sections, and editorial standards
- Value, credibility, and relevance to readers
- Titles, summaries, links, and image checks
- The final cover and accepted version
- Whether a draft is created or anything is published
03 · IN PRODUCTION
Already running in real production
Built for FuTalk Design Diary every week—not unattended publishing, but a workflow reviewed at every consequential step
- SOP SYSTEM · COMPLETEReal practice became standards
Sources, section rules, owner inbox, evidence chain, and quality gates are established.
- END TO END · COMPLETEFrom candidates to verified drafts
Discovery, translation, imagery, covers, draft creation, and read-back verification run in production.
- PRODUCTION · NOWUsed and hardened every week
Improving capture reliability and quality gates while tracking failures and rework.
- MODULARITY · NEXTSeparate specific from reusable
Distil stable rules and evaluate which capabilities can become reusable components.
- Readable weeklyFinal Markdown and a near-final WeChat HTML preview.
- Visual outputsA 900×383 cover and correctly proportioned article images.
- WeChat packageA structured package, created and read back only after approval.
- Audit evidenceCandidate, section, image, cover, source, and visual-review records.
PROCESS JOURNAL