[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVPS44ET8WWTFGA3TFF6ES":3,"skill-same:01M7EVPS44ET8WWTFGA3TFF6ES":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EVPS44ET8WWTFGA3TFF6ES","regex-pro",null,"Write, test, and debug regular expressions with pattern recipes, engine quirks, and performance safety.","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-regex-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: regex-pro\ndescription: Write, test, and debug regular expressions with pattern recipes, engine quirks, and performance safety.\ncategory: utilities\n---\n\n## Overview\n\nRegular expressions are a precision instrument most people wield like a hammer. This skill covers\nwriting correct, readable, safe regex: the core syntax, pattern recipes for common tasks, testing\nmethodology, engine differences, and catastrophic backtracking — the performance trap that turns a\nbad pattern into a denial of service.\n\n## When to use\n\n- Writing patterns for validation, extraction, or search-and-replace\n\n- Debugging a regex that doesn't match (or matches too much)\n\n- Choosing between regex and simpler string methods\n\n- Reviewing regex for performance and safety\n\n- Learning regex systematically rather than by Stack Overflow\n\n## Core concepts\n\n- - **The essential syntax.** Literals, `.` (any), `\\d \\w \\s` (digit\u002Fword\u002Fspace) and negations `\\D\n  \\W \\S`, quantifiers `* + ? {n,m}`, anchors `^ $ \\b`, groups `()` with alternation `|`, character\n  classes `[]` with ranges and negation `[^]`. This covers 90% of real patterns.\n- - **Greedy vs lazy.** `.*` grabs as much as possible (greedy); `.*?` grabs as little as possible\n  (lazy). `\u003C.*>` on `\u003Cb>hi\u003C\u002Fb>` matches the whole string; `\u003C.*?>` matches `\u003Cb>`. Default greed\n  causes most \"it matched too much\" bugs.\n- - **Groups and backreferences.** `(...)` captures; `(?:...)` groups without capturing (prefer for\n  performance and clarity); `\\1` refers back to group 1. Named groups `(?P\u003Cname>...)` (Python) make\n  complex patterns readable.\n- - **Anchors change everything.** `^\\d+$` validates the entire string is digits; `\\d+` without\n  anchors finds digits anywhere. Validation without anchors isn't validation — it's searching.\n- - **Engine differences.** PCRE, JavaScript, Python `re`, Go, Java — lookbehind support, named\n  group syntax, and Unicode handling vary. Test in the target engine, not just a generic tester.\n- - **Catastrophic backtracking.** Nested quantifiers like `(a+)+$` on non-matching input cause\n  exponential blowup — a 30-character string can hang for hours. This is a security issue in\n  servers. Recognize the shape: quantified group containing quantifiers, especially with overlapping\n  character classes.\n\n## Practical workflow\n\n1. 1. **Define the language precisely.** What exactly should match? Write 5 positive and 5 negative\n   examples before writing the pattern. Vague requirements produce vague patterns.\n2. 2. **Build incrementally.** Start with the simplest core, test, then add one element at a time.\n   `^\\d{4}` → `^\\d{4}-\\d{2}` → `^\\d{4}-\\d{2}-\\d{2}$`. Each step verified before the next.\n3. 3. **Test both sides.** Every pattern gets positive tests (must match) and negative tests (must\n   not match) — including adversarial inputs: empty strings, unicode, newlines, very long strings.\n4. 4. **Prefer clarity.** Named groups, comments (`(?x)` verbose mode in Python), and breaking\n   complex patterns into multiple simpler checks. A regex nobody can read is a bug waiting to\n   happen.\n5. 5. **Consider alternatives.** Email validation via regex is a famous tarpit — use a\n   parser\u002Flibrary. HTML parsing with regex is a classic mistake — use a parser. Regex excels at:\n   delimited formats, log lines, simple tokens, search\u002Freplace.\n6. 6. **Performance-check risky patterns.** Test with pathological inputs (long non-matching\n   strings). If it hangs, rewrite: possessive quantifiers where supported, atomic groups, or\n   restructure to avoid nested quantifiers.\n\n**Common recipes:**\n- Email (pragmatic, not RFC-perfect): `^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\\.[A-Za-z]{2,}$`\n\n- URL-ish: `https?:\u002F\u002F[^\\s\u002F$.?#].[^\\s]*`\n\n- ISO date: `^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\\d|3[01])$`\n\n- Whitespace trim: `^\\s+|\\s+$` (replace with empty)\n\n- Quoted string (simple): `\"([^\"\\\\]|\\\\.)*\"` (handles escapes, avoids catastrophic backtracking)\n\n## Common pitfalls\n\n- - **Unanchored validation.** `\u002F\\d+\u002F` \"validates\" `abc123` as numeric. Anchor both ends for\n  validation.\n- - **Greedy dot.** `\".*\"` matching across multiple quoted strings. Use lazy `.*?` or negated\n  classes `[^\"]*`.\n- - **Forgetting to escape.** `.` `(` `[` `+` `*` `?` in literals. In most languages, prefer raw\n  strings (`r\"\\d+\\.\\d+\"`) to avoid backslash-escaping hell.\n- - **Catastrophic backtracking.** `(x+x+)+y` style patterns on user input. Audit any regex that\n  processes untrusted input — it's a ReDoS vector.\n- - **Over-engineering.** A 200-character email regex that's still wrong. Match the requirement's\n  actual strictness; use libraries for genuinely complex grammars.\n- - **Not testing the engine.** A pattern tested on regex101 with PCRE flavor failing in JavaScript\n  (no lookbehind in older JS) or Go (no backreferences). Always verify in the deployment engine.\n","## Overview\n\nRegular expressions are a precision instrument most people wield like a hammer. This skill covers\nwriting correct, readable, safe regex: the core syntax, pattern recipes for common tasks, testing\nmethodology, engine differences, and catastrophic backtracking — the performance trap that turns a\nbad pattern into a denial of service.\n\n## When to use\n\n- Writing patterns for validation, extraction, or search-and-replace\n\n- Debugging a regex that doesn't match (or matches too much)\n\n- Choosing between regex and simpler string methods\n\n- Reviewing regex for performance and safety\n\n- Learning regex systematically rather than by Stack Overflow\n\n## Core concepts\n\n- - **The essential syntax.** Literals, `.` (any), `\\d \\w \\s` (digit\u002Fword\u002Fspace) and negations `\\D\n  \\W \\S`, quantifiers `* + ? {n,m}`, anchors `^ $ \\b`, groups `()` with alternation `|`, character\n  classes `[]` with ranges and negation `[^]`. This covers 90% of real patterns.\n- - **Greedy vs lazy.** `.*` grabs as much as possible (greedy); `.*?` grabs as little as possible\n  (lazy). `\u003C.*>` on `\u003Cb>hi\u003C\u002Fb>` matches the whole string; `\u003C.*?>` matches `\u003Cb>`. Default greed\n  causes most \"it matched too much\" bugs.\n- - **Groups and backreferences.** `(...)` captures; `(?:...)` groups without capturing (prefer for\n  performance and clarity); `\\1` refers back to group 1. Named groups `(?P\u003Cname>...)` (Python) make\n  complex patterns readable.\n- - **Anchors change everything.** `^\\d+$` validates the entire string is digits; `\\d+` without\n  anchors finds digits anywhere. Validation without anchors isn't validation — it's searching.\n- - **Engine differences.** PCRE, JavaScript, Python `re`, Go, Java — lookbehind support, named\n  group syntax, and Unicode handling vary. Test in the target engine, not just a generic tester.\n- - **Catastrophic backtracking.** Nested quantifiers like `(a+)+$` on non-matching input cause\n  exponential blowup — a 30-character string can hang for hours. This is a security issue in\n  servers. Recognize the shape: quantified group containing quantifiers, especially with overlapping\n  character classes.\n\n## Practical workflow\n\n1. 1. **Define the language precisely.** What exactly should match? Write 5 positive and 5 negative\n   examples before writing the pattern. Vague requirements produce vague patterns.\n2. 2. **Build incrementally.** Start with the simplest core, test, then add one element at a time.\n   `^\\d{4}` → `^\\d{4}-\\d{2}` → `^\\d{4}-\\d{2}-\\d{2}$`. Each step verified before the next.\n3. 3. **Test both sides.** Every pattern gets positive tests (must match) and negative tests (must\n   not match) — including adversarial inputs: empty strings, unicode, newlines, very long strings.\n4. 4. **Prefer clarity.** Named groups, comments (`(?x)` verbose mode in Python), and breaking\n   complex patterns into multiple simpler checks. A regex nobody can read is a bug waiting to\n   happen.\n5. 5. **Consider alternatives.** Email validation via regex is a famous tarpit — use a\n   parser\u002Flibrary. HTML parsing with regex is a classic mistake — use a parser. Regex excels at:\n   delimited formats, log lines, simple tokens, search\u002Freplace.\n6. 6. **Performance-check risky patterns.** Test with pathological inputs (long non-matching\n   strings). If it hangs, rewrite: possessive quantifiers where supported, atomic groups, or\n   restructure to avoid nested quantifiers.\n\n**Common recipes:**\n- Email (pragmatic, not RFC-perfect): `^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\\.[A-Za-z]{2,}$`\n\n- URL-ish: `https?:\u002F\u002F[^\\s\u002F$.?#].[^\\s]*`\n\n- ISO date: `^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\\d|3[01])$`\n\n- Whitespace trim: `^\\s+|\\s+$` (replace with empty)\n\n- Quoted string (simple): `\"([^\"\\\\]|\\\\.)*\"` (handles escapes, avoids catastrophic backtracking)\n\n## Common pitfalls\n\n- - **Unanchored validation.** `\u002F\\d+\u002F` \"validates\" `abc123` as numeric. Anchor both ends for\n  validation.\n- - **Greedy dot.** `\".*\"` matching across multiple quoted strings. Use lazy `.*?` or negated\n  classes `[^\"]*`.\n- - **Forgetting to escape.** `.` `(` `[` `+` `*` `?` in literals. In most languages, prefer raw\n  strings (`r\"\\d+\\.\\d+\"`) to avoid backslash-escaping hell.\n- - **Catastrophic backtracking.** `(x+x+)+y` style patterns on user input. Audit any regex that\n  processes untrusted input — it's a ReDoS vector.\n- - **Over-engineering.** A 200-character email regex that's still wrong. Match the requirement's\n  actual strictness; use libraries for genuinely complex grammars.\n- - **Not testing the engine.** A pattern tested on regex101 with PCRE flavor failing in JavaScript\n  (no lookbehind in older JS) or Go (no backreferences). Always verify in the deployment engine.\n",{"name":5,"category":24,"description":7},"utilities","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-regex-pro",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill regex-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill regex-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill regex-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-regex-pro\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"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":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"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",[],[]]