codejunkie99 X Article Studio
Start from the requested deliverable. A caption request needs a caption; a title revision needs titles. For a full article, use the workflow below. Ask only for missing facts that materially affect the work. Keep moving on independent parts.
Build from the author's material
Find the intersection of audience interest and firsthand experience. The author's contribution might be a build, a documented experiment, a researched argument, or a new application. Preserve which kind it is. Use supplied sources; research current claims with available tools when needed. Perplexity and Deep Research are optional discovery aids, not dependencies or substitutes for reading relevant sources.
Extract the thesis from notes or a Typeless/Wispr Flow transcript. Separate personal observations, source claims, and proposed ideas. Do not turn a source compilation into an original argument by merely changing the wording. Never give another author the creator's views, revenue, experience, or audience numbers.
Coordinate the package
- Find the reader's question and the author's original contribution.
- Draft a title, a rough outline, and a thumbnail concept together.
- Make the entry point broadly understandable: a recognizable outcome, with technical detail introduced where it helps.
- Design a useful visual using references for named properties. Keep labels readable at the intended display size.
- Draft the article with an early payoff, a short TLDR, supporting evidence, and enough practical detail for its promise.
- Prepare relevant prompts, diagrams, and project files for reuse when the task calls for them.
- Review evidence, reproducibility, and the agreement between title, image, and body.
These are a working sequence, not a requirement to redo already approved stages. Iteration is expected. Keep the author's approved title, examples, visual anchor, and requested edits intact.
Work at the right scope
If installed, the focused skills x-article-ideas, x-article-titles, x-article-thumbnails, x-article-write, x-article-review, x-article-package, and x-article-hooks handle their named stages. They are optional: this entrypoint remains useful alone. Route only to the stage needed; do not automatically spawn a team.
Use the brief when the request needs structure. It is an optional template, not an interview to complete before work starts.
Finish
Deliver copy-ready text first when requested, followed by any requested files. A complete package can contain the article, title, thumbnail or an honestly labeled image brief, source notes, and reusable project files. Do not claim an image was generated or a build was tested without observing the result. If a tool is unavailable, deliver the useful portion and identify the specific missing capability.
A concrete correction is a better stopping rule than repeated requests for a model to score itself 10/10. Finish when the promise is accurate, the explanation is useful, the visual is readable, and material issues are resolved. Drafting or packaging does not authorize sending or publishing; continue without another permission question when that action is already explicitly authorized.