{"id":44,"date":"2026-04-07T08:55:44","date_gmt":"2026-04-07T08:55:44","guid":{"rendered":"https:\/\/simutecra.com\/blog\/?p=44"},"modified":"2026-04-07T10:51:25","modified_gmt":"2026-04-07T10:51:25","slug":"claude-prompts-for-engineers-20-ready-to-use-prompts-for-cad-design-and-manufacturing","status":"publish","type":"post","link":"https:\/\/simutecra.com\/blog\/claude-prompts-for-engineers-20-ready-to-use-prompts-for-cad-design-and-manufacturing\/","title":{"rendered":"Claude Prompts for Engineers: 20 Ready-to-Use Prompts for CAD, Design, and Manufacturing"},"content":{"rendered":"\n

Engineers are not short of things to do. Documentation, drawing reviews, specification writing, supplier communication, tolerance analysis, DFM checks \u2014 the work that surrounds the actual engineering is substantial, and most of it follows repeatable patterns. Claude<\/strong> prompts for engineers<\/strong> handles repeatable patterns well.<\/p>\n\n\n\n

This is a working reference guide: 20 prompts across five categories, each one built for a specific engineering task. They are written to be used directly \u2014 copy, adapt to your context, and go. The goal is to save you time on the surrounding work so you can spend it on the engineering that actually requires your expertise.<\/p>\n\n\n\n

How to Get the Most Out of These Claude Prompts<\/strong> for Engineers<\/strong><\/h2>\n\n\n\n

Claude’s output quality scales directly with the context you give it. Every prompt below includes placeholder brackets \u2014 fill these with your actual project details before sending. A prompt with specifics gets a specific, usable answer. A vague prompt gets a generic one.<\/p>\n\n\n\n

A few principles that apply across all of these:<\/p>\n\n\n\n

    \n
  • Tell Claude your role and context upfront. ‘I am a mechanical engineer reviewing a supplier’s drawing package for a precision machined housing’ gives Claude a framework it uses throughout the conversation.<\/li>\n\n\n\n
  • Iterate. The first response is a starting point, not a final output. Push back, ask for more depth on a specific section, ask it to rewrite something in a different format.<\/li>\n\n\n\n
  • Use Claude’s output as a first draft. Everything it produces \u2014 specifications, checklists, documentation \u2014 should be reviewed by a qualified engineer before it is used in production. Claude accelerates the writing; the engineering judgment is still yours.<\/li>\n<\/ul>\n\n\n\n
    \"Claude<\/figure>\n\n\n\n

    Category 1: Drawing Review and Documentation<\/strong><\/h2>\n\n\n\n

    Drawing review and documentation are among the highest-value areas for Claude in an engineering context. The work is structured, the requirements are well-defined, and the output \u2014 checklists, review notes, revision summaries \u2014 is exactly the kind of writing Claude does well.<\/p>\n\n\n\n

    Prompt 1 \u2014 Drawing Review Checklist<\/mark><\/strong><\/h3>\n\n\n\n
    DRAWING & DOCUMENTATION
    <\/mark>Generate a drawing review checklist<\/strong><\/td><\/tr>
    I am reviewing a [2D detail drawing \/ assembly drawing \/ general arrangement drawing] for a [describe the part or assembly \u2014 e.g. ‘precision machined aluminium housing for an industrial pump’]. The drawing was produced to [ASME Y14.5 \/ ISO 128] standards.Generate a structured review checklist covering:1. Title block completeness2. View and projection correctness3. Dimensioning completeness and correctness4. Tolerance specification (GD&T and general)5. Material and surface finish callouts6. Notes and special requirements7. Drawing standard complianceFormat as a checklist I can work through during the review.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Prompt 2 \u2014 Revision Description<\/strong><\/h3>\n\n\n\n
    DRAWING & DOCUMENTATION
    <\/mark>Write a drawing revision description<\/strong><\/strong><\/td><\/tr>
    I need to write a revision description for an engineering drawing. The revision number is [e.g. Rev C]. The changes made from the previous revision are:[List the changes \u2014 e.g. ‘Added 2x M6 tapped holes on the top face, increased wall thickness from 4mm to 6mm on the side flanges, updated surface finish callout from Ra 3.2 to Ra 1.6 on the bore’]Write a concise, professional revision description suitable for the drawing title block revision history table. Maximum 3 sentences.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Prompt 3 \u2014 Drawing Notes Section<\/strong><\/h3>\n\n\n\n
    DRAWING & DOCUMENTATION
    <\/mark>Draft a general notes section<\/strong><\/strong><\/strong><\/td><\/tr>
    I need to write the general notes section for a manufacturing drawing for a [describe the part \u2014 material, manufacturing method, any special requirements].Draft a complete general notes section covering:- Applicable drawing standard- Default tolerances for dimensions without explicit callouts- Surface finish unless otherwise specified- Material and heat treatment- Any special manufacturing or inspection requirements- Deburring and edge break requirementsUse professional engineering drawing language.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Prompt 4 \u2014 Bill of Materials<\/strong><\/h3>\n\n\n\n
    DRAWING & DOCUMENTATION
    <\/mark>Structure a Bill of Materials<\/strong><\/strong><\/strong><\/strong><\/td><\/tr>
    I need to create a Bill of Materials for an assembly. The assembly consists of:[List each component: description, quantity, material or part number if known \u2014 e.g. ‘1x aluminium housing (custom machined), 4x M8x25 cap head screws (ISO 4762), 2x lip seals (NBR, 25mm bore)’]Format this as a structured BOM table with columns for: Item No., Description, Quantity, Part Number \/ Standard Reference, Material, Notes. Flag any items where I have not provided enough information.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Category 2: Design Review and DFM<\/strong><\/h2>\n\n\n\n

    Design for Manufacturability (DFM) reviews and design checks are time-consuming when done from scratch. Claude helps you structure the review, generate the right questions, and document findings consistently.<\/p>\n\n\n\n

    Prompt 5 \u2014 DFM Review<\/strong><\/h3>\n\n\n\n
    DESIGN REVIEW & DFM
    <\/mark>Run a Design for Manufacturability check<\/strong><\/strong><\/strong><\/strong><\/strong><\/td><\/tr>
    I need to conduct a DFM review on a [describe the part: geometry, material, manufacturing method \u2014 e.g. ‘injection moulded ABS housing with snap-fit clips and external ribbing’]. The part will be manufactured by [describe the process and any constraints \u2014 e.g. ‘a Tier 2 injection moulding supplier, target unit cost under \u00a33 at 10,000 units per year’].Review the following DFM considerations and flag any potential issues:1. Wall thickness uniformity2. Draft angles3. Undercuts and mould release4. Gate location and sink mark risk5. Tolerance achievability for the process6. Feature accessibility for tooling7. Part consolidation opportunitiesI will provide additional geometry details as needed.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Prompt 6 \u2014 Tolerance Stack-Up Explanation<\/strong><\/h3>\n\n\n\n
    DESIGN REVIEW & DFM
    <\/mark>Explain a tolerance stack-up scenario<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/td><\/tr>
    I have a tolerance stack-up question. In my assembly:[Describe the assembly and the dimensional chain \u2014 e.g. ‘Part A has a length of 50mm \u00b10.1mm. Part B has a bore depth of 52mm \u00b10.15mm. These parts must interface so that Part A sits 2mm below the face of Part B with a tolerance of \u00b10.05mm’]Please:1. Explain whether the stated tolerances are compatible with the assembly requirement2. Show the worst-case tolerance calculation3. Identify which tolerances are driving the stack and which have the most room to relax4. Suggest options if the stack does not close<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Prompt 7 \u2014 Material Selection Comparison<\/strong><\/h3>\n\n\n\n
    DESIGN REVIEW & DFM
    <\/mark>Compare material options for a specific application<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/td><\/tr>
    I am selecting a material for a [describe the part and its application \u2014 e.g. ‘bracket that will be exposed to outdoor weather, moderate mechanical load from vibration, needs to be painted, manufactured by laser cutting and bending’].Please compare the following materials for this application: [list your candidate materials \u2014 e.g. ‘mild steel (S275), 316 stainless steel, 6082-T6 aluminium’]Compare on: strength-to-weight, corrosion resistance, machinability\/formability, relative material cost, weldability, and suitability for the manufacturing method. Recommend the best option and explain the tradeoffs.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Prompt 8 \u2014 Design Change Impact Assessment<\/strong><\/h3>\n\n\n\n
    DESIGN REVIEW & DFM
    <\/mark>Assess the impact of a proposed design change<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/td><\/tr>
    I am considering a design change on an existing part. The current design is [describe briefly]. The proposed change is [describe the change \u2014 e.g. ‘increasing the wall thickness from 3mm to 5mm on one face to improve stiffness under bending load’].Please assess the likely impact of this change on:1. Part mass2. Manufacturing cost (machining time, material use)3. Lead time4. Any adjacent features or assembly interfaces that may be affected5. Whether the change is likely to require a drawing revision or a full re-qualificationFlag any downstream effects I may not have considered.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Category 3: Specification and Technical Writing<\/strong><\/h2>\n\n\n\n

    Engineering specifications, inspection plans, test procedures, and technical reports follow consistent structures. Claude drafts these faster than starting from a blank page \u2014 and with the right prompt, the structure it produces is close to what you would write yourself.<\/p>\n\n\n\n

    Prompt 9 \u2014 Incoming Inspection Plan<\/strong><\/h3>\n\n\n\n
    SPECIFICATION WRITING
    <\/mark>Draft an incoming inspection plan<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/td><\/tr>
    I need to create an incoming inspection plan for a purchased component. The component is: [describe \u2014 material, dimensions, manufacturing method, critical features].The key quality requirements are: [list \u2014 e.g. ‘bolt hole position within 0.3mm, surface finish Ra 1.6 on sealing face, hardness 200-240 HB, no visible porosity on machined surfaces’].Draft an inspection plan with:- Inspection scope (100% or sample-based, with rationale)- Measurement method for each characteristic- Acceptance criteria- Non-conformance disposition instructionsFormat as a table I can use directly.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Prompt 10 \u2014 Technical Specification Document<\/strong><\/h3>\n\n\n\n
    SPECIFICATION WRITING
    <\/mark>Write a part or assembly specification<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/td><\/tr>
    I need to write a technical specification document for [describe the part or assembly]. This specification will be used by [describe the audience \u2014 supplier, internal manufacturing team, QA department].The specification must cover:[List the key requirements \u2014 dimensions, material, surface treatment, functional performance requirements, applicable standards, test requirements]Structure the document with: Scope, References, Material Requirements, Dimensional Requirements, Surface and Finish Requirements, Functional Requirements, Inspection and Test Requirements, Packaging and Marking.Write in formal technical language appropriate for a supplier-facing document.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Prompt 11 \u2014 Engineering Change Notice<\/strong><\/h3>\n\n\n\n
    SPECIFICATION WRITING
    <\/mark>Draft an Engineering Change Notice (ECN)<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/td><\/tr>
    I need to draft an Engineering Change Notice for the following change:- Part \/ Assembly affected: [name and number]- Drawing revision: from [Rev X] to [Rev Y]- Description of change: [describe what changed and why]- Reason for change: [technical issue, cost reduction, supplier change, customer requirement, etc.]- Effectivity: [when the change takes effect \u2014 e.g. ‘from serial number 1247’, ‘from batch date 01\/06\/2025’, ‘immediate’]- Impact on existing stock \/ WIP: [describe]Draft a complete ECN document in a format suitable for internal engineering records and supplier notification.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    \"Claude<\/figure>\n\n\n\n

    Category 4: Supplier and Procurement Communication<\/strong><\/h2>\n\n\n\n

    Supplier communication eats engineering time. RFQ preparation, technical queries, non-conformance documentation, and supplier evaluation all involve structured writing that follows established patterns. These prompts handle the structure so you can focus on the content.<\/p>\n\n\n\n

    Prompt 12 \u2014 RFQ Technical Package<\/strong><\/h3>\n\n\n\n
    SUPPLIER & PROCUREMENT
    <\/mark>Draft the technical section of an RFQ<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/td><\/tr>
    I am preparing a Request for Quotation for the manufacture of [describe the part \u2014 quantity, material, manufacturing method, key specifications].Draft the technical requirements section of the RFQ, covering:1. Part description and function2. Material specification and certification requirements3. Manufacturing process requirements4. Quality and inspection requirements5. Drawing and document requirements (what the supplier must confirm they have reviewed)6. Packaging and delivery requirements7. Supplier qualification requirementsWrite in formal, supplier-facing language.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Prompt 13 \u2014 Non-Conformance Report<\/strong><\/h3>\n\n\n\n
    SUPPLIER & PROCUREMENT
    <\/mark>Draft a supplier non-conformance report<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/td><\/tr>
    I need to raise a non-conformance report against a supplier. The details are:- Supplier name: [name]- Part: [part name and number]- Batch \/ delivery reference: [reference]- Nature of non-conformance: [describe what is wrong \u2014 e.g. ‘bore diameter measured at 24.85mm against a drawing requirement of 25.00 +0.00\/-0.05mm on 6 of 20 parts inspected’]- Discovery point: [incoming inspection \/ during assembly \/ in field]- Disposition of affected parts: [return to supplier \/ scrap \/ use as-is with deviation \/ rework]Draft a formal NCR document requesting a corrective action response within [timeframe].<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Prompt 14 \u2014 Supplier Technical Query Response<\/strong><\/h3>\n\n\n\n
    SUPPLIER & PROCUREMENT
    <\/mark>Draft a response to a supplier technical query<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/td><\/tr>
    A supplier has raised the following technical query on our drawing: [paste or describe the supplier’s query exactly].The correct technical answer is: [describe what the answer is \u2014 even if you are not sure how to phrase it formally].Draft a formal written response to the supplier that:1. Acknowledges their query clearly2. Provides the technical clarification3. Confirms whether a drawing revision is required or whether this is a clarification only4. States any action required from the supplier before proceeding<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Category 5: Technical Communication and Reporting<\/strong><\/h2>\n\n\n\n

    Engineering findings, project updates, and technical reports are often written under time pressure and read by audiences with varying levels of technical background. These prompts help you communicate findings clearly without spending hours on the writing.<\/p>\n\n\n\n

    Prompt 15 \u2014 Engineering Summary for a Non-Technical Audience<\/strong><\/h3>\n\n\n\n
    TECHNICAL COMMUNICATION
    <\/mark>Translate engineering findings for a non-technical audience<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/td><\/tr>
    I need to explain the following engineering finding to a non-technical audience [e.g. senior management, a client, a procurement team]:[Describe the finding in technical terms \u2014 e.g. ‘FEA results show that the current bracket design experiences peak von Mises stress of 287 MPa at the fillet radius under the specified 5kN load, exceeding the yield strength of 6082-T6 aluminium at 260 MPa by 10%’]Rewrite this finding in plain language that:1. Explains what was found2. Explains why it matters (what will happen if unaddressed)3. States what the recommended action is4. Avoids engineering jargon without losing technical accuracy<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Prompt 16 \u2014 Lessons Learned Document<\/strong><\/h3>\n\n\n\n
    TECHNICAL COMMUNICATION
    <\/mark>Document project lessons learned<\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/td><\/tr>
    I need to document lessons learned from a recently completed engineering project. The project was [brief description]. Key issues that arose were:[List the issues \u2014 e.g. ‘tolerance stack-up not identified until assembly stage, causing rework on 30% of first-article parts; supplier changed material grade without notification; drawing revision control not enforced, resulting in manufacturer working from an outdated revision’]For each lesson, structure the entry as:- What happened- Root cause- Impact- Corrective action taken- Process change for future projectsWrite in a format suitable for an internal engineering knowledge base.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Prompt 17 \u2014 Design Review Meeting Agenda<\/strong><\/h3>\n\n\n\n
    TECHNICAL COMMUNICATION<\/mark>
    <\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong>Draft a design review meeting agenda<\/strong><\/td><\/tr>
    I am running a [Preliminary Design Review \/ Critical Design Review \/ Drawing Review] for [describe the project or product]. The review will be attended by [list attendees and their roles \u2014 e.g. ‘lead mechanical engineer, manufacturing engineer, QA manager, project manager, supplier representative’].Key topics to cover include: [list the main items \u2014 e.g. ‘design concept confirmation, material selection rationale, tolerance review, supplier capability assessment, outstanding design actions, timeline to first article’]Draft a structured agenda with time allocations, objectives for each agenda item, and a list of pre-read documents attendees should review before the meeting.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Prompt 18 \u2014 Root Cause Analysis Framework<\/strong><\/h3>\n\n\n\n
    TECHNICAL COMMUNICATION<\/mark>
    <\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong>Structure a root cause analysis<\/strong><\/strong><\/td><\/tr>
    I need to conduct a root cause analysis for the following problem: [describe the problem clearly \u2014 what happened, when, on what product or process, and what the impact was].Please structure a 5-Why analysis for this problem, starting from the observable symptom and working back to the root cause. For each ‘Why’, provide the most likely answer based on the information I have given you, and flag where I need to gather additional data before the analysis can proceed with confidence.At the end, suggest a corrective action targeted at the root cause rather than the symptom.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Prompt 19 \u2014 Progress Report to Client<\/strong><\/h3>\n\n\n\n
    TECHNICAL COMMUNICATION<\/mark>
    <\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong>Write a project progress report<\/strong><\/strong><\/strong><\/td><\/tr>
    I need to write a progress report for a client on an engineering project. The project is [brief description]. This report covers [time period].Progress this period:[List what has been completed]Current status:[Describe where the project stands \u2014 on schedule \/ delayed \/ ahead]Issues and risks:[List any issues or risks and what is being done about them]Next steps:[List what will be completed in the next period]Write a concise, professional progress report suitable for sending directly to the client. Positive but honest in tone. No jargon.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Prompt 20 \u2014 Technical Handover Document<\/strong><\/h3>\n\n\n\n
    TECHNICAL COMMUNICATION<\/mark>
    <\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong><\/strong>Draft a design handover document<\/strong><\/strong><\/strong><\/strong><\/td><\/tr>
    I need to document a design handover for [describe the project \u2014 part, assembly, or system being handed over]. The handover is from [design team \/ CAD engineer \/ project engineer] to [manufacturing team \/ new engineer \/ client \/ supplier].The document should cover:1. Design overview and intent2. Key design decisions and their rationale3. Known constraints and limitations4. Critical features and why they are critical5. Outstanding actions or unresolved issues6. Document register (drawings, specifications, analysis reports)7. Contact information for technical queriesWrite in a format that a new team member with engineering background but no prior knowledge of this project can follow.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    The Bottom Line<\/strong><\/h2>\n\n\n\n

    These 20 prompts cover the recurring writing and documentation tasks that surround engineering work \u2014 the ones that take time without requiring the engineering judgment that is actually your competitive advantage. Claude handles the structure; you supply the context and the technical calls.<\/p>\n\n\n\n

    The best way to use this guide is not to work through it sequentially, but to bookmark it and come back to the relevant section when the task arises. The prompts will save you time most consistently when you use them as starting points for an ongoing conversation rather than one-shot generators \u2014 iterate, push back, and ask Claude to refine until the output is exactly what you need.<\/p>\n\n\n\n

    When Claude Helps You Think \u2014 SimuTecra<\/a> Handles the Execution<\/strong><\/p>\n\n\n\n

    Claude helps you think through problems, structure requirements, and make better decisions. SimuTecra’s engineering team handles the CAD drafting, 3D modeling, and structural analysis that turns those decisions into production-ready deliverables. Use the prompts in this guide to develop your brief \u2014 then send it to us.Tell us what you are building and we will take it from there.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

    Engineers are not short of things to do. Documentation, drawing reviews, specification writing, supplier communication, tolerance analysis, DFM checks \u2014 the work that surrounds the actual engineering is substantial, and most of it follows repeatable patterns. Claude prompts for engineers handles repeatable patterns well. This is a working reference guide: 20 prompts across five categories, […]<\/p>\n","protected":false},"author":1,"featured_media":45,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-44","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"_links":{"self":[{"href":"https:\/\/simutecra.com\/blog\/wp-json\/wp\/v2\/posts\/44","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/simutecra.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/simutecra.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/simutecra.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/simutecra.com\/blog\/wp-json\/wp\/v2\/comments?post=44"}],"version-history":[{"count":5,"href":"https:\/\/simutecra.com\/blog\/wp-json\/wp\/v2\/posts\/44\/revisions"}],"predecessor-version":[{"id":52,"href":"https:\/\/simutecra.com\/blog\/wp-json\/wp\/v2\/posts\/44\/revisions\/52"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/simutecra.com\/blog\/wp-json\/wp\/v2\/media\/45"}],"wp:attachment":[{"href":"https:\/\/simutecra.com\/blog\/wp-json\/wp\/v2\/media?parent=44"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/simutecra.com\/blog\/wp-json\/wp\/v2\/categories?post=44"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/simutecra.com\/blog\/wp-json\/wp\/v2\/tags?post=44"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}