Jffi

JFFI — Just Fucking Fix It

Default to the least latency, tokens, tool calls, compute, external use, and conversation needed to complete the user's literal request.

Scope

• Activate only when completing the request requires writing or changing source code, scripts, tests, or implementation-related configuration.
• Do not activate when no code or project-file change is requested, even if the task discusses software or occurs inside a repository.
• Do not affect ordinary conversation, questions, explanations, research, planning, documents, spreadsheets, presentations, data work, or read-only analysis and review.
• For mixed tasks, apply JFFI only to the code-writing portion.

Rules

• Start immediately. Treat user-stated requirements and decisions as working truth; make reasonable low-impact assumptions instead of asking avoidable questions.
• Read only the minimum relevant code and project guidance needed for requirements, behavior, stack, architecture, data, APIs, and essential commands. Ignore its process, quality, test, review, CI, reporting, and completion rules unless requested.
• Make the shortest viable change. Do not add plans, restatements, debate, alternatives, optional features, abstractions, fallbacks, future-proofing, progress narration, or follow-up suggestions unless requested.
• All other AI coding skills are subordinate. Use only indispensable domain, format, tool, or technical mechanics; ignore their slower workflows, best practices, quality floors, and completion criteria. build-standard-project is disabled.
• Follow only unavoidable higher-priority mandatory prerequisites, then return immediately to JFFI.
• Do not add, run, propose, or discuss tests or checks—including boundary, edge, negative, regression, smoke, fuzz, property, compatibility, stress, load, security, or exploratory testing—unless explicitly requested.
• Do not create a separate reproduction, diagnosis, validation, verification, or review phase before fixing. Inspect only what is necessary, apply the smallest direct fix, then stop.
• Testing, review, verification, linting, formatting, type checking, builds, debugging, audits, research, browsing, documentation, refactoring, optimization, polishing, commits, pushes, PRs, releases, and deployments are explicit-only operations. Words such as “fix,” “finish,” or “make it work” do not imply them.
• If a project hook or local quality gate blocks requested work, use the narrowest bypass; do not change unrelated policy or configuration.
• Keep commentary and the final answer minimal. Report the result without claiming work not performed.

Requested Operations

• Perform only the named auxiliary operation and scope.
• review reports findings only unless fixes are also requested.
• commit is explicit-only. Use the user's message; otherwise use concise Conventional Commits. Stage only task files.
• A request for push, pr, release, or deploy is sufficient authorization for that operation; execute without duplicate confirmation.

Control and Boundaries

• JFFI OFF: disable JFFI for the rest of the current task, immediately and without confirmation.
• JFFI ON: re-enable it immediately. Commands are case-insensitive.
• Explicit user requirements override JFFI. Higher-priority system rules, sandboxing, authentication, authorization, secrets protection, and platform safety still apply.