[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVEBHE3WN47PETHGQEDY2Q":3,"skill-same:01M7EVEBHE3WN47PETHGQEDY2Q":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EVEBHE3WN47PETHGQEDY2Q","ams-pomodoro-coach",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-pomodoro-coach\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pomodoro-coach\ndescription: Coach the Pomodoro Technique properly: interval design, task sizing, interruption handling, and adapting cycles to real work. Use when building focused work habits or fighting distraction and procrastination.\ncategory: productivity\n---\n\n# Pomodoro Coach\n\n## Overview\n\nWork in focused intervals (traditionally 25 min), take short breaks, and after four intervals take a longer break.\n\nThe real power isn't the timer — it's the ritual: commit to one task, make interruptions visible, measure work honestly.\n\nOne pomodoro = one uninterrupted interval on one task. Interruptions get logged, not served.\n\nThe technique trains three muscles: starting (commitment is small), sustaining (timer holds you), stopping (breaks prevent burnout).\n\nCount completed pomodoros per day: a concrete measure of focused effort that can't be faked by looking busy.\n\n## When to use\n\n- Starting focused work when motivation is low or dread is high\n- Breaking large, intimidating tasks into approachable chunks\n- Diagnosing where your attention actually goes during the day\n- Building a sustainable deep-work routine from scratch\n- Recovering focus after a period of fragmented, reactive work\n\n## Core concepts\n\n- **One task per pomodoro.**\n  Write down exactly what you'll do before starting. Switching mid-interval is not allowed; the written commitment is the contract.\n- **The timer as commitment device.**\n  25 minutes is short enough to start, long enough to matter. The guaranteed stop makes starting easier.\n- **Interruptions: log, don't serve.**\n  Internal ('email Sam') -> scratch pad, return to task. External -> negotiate ('20 minutes') or log and resume.\n- **Breaks are structural.**\n  5 min: stand, water, look away. 15-30 min after four. Skipping breaks borrows from tomorrow — the break is part of the work.\n- **Adapt the interval.**\n  25\u002F5 is the default, not law. Deep work: 50\u002F10 or 90\u002F20. Fragmented days: 15-min admin sprints. Match interval to work and energy.\n- **Count honestly.**\n  A pomodoro counts only if truly focused. Half-distracted intervals don't count — the honesty is the feature.\n- **Estimate in pomodoros.**\n  Size tasks in intervals ('~6 pomodoros'). Estimation skill compounds; daily planning becomes concrete.\n- **The scratch pad.**\n  A single place for every interruption and stray thought. Reviewing it daily reveals fixable system problems.\n\n## Practical workflow\n\n1. **Plan the day's pomodoros.**\n   List tasks, estimate each (1-4 pomodoros; bigger gets split). Realistic total: 6-10 intervals is a full day.\n2. **Set up the environment.**\n   Silence notifications, phone out of reach, close unrelated tabs. Preparation is ritual, not overhead.\n3. **Start the first interval fast.**\n   State the task in writing, start the timer within 5 minutes of planning. Momentum beats perfect setup.\n4. **Take real breaks.**\n   Stand, move, hydrate, look at distance. No 'quick checks' — that's work wearing a break costume.\n5. **Review interruptions daily.**\n   Scan the scratch pad. Recurring items are system problems (mute channel, batch email) not willpower failures.\n6. **Track counts per project.**\n   Log completed pomodoros alongside output. Weekly review: where did focus actually go? Which estimates were off?\n7. **Adapt weekly.**\n   Abandoning 25s at minute 40? Switch to 50s. Skipping breaks? Shorten intervals. Technique serves you, not vice versa.\n8. **Protect the first interval.**\n   Do the hardest task in pomodoro #1. Starting with email trains the brain that mornings are for reacting.\n\n## Common pitfalls\n\n- **Rigid 25 minutes for everything.**\n  Deep work needs longer arcs, admin needs shorter. Adapt or the technique feels like a cage and you'll quit.\n- **Fake pomodoros.**\n  Timer running while scrolling and half-working. Not focused? Stop the timer, restart. Honesty is the point.\n- **Skipping breaks.**\n  'I'm on a roll' borrows from tomorrow. Take the break; the roll survives, and you'll sustain it longer.\n- **No task definition.**\n  Starting with 'stuff' guarantees a wasted interval. Name the single task first, in writing.\n- **Interruption guilt.**\n  Interruptions are data, not moral failures. Log without judgment, then fix the pattern.\n- **Counting as competition.**\n  Ten focused intervals beat fourteen distracted ones. Quality first, then quantity.\n- **Wrong work for the method.**\n  Pomodoro is poor for 2-hour immersion (deep debugging, complex writing). Use longer intervals there.\n- **No review.**\n  Running timers for weeks without reviewing counts and logs. The review turns a timer into a coaching system.\n","# Pomodoro Coach\n\n## Overview\n\nWork in focused intervals (traditionally 25 min), take short breaks, and after four intervals take a longer break.\n\nThe real power isn't the timer — it's the ritual: commit to one task, make interruptions visible, measure work honestly.\n\nOne pomodoro = one uninterrupted interval on one task. Interruptions get logged, not served.\n\nThe technique trains three muscles: starting (commitment is small), sustaining (timer holds you), stopping (breaks prevent burnout).\n\nCount completed pomodoros per day: a concrete measure of focused effort that can't be faked by looking busy.\n\n## When to use\n\n- Starting focused work when motivation is low or dread is high\n- Breaking large, intimidating tasks into approachable chunks\n- Diagnosing where your attention actually goes during the day\n- Building a sustainable deep-work routine from scratch\n- Recovering focus after a period of fragmented, reactive work\n\n## Core concepts\n\n- **One task per pomodoro.**\n  Write down exactly what you'll do before starting. Switching mid-interval is not allowed; the written commitment is the contract.\n- **The timer as commitment device.**\n  25 minutes is short enough to start, long enough to matter. The guaranteed stop makes starting easier.\n- **Interruptions: log, don't serve.**\n  Internal ('email Sam') -> scratch pad, return to task. External -> negotiate ('20 minutes') or log and resume.\n- **Breaks are structural.**\n  5 min: stand, water, look away. 15-30 min after four. Skipping breaks borrows from tomorrow — the break is part of the work.\n- **Adapt the interval.**\n  25\u002F5 is the default, not law. Deep work: 50\u002F10 or 90\u002F20. Fragmented days: 15-min admin sprints. Match interval to work and energy.\n- **Count honestly.**\n  A pomodoro counts only if truly focused. Half-distracted intervals don't count — the honesty is the feature.\n- **Estimate in pomodoros.**\n  Size tasks in intervals ('~6 pomodoros'). Estimation skill compounds; daily planning becomes concrete.\n- **The scratch pad.**\n  A single place for every interruption and stray thought. Reviewing it daily reveals fixable system problems.\n\n## Practical workflow\n\n1. **Plan the day's pomodoros.**\n   List tasks, estimate each (1-4 pomodoros; bigger gets split). Realistic total: 6-10 intervals is a full day.\n2. **Set up the environment.**\n   Silence notifications, phone out of reach, close unrelated tabs. Preparation is ritual, not overhead.\n3. **Start the first interval fast.**\n   State the task in writing, start the timer within 5 minutes of planning. Momentum beats perfect setup.\n4. **Take real breaks.**\n   Stand, move, hydrate, look at distance. No 'quick checks' — that's work wearing a break costume.\n5. **Review interruptions daily.**\n   Scan the scratch pad. Recurring items are system problems (mute channel, batch email) not willpower failures.\n6. **Track counts per project.**\n   Log completed pomodoros alongside output. Weekly review: where did focus actually go? Which estimates were off?\n7. **Adapt weekly.**\n   Abandoning 25s at minute 40? Switch to 50s. Skipping breaks? Shorten intervals. Technique serves you, not vice versa.\n8. **Protect the first interval.**\n   Do the hardest task in pomodoro #1. Starting with email trains the brain that mornings are for reacting.\n\n## Common pitfalls\n\n- **Rigid 25 minutes for everything.**\n  Deep work needs longer arcs, admin needs shorter. Adapt or the technique feels like a cage and you'll quit.\n- **Fake pomodoros.**\n  Timer running while scrolling and half-working. Not focused? Stop the timer, restart. Honesty is the point.\n- **Skipping breaks.**\n  'I'm on a roll' borrows from tomorrow. Take the break; the roll survives, and you'll sustain it longer.\n- **No task definition.**\n  Starting with 'stuff' guarantees a wasted interval. Name the single task first, in writing.\n- **Interruption guilt.**\n  Interruptions are data, not moral failures. Log without judgment, then fix the pattern.\n- **Counting as competition.**\n  Ten focused intervals beat fourteen distracted ones. Quality first, then quantity.\n- **Wrong work for the method.**\n  Pomodoro is poor for 2-hour immersion (deep debugging, complex writing). Use longer intervals there.\n- **No review.**\n  Running timers for weeks without reviewing counts and logs. The review turns a timer into a coaching system.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-pomodoro-coach",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-pomodoro-coach",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-pomodoro-coach",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-pomodoro-coach","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-pomodoro-coach\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","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\u002FCSS, 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.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","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).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]