[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMRYDD338YZXZY037389TH":3,"skill-same:01M7EMRYDD338YZXZY037389TH":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},"01M7EMRYDD338YZXZY037389TH","ams-deep-work-planner",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-deep-work-planner\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: deep-work-planner\ndescription: Plan and protect deep work: scheduling focus blocks, task selection, shutdown rituals, and measuring depth. Use when important work never gets sustained attention or days fill with shallow tasks.\ncategory: productivity\n---\n\n# Deep Work Planner\n\n## Overview\n\nDeep work = cognitively demanding tasks done in distraction-free concentration. It's where valuable output comes from — and it's incompatible with a fragmented calendar.\n\nShallow work (email, admin, meetings) expands to fill all available time unless deep work is scheduled first.\n\nPlanning deep work means: choosing the right tasks, blocking the time, designing the environment, and defending the blocks.\n\n## When to use\n\n- Important projects stall while email and meetings consume days\n- Wanting a sustainable routine of focused creative work\n- Knowledge workers feeling busy but unproductive\n- Designing team norms that protect maker time\n- Students or researchers needing long thesis\u002Fwriting blocks\n\n## Core concepts\n\n- **Deep vs. shallow.**\n  Deep: cognitively demanding, creates new value, hard to replicate. Shallow: logistical, easy to replicate, necessary but not valuable. Audit your week by this split.\n- **Time blocking.**\n  Deep work gets calendar blocks — 90+ minutes, ideally 2-4 hours. Unscheduled deep work doesn't happen; shallow work is the default.\n- **Task selection.**\n  Not all hard tasks deserve depth. Choose: high-leverage, deadline-meaningful, requiring sustained thought. One deep task per block.\n- **The shutdown ritual.**\n  End-of-day complete shutdown: review, capture open loops, close everything. Protects evenings and makes mornings start clean.\n- **Attention residue.**\n  Switching tasks leaves mental residue that degrades the next task. Single-task blocks + real breaks beat 'multitasking.'\n- **Depth metrics.**\n  Track deep hours per week and per project. What gets measured gets protected. 10-15 deep hours\u002Fweek is excellent for most roles.\n- **Energy alignment.**\n  Schedule deep blocks in peak energy (usually morning). Guard the golden hours; shallow work fills the troughs.\n- **Boredom tolerance.**\n  Deep work requires tolerating boredom without reaching for the phone. This is trainable — start with 50-min blocks and extend.\n\n## Practical workflow\n\n1. **Audit the week.**\n   Classify last week's hours: deep vs. shallow. Most find \u003C5 deep hours. That's the baseline to beat.\n2. **Choose deep tasks.**\n   List this week's 2-3 highest-leverage cognitively-demanding tasks. These earn the blocks; everything else is shallow.\n3. **Block 3-5 sessions.**\n   90-180 min blocks, mornings preferred, on the calendar as unmovable commitments. Start with 3\u002Fweek; build up.\n4. **Design the environment.**\n   Phone out of room, notifications off, door closed \u002F status set, materials ready. Friction against distraction, not willpower.\n5. **Define block protocol.**\n   One task per block, timer optional, scratch pad for intrusions, break after. Same ritual every time builds the habit.\n6. **Run the shutdown ritual.**\n   End of day: 10 min to close loops, plan tomorrow's first block, shut down completely. No 'quick checks' after.\n7. **Track depth weekly.**\n   Log deep hours per block. Review: total, per project, interruptions. Trend matters more than any single week.\n8. **Defend and expand.**\n   Treat blocks like client meetings. Quarterly: can you add one more block? Can meetings move off golden hours?\n\n## Common pitfalls\n\n- **Scheduling but not defending.**\n  Blocks that every 'urgent' request overrides. An undefended block teaches everyone it's fake. Defend or delete.\n- **Too-ambitious start.**\n  Five 3-hour blocks in week one. Start with 2-3 ninety-minute blocks; build the muscle before the marathon.\n- **Wrong tasks in blocks.**\n  Deep blocks spent on email triage. Blocks are for the 2-3 chosen deep tasks only — ruthlessly.\n- **Phone in the room.**\n  'On silent, face down' still tempts and still interrupts (vibration, screen glow). Out of the room, or it doesn't count.\n- **Skipping the shutdown.**\n  Evenings bleed into work, mornings start groggy. The shutdown ritual is what makes deep work sustainable.\n- **Measuring only hours.**\n  4 'deep' hours of distracted half-work. Honest focus matters more than clock time — pair with interruption logging.\n- **All depth, no shallow time.**\n  Deep blocks with no scheduled shallow time means shallow tasks invade the blocks. Schedule admin\u002Femail windows too.\n- **Ignoring energy.**\n  Deep blocks at 4pm for a morning person. Align with chronotype or fight biology every session.\n","# Deep Work Planner\n\n## Overview\n\nDeep work = cognitively demanding tasks done in distraction-free concentration. It's where valuable output comes from — and it's incompatible with a fragmented calendar.\n\nShallow work (email, admin, meetings) expands to fill all available time unless deep work is scheduled first.\n\nPlanning deep work means: choosing the right tasks, blocking the time, designing the environment, and defending the blocks.\n\n## When to use\n\n- Important projects stall while email and meetings consume days\n- Wanting a sustainable routine of focused creative work\n- Knowledge workers feeling busy but unproductive\n- Designing team norms that protect maker time\n- Students or researchers needing long thesis\u002Fwriting blocks\n\n## Core concepts\n\n- **Deep vs. shallow.**\n  Deep: cognitively demanding, creates new value, hard to replicate. Shallow: logistical, easy to replicate, necessary but not valuable. Audit your week by this split.\n- **Time blocking.**\n  Deep work gets calendar blocks — 90+ minutes, ideally 2-4 hours. Unscheduled deep work doesn't happen; shallow work is the default.\n- **Task selection.**\n  Not all hard tasks deserve depth. Choose: high-leverage, deadline-meaningful, requiring sustained thought. One deep task per block.\n- **The shutdown ritual.**\n  End-of-day complete shutdown: review, capture open loops, close everything. Protects evenings and makes mornings start clean.\n- **Attention residue.**\n  Switching tasks leaves mental residue that degrades the next task. Single-task blocks + real breaks beat 'multitasking.'\n- **Depth metrics.**\n  Track deep hours per week and per project. What gets measured gets protected. 10-15 deep hours\u002Fweek is excellent for most roles.\n- **Energy alignment.**\n  Schedule deep blocks in peak energy (usually morning). Guard the golden hours; shallow work fills the troughs.\n- **Boredom tolerance.**\n  Deep work requires tolerating boredom without reaching for the phone. This is trainable — start with 50-min blocks and extend.\n\n## Practical workflow\n\n1. **Audit the week.**\n   Classify last week's hours: deep vs. shallow. Most find \u003C5 deep hours. That's the baseline to beat.\n2. **Choose deep tasks.**\n   List this week's 2-3 highest-leverage cognitively-demanding tasks. These earn the blocks; everything else is shallow.\n3. **Block 3-5 sessions.**\n   90-180 min blocks, mornings preferred, on the calendar as unmovable commitments. Start with 3\u002Fweek; build up.\n4. **Design the environment.**\n   Phone out of room, notifications off, door closed \u002F status set, materials ready. Friction against distraction, not willpower.\n5. **Define block protocol.**\n   One task per block, timer optional, scratch pad for intrusions, break after. Same ritual every time builds the habit.\n6. **Run the shutdown ritual.**\n   End of day: 10 min to close loops, plan tomorrow's first block, shut down completely. No 'quick checks' after.\n7. **Track depth weekly.**\n   Log deep hours per block. Review: total, per project, interruptions. Trend matters more than any single week.\n8. **Defend and expand.**\n   Treat blocks like client meetings. Quarterly: can you add one more block? Can meetings move off golden hours?\n\n## Common pitfalls\n\n- **Scheduling but not defending.**\n  Blocks that every 'urgent' request overrides. An undefended block teaches everyone it's fake. Defend or delete.\n- **Too-ambitious start.**\n  Five 3-hour blocks in week one. Start with 2-3 ninety-minute blocks; build the muscle before the marathon.\n- **Wrong tasks in blocks.**\n  Deep blocks spent on email triage. Blocks are for the 2-3 chosen deep tasks only — ruthlessly.\n- **Phone in the room.**\n  'On silent, face down' still tempts and still interrupts (vibration, screen glow). Out of the room, or it doesn't count.\n- **Skipping the shutdown.**\n  Evenings bleed into work, mornings start groggy. The shutdown ritual is what makes deep work sustainable.\n- **Measuring only hours.**\n  4 'deep' hours of distracted half-work. Honest focus matters more than clock time — pair with interruption logging.\n- **All depth, no shallow time.**\n  Deep blocks with no scheduled shallow time means shallow tasks invade the blocks. Schedule admin\u002Femail windows too.\n- **Ignoring energy.**\n  Deep blocks at 4pm for a morning person. Align with chronotype or fight biology every session.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-deep-work-planner",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-deep-work-planner",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-deep-work-planner",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-deep-work-planner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-deep-work-planner\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",[],[]]