[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EN1Z2ABYXHSC8QRTZWS9VJ":3,"skill-same:01M7EN1Z2ABYXHSC8QRTZWS9VJ":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},"01M7EN1Z2ABYXHSC8QRTZWS9VJ","ams-focus-modes",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-focus-modes\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: focus-modes\ndescription: Design focus modes that actually protect attention: Do Not Disturb schedules, app filtering, notification tiers, and context-specific setups. Use when interruptions fragment your day or 'do not disturb' never stays on.\ncategory: productivity\n---\n\n# Focus Modes\n\n## Overview\n\nAttention is the scarcest resource; every notification is a bid for it. Focus modes are the defense system.\n\nModern OSes offer scheduled, context-aware modes: Work, Personal, Sleep, custom — each with allowed people, apps, and screens.\n\nThe skill isn't turning on Do Not Disturb — it's designing modes for real contexts and making them automatic.\n\nEffective modes: scheduled, location\u002Fapp-triggered, with clear notification tiers and emergency bypasses.\n\n## When to use\n\n- Constant interruptions fragmenting deep work\n- Work notifications invading evenings and weekends\n- Needing different notification rules for different contexts\n- Parents\u002Fteams needing emergency bypass without full access\n- Building a sustainable attention-protection system\n\n## Core concepts\n\n- **Notification tiers.**\n  Tier 1: nothing (deep work). Tier 2: people only (meetings day). Tier 3: people + key apps (general work). Tier 4: everything (off duty). Design modes per tier.\n- **Scheduled modes.**\n  Work hours, sleep hours, focus blocks — automatic by time. Manual modes get forgotten; scheduled modes persist.\n- **Context triggers.**\n  Activate by location (office), app (opening IDE = coding mode), or calendar event. The mode follows the context, not your memory.\n- **Allowed lists.**\n  Per mode: which people and apps break through. Default-deny; allowlist deliberately. Most apps never earn breakthrough.\n- **Emergency bypass.**\n  Repeated calls or favorites bypass — for genuine emergencies. Communicate the bypass to family so it works when needed.\n- **Home\u002Flock screen filtering.**\n  Modes can hide notification badges, dim wallpapers, filter app content (work apps hidden in personal mode). Reduce visual temptation.\n- **Status sharing.**\n  Auto-reply \u002F status visible to contacts ('in Focus until 3pm'). Sets expectations; reduces the social cost of unavailability.\n- **Cross-device sync.**\n  Modes sync across phone, tablet, watch, computer. One configuration protects all screens — verify sync works.\n\n## Practical workflow\n\n1. **Inventory interruptions.**\n   One week: note what breaks your focus, when, from which app\u002Fperson. Data before design.\n2. **Define 3-4 modes.**\n   Deep Work (nothing), Work (people + key apps), Personal (work apps silenced), Sleep (emergencies only). Fewer, sharper modes win.\n3. **Set schedules.**\n   Work mode 9-6 weekdays, sleep mode nightly, deep-work blocks 2-3x weekly. Automatic beats manual.\n4. **Build allowlists.**\n   Per mode, list who\u002Fwhat breaks through. Start strict; loosen only for proven need.\n5. **Configure bypasses.**\n   Family favorites bypass sleep mode; repeated calls bypass deep work. Test the bypass — trust but verify.\n6. **Set up triggers.**\n   Location, app-launch, or calendar triggers where supported. Remove the manual step.\n7. **Share status.**\n   Enable auto-replies\u002Fstatus so colleagues see 'Focus until 3pm' instead of silence.\n8. **Review monthly.**\n   Which interruptions still got through? Which allowed apps abused it? Tighten allowlists; adjust schedules.\n\n## Common pitfalls\n\n- **One permanent DND.**\n  Leaving Do Not Disturb on forever, then missing genuinely important things. Modes should be contextual, not permanent.\n- **Manual-only modes.**\n  Modes you must remember to toggle get toggled never. Schedule and trigger everything possible.\n- **Allowlist creep.**\n  'Just this one app' repeated monthly. Audit quarterly; most breakthrough permissions were mistakes.\n- **No emergency path.**\n  So locked down that real emergencies can't reach you. Bypass for favorites\u002Frepeated calls is essential, especially overnight.\n- **Ignoring the watch.**\n  Phone silenced, watch buzzing every notification. Configure wearables as part of the system, not separately.\n- **Status not shared.**\n  Colleagues see silence and assume ignoring. Shared status ('in focus') converts unavailability from rude to professional.\n- **Too many modes.**\n  Seven micro-modes for every mood. Nobody maintains them. Three to four sharp modes maximum.\n- **Evening work leakage.**\n  No personal mode means work pings at 10pm. The boundary needs a mode, not willpower.\n","# Focus Modes\n\n## Overview\n\nAttention is the scarcest resource; every notification is a bid for it. Focus modes are the defense system.\n\nModern OSes offer scheduled, context-aware modes: Work, Personal, Sleep, custom — each with allowed people, apps, and screens.\n\nThe skill isn't turning on Do Not Disturb — it's designing modes for real contexts and making them automatic.\n\nEffective modes: scheduled, location\u002Fapp-triggered, with clear notification tiers and emergency bypasses.\n\n## When to use\n\n- Constant interruptions fragmenting deep work\n- Work notifications invading evenings and weekends\n- Needing different notification rules for different contexts\n- Parents\u002Fteams needing emergency bypass without full access\n- Building a sustainable attention-protection system\n\n## Core concepts\n\n- **Notification tiers.**\n  Tier 1: nothing (deep work). Tier 2: people only (meetings day). Tier 3: people + key apps (general work). Tier 4: everything (off duty). Design modes per tier.\n- **Scheduled modes.**\n  Work hours, sleep hours, focus blocks — automatic by time. Manual modes get forgotten; scheduled modes persist.\n- **Context triggers.**\n  Activate by location (office), app (opening IDE = coding mode), or calendar event. The mode follows the context, not your memory.\n- **Allowed lists.**\n  Per mode: which people and apps break through. Default-deny; allowlist deliberately. Most apps never earn breakthrough.\n- **Emergency bypass.**\n  Repeated calls or favorites bypass — for genuine emergencies. Communicate the bypass to family so it works when needed.\n- **Home\u002Flock screen filtering.**\n  Modes can hide notification badges, dim wallpapers, filter app content (work apps hidden in personal mode). Reduce visual temptation.\n- **Status sharing.**\n  Auto-reply \u002F status visible to contacts ('in Focus until 3pm'). Sets expectations; reduces the social cost of unavailability.\n- **Cross-device sync.**\n  Modes sync across phone, tablet, watch, computer. One configuration protects all screens — verify sync works.\n\n## Practical workflow\n\n1. **Inventory interruptions.**\n   One week: note what breaks your focus, when, from which app\u002Fperson. Data before design.\n2. **Define 3-4 modes.**\n   Deep Work (nothing), Work (people + key apps), Personal (work apps silenced), Sleep (emergencies only). Fewer, sharper modes win.\n3. **Set schedules.**\n   Work mode 9-6 weekdays, sleep mode nightly, deep-work blocks 2-3x weekly. Automatic beats manual.\n4. **Build allowlists.**\n   Per mode, list who\u002Fwhat breaks through. Start strict; loosen only for proven need.\n5. **Configure bypasses.**\n   Family favorites bypass sleep mode; repeated calls bypass deep work. Test the bypass — trust but verify.\n6. **Set up triggers.**\n   Location, app-launch, or calendar triggers where supported. Remove the manual step.\n7. **Share status.**\n   Enable auto-replies\u002Fstatus so colleagues see 'Focus until 3pm' instead of silence.\n8. **Review monthly.**\n   Which interruptions still got through? Which allowed apps abused it? Tighten allowlists; adjust schedules.\n\n## Common pitfalls\n\n- **One permanent DND.**\n  Leaving Do Not Disturb on forever, then missing genuinely important things. Modes should be contextual, not permanent.\n- **Manual-only modes.**\n  Modes you must remember to toggle get toggled never. Schedule and trigger everything possible.\n- **Allowlist creep.**\n  'Just this one app' repeated monthly. Audit quarterly; most breakthrough permissions were mistakes.\n- **No emergency path.**\n  So locked down that real emergencies can't reach you. Bypass for favorites\u002Frepeated calls is essential, especially overnight.\n- **Ignoring the watch.**\n  Phone silenced, watch buzzing every notification. Configure wearables as part of the system, not separately.\n- **Status not shared.**\n  Colleagues see silence and assume ignoring. Shared status ('in focus') converts unavailability from rude to professional.\n- **Too many modes.**\n  Seven micro-modes for every mood. Nobody maintains them. Three to four sharp modes maximum.\n- **Evening work leakage.**\n  No personal mode means work pings at 10pm. The boundary needs a mode, not willpower.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-focus-modes",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-focus-modes",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-focus-modes",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-focus-modes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-focus-modes\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",[],[]]