focus
Skill2 starsChanged 5 months agoMITView on GitHub
Declare a focus contract for the current task to keep context lean — scopes which files/dirs are in play, bans out-of-scope exploration, and routes broad searches to subagents. Use when starting a task, when the user says "focus on X", or when the session is drifting across unrelated parts of the codebase.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- whawkinsiv/solo-founder-skillstheir own version, first seen Oct 25, 2026
- wheslleyrimar/BuildCLI-Agentstheir own version, first seen Oct 22, 2026
- whawkinsiv/claude-code-skillstheir own version, first seen Oct 17, 2026
- chrdrk/claude-focustheir own version, first seen Oct 13, 2026
- Haumer/claude-skillstheir own version, first seen Oct 11, 2026
- devinat1/skillstheir own version, first seen Oct 6, 2026
Used with
Projects with it also use build.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Microsoft AzureSkillbuild
Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- whawkinsiv/solo-founder-skills★ 260same name
- whawkinsiv/claude-code-skills★ 258same name
- kennethleungty/claude-music★ 23same name
- wheslleyrimar/BuildCLI-Agents★ 3same name
- devinat1/skills★ 1same name
- vishk23/screenblock-mcp★ 1same name
- breethomas/bette-os★ 0same name
- chrdrk/claude-focus★ 0same name
- Haumer/claude-skills★ 0same name
- markbaindesign/bain-studio★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- checkpointSkill
- dietSkill
- resumeSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Write .amber/FOCUS.md in the project root (create the directory if needed):
- Distinctive: line 32
Keep it under 20 lines. This file is re-injected after every compaction, so every line costs tokens forever — earn each one.
- Distinctive: line 36
Read only in-scope files, and only the parts you need (offset/limit on large files).
- Distinctive: line 37
When you need broad codebase knowledge (where is X defined, how is Y used everywhere), delegate to an Explore subagent and consume only its …
- Distinctive: line 38
If the user asks for something out of scope, do it, but say so and offer to update the contract.
- Very specific: line 39
When the task's done criteria are met, say so and suggest /amber:checkpoint if the session continues.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/amber:focus — set a focus contract
The user wants to work on: $ARGUMENTS
A focus contract is how this session stays cheap and sharp. Big contexts make models dumber (context rot) and die in compaction. Your job now:
1. Define the scope
From the task description (ask one clarifying question only if genuinely ambiguous), determine:
- In-scope paths: the files/directories this task will actually touch. Be narrow. Use Glob/Grep to identify them — do not read whole files yet.
- Out-of-scope: everything else, named explicitly if the user has been drifting there.
- Done criteria: 1–3 checkable statements for what "finished" means.
2. Write the contract
Write .amber/FOCUS.md in the project root (create the directory if needed):
# Focus contract
- Task: <one sentence>
- In scope: <paths/globs>
- Out of scope: <paths or topics, if relevant>
- Done when: <checkable criteria>
- Set: <ISO date>Keep it under 20 lines. This file is re-injected after every compaction, so every line costs tokens forever — earn each one.
3. Obey the contract for the rest of the session
- Read only in-scope files, and only the parts you need (offset/limit on large files).
- When you need broad codebase knowledge (where is X defined, how is Y used everywhere), delegate to an Explore subagent and consume only its conclusion — never pull file dumps into the main context.
- If the user asks for something out of scope, do it, but say so and offer to update the contract.
- When the task's done criteria are met, say so and suggest
/amber:checkpointif the session continues.
Confirm the contract to the user in 2–3 sentences, then start the task.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.