--- title: "Use Claude Projects as a working editorial desk" description: "Build a Claude writing project around approved references, your own voice, claim checking and a repeatable editorial review." author: Power of AI date: 2026-09-06 url: https://powerofai.ca/claude/projects-and-writing --- # Use Claude Projects as a working editorial desk Build a Claude writing project around approved references, your own voice, claim checking and a repeatable editorial review. Bring your material. Keep your point of view. A useful writing assistant needs more than a request to sound natural. It needs to know what you believe, which facts you can support and who will read the piece. A project gives that context a home. The aim is to spend less time reconstructing the background and more time making choices that improve the writing. ## Create a small, purposeful reference shelf Claude Projects support uploaded knowledge and project instructions. Use them for a coherent body of work: a newsletter, a community organization or a research topic. Start with a few current, approved references and a short description of the audience. A large folder full of contradictory drafts can make the starting point less clear. Name documents so their roles are obvious: approved facts, voice samples, working notes and retired drafts. Keep dates on information that can change. Ask Claude to identify which references support the current assignment and flag conflicts before drafting. A project provides context; you still need to check whether a particular answer used the right part of it. ## Explain what makes your writing yours Choose two short passages you wrote and annotate what you want preserved. Perhaps you lead with a specific scene, use short transitions and leave the reader space to disagree. Explain which features are incidental, too. A sarcastic line from one essay should not turn every customer email into a performance. State your position in ordinary language before asking for polish. If you do not yet know the argument, ask for an interview: one question at a time about what surprised you, what changed your mind and what the reader needs to understand. Keep personal experiences grounded in things you actually supply. ### A request you can adapt Interview me about this piece before drafting. Ask one useful question at a time. Then propose an outline using my position and the approved references. Preserve uncertainty. Do not invent an anecdote, quotation or experience. Put claims needing a source in a separate list. ## Revise in passes with different jobs First check the argument. Does the opening promise something the article delivers? Does each section advance that point? Next check the evidence. Open the source for every consequential factual claim. Then work on rhythm, examples and sentence length. Separating these passes makes it easier to see whether an elegant edit has weakened the meaning. Ask for a short explanation of substantial changes. If a sentence became stronger, did its evidence become stronger too? If a caveat disappeared, was it redundant or inconvenient? Restore uncertainty when the available material warrants it. A readable draft should help the reader understand your confidence, not conceal its limits. ## Keep a reusable editorial checklist Before sharing, read the piece aloud and check names, dates, links and quotations against the originals. Inspect the title and excerpt separately; those short surfaces often make claims broader than the article. Remove placeholder language and verify any image caption. A polished body cannot compensate for an inaccurate headline. When the work is finished, save the final version alongside its source list and a few notes about the edits that helped. Add recurring preferences to the project instructions only after they prove useful. Over time, this becomes an editorial practice you can repeat, with the assistant helping you concentrate on the judgments that remain yours. ## Take this into your next task Give the assistant a clear argument and a trustworthy reference shelf, then review meaning before style. [Build a project brief](/showcase#brief-builder). ## Sources and editorial notes Reviewed September 6, 2026. Product capabilities depend on the app, plan, region and workspace settings. Workflows and prompts are authored teaching material, not recorded model results or measured time-saving claims. - [Anthropic: projects and project knowledge](https://support.claude.com/en/articles/9517075-what-are-projects) ## Keep going - [Research with Claude without losing the source trail](/claude/research-with-documents) - [Continue the guide](/writing/astra-writing-prompt) - [Create Useful Documents and Presentations with AI](/workflows/documents-and-presentations)