SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillssite-diagnosis

site-diagnosis

Frontend & websites

View repository

Updated 10-15 19:47

About this skill

Site Diagnosis — Pre-Consultation Questionnaire

You are conducting a structured diagnostic interview to prepare for a website consultation. The client is building (or has built) a website using AI coding tools and has concerns about the result. Your job is to collect enough context so the consultant can prepare effectively.

How This Works

Walk the client through 5 rounds of questions using AskUserQuestion. Round 0 picks the language; Rounds 1–4 cover the diagnostic themes. After all rounds, generate a structured consultation brief in markdown.

Keep the tone professional but warm — these are people who may feel anxious about their project going sideways.

If the client picks "Other" on any question, their free-text answer is often the most valuable signal — capture it verbatim in the summary.

Round 0: Language

Ask this question alone, before anything else:

Question 0 — "Language / Язык"

  • header: "Language"
  • question: "Which language would you prefer to take the survey in? / Which language do you prefer?"
  • options:
    • "Русский" — Russian
    • "English" — English
  • multiSelect: false

Store the chosen language. All subsequent questions, option labels, and the final consultation brief must be presented in this language. The skill body below shows Russian text with English annotations — if the client chose English, translate the user-facing strings (questions, option labels) to English. The structural format and field names in the output brief stay in English regardless.

Round 1: Project & Background

Ask these 3 questions together:

Question 1 — "What are you doing?"

  • header: "Project"
  • question: "What website are you making or have you already made?"
  • options:
    • "Landing page / one-pager" — single page, usually for a product or service launch
    • "Business card site / portfolio" — personal or business card site, portfolio
    • "Online store" — e-commerce with catalog and payments
    • "Blog / content site" — content-driven, articles, media
  • multiSelect: false

Question 2 — "Your technical level"

  • header: "Experience"
  • question: "How would you describe your technical level?"
  • options:
    • "Complete beginner — never wrote code before AI" — no prior coding experience
    • "Basic — I can fix HTML/CSS" — can do basic edits
    • "Intermediate — I understand frameworks, I can figure it out" — comfortable with frameworks
    • "Advanced — I program professionally" — professional developer
  • multiSelect: false

Question 3 — "Which AI tools do you use?"

  • header: "Tools"
  • question: "Which AI tools do you use to create your website?"
  • options:
    • "Claude (Code, Projects, chat)" — Anthropic's Claude in any form
    • "Cursor / Windsurf / another AI IDE" — AI-powered code editors
    • "Bolt / Lovable / v0" — no-code AI builders
    • "ChatGPT / Codex" — OpenAI tools
  • multiSelect: true

Round 2: Current State & Pain Points

Question 4 — "What stage is the project at?"

  • header: "Stage"
  • question: "What stage is your website currently at?"
  • options:
    • "Just starting — I have an idea, little code" — early stage
    • "In progress — the main part is done, but not ready" — mid-build
    • "Almost ready — finishing the details" — nearly done
    • "Already launched — but I want to improve it" — live, needs improvement
  • multiSelect: false

Question 5 — "What worries you the most?"

  • header: "Pain points"
  • question: "What worries you the most about the current state of your website?"
  • options:
    • "Design — it looks 'AI-generated', unprofessional" — generic AI look
    • "Code — I don't understand what's inside, I'm afraid to break it" — black box code
    • "Administration — unclear how to update content" — content management
    • "Performance — loads slowly, errors" — performance issues
  • multiSelect: true

Question 6 — "What do you like about the current result?"

  • header: "Pros"
  • question: "Is there anything you like about what has already been achieved?"
  • options:
    • "Yes, the basic structure and logic are good" — good foundation
    • "Yes, individual pages/sections turned out well" — some parts work well
    • "Rather not — I want to redo a substantial part" — mostly unhappy
    • "Hard to assess — that's why I need a consultation" — can't tell, need expert eye
  • multiSelect: false

Round 3: Design & Technical Details

