More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Brief Me — Pre-Build Requirements Interview

    1

    Interviews you about a site or app's business requirements — audience, value proposition, goal, tone — before any mockup or code gets written, and hands off the answers as a durable BRIEF.md file.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Brief Me — Pre-Build Requirements Interview

    Brief Me — Pre-Build Requirements Interview

    Example session with this skill installed

    I want to build a landing page for IRONCLAD STRENGTH, a boutique strength-training gym opening its second location in Austin, Texas — 3,200 sq ft, 8 private coaching bays, 12-person max class size, $189/month, targeting professionals aged 28-45 who tried commercial gyms and quit within 3 months. Interview me first so we get the requirements right before any design work starts.

    • Read your context and instructions
    • Compiled the brief me

    I'll run a short structured interview before we design anything — four rounds of questions, each with concrete options plus an open "Other" field, so most answers are quick confirmations rather than free-typing.

    Round 1 (site type / target / value proposition / goal): Landing page (single-page pitch) -> General consumers (B2C) -> Quality/trust (certified coach + written program, not an anonymous big-box gym) -> Free trial session booking.

    Round 2 (persona detail): 28-45, dual-income, mid-to-upper disposable income — gym dropouts, not gym novices.

    Round 3 (differentiation / device priority / brand assets — "scale" skipped automatically, nothing to enumerate on a single-page pitch): Design/UX differentiation -> Roughly even mobile/desktop split -> Logo and brand colors already exist (second location).

    Round 4 (notes): Avoid flashy effects — no "grind harder" clichés, no sweat-drenched hero shots, no countdown-timer urgency.

    Here's BRIEF.md, written to your project root:

    BRIEF

    Site Type

    A single-page landing page (LP) focused on one conversion goal: booking a free trial session.

    Target Audience

    General consumers (B2C) — working professionals aged 28-45.

    Persona Detail
    Dual-income professionals aged 28-45 with mid-to-upper disposable income. Have tried commercial/big-box gyms before and quit within 3 months — they're not gym novices, they're gym dropouts looking for something that actually sticks.

    Product / Value Proposition

    Quality and trust: accountability over anonymity. Every member gets a certified coach and a written program — not just a keycard swipe into an empty room. Positioned above budget gyms ($20-40/month) and below fully personal training ($400+/month), at $189/month for a boutique 3,200 sq ft facility with 8 private coaching bays and a 12-person class cap.

    Competitive Differentiation

    Design and UX. The gym's actual edge is coaching structure, but the landing page itself needs to look and feel categorically different from typical fitness marketing — premium and trustworthy rather than loud or intense.

    Device Priority

    Roughly even split between mobile and desktop — prospective members are expected to browse on mobile during commutes and revisit on desktop before booking.

    Existing Brand Assets

    Logo and brand colors already exist (this is the brand's second location). Treat them as a fixed constraint in the next build step's color/style question rather than a free choice.

    Goal (Conversion)

    Convert landing page visitors into a booked free trial session — not a generic contact form, not a membership signup without trying the space first.

    Notes

    Avoid loud, "grind harder" fitness clichés — no sweat-drenched hero shots, no aggressive red/yellow accent colors, no countdown-timer urgency tactics. The tone should read as calm, premium, and trustworthy, closer to a boutique wellness brand than a typical gym flyer.

    Next steps: BRIEF.md is saved. Hand it to whatever mockup-building or coding workflow you use next — many agentic build workflows pick up a BRIEF.md in the project root automatically, or you can just reference/paste it in as context.

    Here's BRIEF.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Ask an agent to "build me a landing page" and it quietly guesses the audience, the value proposition, and the goal from thin context — guesses you never actually confirmed, and that quality varies with however much you happened to type in the prompt. This skill surfaces those guesses as explicit questions up front, in one short structured interview, and hands off the answers as a durable file instead of a paragraph that gets lost in the conversation. Works the same way whether you're defining a marketing website, a web app screen, or a mobile/product UI — the very first question is simply "what kind of site or app is this."

    What it does

    • Asks about site/app type, target audience, and the core value proposition
    • Follows up with a persona-level question (age range, income level, occupation, life stage) — not just a broad B2C/B2B label
    • Asks about competitive differentiation, scale, device priority, and existing brand assets — whichever apply, skipping what clearly doesn't (e.g. no "scale" question for a single-page pitch)
    • Asks the conversion goal and any open-ended notes or constraints (tone, things to avoid, accessibility needs)
    • Writes everything to BRIEF.md in your project root, in whatever language you're using in the conversation

    How it works

    1. Four rounds of interview questions — four questions, then one, then up to four, then one — each with concrete options plus an open "Other" field
    2. This is a one-shot interview, not a back-and-forth grilling session
    3. The answers are synthesized into a structured BRIEF.md
    4. It stops there — it does not chain into any other skill automatically

    Tip: more detail in, sharper brief out

    You don't need to answer from a blank slate. Paste in a rough business description — even one unstructured paragraph — and the skill turns it into concrete multiple-choice options with a recommended pick for each question, so most of the interview becomes confirming inferences rather than typing from scratch. The more specifics you give it upfront (numbers, competitors, a target age range), the sharper its questions get and the more useful the resulting BRIEF.md is.

    What it is not

    It does not ask design-style questions (colors, fonts, layout) — that belongs to whatever mockup or build step comes next. This skill stays one level above, at the business-requirements level, and produces exactly one file.

    Requirements

    None beyond a Claude Code agent. No local file access beyond writing BRIEF.md to the project root, no network calls, no other skills required. Works standalone in any project.

    Works well with

    BRIEF.md is a plain Markdown file — hand it to whatever mockup-building, scaffolding, or coding workflow you use next. Many agentic build workflows will pick up a BRIEF.md sitting in the project root on their own; otherwise just reference or paste it in as context. This skill can also be called by your own orchestrator skill if you want to pipe the interview answers directly into a project-setup step instead of writing the file (see "Orchestrated mode" in SKILL.md).

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for UX & UI Design.

    Produces requirements text only — it does not generate a mockup, wireframe, or code itself. Persona and scale questions are skipped when they clearly don't apply (e.g. scale for a single-page pitch), so a very unusual project type may need a manually-added BRIEF.md section afterward. Does not integrate automatically with any specific third-party mockup tool — BRIEF.md is a plain Markdown handoff file.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    Write Files

    This skill only writes BRIEF.md to the project root after an interactive interview. It makes no other file writes, no terminal commands, no network calls, and reads no other project files (it only checks whether BRIEF.md, CLAUDE.md, or DESIGN.md already exist as siblings before writing, to avoid a naming collision).

    Listed1 month ago
    Updated1 month ago

    What's inside

    Frequently Asked Questions

    No. This skill only produces a BRIEF.md requirements file through a short interview. Building the mockup or site is a separate step you run afterward with whatever tool you normally use.

    Whatever language you're using in the conversation — it doesn't hardcode a language, and BRIEF.md is written in that same language.

    No. It only uses the standard AskUserQuestion interaction and writes one Markdown file. No API keys, no network access, no external server.

    No. If one already exists in the project root, it asks whether to overwrite it or use a different filename before writing anything.

    Yes. The third round (competitive differentiation, scale, device priority, brand assets) only asks what's relevant — for example a single-page pitch skips the "scale" question automatically.

    Yes. It supports an "Orchestrated mode" where it returns the interview answers directly instead of writing the file, so a calling skill can pipe them into its own setup flow.

    New in UX & UI Design