Prompts na gyaran AI

Yadda yake aiki

Abubuwan data biyu suna haɗuwa idan aka danna:

• The finding — the issue summary, affected surface, remediation guidance, and safe evidence needed to help your coding agent fix it.
• Your app context — FixVibe uses scan context when available to choose a framework-aware remediation shape, and falls back to a generic recipe when it cannot infer enough context.

Fix prompts are rendered server-side from FixVibe remediation guidance. They are designed for copy-paste use in Cursor, Claude Desktop, Copilot, or another coding agent without exposing the internal prompt registry in the browser.

Yadda prompt yake kama

Fix the "Reflected XSS in /search?q=" vulnerability at /search.

Issue: Query parameter q is rendered into the response body without
escaping; an attacker can inject <script> via crafted URLs.

Codebase context: Next.js.

Recommended fix:
In Next.js, render user-supplied values through JSX ({value}) so React's
automatic escaping kicks in. For server components rendering rich HTML,
sanitize with DOMPurify (server-side via JSDOM) before output.

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 security 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: CWE-79 — see https://cwe.mitre.org/data/definitions/79.html

Frameworks da ake tallafawa

Muna nuna framework-specific snippets don:

• Next.js, React, Vue, Nuxt, Svelte (bangaren frontend)
• Express, Fastify (backend na Node.js)
• Django, Flask (Python)
• Ruby on Rails
• Laravel (PHP)
• ASP.NET Core fallback guidance

Framework context is best-effort. If FixVibe cannot infer enough safely from the scan, the prompt asks your coding agent to inspect the repository before applying the fix.

Yi amfani da shi daga AI-agent ɗinka

Idan ka haɗa MCP server, ana fallasa wannan prompt ɗin a matsayin slash command. Daga Claude Desktop:

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

The server looks up the finding, applies available scan context, renders the remediation prompt, and injects it into your conversation as the user message. No third-party LLM API call is made by FixVibe for this templated prompt.

Dalilin da ya sa ba ma kiran Claude kowane danna

A lokacin launch mun yi tunanin kiran Anthropic API a kowane danna don tace prompt da codebase context. Ba mu yi ba, saboda:

• Agent ɗin da mai amfani yake liƙawa cikinsa tuni yana da codebase context; suna amfani da Cursor / Claude Desktop tare da repo ɗinsu a buɗe.
• Server-side templating covers the common remediation paths without any per-click model call.
• Za a iya samun opt-in “Refine with AI for my codebase” da zai kira API daga baya idan masu amfani suna so. A yau, a’a.