[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79P0EYW3BYSCSCHHR2DNHNB":3,"skill-same:01M79P0EYW3BYSCSCHHR2DNHNB":48},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M79P0EYW3BYSCSCHHR2DNHNB","growth-log",null,"Write growth log entries that extract reusable patterns from completed work — root cause, transferable rule, and a recognizable signal — instead of diary-style event narration, with a 4-8 sentence template and merge-duplicates discipline. Use when capturing what was learned after a complex task, debugging session, failure, or rollback, when reviewing progress over a period, or when a delivery gate asks what was learned.","JunMystery\u002FAgent-Guidance","JunMystery","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F161468934?v=4","01M79MTMV8F0BY8NK1A92RA8A0","Jun","01M79MTMWCFBKPHN5B25E6V20B",0,"MIT","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fgrowth-log\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: growth-log\ndescription: Write growth log entries that extract reusable patterns from completed work — root cause, transferable rule, and a recognizable signal — instead of diary-style event narration, with a 4-8 sentence template and merge-duplicates discipline. Use when capturing what was learned after a complex task, debugging session, failure, or rollback, when reviewing progress over a period, or when a delivery gate asks what was learned.\nmetadata:\n  version: 1.1.0\n  origin: ECC\n---\n\n# Growth Log Skill\n\n> **The problem:** Most people write \"fixed a bug in X\" as a learning log. That's a diary entry, not a learning artifact. A real growth log extracts the *pattern* so you recognize it next time.\n>\n> **This skill teaches:** How to write learning entries that compound across sessions. Works with any note-taking system — Markdown files, Notion, Obsidian, plain text. Templates are generic; adapt to your setup.\n\n## When to Activate\n\n- After completing a complex task (multi-file, new feature, architecture change)\n- After a failure, mistake, or \"that was harder than expected\" moment\n- When you want to review what you've learned over a period\n\n**When NOT to activate:** Trivial changes (typo fixes, single-line tweaks, config value changes with no debugging). The threshold: *did this task involve debugging, redoing, rollback, or a non-obvious decision?* If yes → write an entry. If no → skip.\n\n## The Three Rules\n\n### Rule 1: Failures > Achievements\n\nA failure is nutritionally denser than a success. One bug that took 2 hours to find teaches more than 3 features that worked first try.\n\n**Bad:** \"Successfully implemented the login flow.\"\n**Good (web dev):** \"Login flow: session token wasn't persisting because the cookie `SameSite` defaulted to `Lax` in Chrome 128+. Pattern: always explicitly set `SameSite=None; Secure` when cross-origin. Signal to recognize: auth breaks after browser upgrade or when crossing origin boundaries.\"\n**Good (data pipeline):** \"CSV import failed silently on empty rows because `pandas.read_csv(dropna=False)` keeps zero-width rows that `len()` counts as valid. Pattern: always `df.dropna(how='all', inplace=True)` before row-count validation.\"\n\n### Rule 2: The Bole Principle (伯乐原则)\n\nBefore writing a new entry, ask: *\"Is this fundamentally the same as something I already recorded?\"*\n\nSame root cause, different symptom → **merge**, don't duplicate. New root cause → new entry.\n\n**How to check:** Search existing entries for keywords from your root cause before writing. If you find a match, add your new symptom as an additional example under the existing entry rather than creating a duplicate.\n\n**Example:** \"Forgot to update the output index after creating a file\" and \"Forgot to update skill ratings after a task\" — same root cause (no automatic capture trigger). Merge into one entry about \"post-task capture gaps.\"\n\n### Rule 3: Must Be Transferable\n\nEvery entry must answer: *\"Next time I face a similar situation, what do I do differently?\"*\n\nIf you can't write that sentence, you haven't extracted the pattern yet.\n\n**How to extract a pattern from a concrete event:**\n1. State what happened in one sentence\n2. Ask \"why?\" iteratively until you reach root cause (usually 3-5 whys)\n3. Generalize: \"What class of problem is this?\" (not \"Chrome 128 bug\" but \"browser default change breaking existing behavior\")\n4. Formulate as: \"Next time I see [signal], I will [action].\"\n5. Name the signal: what specific observable tells you this pattern is active?\n\n## Entry Template\n\n**Scope:** One entry per distinct root cause. Typical length: 4-8 sentences. If it takes >2 minutes to write, you're narrating events. If \u003C30 seconds, you haven't gone deep enough.\n\n```markdown\n## [Title: the pattern, not the event]\n\n### Context\n- What was I trying to do?\n- What went wrong \u002F what worked surprisingly well?\n\n### Root Cause \u002F Core Insight\n- The underlying mechanism, not just the symptom\n\n### The Pattern (transferable)\n- Next time [similar situation], I will [specific action].\n- Signal to recognize: [what observable tells me this pattern is active?]\n\n### Related\n- [entry-name](..\u002Fpath\u002Fto\u002Frelated-entry.md)\n```\n\n## Entry Types\n\nAll four types use the template above. The type determines which sections carry the most weight:\n\n| Type | When to Use | Emphasis | Example Title |\n|------|------------|----------|---------------|\n| **Failure** | Something broke, needed debugging, or required rework | Root Cause | \"Config inheritance ≠ behavior inheritance across sessions\" |\n| **Methodology** | A repeatable process emerged from the work | Context \u002F Pattern | \"PPT → open-book exam study guide: three-layer structure\" |\n| **Pattern Discovery** | A reusable insight about tools, systems, or thinking | Pattern section | \"PR description template: describe the gap, not the feature\" |\n| **Capability Change** | A measurable skill improvement | Context (before vs after) | \"Git: from clone\u002Fpush to independent PR with 12 commits\" |\n\n## Quality Checklist\n\nBefore finalizing a growth log entry:\n\n- [ ] Does the title name the *pattern*, not the event?\n- [ ] Is there a \"Next time I will...\" sentence?\n- [ ] Is the \"Signal to recognize\" specific enough to trigger the pattern next time?\n- [ ] Did I search existing entries for duplicates before writing? (Bole Principle)\n- [ ] Is the root cause distinguished from the symptom?\n- [ ] Are related memories cross-linked?\n- [ ] Is the entry 4-8 sentences? Shorter = too shallow; longer = narrating events.\n\n## Anti-Patterns\n\n- Avoid: \"Fixed bug in payment module\" (event, not pattern)\n- Avoid: Copying the git commit message verbatim (commits describe what changed; logs extract why it matters)\n- Avoid: Writing an entry for every commit (only when a pattern emerges)\n- Avoid: Skipping the transferable sentence (without it, it's just a diary — this is non-negotiable)\n- Avoid: Duplicating the same pattern under different titles (violates Bole Principle — search before writing)\n\n## Storage\n\nStore entries wherever you keep notes. Common patterns:\n- Markdown files in a `growth-log\u002F` directory (one file per day: `YYYY-MM-DD.md`)\n- A dedicated section in Notion, Obsidian, or your note-taking app\n- Plain text files with a consistent naming convention\n\nPick one convention and stick to it. Searchability matters more than format.\n\n## If You Use Delivery Gate\n\nThe `delivery-gate` Stop hook checks that learning files were modified today via filesystem timestamps. This skill teaches *what to write* — so the file that delivery-gate checks actually contains useful patterns, not empty timestamps.\n\n```\nTask completes → delivery-gate checks: was the learning file touched today?\n  → Stale (no file modified): block — \"what did you learn?\"\n  → Fresh (file touched): pass — this skill ensures the content is useful\n```\n\nHaving enforcement without methodology → empty entries. Having methodology without enforcement → forgotten captures. Each is independently useful; together they close the loop.\n","# Growth Log Skill\n\n> **The problem:** Most people write \"fixed a bug in X\" as a learning log. That's a diary entry, not a learning artifact. A real growth log extracts the *pattern* so you recognize it next time.\n>\n> **This skill teaches:** How to write learning entries that compound across sessions. Works with any note-taking system — Markdown files, Notion, Obsidian, plain text. Templates are generic; adapt to your setup.\n\n## When to Activate\n\n- After completing a complex task (multi-file, new feature, architecture change)\n- After a failure, mistake, or \"that was harder than expected\" moment\n- When you want to review what you've learned over a period\n\n**When NOT to activate:** Trivial changes (typo fixes, single-line tweaks, config value changes with no debugging). The threshold: *did this task involve debugging, redoing, rollback, or a non-obvious decision?* If yes → write an entry. If no → skip.\n\n## The Three Rules\n\n### Rule 1: Failures > Achievements\n\nA failure is nutritionally denser than a success. One bug that took 2 hours to find teaches more than 3 features that worked first try.\n\n**Bad:** \"Successfully implemented the login flow.\"\n**Good (web dev):** \"Login flow: session token wasn't persisting because the cookie `SameSite` defaulted to `Lax` in Chrome 128+. Pattern: always explicitly set `SameSite=None; Secure` when cross-origin. Signal to recognize: auth breaks after browser upgrade or when crossing origin boundaries.\"\n**Good (data pipeline):** \"CSV import failed silently on empty rows because `pandas.read_csv(dropna=False)` keeps zero-width rows that `len()` counts as valid. Pattern: always `df.dropna(how='all', inplace=True)` before row-count validation.\"\n\n### Rule 2: The Bole Principle (伯乐原则)\n\nBefore writing a new entry, ask: *\"Is this fundamentally the same as something I already recorded?\"*\n\nSame root cause, different symptom → **merge**, don't duplicate. New root cause → new entry.\n\n**How to check:** Search existing entries for keywords from your root cause before writing. If you find a match, add your new symptom as an additional example under the existing entry rather than creating a duplicate.\n\n**Example:** \"Forgot to update the output index after creating a file\" and \"Forgot to update skill ratings after a task\" — same root cause (no automatic capture trigger). Merge into one entry about \"post-task capture gaps.\"\n\n### Rule 3: Must Be Transferable\n\nEvery entry must answer: *\"Next time I face a similar situation, what do I do differently?\"*\n\nIf you can't write that sentence, you haven't extracted the pattern yet.\n\n**How to extract a pattern from a concrete event:**\n1. State what happened in one sentence\n2. Ask \"why?\" iteratively until you reach root cause (usually 3-5 whys)\n3. Generalize: \"What class of problem is this?\" (not \"Chrome 128 bug\" but \"browser default change breaking existing behavior\")\n4. Formulate as: \"Next time I see [signal], I will [action].\"\n5. Name the signal: what specific observable tells you this pattern is active?\n\n## Entry Template\n\n**Scope:** One entry per distinct root cause. Typical length: 4-8 sentences. If it takes >2 minutes to write, you're narrating events. If \u003C30 seconds, you haven't gone deep enough.\n\n```markdown\n## [Title: the pattern, not the event]\n\n### Context\n- What was I trying to do?\n- What went wrong \u002F what worked surprisingly well?\n\n### Root Cause \u002F Core Insight\n- The underlying mechanism, not just the symptom\n\n### The Pattern (transferable)\n- Next time [similar situation], I will [specific action].\n- Signal to recognize: [what observable tells me this pattern is active?]\n\n### Related\n- [entry-name](..\u002Fpath\u002Fto\u002Frelated-entry.md)\n```\n\n## Entry Types\n\nAll four types use the template above. The type determines which sections carry the most weight:\n\n| Type | When to Use | Emphasis | Example Title |\n|------|------------|----------|---------------|\n| **Failure** | Something broke, needed debugging, or required rework | Root Cause | \"Config inheritance ≠ behavior inheritance across sessions\" |\n| **Methodology** | A repeatable process emerged from the work | Context \u002F Pattern | \"PPT → open-book exam study guide: three-layer structure\" |\n| **Pattern Discovery** | A reusable insight about tools, systems, or thinking | Pattern section | \"PR description template: describe the gap, not the feature\" |\n| **Capability Change** | A measurable skill improvement | Context (before vs after) | \"Git: from clone\u002Fpush to independent PR with 12 commits\" |\n\n## Quality Checklist\n\nBefore finalizing a growth log entry:\n\n- [ ] Does the title name the *pattern*, not the event?\n- [ ] Is there a \"Next time I will...\" sentence?\n- [ ] Is the \"Signal to recognize\" specific enough to trigger the pattern next time?\n- [ ] Did I search existing entries for duplicates before writing? (Bole Principle)\n- [ ] Is the root cause distinguished from the symptom?\n- [ ] Are related memories cross-linked?\n- [ ] Is the entry 4-8 sentences? Shorter = too shallow; longer = narrating events.\n\n## Anti-Patterns\n\n- Avoid: \"Fixed bug in payment module\" (event, not pattern)\n- Avoid: Copying the git commit message verbatim (commits describe what changed; logs extract why it matters)\n- Avoid: Writing an entry for every commit (only when a pattern emerges)\n- Avoid: Skipping the transferable sentence (without it, it's just a diary — this is non-negotiable)\n- Avoid: Duplicating the same pattern under different titles (violates Bole Principle — search before writing)\n\n## Storage\n\nStore entries wherever you keep notes. Common patterns:\n- Markdown files in a `growth-log\u002F` directory (one file per day: `YYYY-MM-DD.md`)\n- A dedicated section in Notion, Obsidian, or your note-taking app\n- Plain text files with a consistent naming convention\n\nPick one convention and stick to it. Searchability matters more than format.\n\n## If You Use Delivery Gate\n\nThe `delivery-gate` Stop hook checks that learning files were modified today via filesystem timestamps. This skill teaches *what to write* — so the file that delivery-gate checks actually contains useful patterns, not empty timestamps.\n\n```\nTask completes → delivery-gate checks: was the learning file touched today?\n  → Stale (no file modified): block — \"what did you learn?\"\n  → Fresh (file touched): pass — this skill ensures the content is useful\n```\n\nHaving enforcement without methodology → empty entries. Having methodology without enforcement → forgotten captures. Each is independently useful; together they close the loop.\n",{"name":5,"metadata":24,"description":7},{"origin":25,"version":26},"ECC","1.1.0","main","5d0a87185c0e172c3901e2a6e5916b6d544b8b94","skills\u002Fgrowth-log","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance","https:\u002F\u002Fgithub.com\u002FJunMystery","AI is the typist, I am the architect. Building efficient, secure, and user-centric products through disciplined AI prompt engineering.","2026-11-13 17:41:25",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add JunMystery\u002FAgent-Guidance --skill growth-log",{"tool":40,"command":41},"bunx","bunx skills add JunMystery\u002FAgent-Guidance --skill growth-log",{"tool":43,"command":44},"pnpm","pnpm dlx skills add JunMystery\u002FAgent-Guidance --skill growth-log","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fgrowth-log\u002FSKILL.md",true,[],[49,55,61,67,73,79],{"skillNo":50,"name":51,"nameZh":6,"description":6,"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},"01M79QR1E309VJ6CTQKB32AWWA","zero-trust-architecture-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-architecture-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79QQV7GHYR02DYGN41S23WN","xss-filter-evasion-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxss-filter-evasion-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79QQNSN7YB8XB61FFSCS3WH","xs-leaks-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxs-leaks-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79QQHZZJKFDY9132G5A65C2","xpath-injection-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxpath-injection-prevention-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M79QQB9ZSD3DJG8658EHQXR1","xml-security-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-security-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79QQ60WKV7PFMXWT9CW8PM6","xml-external-entity-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-external-entity-prevention-cheat-sheet\u002FSKILL.md",[],[]]