AGENT SKILL

ams-focus-modes

暂无简介

License 许可
MIT
所属仓库
TanNhatCMS/jarvis
最近更新
2026-11-07
Stars
★ 0
Forks
1

03 SKILL.md 正文

Focus Modes

Overview

Attention is the scarcest resource; every notification is a bid for it. Focus modes are the defense system.

Modern OSes offer scheduled, context-aware modes: Work, Personal, Sleep, custom — each with allowed people, apps, and screens.

The skill isn't turning on Do Not Disturb — it's designing modes for real contexts and making them automatic.

Effective modes: scheduled, location/app-triggered, with clear notification tiers and emergency bypasses.

When to use

  • Constant interruptions fragmenting deep work
  • Work notifications invading evenings and weekends
  • Needing different notification rules for different contexts
  • Parents/teams needing emergency bypass without full access
  • Building a sustainable attention-protection system

Core concepts

  • Notification tiers. 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.
  • Scheduled modes. Work hours, sleep hours, focus blocks — automatic by time. Manual modes get forgotten; scheduled modes persist.
  • Context triggers. Activate by location (office), app (opening IDE = coding mode), or calendar event. The mode follows the context, not your memory.
  • Allowed lists. Per mode: which people and apps break through. Default-deny; allowlist deliberately. Most apps never earn breakthrough.
  • Emergency bypass. Repeated calls or favorites bypass — for genuine emergencies. Communicate the bypass to family so it works when needed.
  • Home/lock screen filtering. Modes can hide notification badges, dim wallpapers, filter app content (work apps hidden in personal mode). Reduce visual temptation.
  • Status sharing. Auto-reply / status visible to contacts ('in Focus until 3pm'). Sets expectations; reduces the social cost of unavailability.
  • Cross-device sync. Modes sync across phone, tablet, watch, computer. One configuration protects all screens — verify sync works.

Practical workflow

  1. Inventory interruptions. One week: note what breaks your focus, when, from which app/person. Data before design.
  2. Define 3-4 modes. Deep Work (nothing), Work (people + key apps), Personal (work apps silenced), Sleep (emergencies only). Fewer, sharper modes win.
  3. Set schedules. Work mode 9-6 weekdays, sleep mode nightly, deep-work blocks 2-3x weekly. Automatic beats manual.
  4. Build allowlists. Per mode, list who/what breaks through. Start strict; loosen only for proven need.
  5. Configure bypasses. Family favorites bypass sleep mode; repeated calls bypass deep work. Test the bypass — trust but verify.
  6. Set up triggers. Location, app-launch, or calendar triggers where supported. Remove the manual step.
  7. Share status. Enable auto-replies/status so colleagues see 'Focus until 3pm' instead of silence.
  8. Review monthly. Which interruptions still got through? Which allowed apps abused it? Tighten allowlists; adjust schedules.

Common pitfalls

  • One permanent DND. Leaving Do Not Disturb on forever, then missing genuinely important things. Modes should be contextual, not permanent.
  • Manual-only modes. Modes you must remember to toggle get toggled never. Schedule and trigger everything possible.
  • Allowlist creep. 'Just this one app' repeated monthly. Audit quarterly; most breakthrough permissions were mistakes.
  • No emergency path. So locked down that real emergencies can't reach you. Bypass for favorites/repeated calls is essential, especially overnight.
  • Ignoring the watch. Phone silenced, watch buzzing every notification. Configure wearables as part of the system, not separately.
  • Status not shared. Colleagues see silence and assume ignoring. Shared status ('in focus') converts unavailability from rude to professional.
  • Too many modes. Seven micro-modes for every mood. Nobody maintains them. Three to four sharp modes maximum.
  • Evening work leakage. No personal mode means work pings at 10pm. The boundary needs a mode, not willpower.

04 同仓库更多 Skills

TanNhatCMS
TanNhatCMS/jarvis

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.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

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.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

★ 0
TanNhatCMS
TanNhatCMS/jarvis

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

★ 0
TanNhatCMS
TanNhatCMS/jarvis

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

★ 0
TanNhatCMS
TanNhatCMS/jarvis

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).

★ 0