[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EN7G0GGPF3ZFH3DWRPMSB9":3,"skill-same:01M7EN7G0GGPF3ZFH3DWRPMSB9":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},"01M7EN7G0GGPF3ZFH3DWRPMSB9","ams-habit-tracker",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-habit-tracker\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: habit-tracker\ndescription: Design habit systems that stick: habit selection, tracking methods, streaks, environment design, and recovery from slips. Use when building new routines or fixing ones that keep failing.\ncategory: productivity\n---\n\n# Habit Tracker\n\n## Overview\n\nHabits are behaviors on autopilot — the closest thing to free productivity.\n\nFormation loop: cue -> routine -> reward. Tracking adds feedback: the checkmark becomes part of the reward.\n\nTracking alone doesn't build habits. The habit must be tiny, cue-linked, and rewarding enough to repeat.\n\nEffective systems: 3-7 habits max, seconds-per-day tracking, misses treated as data not failure.\n\nDesign for your lowest-energy self. Motivation starts habits; systems sustain them.\n\n## When to use\n\n- Starting new habits (exercise, reading, meditation, writing, languages)\n- Breaking bad habits by replacing them with better ones\n- Choosing a habit-tracking app or analog method\n- Recovering after falling off a routine\n- Designing team or family habit challenges\n\n## Core concepts\n\n- **Start ridiculously small.**\n  'Read 2 pages' sticks; 'read 20 pages' fails. Initial goal is showing up, not output. Scale after the identity forms.\n- **Habit stacking.**\n  Attach to an existing habit: 'After coffee, I journal.' Existing habits are the most reliable cues available.\n- **Implementation intentions.**\n  'I will [behavior] at [time] in [location].' Specificity beats motivation. 'Walk 15 min at 7am' works; 'exercise more' doesn't.\n- **Environment design.**\n  Good habits obvious (shoes by door), bad habits hard (phone in another room). Willpower is unreliable; friction is forever.\n- **Never miss twice.**\n  One miss is an accident; two is a new habit of skipping. After a slip, resume immediately — never 'restart Monday.'\n- **Identity over outcomes.**\n  'I'm a reader' outlasts 'lose 5kg.' Each completion is a vote for the identity. Track the votes.\n- **Track, don't judge.**\n  The tracker is a dashboard, not a courtroom. Gaps reveal obstacles to design around, not failures to feel bad about.\n- **Minimum viable version.**\n  Define the bad-day version of each habit explicitly. The 2-minute version keeps the streak of showing up alive.\n\n## Practical workflow\n\n1. **Choose 3-5 habits max.**\n   Fewer than you want. Each under 10 minutes initially, with a 2-minute starter version for bad days.\n2. **Write implementation intentions.**\n   Exact behavior, cue, time, place — plus the minimum version. Vague plans produce vague results.\n3. **Pick a tracking method.**\n   App, spreadsheet, wall calendar, notebook grid. Under 10 seconds per habit per day, visible, satisfying to mark.\n4. **Design the environment first.**\n   Change one thing per habit before day one: reduce friction or add a cue. Don't wait to fail first.\n5. **Set a weekly review.**\n   Which habits are automatic? Which need redesign (size, cue, time) rather than more willpower? Adjust the system.\n6. **Handle slips by protocol.**\n   Miss once: note cause, resume tomorrow. Miss twice: shrink the habit or change the cue immediately.\n7. **Evolve quarterly.**\n   Graduate easy habits, retire automatic ones from active tracking, add one new habit at a time. Keep the list short forever.\n8. **Pair habits with rewards.**\n   After the routine, something genuinely pleasant — even just marking the X. The loop needs its reward to close.\n\n## Common pitfalls\n\n- **Too many habits at once.**\n  Ten new habits in January, zero by February. One at a time is faster long-term because it survives.\n- **All-or-nothing tracking.**\n  Binary pass\u002Ffail punishes the 20-minute walk that was still worthwhile. Partial credit keeps showing up alive.\n- **Tracking without design.**\n  Logging failures for months without changing cue, size, or environment. Data without redesign is a guilt log.\n- **Streak obsession.**\n  A broken 100-day streak can end the habit ('it's ruined'). Value the 90%-of-days trend over the unbroken chain.\n- **Vague habits.**\n  'Be healthier' can't be tracked. 'No soda on weekdays' can. No checkmark possible = not a habit yet.\n- **Relying on motivation.**\n  Design every habit for your busiest, most distracted, lowest-energy self — that's who has to do it.\n- **Punishing rest.**\n  7-days-a-week with no recovery leads to burnout and abandonment. Schedule rest days deliberately.\n- **Copying someone's stack.**\n  Borrow principles, not schedules. Build from your life, chronotype, and constraints — not an influencer's routine.\n","# Habit Tracker\n\n## Overview\n\nHabits are behaviors on autopilot — the closest thing to free productivity.\n\nFormation loop: cue -> routine -> reward. Tracking adds feedback: the checkmark becomes part of the reward.\n\nTracking alone doesn't build habits. The habit must be tiny, cue-linked, and rewarding enough to repeat.\n\nEffective systems: 3-7 habits max, seconds-per-day tracking, misses treated as data not failure.\n\nDesign for your lowest-energy self. Motivation starts habits; systems sustain them.\n\n## When to use\n\n- Starting new habits (exercise, reading, meditation, writing, languages)\n- Breaking bad habits by replacing them with better ones\n- Choosing a habit-tracking app or analog method\n- Recovering after falling off a routine\n- Designing team or family habit challenges\n\n## Core concepts\n\n- **Start ridiculously small.**\n  'Read 2 pages' sticks; 'read 20 pages' fails. Initial goal is showing up, not output. Scale after the identity forms.\n- **Habit stacking.**\n  Attach to an existing habit: 'After coffee, I journal.' Existing habits are the most reliable cues available.\n- **Implementation intentions.**\n  'I will [behavior] at [time] in [location].' Specificity beats motivation. 'Walk 15 min at 7am' works; 'exercise more' doesn't.\n- **Environment design.**\n  Good habits obvious (shoes by door), bad habits hard (phone in another room). Willpower is unreliable; friction is forever.\n- **Never miss twice.**\n  One miss is an accident; two is a new habit of skipping. After a slip, resume immediately — never 'restart Monday.'\n- **Identity over outcomes.**\n  'I'm a reader' outlasts 'lose 5kg.' Each completion is a vote for the identity. Track the votes.\n- **Track, don't judge.**\n  The tracker is a dashboard, not a courtroom. Gaps reveal obstacles to design around, not failures to feel bad about.\n- **Minimum viable version.**\n  Define the bad-day version of each habit explicitly. The 2-minute version keeps the streak of showing up alive.\n\n## Practical workflow\n\n1. **Choose 3-5 habits max.**\n   Fewer than you want. Each under 10 minutes initially, with a 2-minute starter version for bad days.\n2. **Write implementation intentions.**\n   Exact behavior, cue, time, place — plus the minimum version. Vague plans produce vague results.\n3. **Pick a tracking method.**\n   App, spreadsheet, wall calendar, notebook grid. Under 10 seconds per habit per day, visible, satisfying to mark.\n4. **Design the environment first.**\n   Change one thing per habit before day one: reduce friction or add a cue. Don't wait to fail first.\n5. **Set a weekly review.**\n   Which habits are automatic? Which need redesign (size, cue, time) rather than more willpower? Adjust the system.\n6. **Handle slips by protocol.**\n   Miss once: note cause, resume tomorrow. Miss twice: shrink the habit or change the cue immediately.\n7. **Evolve quarterly.**\n   Graduate easy habits, retire automatic ones from active tracking, add one new habit at a time. Keep the list short forever.\n8. **Pair habits with rewards.**\n   After the routine, something genuinely pleasant — even just marking the X. The loop needs its reward to close.\n\n## Common pitfalls\n\n- **Too many habits at once.**\n  Ten new habits in January, zero by February. One at a time is faster long-term because it survives.\n- **All-or-nothing tracking.**\n  Binary pass\u002Ffail punishes the 20-minute walk that was still worthwhile. Partial credit keeps showing up alive.\n- **Tracking without design.**\n  Logging failures for months without changing cue, size, or environment. Data without redesign is a guilt log.\n- **Streak obsession.**\n  A broken 100-day streak can end the habit ('it's ruined'). Value the 90%-of-days trend over the unbroken chain.\n- **Vague habits.**\n  'Be healthier' can't be tracked. 'No soda on weekdays' can. No checkmark possible = not a habit yet.\n- **Relying on motivation.**\n  Design every habit for your busiest, most distracted, lowest-energy self — that's who has to do it.\n- **Punishing rest.**\n  7-days-a-week with no recovery leads to burnout and abandonment. Schedule rest days deliberately.\n- **Copying someone's stack.**\n  Borrow principles, not schedules. Build from your life, chronotype, and constraints — not an influencer's routine.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-habit-tracker",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-habit-tracker",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-habit-tracker",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-habit-tracker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-habit-tracker\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",[],[]]