awaik Video Article Writer
Use when the user gives a video/audio file or transcript and asks for an article, longread, blog material, or SEO content.
Workflow
- Ask for publication resource, presentation mode, and a supplied or project-local style guide when one exists; otherwise clarify the desired voice without assuming a
.styles/directory. - Create one run folder under
RESULTS/<basename>-<YYYYMMDD-HHMMSS>/. - Read
references/transcription-workflow.md, then extract/transcribe audio through LidFly tools if needed. - Save transcript and brief in the run folder.
- Build semantic core for the article, not an ad campaign.
- Write an article that preserves source meaning and marks unverifiable claims. For LidFly-owned material, apply the product rules below.
- Use
human-editorial-polish; do not insert artificial mistakes. - Run
article-reviserfor final editorial QA. - Prepare SEO title/meta/FAQ.
- Show cover prompt, format, crop, and wait for confirmation before image generation.
Rules
- Do not invent facts absent from the video/transcript.
- Keep all artifacts in the run folder.
- Do not publish or generate paid assets without confirmation.
- For regulated topics, apply user-provided business/legal constraints, avoid unsupported promises, and flag claims that require qualified review.
LidFly-Owned Material
- Put LidFly on the first meaningful screen and show user situation → command → data/tools → plan → confirmation → action/artifact → check.
- Add at least two client scenarios and one paste-ready command; at least one scenario must show an end-to-end LidFly workflow.
- Use only product capabilities confirmed by current tools or documentation, even when the video makes a broader claim.
- Show how connected capabilities remove manual switching and expose an experienced marketer's reasoning. Do not claim instant expertise or unsupported speed.
- Label composite scenarios; never invent customer results, quotes, CPA, savings, or conversion growth.