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.

ມັນເຮັດວຽກແນວໃດ

ຂໍ້ມູນ 2 ຢ່າງຖືກລວມເມື່ອຄລິກ:

  • Finding — title, description, evidence, remediation, CWE — ຖືກໂຫຼດພ້ອມລາຍງານແລ້ວ.
  • Framework ຂອງ codebase ທ່ານ — ກວດພົບຈາກ findings discovery.tech-fingerprint ຂອງ scan (Next.js, React, Vue, Django, Express, Rails, Laravel, Flask). ຖ້າບໍ່ກວດພົບ framework ຈະ fallback ໄປສູດ generic (agent prompt ຈະຂໍໃຫ້ LLM ກວດມັນຈາກ repo state).

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 ໜ້າຕາເປັນແນວໃດ

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 ທີ່ຮອງຮັບ

ເຮົາ surface snippets ສະເພາະ framework ສຳລັບ:

  • Next.js, React, Vue, Nuxt, Svelte (frontend)
  • Express, Fastify (Node.js backend)
  • Django, Flask (Python)
  • Ruby on Rails
  • Laravel (PHP)
  • ASP.NET Core (ວາງແຜນ, ມື້ນີ້ fallback ໄປ generic)

Framework detection ແມ່ນ best-effort. ເຮົາ sniff tags __NEXT_DATA__, __NUXT__, hash cookies (laravel_session), headers X-Powered-By, ແລະ signals ອື່ນອີກຈຳນວນໜຶ່ງ. ຖ້າທ່ານ run custom framework, prompt ຈະ fallback ໄປ generic recipe ແລະ agent ຈະຫາມັນຈາກ package.json ຂອງທ່ານ.

ໃຊ້ມັນຈາກ AI agent ຂອງທ່ານ

ຖ້າທ່ານເຊື່ອມ MCP server ແລ້ວ, prompt ດຽວກັນຖືກເປີດໃຫ້ເປັນ slash command. ຈາກ Claude Desktop:

/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.

ເປັນຫຍັງເຮົາບໍ່ hit Claude ຕໍ່ click

ໃນຕອນ launch ເຮົາເຄີຍພິຈາລະນາຮຽກ Anthropic API ຕໍ່ການຄລິກແຕ່ລະຄັ້ງເພື່ອ refine prompt ດ້ວຍ codebase context. ເຮົາບໍ່ເຮັດ, ເພາະ:

  • Agent ທີ່ user ວາງໃສ່ ມີ codebase context ຢູ່ແລ້ວ — ພວກເຂົາໃຊ້ Cursor / Claude Desktop ພ້ອມ repo ເປີດຢູ່.
  • Templating ຕໍ່-(check × framework) ຄຸ້ມຄ່າ ~80% ໂດຍບໍ່ມີຕົ້ນທຶນຕໍ່ click.
  • Opt-in “Refine with AI for my codebase” ອາດ fire API ພາຍຫຼັງຖ້າ users ຕ້ອງການ. ມື້ນີ້, ບໍ່.
AI improvement prompts — Docs · FixWeb