FixWeb

// docs / ai fix prompts

AI improvement prompts

Every finding has a Copy prompt button beneath the remediation. Click it, paste into Claude / Cursor / Copilot, and the agent gets the canonical improvement recipe for that website-quality issue — no Claude API call from us.

Akkamitti hojjeta

Yeroo cuqaastu deetaan lamaan walitti dhufa:

  • Argannoo — title, description, evidence, remediation, CWE — gabaasa waliin duraan fe'ameera.
  • Framework codebase keetii — argannoowwan discovery.tech-fingerprint scan irraa adda baafama (Next.js, React, Vue, Django, Express, Rails, Laravel, Flask). Framework hin argamne yoo ta'e gara recipe waliigalaa deebi'a (prompt agent booda LLM akka repo state irraa adda baasu gaafata).

Templates live in lib/scanner/fix-prompts.ts. The registry has check-specific guidance for crawlability, search presentation, semantic content, structured data, media, performance, accessibility, forms, mobile/i18n, runtime, owner journeys, and repo-quality issues. For everything else, the existing remediation field on the finding becomes the generic recipe.

Prompt akkam fakkaata

Fix the "Hero image is lazy-loaded and missing dimensions" finding on /pricing.

Issue: The largest above-the-fold image is marked loading="lazy" and has
no explicit width/height. That can delay LCP and create layout shift.

Codebase context: Next.js.

Recommended fix:
Use next/image or the existing image component with explicit width/height,
responsive sizes, meaningful alt text, and priority/fetchPriority for the
first major visual on the page.

Constraints:
- Don't break existing tests; run the test suite after the change.
- Match the codebase's existing style and lint config.
- Add a brief comment explaining the performance reasoning only where the
  fix would otherwise look arbitrary.
- If the fix needs a new dependency, install it via the project's
  package manager (npm / pnpm / pip / bundle / composer).

Reference: Core Web Vitals / Largest Contentful Paint guidance.

Frameworks deeggaraman

Nuti snippets framework-specific kanaaf mul'isna:

  • Next.js, React, Vue, Nuxt, Svelte (frontend)
  • Express, Fastify (Node.js backend)
  • Django, Flask (Python)
  • Ruby on Rails
  • Laravel (PHP)
  • ASP.NET Core (karoorfame; har'a gara generic deebi'a)

Framework detection best-effort dha. Tags __NEXT_DATA__, __NUXT__, hash cookies (laravel_session), headers X-Powered-By, fi mallattoolee muraasa biroo ni sniff goona. Yoo custom framework hojjechaa jirta ta'e, prompt gara recipe generic deebi'a, agent immoo package.json keetii irraa ni hubata.

AI agent kee irraa itti fayyadami

Yoo MCP server walitti hidde, prompt walfakkaatu akka slash command ni mul'ata. Claude Desktop irraa:

/fixweb-fix finding_id=550e8400-e29b-41d4-a716-446655440000

The renderer looks up the finding, detects the framework from the parent scan when available, renders the templated prompt, and injects it into your conversation as the user message. No round-trip to our Claude API; templates are pure and free.

Maaliif cuqaasuu hundaan Claude hin waamnu

Yeroo jalqabnu cuqaasuu hundaaf Anthropic API waamnee prompt codebase context waliin fooyyessuu yaadne. Garuu hin goone, sababni isaa:

  • Agent fayyadamaan keessa maxxansu duraanis codebase context qaba; isaan Cursor / Claude Desktop repo isaanii banamee fayyadamu.
  • Templating per-(check × framework) baasii per-click tokko malee gatii ~80% uwwisa.
  • Filannoon “AI'n codebase koo caalaatti sirreessi” booda API kakaasuu danda'a yoo fayyadamtoonni barbaadan. Har'a garuu hin jiru.
AI improvement prompts — Docs · FixWeb