3
Skill4 starsChanged 3 months agoMITView on GitHub
Standard execution timebox for moderately involved tasks. Use when the user invokes /3 and target completion within 13 minutes with implementation, testing, and nearby regression checks.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- 1Skill
- 2Skill
- 4Skill
- 5Skill
- ae-extendscriptSkill
- asapSkill
- backbeforeSkill
- componentsSkill
- githubSkill
- huhSkill
- instantSkill
- motion-animateSkill
- motion-assetsSkill
- motion-designSkill
- motion-pipelineSkill
- motion-planSkill
- quick-contextSkill
- shader-uiSkill
- thumbnailSkill
- ui-intergritySkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Treat this as a moderately involved task and complete it end to end.
- Distinctive: line 20
Test the main flow plus important edge cases.
- Distinctive: line 21
Check nearby functionality likely to be affected.
- Distinctive: line 22
Use available tools efficiently and in parallel when possible.
- Distinctive: line 23
Avoid excessive research, commentary, and unrelated refactoring.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/3 — Standard
Treat this as a moderately involved task and complete it end to end.
Timebox
Target completion in under 13 minutes. Maintain the same high quality expected at every execution level.
Behavior
- Inspect all directly relevant code and dependencies.
- Identify the likely root cause before making structural fixes.
- Implement a complete solution rather than a temporary patch.
- Preserve existing architecture unless changing it is clearly justified.
- Test the main flow plus important edge cases.
- Check nearby functionality likely to be affected.
- Use available tools efficiently and in parallel when possible.
- Avoid excessive research, commentary, and unrelated refactoring.
- Resolve ordinary implementation decisions independently.
Spend most of the time building and validating, not explaining. Finish once the requested behavior is implemented and verified.
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.