[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BVP3NPQ296A2J30WAM4STB":3,"skill-same:01M6BVP3NPQ296A2J30WAM4STB":111},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6BVP3NPQ296A2J30WAM4STB","hindsight-cloud",null,"Store team knowledge, project conventions, and learnings from tasks. Use to remember what works and recall context before new tasks. Connects to Hindsight Cloud. (user)","feniix\u002Fdotfiles","feniix","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F91633?v=4","01M6BVMJ0Q5E6HZ4JTEWYBBKV9","Sebastian B Otaegui","01M6BVMJ53ZV8DFKXTRBPESTF3",8,"MIT","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fhindsight-cloud\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"cloud","hindsight","hindsight cloud","context","new","recall context","store","project","conventions","learnings","use","user","remember","recall","knowledge","team","tasks","project conventions","2026-11-10 10:12:30",false,"---\nname: hindsight-cloud\ndescription: Store team knowledge, project conventions, and learnings from tasks. Use to remember what works and recall context before new tasks. Connects to Hindsight Cloud. (user)\n---\n\n# Hindsight Memory Skill (Cloud)\n\nYou have persistent memory via **Hindsight Cloud**. This memory bank is **shared with the team**, so knowledge stored here benefits everyone working on this codebase.\n\n**Recall context before tasks, and propose team knowledge worth keeping.** Because the bank is shared with the team, **never store anything without asking the user first**: show what you would store and wait for a yes.\n\n## Setup Check (First-Time Only)\n\nBefore using memory commands, verify the Hindsight CLI is configured. The config file holds the API key, so never print it (no `cat`, `less` or `grep` without `-q`); only check that it is there:\n\n```bash\nif [ -s ~\u002F.hindsight\u002Fconfig ] && grep -q '^[[:space:]]*api_key[[:space:]]*=' ~\u002F.hindsight\u002Fconfig; then\n  echo \"hindsight: configured\"\nelse\n  echo \"hindsight: not configured\"\nfi\n```\n\n**If it reports not configured**, help the user set it up:\n\n1. **Install the CLI** (if `hindsight` command not found):\n   ```bash\n   curl -fsSL https:\u002F\u002Fhindsight.vectorize.io\u002Fget-cli | bash\n   ```\n\n2. **Create the config file** - ask the user for their **API Key** (get it from https:\u002F\u002Fui.hindsight.vectorize.io):\n   ```bash\n   mkdir -p ~\u002F.hindsight\n   cat > ~\u002F.hindsight\u002Fconfig \u003C\u003C 'EOF'\n   api_url = \"https:\u002F\u002Fapi.hindsight.vectorize.io\"\n   api_key = \"\u003Cuser's API key>\"\n   EOF\n   chmod 600 ~\u002F.hindsight\u002Fconfig\n   ```\n\n3. **Get the bank ID** - ask the user for their team's bank ID (e.g., `team-myproject`)\n\nAfter setup, use the bank ID in all commands below.\n\n## How Hindsight Works\n\nWhen you call `retain`, Hindsight does **not** store the string as-is. The server runs an internal pipeline that:\n\n1. **Extracts structured facts** from the content using an LLM\n2. **Identifies entities** (people, tools, concepts) and links related facts\n3. **Builds temporal and causal relationships** between facts\n4. **Generates embeddings** for semantic search\n\nThis means you should pass **rich, full-context content** — the server is better at extracting what matters than a pre-summarized string. Your job is to decide **when** to store, not **what** to extract.\n\n## Commands\n\nReplace `\u003Cbank-id>` with the user's actual bank ID (e.g., `team-frontend`).\n\n### Store a memory\n\nUse `memory retain` to store what you learn. Pass full context — raw observations, session notes, or detailed descriptions:\n\n```bash\nhindsight memory retain \u003Cbank-id> \"The project uses ESLint configured with the Airbnb rule set and Prettier for formatting. Auto-fix on save is enabled in the editor config.\"\nhindsight memory retain \u003Cbank-id> \"Ran the test suite with NODE_ENV=test. Tests pass. Without NODE_ENV=test, the suite fails with a missing config error.\" --context procedures\nhindsight memory retain \u003Cbank-id> \"Build failed on Node 18 with error 'ERR_UNSUPPORTED_ESM_URL_SCHEME'. Switched to Node 20 and build succeeded.\" --context learnings\nhindsight memory retain \u003Cbank-id> \"Alice reviewed the PR and asked for verbose commit messages that explain the motivation, not just what changed.\" --context preferences\n```\n\nYou can also pass a raw conversation transcript with timestamps:\n\n```bash\nhindsight memory retain \u003Cbank-id> \"[2026-03-16T10:12:03] User: The auth tests keep failing on CI but pass locally. Any idea?\n[2026-03-16T10:12:45] Assistant: Let me check the CI logs. Looks like the tests are running without the TEST_DATABASE_URL env var set — they fall back to the production DB URL and hit a connection timeout.\n[2026-03-16T10:13:20] User: Ah right, I never added that to the CI secrets. Adding it now.\n[2026-03-16T10:15:02] User: That fixed it. All green now.\" --context learnings\n```\n\n### Recall memories\n\nUse `memory recall` BEFORE starting tasks to get relevant context:\n\n```bash\nhindsight memory recall \u003Cbank-id> \"project conventions and coding standards\"\nhindsight memory recall \u003Cbank-id> \"Alice preferences for this project\"\nhindsight memory recall \u003Cbank-id> \"what issues have we encountered before\"\nhindsight memory recall \u003Cbank-id> \"how does the auth module work\"\n```\n\n### Reflect on memories\n\nUse `memory reflect` to synthesize context:\n\n```bash\nhindsight memory reflect \u003Cbank-id> \"How should I approach this task based on past experience?\"\n```\n\n## IMPORTANT: When to Store Memories\n\nThis is a **shared team bank**. Store knowledge that benefits the team. For individual preferences, include the person's name.\n\n**Always ask before storing.** Everything below is a candidate to *propose*, not to store on your own: tell the user what you would retain (and in which bank), and run `memory retain` only after they agree. Never store secrets, credentials or anything the user has not cleared for the team.\n\n### Project\u002FTeam Conventions (shared)\n- Coding standards (\"Project uses 2-space indentation\")\n- Required tools and versions (\"Project requires Node 20+, PostgreSQL 15+\")\n- Linting and formatting rules (\"ESLint with Airbnb config\")\n- Testing conventions (\"Integration tests require Docker running\")\n- Branch naming and PR conventions\n\n### Individual Preferences (attribute to person)\n- Personal coding style (\"Alice prefers explicit type annotations\")\n- Communication preferences (\"Bob prefers detailed PR descriptions\")\n- Tool preferences (\"Carol uses vim keybindings\")\n\n### Procedure Outcomes\n- Steps that successfully completed a task\n- Commands that worked (or failed) and why\n- Workarounds discovered\n- Configuration that resolved issues\n\n### Learnings from Tasks\n- Bugs encountered and their solutions\n- Performance optimizations that worked\n- Architecture decisions and rationale\n- Dependencies or version requirements\n\n### Team Knowledge\n- Onboarding information for new team members\n- Common pitfalls and how to avoid them\n- Architecture decisions and their rationale\n- Integration points with external systems\n- Domain knowledge and business logic explanations\n\n## IMPORTANT: When to Recall Memories\n\n**Always recall** before:\n- Starting any non-trivial task\n- Making decisions about implementation\n- Suggesting tools, libraries, or approaches\n- Writing code in a new area of the project\n- When answering questions about the codebase\n- When a team member asks how something works\n\n## Best Practices\n\n1. **Propose promptly, store on approval**: When you discover something worth keeping, offer it to the user right away and store it once they say yes\n2. **Pass rich context**: Include full observations, not pre-summarized strings — the server extracts facts automatically\n3. **Include outcomes**: Store what happened AND why, including failures and workarounds\n4. **Recall first**: Always check for relevant context before starting work\n5. **Think team-first**: Store knowledge that would help other team members\n6. **Attribute individual preferences**: Store \"Alice reviewed the PR and asked for X\" not just \"User prefers X\"\n7. **Distinguish project vs personal**: Project conventions apply to everyone; personal preferences are per-person\n8. **Use `--context` for metadata**: The `--context` flag labels the type of memory (e.g., `procedures`, `learnings`, `preferences`), not a replacement for full content\n","# Hindsight Memory Skill (Cloud)\n\nYou have persistent memory via **Hindsight Cloud**. This memory bank is **shared with the team**, so knowledge stored here benefits everyone working on this codebase.\n\n**Recall context before tasks, and propose team knowledge worth keeping.** Because the bank is shared with the team, **never store anything without asking the user first**: show what you would store and wait for a yes.\n\n## Setup Check (First-Time Only)\n\nBefore using memory commands, verify the Hindsight CLI is configured. The config file holds the API key, so never print it (no `cat`, `less` or `grep` without `-q`); only check that it is there:\n\n```bash\nif [ -s ~\u002F.hindsight\u002Fconfig ] && grep -q '^[[:space:]]*api_key[[:space:]]*=' ~\u002F.hindsight\u002Fconfig; then\n  echo \"hindsight: configured\"\nelse\n  echo \"hindsight: not configured\"\nfi\n```\n\n**If it reports not configured**, help the user set it up:\n\n1. **Install the CLI** (if `hindsight` command not found):\n   ```bash\n   curl -fsSL https:\u002F\u002Fhindsight.vectorize.io\u002Fget-cli | bash\n   ```\n\n2. **Create the config file** - ask the user for their **API Key** (get it from https:\u002F\u002Fui.hindsight.vectorize.io):\n   ```bash\n   mkdir -p ~\u002F.hindsight\n   cat > ~\u002F.hindsight\u002Fconfig \u003C\u003C 'EOF'\n   api_url = \"https:\u002F\u002Fapi.hindsight.vectorize.io\"\n   api_key = \"\u003Cuser's API key>\"\n   EOF\n   chmod 600 ~\u002F.hindsight\u002Fconfig\n   ```\n\n3. **Get the bank ID** - ask the user for their team's bank ID (e.g., `team-myproject`)\n\nAfter setup, use the bank ID in all commands below.\n\n## How Hindsight Works\n\nWhen you call `retain`, Hindsight does **not** store the string as-is. The server runs an internal pipeline that:\n\n1. **Extracts structured facts** from the content using an LLM\n2. **Identifies entities** (people, tools, concepts) and links related facts\n3. **Builds temporal and causal relationships** between facts\n4. **Generates embeddings** for semantic search\n\nThis means you should pass **rich, full-context content** — the server is better at extracting what matters than a pre-summarized string. Your job is to decide **when** to store, not **what** to extract.\n\n## Commands\n\nReplace `\u003Cbank-id>` with the user's actual bank ID (e.g., `team-frontend`).\n\n### Store a memory\n\nUse `memory retain` to store what you learn. Pass full context — raw observations, session notes, or detailed descriptions:\n\n```bash\nhindsight memory retain \u003Cbank-id> \"The project uses ESLint configured with the Airbnb rule set and Prettier for formatting. Auto-fix on save is enabled in the editor config.\"\nhindsight memory retain \u003Cbank-id> \"Ran the test suite with NODE_ENV=test. Tests pass. Without NODE_ENV=test, the suite fails with a missing config error.\" --context procedures\nhindsight memory retain \u003Cbank-id> \"Build failed on Node 18 with error 'ERR_UNSUPPORTED_ESM_URL_SCHEME'. Switched to Node 20 and build succeeded.\" --context learnings\nhindsight memory retain \u003Cbank-id> \"Alice reviewed the PR and asked for verbose commit messages that explain the motivation, not just what changed.\" --context preferences\n```\n\nYou can also pass a raw conversation transcript with timestamps:\n\n```bash\nhindsight memory retain \u003Cbank-id> \"[2026-03-16T10:12:03] User: The auth tests keep failing on CI but pass locally. Any idea?\n[2026-03-16T10:12:45] Assistant: Let me check the CI logs. Looks like the tests are running without the TEST_DATABASE_URL env var set — they fall back to the production DB URL and hit a connection timeout.\n[2026-03-16T10:13:20] User: Ah right, I never added that to the CI secrets. Adding it now.\n[2026-03-16T10:15:02] User: That fixed it. All green now.\" --context learnings\n```\n\n### Recall memories\n\nUse `memory recall` BEFORE starting tasks to get relevant context:\n\n```bash\nhindsight memory recall \u003Cbank-id> \"project conventions and coding standards\"\nhindsight memory recall \u003Cbank-id> \"Alice preferences for this project\"\nhindsight memory recall \u003Cbank-id> \"what issues have we encountered before\"\nhindsight memory recall \u003Cbank-id> \"how does the auth module work\"\n```\n\n### Reflect on memories\n\nUse `memory reflect` to synthesize context:\n\n```bash\nhindsight memory reflect \u003Cbank-id> \"How should I approach this task based on past experience?\"\n```\n\n## IMPORTANT: When to Store Memories\n\nThis is a **shared team bank**. Store knowledge that benefits the team. For individual preferences, include the person's name.\n\n**Always ask before storing.** Everything below is a candidate to *propose*, not to store on your own: tell the user what you would retain (and in which bank), and run `memory retain` only after they agree. Never store secrets, credentials or anything the user has not cleared for the team.\n\n### Project\u002FTeam Conventions (shared)\n- Coding standards (\"Project uses 2-space indentation\")\n- Required tools and versions (\"Project requires Node 20+, PostgreSQL 15+\")\n- Linting and formatting rules (\"ESLint with Airbnb config\")\n- Testing conventions (\"Integration tests require Docker running\")\n- Branch naming and PR conventions\n\n### Individual Preferences (attribute to person)\n- Personal coding style (\"Alice prefers explicit type annotations\")\n- Communication preferences (\"Bob prefers detailed PR descriptions\")\n- Tool preferences (\"Carol uses vim keybindings\")\n\n### Procedure Outcomes\n- Steps that successfully completed a task\n- Commands that worked (or failed) and why\n- Workarounds discovered\n- Configuration that resolved issues\n\n### Learnings from Tasks\n- Bugs encountered and their solutions\n- Performance optimizations that worked\n- Architecture decisions and rationale\n- Dependencies or version requirements\n\n### Team Knowledge\n- Onboarding information for new team members\n- Common pitfalls and how to avoid them\n- Architecture decisions and their rationale\n- Integration points with external systems\n- Domain knowledge and business logic explanations\n\n## IMPORTANT: When to Recall Memories\n\n**Always recall** before:\n- Starting any non-trivial task\n- Making decisions about implementation\n- Suggesting tools, libraries, or approaches\n- Writing code in a new area of the project\n- When answering questions about the codebase\n- When a team member asks how something works\n\n## Best Practices\n\n1. **Propose promptly, store on approval**: When you discover something worth keeping, offer it to the user right away and store it once they say yes\n2. **Pass rich context**: Include full observations, not pre-summarized strings — the server extracts facts automatically\n3. **Include outcomes**: Store what happened AND why, including failures and workarounds\n4. **Recall first**: Always check for relevant context before starting work\n5. **Think team-first**: Store knowledge that would help other team members\n6. **Attribute individual preferences**: Store \"Alice reviewed the PR and asked for X\" not just \"User prefers X\"\n7. **Distinguish project vs personal**: Project conventions apply to everyone; personal preferences are per-person\n8. **Use `--context` for metadata**: The `--context` flag labels the type of memory (e.g., `procedures`, `learnings`, `preferences`), not a replacement for full content\n",{"name":5,"description":7},"main","23e30a8887155f1bfa8c727b3c81128c3f918088","agents\u002Fskills\u002Fhindsight-cloud",0,"https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Ffeniix","https:\u002F\u002Ffeniix-hq.net\u002F","Systems and platform engineer. Kubernetes, Terraform, CI\u002FCD, observability; MCP and agent tooling. asdf plugins, Prometheus Operator.","2026-11-09 04:16:06",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add feniix\u002Fdotfiles --skill hindsight-cloud",{"tool":57,"command":58},"bunx","bunx skills add feniix\u002Fdotfiles --skill hindsight-cloud",{"tool":60,"command":61},"pnpm","pnpm dlx skills add feniix\u002Fdotfiles --skill hindsight-cloud","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fhindsight-cloud\u002FSKILL.md",true,[65,71,75,79,83,87,91,95,99,103,107],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"agents\u002Fopenai.yaml","REFERENCE","参考文档",834,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-antigravity-maintainer-batch-release\u002Fagents\u002Fopenai.yaml",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002F2026-11-02-maintenance.md",1520,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-antigravity-maintainer-batch-release\u002Freferences\u002F2026-11-02-maintenance.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fci-audit-improvements.md",3235,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-antigravity-maintainer-batch-release\u002Freferences\u002Fci-audit-improvements.md",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fcomponent-validation.md",12335,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-antigravity-maintainer-batch-release\u002Freferences\u002Fcomponent-validation.md",{"path":84,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fcontribution-intake.md",9008,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-antigravity-maintainer-batch-release\u002Freferences\u002Fcontribution-intake.md",{"path":88,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fcore-preview.md",5243,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-antigravity-maintainer-batch-release\u002Freferences\u002Fcore-preview.md",{"path":92,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fmaintenance-contract.md",32399,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-antigravity-maintainer-batch-release\u002Freferences\u002Fmaintenance-contract.md",{"path":96,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fmaintenance-cycle.md",12574,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-antigravity-maintainer-batch-release\u002Freferences\u002Fmaintenance-cycle.md",{"path":100,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fpublic-surfaces.md",2510,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-antigravity-maintainer-batch-release\u002Freferences\u002Fpublic-surfaces.md",{"path":104,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Frelease-finalization.md",5024,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-antigravity-maintainer-batch-release\u002Freferences\u002Frelease-finalization.md",{"path":108,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fskillspector.md",6794,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-antigravity-maintainer-batch-release\u002Freferences\u002Fskillspector.md",[112,138,157,188,202,214],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":37},"01M70M28HFDKQPGSWESHGB0HV4","security-audit","Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full\u002Fcomprehensive\u002Fend-to-end reviews, or requested report artifacts.","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fsecurity-audit\u002FSKILL.md",[],[119,120,121,122,123,124,125,126,127,128,129,29,130,131,132,133,134,135,136,137],"security","audit","security audit","review","cli","workflow","libraries","run","Tools","vulnerability","security guidance","only","codebase audit","full","tests","end","complete","reviews","for",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":154,"publishedAt":37},"01M6BVT1CVKQNSANZMZTNBDDY5","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[144,149],{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":150,"categoryName":151,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[155,156],"writing shape","writing",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":161,"licenseFileUrl":162,"sourceHtmlUrl":163,"categories":164,"keywords":171,"publishedAt":37},"01M6BVSP7TBXD5GBW6KBTN5GGC","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[165,168],{"categoryNo":166,"categoryName":167,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":169,"categoryName":170,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000009","前端开发",[172,173,174,137,175,176,177,178,179,180,181,182,183,184,185,186,187],"testing","webapp testing","webapp","logs","with","local","behavior","applications","toolkit","ui","frontend","screenshots","playwright","web","debugging","browser",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":37},"01M6BVSMEE5GRR6ZCM43JNR73Y","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[190,195,196,197,198,199,200,201],"chunk","plan","decision","work","one at a time","session","issue",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":208,"publishedAt":37},"01M6BVS3BHEG1D2RPZ2J6GNV90","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[209,210,211,212,213,196],"to tickets","text","spec","file","SET",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":220,"publishedAt":37},"01M6BVRT61DF4XJE3ZERBBV0AW","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002Ffeniix\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002Fskills\u002Ftdd\u002FSKILL.md",[],[216,221,222,223,224,225,226,30,227,29,228],"test","integration tests","development","integration","refactor","first","fix","red-green-refactor"]