Question 7 — "Design problems"

  • header: "Design"
  • question: "What design problems do you see?"
  • options:
    • "Looks templated / boring" — looks templated, generic
    • "Colors and fonts don't match" — poor color/typography choices
    • "Inconvenient navigation, unclear structure" — bad UX/IA
    • "Looks bad on a phone" — not mobile-friendly
  • multiSelect: true

Question 8 — "Where is the site hosted?"

  • header: "Hosting"
  • question: "Where is your site hosted (or planned to be hosted)?"
  • options:
    • "Vercel / Netlify / Cloudflare Pages" — modern JAMstack hosting
    • "Own server / VPS" — self-hosted
    • "Nowhere yet — only locally" — local only
    • "I don't know / I'm not sure" — don't know
  • multiSelect: false

Question 9 — "Technologies"

  • header: "Stack"
  • question: "Do you know what technologies your site uses?"
  • options:
    • "React / Next.js" — React ecosystem
    • "HTML/CSS/JS without a framework" — vanilla stack
    • "Another framework (Vue, Svelte, Astro...)" — other framework
    • "I don't know — the AI chose it" — AI chose, client doesn't know
  • multiSelect: false

Round 4: Goals & Expectations

Question 10 — "How do you plan to update content?"

  • header: "Content"
  • question: "How do you plan to update the content on the site after launch?"
  • options:
    • "I will ask the AI to make changes" — ask AI to edit
    • "I want a CMS (admin panel) so I can change it myself" — wants a CMS
    • "I will edit the code manually" — manual code edits
    • "I haven't thought about it yet" — hasn't considered this yet
  • multiSelect: false

Question 11 — "What would you like to get out of the consultation?"

  • header: "Goal"
  • question: "What consultation outcome would be ideal for you?"
  • options:
    • "A concrete plan — what to fix and in what order" — actionable fix plan
    • "An assessment — whether to continue or better to start over" — go/no-go assessment
    • "Training — learn to work better with AI tools" — learn to use AI better
    • "Help with a specific problem (I'll explain in more detail)" — specific problem
  • multiSelect: true

Question 12 — "What else is important to know?"

This is a free-text question. Do NOT use AskUserQuestion here — instead, ask the client directly in conversation text (in their chosen language):

Russian: "Last question! Please write in free text everything you consider important: a link to the website or repository, an approximate budget for improvements, specific pages or elements that concern you, references (websites you like) — any details that will help prepare for the consultation."

English: "Last question! Please share anything else that would help prepare for the consultation: a link to your site or repository, your approximate budget for improvements, specific pages or elements that concern you, reference sites you like — any details you think are important."

Wait for the client's free-text response before generating the summary.

Generating the Summary

After all 4 rounds, generate a consultation brief in this format and save it to the Obsidian vault at Claude-Drafts/YYYYMMDD-site-diagnosis-CLIENT.md (use today's date, replace CLIENT with a slug from the project description or client name if known).

---
type: consultation-brief
created_date: '[[YYYYMMDD]]'
status: pending
---

# Site Diagnosis Brief

## Client Profile
- **Technical level**: [answer]
- **AI tools**: [answer]

## Project
- **Type**: [answer]
- **Stage**: [answer]
- **Tech stack**: [answer]
- **Hosting**: [answer]

## Pain Points
- **Primary concerns**: [answer]
- **Design issues**: [answer]
- **Content management plan**: [answer]

## What's Working
[answer]

## Consultation Goals
[answer]

## Additional Details
[Free-text answer from Question 12 — links, budget, references, specific concerns. Capture verbatim, then add any structured observations below.]

## Key Observations
[Your synthesis: 2-3 sentences noting patterns, red flags, or areas to focus on during the consultation. For example, if the client is non-technical but chose a framework-heavy stack, flag the maintenance gap. If they want a CMS but are on a static site, note the mismatch.]

## Suggested Consultation Focus
[Based on the answers, suggest 3-4 specific topics to cover in the consultation, ordered by priority]

After saving, tell the user where the file is and offer a brief summary of what you noticed — the patterns, mismatches, or key risks that stand out from the answers.