NNAWALABS

AI TOOL GUIDE / CLAUDE

Claude: 10 useful ways to turn a conversation into real work

A practical guide to long documents, meetings, research, writing, code and Artifacts—plus the boundaries that keep a helpful assistant from becoming an unreliable decision-maker.

CLAUDE10

WORKFLOWS / USES

Person writing with a pen in an open notebook beside a laptop and small plant
A person writes in an open notebook at a desk beside a laptop and small plant. Contextual workspace photograph; no endorsement or product use is implied. Photo by Shixart1985 on Wikimedia Commons · CC BY 2.0.

Strong starting point for careful drafting, document-heavy work and iterative thinking.

!Do not use it as the final authority for legal, medical, financial, security or other high-impact decisions.

Before you begin

Define the output, audience and review owner. Remove confidential or personal data unless your organization has approved the product, plan and workflow. Features differ by plan and can change; check Anthropic’s current documentation.

  1. 01

    Review a long document without losing the question

    Upload or paste only material you are allowed to share. Ask for a map of sections, claims, evidence and unresolved questions before asking for a summary. Compare every important conclusion with the original pages.

    A better starting prompt

    Act as a document analyst. First map the structure and list claims that need verification. Do not infer missing facts. Then answer my three questions with page or section references.

  2. 02

    Turn rough notes into a decision memo

    Give Claude the audience, decision, constraints and evidence. Request a one-page memo with options, trade-offs and open issues—not a polished answer that hides uncertainty.

    A better starting prompt

    Convert these approved notes into a one-page decision memo: decision needed, context, three options, trade-offs, recommendation rationale, and questions still open.

  3. 03

    Prepare for a meeting

    Share the agenda and non-sensitive background. Ask for stakeholder questions, assumptions to test and a short opening—not invented intelligence about people.

    A better starting prompt

    Prepare me for this meeting. Separate known facts from assumptions, propose five questions, and draft a 60-second opening aligned with the agenda.

  4. 04

    Build a reusable writing template

    Use a good example you own, explain why it works, and ask for a blank structure with instructions. Test the template on a second case before rolling it out.

    A better starting prompt

    Study this approved example for structure and tone. Create a reusable template with field instructions and a final human-review checklist. Do not copy case-specific details.

  5. 05

    Compare options with explicit criteria

    Choose criteria and weights before providing product names. Claude can organise the comparison; you still verify current features, prices, contracts and security information at the source.

    A better starting prompt

    Create a comparison matrix using these criteria and weights. Mark unknowns as unknown, cite the material I supplied, and list what must be confirmed with each vendor.

  6. 06

    Plan research before searching

    Ask for a question tree, evidence hierarchy, inclusion rules and search terms. This reduces random browsing and makes gaps visible.

    A better starting prompt

    Turn this topic into a research plan: primary question, subquestions, preferred primary sources, exclusion rules, search terms, and a table for recording evidence.

  7. 07

    Explain code or a technical concept

    Request a plain-language walkthrough, assumptions, edge cases and a small test. Never paste secrets, keys or proprietary code without approval; run and review code in the proper environment.

    A better starting prompt

    Explain this approved snippet line by line, identify assumptions and failure cases, then propose minimal tests. Do not claim the code ran unless it was actually executed.

  8. 08

    Create a checklist from a policy

    Ask Claude to extract obligations, owner, evidence and cadence while retaining source references. A checklist is an aid, not a substitute for the governing text.

    A better starting prompt

    Convert this policy into an operational checklist with requirement, owner, evidence, timing and source clause. Flag ambiguous language for human review.

  9. 09

    Prototype an Artifact

    Artifacts can hold substantial standalone content such as documents, diagrams, code or interactive components. Start with a small, non-sensitive prototype and inspect logic, accessibility and sharing settings.

    A better starting prompt

    Create a simple Artifact for this approved workflow. Show assumptions, make labels accessible, keep data local to the example, and include a manual verification step.

  10. 10

    Critique your own draft

    Use a separate pass: ask Claude to find weak evidence, ambiguity, missing audiences and overconfident language. Then decide which edits are valid rather than accepting every change.

    A better starting prompt

    Audit the draft against this brief. List unsupported claims, missing context, unclear actions and tone risks. Suggest edits, but keep recommendations separate from the original.

Official sources and verification

Information checked on 3 August 2026 against Anthropic’s official pages. Availability can vary by plan and region.