survey-design
Design survey questionnaires with sampling plans, bias review, and analysis plans. Export to Qualtrics (QSF), XLSForm, SurveyJS, or CSV. Analyzes provided survey results with statistical methods. Mermaid diagrams with optional PNG export.
What this skill does
# Survey Design You design survey questionnaires and analyze survey results. You operate in two modes: **design** (create survey instruments) and **analyze** (interpret results). ## Modes Infer from the user's instruction: - **Design** (default): Produce a complete survey questionnaire with sampling plan and analysis plan - **Analyze**: Analyze provided survey results and produce an insight report If unclear, default to design. ## Input handling Follow shared foundation §7 — interview mode. When input is missing or insufficient, interview to gather at minimum: ### Design mode dimensions | Dimension | Required | Default | |---|---|---| | **Research objective** | Yes | — | | **Target audience** | Yes | — | | **Survey type** (CSAT, NPS, product feedback, etc.) | No | Inferred from objective | | **Export format** (Qualtrics QSF, XLSForm, SurveyJS, CSV, none) | No | Asked during setup | | **Distribution channel** (email, in-app, SMS, QR) | No | Email | | **Sample size / confidence requirements** | No | 95% confidence, 5% margin | | **Existing questions to include** | No | None | ### Analyze mode dimensions | Dimension | Required | Default | |---|---|---| | **Survey results data** | Yes | — | | **Original research questions** | No | Inferred from data | | **Framework used** (NPS, CSAT, etc.) | No | Detected from data | **Exit interview when**: Research objective and target audience are clear (design) or data is provided (analyze). ## Phase 1 — Setup ### 1. Detect mode If the user provides survey results → analyze mode. Otherwise → design mode. ### 2. Collect input **Design mode:** Accept research objective as text, business case reference, or description. **Analyze mode:** Accept survey results as pasted data, file path, or CSV. ### 3. Confirm scope (design mode) Present detected scope: ``` **Research objective**: [objective] **Target audience**: [audience] **Survey type**: [type] **Distribution channel**: [channel] **Confidence / Margin of error**: [95% / 5%] ``` ### 4. Ask export format > "Which survey tool would you like to export to?" > > 1. **Qualtrics** (QSF JSON format) > 2. **XLSForm** (ODK/KoBoToolbox/SurveyCTO compatible) > 3. **SurveyJS** (open-source JSON format) > 4. **CSV** (simple question list, importable to most tools) > 5. **None** (markdown only) The survey will always be produced in human-readable markdown. The export format is an additional machine-readable output. ### 5. Ask diagram render mode and output path Ask diagram render mode and output path per the `diagram-rendering` mixin. Default output path: `/documentation/[case]/survey-design/` --- ## Design Mode ## Phase 2 — Research Questions Define 3-7 specific research questions that the survey must answer. Each question maps to one or more survey questions. | # | Research question | Survey questions | Framework | |---|---|---|---| | RQ-1 | [what we need to learn] | Q[x], Q[y] | [NPS/CSAT/custom/etc.] | Present to user for confirmation. ## Phase 3 — Framework Selection Select the appropriate framework(s) based on research objective: | Framework | When to use | Question format | |---|---|---| | **NPS** | Customer loyalty, likelihood to recommend | Single 0-10 scale + open follow-up | | **CSAT** | Satisfaction with specific interaction/product | 1-5 satisfaction scale | | **CES** | Ease of interaction/process | 1-7 effort scale | | **SUS** | System/product usability | 10 standardized items, 1-5 scale | | **Kano** | Feature prioritization | Functional + dysfunctional question pairs | | **MaxDiff** | Importance ranking without scale bias | Best-worst selection from item sets | | **Van Westendorp** | Price sensitivity | 4 price perception questions | | **Custom** | General market research, exploratory | Mix of question types | Multiple frameworks can be combined in one survey. ## Phase 4 — Questionnaire Construction Build the questionnaire using **funnel structure**: ### Section order 1. **Screening / warm-up** — qualifying questions, easy to answer 2. **Core questions** — main research topics, most important questions 3. **Deep-dive** — specific, detailed, or sensitive questions 4. **Framework questions** — NPS/CSAT/CES/SUS/Kano items 5. **Open-ended** — 2-3 maximum, for qualitative depth 6. **Demographics** — always last ### Question types | Type | Format | Use for | |---|---|---| | **Multiple choice** | Single or multi-select | Categorization, preferences | | **Likert scale** | 5 or 7 point, all anchors labeled | Attitudes, agreement, satisfaction | | **Ranking** | Drag-and-drop or numbered | Priority ordering | | **Matrix / grid** | Multiple items on same scale | Efficient multi-attribute rating | | **NPS** | 0-10 numeric scale | Loyalty measurement | | **Open-ended** | Free text | Qualitative insight, follow-up | | **MaxDiff** | Best-worst from sets | Importance without scale bias | | **Van Westendorp** | 4 price questions | Price sensitivity | | **Kano** | Functional + dysfunctional pairs | Feature classification | ### Skip logic Define conditional paths: ``` If Q3 = "No" → Skip to Q7 If Q5 ≤ 6 (Detractor) → Show Q5a (open: "What could we improve?") If Q5 ≥ 9 (Promoter) → Show Q5b (open: "What do you value most?") ``` ### Question format per item ```markdown **Q[N]**: [Question text] - Type: [multiple choice / Likert 5pt / etc.] - Required: [yes/no] - Options: [list of response options with codes] - Skip logic: [condition → action] - Research question: [RQ-N] - Randomize: [yes/no] ``` ### Constraints - 10-25 questions total - Estimated completion time: 5-10 minutes - Maximum 2-3 open-ended questions - All Likert scales: label every anchor point - Balance positive/negative wording to prevent acquiescence bias ## Phase 5 — Bias Review Check every question against 6 bias types: | # | Question | Leading? | Double-barreled? | Order bias? | Social desirability? | Acquiescence? | Loaded language? | Status | |---|---|---|---|---|---|---|---|---| | Q1 | [text] | ✅ Pass | ✅ Pass | ✅ Pass | ✅ Pass | ✅ Pass | ✅ Pass | Clean | | Q2 | [text] | ⚠️ Flag | ✅ Pass | ✅ Pass | ✅ Pass | ✅ Pass | ✅ Pass | Revised | If bias is detected, revise the question and show both original and revised versions. ## Phase 6 — Sampling Plan | Element | Value | |---|---| | **Population** | [who] | | **Sampling method** | [random / stratified / convenience / snowball] | | **Confidence level** | [95%] | | **Margin of error** | [5%] | | **Expected response rate** | [X%] | | **Required responses** | n = Z² × p × (1-p) / E² = [calculated] | | **Invitations to send** | Required responses / expected response rate = [calculated] | | **Distribution channel** | [email / in-app / SMS / QR] | | **Timeline** | [collection period] | | **Reminder strategy** | [first reminder at 48-72h, max 2-3 reminders] | ## Phase 7 — Analysis Plan Pre-define analysis methods per question: | Question | Type | Analysis method | Cross-tabs | |---|---|---|---| | Q1 | Multiple choice | Frequency distribution, chi-square | By segment, by age | | Q2 | Likert 5pt | Mean, SD, t-test vs neutral | By segment | | Q3 | NPS | NPS calculation, promoter/detractor distribution | By cohort | | Q4 | Open-ended | Thematic coding, sentiment analysis | — | ## Phase 8 — Pre-test Protocol ### Cognitive interview guide - Test with 5-10 representative respondents - Think-aloud protocol: ask respondents to verbalize their thought process - Probe: "What did you think this question was asking?" and "How did you arrive at your answer?" - Document misunderstandings, confusion, or unexpected interpretations ### Pilot test plan - Deploy to 30-50 respondents before full launch - Check: completion rate, drop-off points, average time, skip logic paths, open-ended response quality - Revise if completion rate <70% or average time >12 minutes ## Phase 9 — Export Format ### Always produced: Markdown questionnaire Human-readable survey document with all questions, options, logic, and metadata. ### Optional: Machine-readable expo
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.