AI导哈

文档办公

organize

ghaida/intent

Structure information so people can find what they need, understand where they are, and navigate confidently. Covers navigation pattern design, taxonomy, labeling systems, search and browse strategy, wayfinding, and IA research methods. Trigger when designing navigation structures, categorization schemes, site maps, taxonomies, labeling systems, search experiences, or asking "how should we organize this?" Also trigger for card sorting, tree testing, information findability problems, or when users report they can't find things. Use this skill any time the structural organization of information is the problem — not the flow through it, not the words in it, not the visual presentation of it.

  • 2863 次安装
  • 229 星标
  • 收录于

安装命令

npx skills add https://github.com/ghaida/intent --skill organize

SKILL.md

Organize

Overview

Information architecture is the structural design of shared information environments. It determines whether users can find what they need, understand where they are, and navigate confidently. Good IA is invisible — users just "get it." Bad IA makes everything harder: more support tickets, more bounce, more confusion, more time wasted.

IA is not navigation design (that's one output of IA). It's not content strategy (that's what fills the structure). It's not visual design (that's how the structure looks). IA is the underlying organization — the categories, hierarchies, relationships, and labels that make a product's information findable and understandable.

Trigger this skill when users ask about:

  • Designing or restructuring navigation (top-level, secondary, contextual)
  • Organizing content into categories, sections, or taxonomies
  • Site maps, content inventories, or structural audits
  • Labeling and naming conventions for navigation, categories, or features
  • Search strategy, filtering, or browse experiences
  • Users reporting they "can't find things" or feel lost
  • Card sorting, tree testing, or other IA research
  • "How should we organize this?" or "Where should this live?"
  • Merging or restructuring product areas after growth or acquisition

相关 Skills

storytellingghaida/intentDiscipline for giving design work narrative structure that makes people care. Provides four canonical patterns — protagonist-arc, choreography, situation/complication/resolution, what-is/what-could-be — each with a goal, shape, and named pathology. Use when design work needs narrative structure, when stakeholders need to see the user's experience as a story, when presenting design rationale to non-design audiences, or when a journey, blueprint, brief, or deck feels lifeless. Trigger phrases: "what's the story here?", "tell the story", "story mode", "narrative mode". Refuses to smooth user data into clean arcs, manufacture strategic tension, substitute emotional appeal for evidence, assume conflict arcs are universal, or engineer stakeholder assent by shortcut.设计与多媒体3193journeyghaida/intentDesign any user-facing experience end-to-end: task flows, multi-step workflows, navigation structures, onboarding, settings, search, content creation, collaboration, signup, checkout, dashboards, notifications, error recovery, and more. Handles cross-platform adaptation (mobile/web/TV/embedded), device-aware design, accessibility, interaction specifications, and multi-channel journey mapping. Trigger when designing user flows of any kind, mapping screen sequences, optimizing task completion, specifying interactions, designing navigation, or asking "how should the user experience X?" Use this skill broadly — any time someone is working through how a user moves through a product experience, this skill applies.设计与多媒体2877intentghaida/intentThe entry point for Intent, a UX and design strategy system. Sets project context, routes to specialized skills, and loads foundational UX knowledge. Activate when starting any UX or product design work, setting project context, routing to other skills, evaluating an existing product's UX, or when the user asks about design intent, user experience strategy, ethical design, dark patterns, or design systems thinking.设计与多媒体2862evaluateghaida/intentStructured UX evaluation that ranks specific issues by severity and states the change that fixes each. Part of the Intent design strategy system. Runs heuristic evaluations, cognitive walkthroughs, anti-pattern detection, and task success analysis. Rates every finding critical, major, minor or cosmetic, names the heuristic it violates, and states the fix in design terms; which skill makes the fix is said in the reply. Trigger on: UX review, design audit, heuristic evaluation, usability assessment, "review this design", "what's wrong with this", "evaluate the experience", "is this accessible", "check for dark patterns", "how good is this UX", "rate this design", "find the problems", or any request to systematically assess the quality of a user experience. This is the diagnostic entry point of the Intent system — the UX doctor that diagnoses issues and refers to specialists.设计与多媒体2836articulateghaida/intentDesign the words in a product — labels, instructions, errors, confirmations, empty states, onboarding copy, tooltips, voice and tone frameworks, and content models. UX writing and content strategy as a deep discipline. Trigger when writing or reviewing UI copy, error messages, empty states, onboarding text, CTAs, tooltips, confirmation dialogs, or any user-facing text in a product. Also trigger for voice and tone frameworks, content models, microcopy patterns, inclusive language guidance, or asking "what should this say?" and "how should we sound?" Use this skill any time the words in an interface are the problem — not the flow they live in, not the structure they navigate, not the visual presentation.营销与写作2813fortifyghaida/intentHarden designs for real-world use by systematically identifying and designing for every condition outside the happy path. Part of the Intent design strategy system. Covers state inventories, error recovery, empty states, loading patterns, first-run experiences, stress testing, internationalization readiness, and latency handling. Trigger on: edge cases, error states, empty states, loading states, first-run experience, onboarding, offline mode, "what happens when", "what if the user", "stress test this", "what could go wrong", "harden this design", "edge case review", "what are the failure modes", zero states, timeout handling, or any question about how a design behaves outside ideal conditions.设计与多媒体2809