Design and build a brand website

Workflow steps

1. 1.Read Website Design Build and supplied materials; infer audience, main action, page scope, and requested delivery stage. Ask only about result-changing gaps.
2. 2.Use Firecrawl only for a supplied public URL and GitHub only for an existing repository; record real content, current behavior, assets, and unknowns.
3. 3.Choose one direction. Use Taste for public marketing pages, Impeccable for responsive and accessible states, and Emil only for needed interactions. Preserve brand constraints.
4. 4.Build the scoped pages in the coding host with real assets and shared components. Use Figma only if requested; keep disconnected forms, login, and payments explicitly labeled.
5. 5.Inspect desktop and mobile together, test CTA destinations, keyboard, long copy, language, and reduced motion; batch fixes and record checks actually run.
6. 6.Deliver runnable source, start instructions, preview, QA, credits, and remaining connections. Deploy only if requested and authorized, then verify the exact live version.

Example prompt for your agent

Run the Aident Loadout use case “Design and build a brand website” (use-case:design-and-build-a-brand-website) from https://loadout.aident.ai/use-cases/design-and-build-a-brand-website. Use the Aident Skill to load this use case and its dedicated Skill IDs (skill:6b2045c7-1852-5e2c-8dfd-4c67f4cb75c0, skill:d407e603-816d-5e5f-9c77-ff7ecad3152b, skill:8aebb734-3cee-5026-aa2c-68e827665f85, skill:078a1295-d7b8-59e8-81f4-e8a48f473d3e), then call its real Loadout capabilities: firecrawl tools, github tools, firecrawl scrape, github get repository content. Ask before any write or paid action. Use our flower-export introduction and product photos to build an English B2B inquiry site. Keep our logo; deliver runnable pages, a preview, and mobile QA. Flag the form if its destination is missing.

Limits and review checkpoints

Needs a coding host for runnable pages and a browser for visual checks. Favorite and sync the complete Skills for local scripts. Figma and deployment are optional host capabilities; forms, login, payments, and publishing need real connections and authorization. No invented proof or implied live launch.

Actions used

• Firecrawl Tools

  Firecrawl Scrape

  Scrapes a publicly accessible URL, optionally performing pre-scrape browser actions or extracting structured JSON using an LLM, to retrieve content in specified formats.

  $0.0008 / callWrite action
• GitHub Tools

  Github Get Repository Content

  Retrieves a file's Base64 encoded content or lists a directory's contents from a GitHub repository.

  FreeWrite action

Skills

Use the dedicated Skill below for the complete setup, eligibility, approval, and recovery workflow.

• @edward-skills3,64849

  Website Design BuildTurn supplied brand content and assets into a responsive brand, B2B inquiry, or SaaS website with a runnable preview and verified delivery.

  Oct 17, 2026
• @Leonxlnx4,470420

  Design Taste FrontendDevelop subject-specific art direction for public websites using the complete Taste v2 reference library and browser inspection workflow.

  Oct 17, 2026
• @pbakaus5,345308

  ImpeccableDesign, audit, and refine interfaces using the complete Impeccable workflow, command references, and pinned local runtime.

  Oct 17, 2026
• @emilkowalski8,027221

  Emil Design EngineeringApply Emil Kowalski’s interaction, motion, accessibility, and component review guidance to frontend implementation.

  Oct 17, 2026

Related use cases

• +2

  Create a reusable brand marketing assets pack

  Use Aident Brand Marketing Pack to build the evidence, messaging, copy, taxonomy, and briefs; use Aident Brand Visual Production to fill reviewed templates and return inspected media; then assemble a verified editable pack in the chosen Lark, Google, or Notion workspace.

• 

Verification and source

Demand and workflow source Website Design Build and reviewed design-engineering Skills