[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVWRW8GF1G0BNXDA2NMFN0":3,"skill-same:01M7EVWRW8GF1G0BNXDA2NMFN0":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},"01M7EVWRW8GF1G0BNXDA2NMFN0","ams-senior-frontend",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-senior-frontend\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: senior-frontend\ndescription: Senior frontend engineer perspective: component architecture, state management, rendering performance, and UX trade-offs. Use when designing UI features, reviewing frontend code, or choosing client-side patterns.\ncategory: development\n---\n\n# Senior Frontend Engineer\n\n## Overview\n\nA senior frontend engineer thinks in **user-perceived outcomes**: time to interactive, jank-free\nscrolling, accessible interactions, and UI that survives bad networks and weird data. This skill\ncaptures how that role approaches frontend work — component boundaries, where state lives, what\nrenders when and why, and how to keep a growing client codebase changeable instead of brittle.\n\nThe through-line: the browser is a hostile, underpowered, unpredictable runtime. Design for it.\n\n## When to use\n\n- Designing a new feature's component structure and data flow.\n- Reviewing frontend code for architecture, performance, or accessibility issues.\n- Choosing between state management approaches (local state, context, stores, server cache).\n- Debugging rendering performance: slow lists, layout thrash, input lag.\n- Deciding what goes client-side vs server-side (SSR, hydration, islands).\n\n## Core concepts\n\n- **Components are boundaries, not folders.** A good component owns one piece of UI *and* the logic\n  that can only live with it. If two components always change together, they're one component. If a\n  component needs ten props to render, its boundary is wrong.\n- **State colocation.** Keep state as low as possible — in the component that uses it. Lift state\n  only when siblings genuinely share it. Global state is for *global* things (auth session, theme),\n  not for avoiding prop passing.\n- **Server state ≠ client state.** Fetched data is a cache with staleness, retries, and invalidation —\n  treat it with a data-fetching library, not hand-rolled `useEffect` fetch spaghetti. UI state\n  (open modals, form drafts) lives separately and dies with the view.\n- **Rendering budget.** Every render should be explainable. Memoization is a targeted fix for measured\n  problems, not a default — wrapping everything in `memo` trades one performance problem for a\n  correctness-and-complexity problem.\n- **Progressive enhancement mindset.** The UI must communicate state: loading, empty, error, offline.\n  Design these four states *first*; the happy path is the easy part.\n- **Accessibility is correctness.** Keyboard operability, focus management, semantic HTML, and\n  sufficient contrast are not polish — a modal that traps no focus is a broken modal.\n\n## Practical workflow\n\n1. **Start from states, not screens.** List every state the feature can be in (loading, empty, error,\n   partial, offline, permission-denied) and sketch each before writing components.\n2. **Draw the data flow.** For each piece of state, name its owner, its readers, and its lifetime.\n   If you can't name the owner, the design isn't done.\n3. **Choose rendering strategy deliberately:**\n   - Static content → static generation \u002F CDN.\n   - Personalized but cacheable → SSR with caching.\n   - Highly interactive islands → hydrate selectively, not the whole page.\n4. **Build the skeleton first** — layout, loading states, error boundaries — then fill in behavior.\n   Users judge speed by when *something meaningful* appears, not when JS finishes.\n5. **Measure before optimizing.** Profile with devtools: which components re-render on each keystroke?\n   Virtualize lists over ~100 rows, debounce expensive work, move work off the main thread only when\n   profiling says the main thread is the bottleneck.\n6. **Review checklist for every PR:**\n   - Keyboard path works; focus visible and logical; no focus loss on dialogs.\n   - No layout shift on load (reserve space for async content).\n   - Works at 320px width and 200% zoom.\n   - Failed requests show a recoverable error state, not a blank screen.\n\nExample state-ownership decision:\n\n```text\nFeature: dashboard with filterable table\n- filters (UI state)      → owned by FilterBar, lifted to Dashboard only because Table needs them\n- table rows (server)     → fetched via query hook, cached by filter key, stale-while-revalidate\n- selected rows (UI)      → owned by Table; cleared when filters change (lifetime = one query)\n- export job (server)     → mutation; progress polled; NOT in global store\n```\n\n## Common pitfalls\n\n- **Prop drilling panic.** Reaching for a global store because props feel tedious. Two levels of\n  props is fine; the store is for cross-cutting concerns, not convenience.\n- **Effect-driven fetching chains.** `useEffect` that fetches, sets state, triggers another effect.\n  This is where race conditions and double-fetches breed — use a query library with request keys.\n- **Ignoring the loading\u002Ferror\u002Fempty states** until QA finds them. They're the majority of real-world\n  renders on flaky networks.\n- **Premature memoization.** `useMemo`\u002F`memo` everywhere \"for performance\" without a profile to\n  justify it — now renders are unpredictable and the code is harder to read.\n- **Hydration mismatches.** Rendering different HTML on server and client (dates, random IDs,\n  `window` checks) causes flicker and bugs. Render deterministically; defer client-only bits.\n- **Div soup.** `\u003Cdiv onClick>` instead of `\u003Cbutton>`: no keyboard support, no semantics, no focus.\n  Use the platform's elements first, custom ARIA second.\n- **Chasing frameworks over fundamentals.** The senior move is knowing *when not to add* a library:\n  every dependency is a liability you didn't write and can't fully control.\n","# Senior Frontend Engineer\n\n## Overview\n\nA senior frontend engineer thinks in **user-perceived outcomes**: time to interactive, jank-free\nscrolling, accessible interactions, and UI that survives bad networks and weird data. This skill\ncaptures how that role approaches frontend work — component boundaries, where state lives, what\nrenders when and why, and how to keep a growing client codebase changeable instead of brittle.\n\nThe through-line: the browser is a hostile, underpowered, unpredictable runtime. Design for it.\n\n## When to use\n\n- Designing a new feature's component structure and data flow.\n- Reviewing frontend code for architecture, performance, or accessibility issues.\n- Choosing between state management approaches (local state, context, stores, server cache).\n- Debugging rendering performance: slow lists, layout thrash, input lag.\n- Deciding what goes client-side vs server-side (SSR, hydration, islands).\n\n## Core concepts\n\n- **Components are boundaries, not folders.** A good component owns one piece of UI *and* the logic\n  that can only live with it. If two components always change together, they're one component. If a\n  component needs ten props to render, its boundary is wrong.\n- **State colocation.** Keep state as low as possible — in the component that uses it. Lift state\n  only when siblings genuinely share it. Global state is for *global* things (auth session, theme),\n  not for avoiding prop passing.\n- **Server state ≠ client state.** Fetched data is a cache with staleness, retries, and invalidation —\n  treat it with a data-fetching library, not hand-rolled `useEffect` fetch spaghetti. UI state\n  (open modals, form drafts) lives separately and dies with the view.\n- **Rendering budget.** Every render should be explainable. Memoization is a targeted fix for measured\n  problems, not a default — wrapping everything in `memo` trades one performance problem for a\n  correctness-and-complexity problem.\n- **Progressive enhancement mindset.** The UI must communicate state: loading, empty, error, offline.\n  Design these four states *first*; the happy path is the easy part.\n- **Accessibility is correctness.** Keyboard operability, focus management, semantic HTML, and\n  sufficient contrast are not polish — a modal that traps no focus is a broken modal.\n\n## Practical workflow\n\n1. **Start from states, not screens.** List every state the feature can be in (loading, empty, error,\n   partial, offline, permission-denied) and sketch each before writing components.\n2. **Draw the data flow.** For each piece of state, name its owner, its readers, and its lifetime.\n   If you can't name the owner, the design isn't done.\n3. **Choose rendering strategy deliberately:**\n   - Static content → static generation \u002F CDN.\n   - Personalized but cacheable → SSR with caching.\n   - Highly interactive islands → hydrate selectively, not the whole page.\n4. **Build the skeleton first** — layout, loading states, error boundaries — then fill in behavior.\n   Users judge speed by when *something meaningful* appears, not when JS finishes.\n5. **Measure before optimizing.** Profile with devtools: which components re-render on each keystroke?\n   Virtualize lists over ~100 rows, debounce expensive work, move work off the main thread only when\n   profiling says the main thread is the bottleneck.\n6. **Review checklist for every PR:**\n   - Keyboard path works; focus visible and logical; no focus loss on dialogs.\n   - No layout shift on load (reserve space for async content).\n   - Works at 320px width and 200% zoom.\n   - Failed requests show a recoverable error state, not a blank screen.\n\nExample state-ownership decision:\n\n```text\nFeature: dashboard with filterable table\n- filters (UI state)      → owned by FilterBar, lifted to Dashboard only because Table needs them\n- table rows (server)     → fetched via query hook, cached by filter key, stale-while-revalidate\n- selected rows (UI)      → owned by Table; cleared when filters change (lifetime = one query)\n- export job (server)     → mutation; progress polled; NOT in global store\n```\n\n## Common pitfalls\n\n- **Prop drilling panic.** Reaching for a global store because props feel tedious. Two levels of\n  props is fine; the store is for cross-cutting concerns, not convenience.\n- **Effect-driven fetching chains.** `useEffect` that fetches, sets state, triggers another effect.\n  This is where race conditions and double-fetches breed — use a query library with request keys.\n- **Ignoring the loading\u002Ferror\u002Fempty states** until QA finds them. They're the majority of real-world\n  renders on flaky networks.\n- **Premature memoization.** `useMemo`\u002F`memo` everywhere \"for performance\" without a profile to\n  justify it — now renders are unpredictable and the code is harder to read.\n- **Hydration mismatches.** Rendering different HTML on server and client (dates, random IDs,\n  `window` checks) causes flicker and bugs. Render deterministically; defer client-only bits.\n- **Div soup.** `\u003Cdiv onClick>` instead of `\u003Cbutton>`: no keyboard support, no semantics, no focus.\n  Use the platform's elements first, custom ARIA second.\n- **Chasing frameworks over fundamentals.** The senior move is knowing *when not to add* a library:\n  every dependency is a liability you didn't write and can't fully control.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-senior-frontend",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-senior-frontend",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-senior-frontend",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-senior-frontend","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-senior-frontend\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",[],[]]