13건 · 관련도순
Define what content a product needs, how it is structured, and who owns it. Use when content itself is the problem. For the words in the interface use `ux-writing` (designer-toolkit); for structural hierarchy use `information-architecture`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design content structure, hierarchy, labelling, and the navigation model. Use when organising what exists. For the UI that exposes it use `navigation-patterns` (interaction-design); for user-generated grouping evidence use `card-sort-analysis` (design-research).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Select and design a navigation pattern — tabs, drawer, hierarchy, or hub — matched to product structure and user tasks. Use when choosing how users move between sections. For the underlying content structure, use `information-architecture` (ux-strategy).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design the structure of a website or product including sitemap, navigation, URL structure, content types, taxonomy, and labeling. Use this skill whenever the user asks to plan a sitemap, design navigation, structure URLs, define content types, build taxonomies, design site search, or organize content at the system level. Triggers on sitemap, site structure, navigation, IA, information architecture, URL structure, content types, taxonomy, categorization, breadcrumbs, hub pages, faceted navigation, site search, labeling. Also triggers when content is being created without a structural plan, or when an existing site's structure is being audited or restructured.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Information architecture, URL hierarchy, internal linking strategy, navigation design, and silo structure for websites. Covers architectural audits, new site planning, crawl equity optimization, and topic cluster mapping.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit and repair an internal knowledge base — staleness, ownership gaps, orphans, duplication, and findability. Use when the wiki is untrusted, docs are out of date, nobody owns pages, or search returns the wrong answer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design the structure, hierarchy, and navigation model for a product's content and features.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan pages, navigation and content sequence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Naming, navigation, a UI that mirrors the data model, confirms for irreversible changes. Use when structuring a large application or naming its entities.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
设计产品整体信息架构和导航结构时使用。适用于多页面产品、复杂功能模块、内容组织。优先使用卡片分类 + 树状结构 + 导航模式选择。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convert a semantic core into crawlable SEO and LLM-friendly information architecture. Use this skill when the user asks for URL structure, page taxonomy, canonical rules, hreflang groups, page roles, pillar/topic/news/article/blog/project separation, multilingual route strategy, or a durable content model such as one short brief plus one longform article. It prevents duplicate public content bodies and hands link-graph work to internal-link-graph-architect.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design UI as information architecture + interaction + visual tone, then translate into implementable specs. Apply when discussing screen design, component design, design systems, or visual hierarchy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.