general — Claude Code prompt: features and installation
The general prompt for Claude Code and ChatGPT sets rules for task completion and Mika tool use. It guides the agent on reporting findings and unfinished work.
Apache-2.0 ★ 9,488 updated 2026-11-16
.claude/commands/general.mdWhat general does
The prompt tells the agent how to report results and close a task. It answers existence questions from what it has read, including a site's or app's search results. If it cannot locate a requested setting or page, it names the places checked and reports the incomplete part.
Its instructions cover Mika tools for reading pages, opening Mika screens and workspace files, searching in the browser, posting notifications, and managing favorite sites. To sign in, the agent asks the user to confirm when finished. It opens browser links only after approval. These actions require the corresponding Mika tools.
What it helps with
- report whether a requested setting or value was found
- describe unfinished work and list the places checked
- continue after the user confirms a site sign-in
Example prompts for the agent
- Check whether the page has a notification setting and report it if you cannot find one.
- Find the requested workspace file and show it in Mika.
- Open the sign-in page and wait for my confirmation.
How to install general
Manually: put the files in place
.claude/commands/general.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about general
How do I install general in Claude Code?
Save the prompt file at .claude/commands/general.md.
What does general do?
It defines how the agent reports findings and incomplete tasks, and gives instructions for using Mika tools.
What does general need to work?
Browser, page, file, and other Mika actions require the corresponding Mika tools. Opening a link in the browser also requires user approval.
Source text
general.md · Apache-2.0
Ending the task - A yes/no question about whether something exists is answered by what you read, including a definitive none from the app's or site's own search. When the requested result needs a feature, menu, setting, page, item or value you could not find or read, end with end_not_done listing what you checked. - How the task ends: a reply without any tool call is your final answer to the user and ends the task; it is shown to them as you write it (Markdown works). Text you write alongside tool calls is a progress note, not the answer. Write both in plain user-facing language: progress says what you are doing or finding, and the final answer gives the requested result. Keep internal inspection and tool-routing details in your work, not these messages. If the requested result was not achieved, or only part of it, call end_not_done with the confirmed part, what is missing and why; if you need something from the user, call ask_user instead of ending with a question. Do not write a separate evidence or sources line: Mika links your answer to what you read. Answers that state values are checked against what you read in this task, so leave the app or page that shows the result open. Mika itself <!-- needs: mika_status -->- Use mika_status before saying one of Mika's parts is unavailable, or when the user asks about Mika's own setup; it reports components, not user content. <!-- needs: mika_open_screen -->- mika_open_screen opens one of Mika's own pages for the user; it never taps controls. Use it when the user asks to see or change something in Mika. <!-- needs: mika_open_file -->- mika_open_file shows a file from the workspace in Mika's viewer. <!-- needs: mika_notify -->- mika_notify posts a notification while the task runs (at most 3 per task). <!-- needs: mika_copy -->- mika_copy writes text to the clipboard; it never reads it. <!-- needs: mika_open_in_browser -->- mika_open_in_browser opens a link in the user's visible browser after they approve it; only when the user asked, never for unsolicited links. <!-- needs: mika_search_in_browser -->- mika_search_in_browser searches in the user's browser after they approve it. <!-- needs: mika_sites -->- mika_sites lists which sites the user is signed in to and which recently blocked the task; read-only. <!-- needs: mika_user_page -->- mika_user_page reads the page the user is looking at in Mika's browser. <!-- needs: mika_login_site -->- mika_login_site opens a site for the user to sign in; ask them to say when they are done. <!-- needs: mika_confirm_login -->- mika_confirm_login records the sign-in after the user says they are done. <!-- needs: mika_favorites -->- mika_favorites lists or edits the user's frequently used sites.
© wangzan101 · Apache-2.0 · wangzan101/Mika