ams-pomodoro-coach
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
03 SKILL.md 正文
Pomodoro Coach
Overview
Work in focused intervals (traditionally 25 min), take short breaks, and after four intervals take a longer break.
The real power isn't the timer — it's the ritual: commit to one task, make interruptions visible, measure work honestly.
One pomodoro = one uninterrupted interval on one task. Interruptions get logged, not served.
The technique trains three muscles: starting (commitment is small), sustaining (timer holds you), stopping (breaks prevent burnout).
Count completed pomodoros per day: a concrete measure of focused effort that can't be faked by looking busy.
When to use
- Starting focused work when motivation is low or dread is high
- Breaking large, intimidating tasks into approachable chunks
- Diagnosing where your attention actually goes during the day
- Building a sustainable deep-work routine from scratch
- Recovering focus after a period of fragmented, reactive work
Core concepts
- One task per pomodoro. Write down exactly what you'll do before starting. Switching mid-interval is not allowed; the written commitment is the contract.
- The timer as commitment device. 25 minutes is short enough to start, long enough to matter. The guaranteed stop makes starting easier.
- Interruptions: log, don't serve. Internal ('email Sam') -> scratch pad, return to task. External -> negotiate ('20 minutes') or log and resume.
- Breaks are structural. 5 min: stand, water, look away. 15-30 min after four. Skipping breaks borrows from tomorrow — the break is part of the work.
- Adapt the interval. 25/5 is the default, not law. Deep work: 50/10 or 90/20. Fragmented days: 15-min admin sprints. Match interval to work and energy.
- Count honestly. A pomodoro counts only if truly focused. Half-distracted intervals don't count — the honesty is the feature.
- Estimate in pomodoros. Size tasks in intervals ('~6 pomodoros'). Estimation skill compounds; daily planning becomes concrete.
- The scratch pad. A single place for every interruption and stray thought. Reviewing it daily reveals fixable system problems.
Practical workflow
- Plan the day's pomodoros. List tasks, estimate each (1-4 pomodoros; bigger gets split). Realistic total: 6-10 intervals is a full day.
- Set up the environment. Silence notifications, phone out of reach, close unrelated tabs. Preparation is ritual, not overhead.
- Start the first interval fast. State the task in writing, start the timer within 5 minutes of planning. Momentum beats perfect setup.
- Take real breaks. Stand, move, hydrate, look at distance. No 'quick checks' — that's work wearing a break costume.
- Review interruptions daily. Scan the scratch pad. Recurring items are system problems (mute channel, batch email) not willpower failures.
- Track counts per project. Log completed pomodoros alongside output. Weekly review: where did focus actually go? Which estimates were off?
- Adapt weekly. Abandoning 25s at minute 40? Switch to 50s. Skipping breaks? Shorten intervals. Technique serves you, not vice versa.
- Protect the first interval. Do the hardest task in pomodoro #1. Starting with email trains the brain that mornings are for reacting.
Common pitfalls
- Rigid 25 minutes for everything. Deep work needs longer arcs, admin needs shorter. Adapt or the technique feels like a cage and you'll quit.
- Fake pomodoros. Timer running while scrolling and half-working. Not focused? Stop the timer, restart. Honesty is the point.
- Skipping breaks. 'I'm on a roll' borrows from tomorrow. Take the break; the roll survives, and you'll sustain it longer.
- No task definition. Starting with 'stuff' guarantees a wasted interval. Name the single task first, in writing.
- Interruption guilt. Interruptions are data, not moral failures. Log without judgment, then fix the pattern.
- Counting as competition. Ten focused intervals beat fourteen distracted ones. Quality first, then quantity.
- Wrong work for the method. Pomodoro is poor for 2-hour immersion (deep debugging, complex writing). Use longer intervals there.
- No review. Running timers for weeks without reviewing counts and logs. The review turns a timer into a coaching system.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).