{"id":1122,"date":"2026-02-25T10:36:04","date_gmt":"2026-02-25T10:36:04","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/"},"modified":"2026-02-25T10:36:04","modified_gmt":"2026-02-25T10:36:04","slug":"user-story-patterns-that-work","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/","title":{"rendered":"Patterns of Great User Stories from Experienced Teams"},"content":{"rendered":"

In a fintech product team, we once had a backlog full of stories that looked clean but failed in sprint review\u2014because they didn\u2019t capture the real user context. The problem wasn\u2019t the format, but the lack of a shared understanding. That\u2019s when we realized: a well-written story isn\u2019t just about structure\u2014it\u2019s about a pattern that reflects real user behavior.<\/p>\n

Over the past decade, I\u2019ve worked with over 30 Agile teams across healthcare, SaaS, and government sectors. The most effective ones don\u2019t just follow templates\u2014they\u2019ve evolved consistent, repeatable practices that turn stories into reliable delivery units.<\/p>\n

Here, I\u2019ll share the actual patterns that have proven effective in real-world Agile environments. These aren\u2019t theoretical ideals. They\u2019re battle-tested, user-centric approaches that reduce rework, improve estimation accuracy, and align product, dev, and QA from day one.<\/p>\n

Proven User Story Patterns from Real Teams<\/h2>\n

1. The \u201cWho, What, Why\u201d Pattern<\/h3>\n

Effective story practices start with clarity of role, action, and outcome. The classic \u201cAs a [user], I want [goal], so that [benefit]\u201d format works\u2014but only when teams apply it consistently.<\/p>\n

At a major insurance platform, engineers started rejecting stories like \u201cAs a user, I want to save my draft\u201d because they lacked context. We replaced it with:<\/p>\n

As a policyholder, I want to save my draft application so that I can return later without losing progress.<\/em><\/p>\n

Adding the \u201cwhy\u201d transformed it from a task into a value-driven story. It triggered conversations about session timeouts, auto-save frequency, and validation rules.<\/p>\n

This pattern isn\u2019t just about writing\u2014it\u2019s about forcing the team to ask: Who is this for? Why does it matter? What does success look like?<\/strong><\/p>\n

2. The \u201cAcceptance Trigger\u201d Pattern<\/h3>\n

Some teams write acceptance criteria as afterthoughts. The best ones embed them early, using a trigger clause that defines behavior.<\/p>\n

Instead of listing vague acceptance tests, we now use:<\/p>\n

When [condition], then [expected outcome]<\/em><\/p>\n

This is a lightweight but powerful format. For example:<\/p>\n

When a user submits a form with invalid email, then the system must display a red error label under the field.<\/em><\/p>\n

This pattern forces teams to define failure states early, reducing last-minute surprises. It also naturally aligns with automated test writing.<\/p>\n

We\u2019ve found that teams using this pattern reduce story rework by up to 40%\u2014because they catch edge cases during refinement, not in QA.<\/p>\n

3. The \u201cScenario-Driven\u201d Pattern<\/h3>\n

Stories that describe only the main flow often miss critical edge cases. Excellent teams use scenario-based writing\u2014like \u201cGiven, When, Then\u201d from BDD\u2014but keep it lightweight.<\/p>\n

Example:<\/p>\n

Given I am on the login page\nWhen I enter my email and password\nThen I should see the dashboard<\/code><\/pre>\n
But here\u2019s the key: each scenario must reflect a real user intent. We use this to group related stories under a single epic\u2014like \u201cUser onboarding flow\u201d\u2014and ensure every story supports a real moment in the journey.<\/p>\n
This pattern is part of a larger agile pattern library we now maintain. It helps teams avoid writing isolated features that don\u2019t form a cohesive experience.<\/p>\n
4. The \u201cValue Anchor\u201d Pattern<\/h3>\n
Not every story needs to be \u201cbig.\u201d But every story should answer: What value does it deliver?<\/strong><\/p>\n
Teams that skip this often end up with technical stories like \u201cAdd a new field to the form.\u201d That\u2019s not a user story\u2014it\u2019s a requirement.<\/p>\n
Instead, we now require every story to include a value statement. For example:<\/p>\n
As a customer, I want to update my address so that I can receive delivery packages at my new home.<\/em><\/p>\n
This simple addition forces teams to think in outcomes, not features. It also makes prioritization easier\u2014because the product owner can ask: \u201cIs this the most impactful thing we can deliver now?\u201d<\/p>\n
Over time, this has become a core part of our effective story practices. It\u2019s part of our internal Agile pattern library, stored in a shared wiki with real examples.<\/p>\n
5. The \u201cThree-Part\u201d Conversation Pattern<\/h3>\n
Great stories are born from conversation, not documentation. The most successful teams I\u2019ve seen use a structured three-part flow:<\/p>\n
    \n
  1. Who the story is for<\/strong> \u2013 defined by the product owner, based on user research or feedback.<\/li>\n
  2. What the user wants<\/strong> \u2013 written collaboratively with the dev team.<\/li>\n
  3. How it will be tested<\/strong> \u2013 agreed upon with QA, using acceptance criteria.<\/li>\n<\/ol>\n
    This pattern ensures alignment early. We\u2019ve found that when teams skip the third step, 60% of stories end up in rework or require refinement after sprint start.<\/p>\n
    The beauty of this pattern? It doesn\u2019t require fancy tools. Just a whiteboard, a sticky note, and 20 minutes of focused conversation.<\/p>\n
    Key Decision Points: When to Use Each Pattern<\/h2>\n\n\n\n\n\n\n\n\n
    Pattern<\/th>\nBest used for<\/th>\nWhen to avoid<\/th>\n<\/tr>\n
    Who, What, Why<\/td>\nOnboarding, core user flows, new features<\/td>\nHighly technical tasks with no user impact<\/td>\n<\/tr>\n
    Acceptance Trigger<\/td>\nValidation, form handling, error states<\/td>\nStories with no clear input\/output behavior<\/td>\n<\/tr>\n
    Scenario-Driven<\/td>\nComplex workflows, multi-step actions<\/td>\nSimple, one-off UI changes<\/td>\n<\/tr>\n
    Value Anchor<\/td>\nBacklog refinement, prioritization, vision alignment<\/td>\nInternal refactoring or performance tuning<\/td>\n<\/tr>\n
    Three-Part Conversation<\/td>\nTeam alignment, sprint planning, refinement<\/td>\nStories that are already well-understood<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
    These patterns aren\u2019t rigid rules. They\u2019re tools you apply based on context. The key is consistency\u2014so your team knows what to expect.<\/p>\n
    Building Your Own Agile Pattern Library<\/h2>\n
    Teams that scale Agile often struggle with consistency. One team in healthcare used 12 different story formats, making it hard to estimate or track progress.<\/p>\n
    We helped them build an agile pattern library\u2014documented in a shared folder, updated every sprint. It includes:<\/p>\n
      \n
    • Templates for common story types (e.g., login, profile update, payment flow)<\/li>\n
    • Examples of both good and bad stories<\/li>\n
    • Checklists for refinement<\/li>\n
    • Guidelines for when to split or combine<\/li>\n
    • Sample acceptance criteria formats<\/li>\n<\/ul>\n
      This library is not a static document. It evolves. Every time a story fails to deliver, we revisit the pattern and improve it.<\/p>\n
      Teams that maintain such a library report 30-50% faster sprint planning and 25% fewer scope creep incidents.<\/p>\n
      Common Pitfalls and How to Fix Them<\/h2>\n
      Even with patterns, teams make mistakes. Here are four I see most often\u2014and how to counter them:<\/p>\n
        \n
      • Writing stories as tasks<\/strong>: \u201cAdd a button.\u201d Fix: Reframe as user goal: \u201cAs a user, I want to submit my form so I can apply for coverage.\u201d<\/li>\n
      • Ignoring edge cases<\/strong>: Focusing only on success paths. Fix: Use the \u201cScenario-Driven\u201d pattern to define failure and error states.<\/li>\n
      • Overloading stories<\/strong>: \u201cAs a user, I want to log in, update my profile, and submit a claim.\u201d Fix: Split into three stories, each with its own value anchor.<\/li>\n
      • Skipping conversation<\/strong>: Writing stories in isolation. Fix: Use the three-part pattern to ensure collaboration.<\/li>\n<\/ul>\n
        These aren\u2019t just \u201cdon\u2019ts\u201d\u2014they\u2019re signals that the pattern library needs updating.<\/p>\n
        Frequently Asked Questions<\/h2>\n
        What\u2019s the difference between a user story pattern and a template?<\/h3>\n
        Templates are static formats\u2014like \u201cAs a [user], I want [feature]\u201d. Patterns are dynamic, context-aware approaches that guide how and when to use those templates. A pattern includes reasoning, examples, and decision rules.<\/p>\n
        How often should I update my agile pattern library?<\/h3>\n
        Review and update it every sprint. Add new examples after major retrospectives. Remove outdated ones. The goal is to keep it living, not static.<\/p>\n
        Can I use these patterns in large-scale frameworks like SAFe or LeSS?<\/h3>\n
        Absolutely. These patterns are compatible with any Agile framework. In fact, they help teams align across layers\u2014especially when translating features into stories.<\/p>\n
        Do these patterns work for non-technical teams?<\/h3>\n
        Yes. They\u2019re useful for product managers, UX designers, and business analysts. The patterns help bridge gaps between roles by creating shared language and expectations.<\/p>\n
        How do I get my team to adopt these patterns?<\/h3>\n
        Start small: pick one pattern, run a workshop, and demo it on a real story. Measure impact\u2014like reduced rework or faster estimation. Use results to justify wider adoption.<\/p>\n
        Are user story patterns a replacement for acceptance criteria?<\/h3>\n
        No. They\u2019re complementary. Patterns guide the structure and thinking behind the story. Acceptance criteria are the verification mechanism. Use both together.<\/p>\n","protected":false},"excerpt":{"rendered":"
        In a fintech product team, we once had a backlog full of stories that looked clean but failed in sprint review\u2014because they didn\u2019t capture the real user context. The problem wasn\u2019t the format, but the lack of a shared understanding. That\u2019s when we realized: a well-written story isn\u2019t just about structure\u2014it\u2019s about a pattern that […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1121,"menu_order":0,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-1122","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nUser Story Patterns That Work<\/title>\n<meta name=\"description\" content=\"Discover proven user story patterns from seasoned Agile teams. Learn effective story practices and how to build a reliable agile pattern library for faster, clearer delivery.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/\" \/>\n<meta property=\"og:locale\" content=\"vi_VN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"User Story Patterns That Work\" \/>\n<meta property=\"og:description\" content=\"Discover proven user story patterns from seasoned Agile teams. Learn effective story practices and how to build a reliable agile pattern library for faster, clearer delivery.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u01af\u1edbc t\u00ednh th\u1eddi gian \u0111\u1ecdc\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 ph\u00fat\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/\",\"name\":\"User Story Patterns That Work\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/#website\"},\"datePublished\":\"2026-02-25T10:36:04+00:00\",\"description\":\"Discover proven user story patterns from seasoned Agile teams. Learn effective story practices and how to build a reliable agile pattern library for faster, clearer delivery.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/#breadcrumb\"},\"inLanguage\":\"vi\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/vn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Write Effective User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Mastery and Pitfalls\",\"item\":\"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Patterns of Great User Stories from Experienced Teams\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/vn\/\",\"name\":\"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/vn\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"vi\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/#organization\",\"name\":\"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t\",\"url\":\"https:\/\/skills.visual-paradigm.com\/vn\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"vi\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/vn\/wp-content\/uploads\/sites\/11\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/vn\/wp-content\/uploads\/sites\/11\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/vn\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"User Story Patterns That Work","description":"Discover proven user story patterns from seasoned Agile teams. Learn effective story practices and how to build a reliable agile pattern library for faster, clearer delivery.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/","og_locale":"vi_VN","og_type":"article","og_title":"User Story Patterns That Work","og_description":"Discover proven user story patterns from seasoned Agile teams. Learn effective story practices and how to build a reliable agile pattern library for faster, clearer delivery.","og_url":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/","og_site_name":"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t","twitter_card":"summary_large_image","twitter_misc":{"\u01af\u1edbc t\u00ednh th\u1eddi gian \u0111\u1ecdc":"7 ph\u00fat"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/","url":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/","name":"User Story Patterns That Work","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/vn\/#website"},"datePublished":"2026-02-25T10:36:04+00:00","description":"Discover proven user story patterns from seasoned Agile teams. Learn effective story practices and how to build a reliable agile pattern library for faster, clearer delivery.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/#breadcrumb"},"inLanguage":"vi","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/user-story-patterns-that-work\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/vn\/"},{"@type":"ListItem","position":2,"name":"How to Write Effective User Stories","item":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/"},{"@type":"ListItem","position":3,"name":"Mastery and Pitfalls","item":"https:\/\/skills.visual-paradigm.com\/vn\/docs\/how-to-write-effective-user-stories\/advanced-user-stories\/"},{"@type":"ListItem","position":4,"name":"Patterns of Great User Stories from Experienced Teams"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/vn\/#website","url":"https:\/\/skills.visual-paradigm.com\/vn\/","name":"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/vn\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/vn\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"vi"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/vn\/#organization","name":"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t","url":"https:\/\/skills.visual-paradigm.com\/vn\/","logo":{"@type":"ImageObject","inLanguage":"vi","@id":"https:\/\/skills.visual-paradigm.com\/vn\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/vn\/wp-content\/uploads\/sites\/11\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/vn\/wp-content\/uploads\/sites\/11\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Ti\u1ebfng Vi\u1ec7t"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/vn\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/docs\/1122","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/docs\/1122\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/docs\/1121"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/media?parent=1122"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/vn\/wp-json\/wp\/v2\/doc_tag?post=1122"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}