[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B4DF4P99CQQ7BHSMDT3HJR":3,"skill-same:01M7B4DF4P99CQQ7BHSMDT3HJR":44},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7B4DF4P99CQQ7BHSMDT3HJR","smart-explore",null,"Token-optimized structural code search using tree-sitter AST parsing. Use instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.","yashpreeto7\u002Fsanctum","yashpreeto7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F157383808?v=4","01M7B4BVRRC6PZYNDFRVJJ4Y77","Yashpreet","01M7B4BVSD4C4JKEKDGNH8ABGH",0,"MIT","https:\u002F\u002Fgithub.com\u002Fyashpreeto7\u002Fsanctum\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclaude-mem\u002Fskills\u002Fsmart-explore\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: smart-explore\ndescription: Token-optimized structural code search using tree-sitter AST parsing. Use instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.\n---\n\n# Smart Explore\n\nStructural code exploration using AST parsing. **This skill overrides your default exploration behavior.** While this skill is active, use smart_search\u002Fsmart_outline\u002Fsmart_unfold as your primary tools instead of Read, Grep, and Glob.\n\n**Core principle:** Index first, fetch on demand. Give yourself a map of the code before loading implementation details. The question before every file read should be: \"do I need to see all of this, or can I get a structural overview first?\" The answer is almost always: get the map.\n\n## Your Next Tool Call\n\nThis skill only loads instructions. You must call the MCP tools yourself. Your next action should be one of:\n\n```\nsmart_search(query=\"\u003Ctopic>\", path=\".\u002Fsrc\")    -- discover files + symbols across a directory\nsmart_outline(file_path=\"\u003Cfile>\")              -- structural skeleton of one file\nsmart_unfold(file_path=\"\u003Cfile>\", symbol_name=\"\u003Cname>\")  -- full source of one symbol\n```\n\nDo NOT run Grep, Glob, Read, or find to discover files first. `smart_search` walks directories, parses all code files, and returns ranked symbols in one call. It replaces the Glob → Grep → Read discovery cycle.\n\n## 3-Layer Workflow\n\n### Step 1: Search -- Discover Files and Symbols\n\n```\nsmart_search(query=\"shutdown\", path=\".\u002Fsrc\", max_results=15)\n```\n\n**Returns:** Ranked symbols with signatures, line numbers, match reasons, plus folded file views (~2-6k tokens)\n\n```\n-- Matching Symbols --\n  function performGracefulShutdown (services\u002Finfrastructure\u002FGracefulShutdown.ts:56)\n  function httpShutdown (services\u002Finfrastructure\u002FHealthMonitor.ts:92)\n  method WorkerService.shutdown (services\u002Fworker-service.ts:846)\n\n-- Folded File Views --\n  services\u002Finfrastructure\u002FGracefulShutdown.ts (7 symbols)\n  services\u002Fworker-service.ts (12 symbols)\n```\n\nThis is your discovery tool. It finds relevant files AND shows their structure. No Glob\u002Ffind pre-scan needed.\n\n**Parameters:**\n\n- `query` (string, required) -- What to search for (function name, concept, class name)\n- `path` (string) -- Root directory to search (defaults to cwd)\n- `max_results` (number) -- Max matching symbols, default 20, max 50\n- `file_pattern` (string, optional) -- Filter to specific files\u002Fpaths\n\n### Step 2: Outline -- Get File Structure\n\n```\nsmart_outline(file_path=\"services\u002Fworker-service.ts\")\n```\n\n**Returns:** Complete structural skeleton -- all functions, classes, methods, properties, imports (~1-2k tokens per file)\n\n**Skip this step** when Step 1's folded file views already provide enough structure. Most useful for files not covered by the search results.\n\n**Parameters:**\n\n- `file_path` (string, required) -- Path to the file\n\n### Step 3: Unfold -- See Implementation\n\nReview symbols from Steps 1-2. Pick the ones you need. Unfold only those:\n\n```\nsmart_unfold(file_path=\"services\u002Fworker-service.ts\", symbol_name=\"shutdown\")\n```\n\n**Returns:** Full source code of the specified symbol including JSDoc, decorators, and complete implementation (~400-2,100 tokens depending on symbol size). AST node boundaries guarantee completeness regardless of symbol size — unlike Read + agent summarization, which may truncate long methods.\n\n**Parameters:**\n\n- `file_path` (string, required) -- Path to the file (as returned by search\u002Foutline)\n- `symbol_name` (string, required) -- Name of the function\u002Fclass\u002Fmethod to expand\n\n## When to Use Standard Tools Instead\n\nUse these only when smart_* tools are the wrong fit:\n\n- **Grep:** Exact string\u002Fregex search (\"find all TODO comments\", \"where is `ensureWorkerStarted` defined?\")\n- **Read:** Small files under ~100 lines, non-code files (JSON, markdown, config)\n- **Glob:** File path patterns (\"find all test files\")\n- **Explore agent:** When you need synthesized understanding across 6+ files, architecture narratives, or answers to open-ended questions like \"how does this entire system work end-to-end?\" Smart-explore is a scalpel — it answers \"where is this?\" and \"show me that.\" It doesn't synthesize cross-file data flows, design decisions, or edge cases across an entire feature.\n\nFor code files over ~100 lines, prefer smart_outline + smart_unfold over Read.\n\n## Workflow Examples\n\n**Discover how a feature works (cross-cutting):**\n\n```\n1. smart_search(query=\"shutdown\", path=\".\u002Fsrc\")\n   -> 14 symbols across 7 files, full picture in one call\n2. smart_unfold(file_path=\"services\u002Finfrastructure\u002FGracefulShutdown.ts\", symbol_name=\"performGracefulShutdown\")\n   -> See the core implementation\n```\n\n**Navigate a large file:**\n\n```\n1. smart_outline(file_path=\"services\u002Fworker-service.ts\")\n   -> 1,466 tokens: 12 functions, WorkerService class with 24 members\n2. smart_unfold(file_path=\"services\u002Fworker-service.ts\", symbol_name=\"startSessionProcessor\")\n   -> 1,610 tokens: the specific method you need\nTotal: ~3,076 tokens vs ~12,000 to Read the full file\n```\n\n**Write documentation about code (hybrid workflow):**\n\n```\n1. smart_search(query=\"feature name\", path=\".\u002Fsrc\")    -- discover all relevant files and symbols\n2. smart_outline on key files                           -- understand structure\n3. smart_unfold on important functions                  -- get implementation details\n4. Read on small config\u002Fmarkdown\u002Fplan files             -- get non-code context\n```\n\nUse smart_* tools for code exploration, Read for non-code files. Mix freely.\n\n**Exploration then precision:**\n\n```\n1. smart_search(query=\"session\", path=\".\u002Fsrc\", max_results=10)\n   -> 10 ranked symbols: SessionMetadata, SessionQueueProcessor, SessionSummary...\n2. Pick the relevant one, unfold it\n```\n\n## Token Economics\n\n| Approach | Tokens | Use Case |\n|----------|--------|----------|\n| smart_outline | ~1,000-2,000 | \"What's in this file?\" |\n| smart_unfold | ~400-2,100 | \"Show me this function\" |\n| smart_search | ~2,000-6,000 | \"Find all X across the codebase\" |\n| search + unfold | ~3,000-8,000 | End-to-end: find and read (the primary workflow) |\n| Read (full file) | ~12,000+ | When you truly need everything |\n| Explore agent | ~39,000-59,000 | Cross-file synthesis with narrative |\n\n**4-8x savings** on file understanding (outline + unfold vs Read). **11-18x savings** on codebase exploration vs Explore agent. The narrower the query, the wider the gap — a 27-line function costs 55x less to read via unfold than via an Explore agent, because the agent still reads the entire file.\n\n## Language Support\n\nSmart-explore uses **tree-sitter AST parsing** for structural analysis. Unsupported file types fall back to text-based search.\n\n### Bundled Languages\n\n| Language | Extensions |\n|----------|-----------|\n| JavaScript | `.js`, `.mjs`, `.cjs` |\n| TypeScript | `.ts` |\n| TSX \u002F JSX | `.tsx`, `.jsx` |\n| Python | `.py`, `.pyw` |\n| Go | `.go` |\n| Rust | `.rs` |\n| Ruby | `.rb` |\n| Java | `.java` |\n| C | `.c`, `.h` |\n| C++ | `.cpp`, `.cc`, `.cxx`, `.hpp`, `.hh` |\n\nFiles with unrecognized extensions are parsed as plain text — `smart_search` still works (grep-style), but `smart_outline` and `smart_unfold` will not extract structured symbols.\n\n### Custom Grammars (`.claude-mem.json`)\n\nYou can register additional tree-sitter grammars for file types not in the bundled list. Create or update `.claude-mem.json` in your project root:\n\n```json\n{\n  \"grammars\": {\n    \"solidity\": {\n      \"package\": \"tree-sitter-solidity\",\n      \"extensions\": [\".sol\"],\n      \"query\": \"solidity-query.scm\"\n    }\n  }\n}\n```\n\nEach key is a language name. `package` is the npm package of the tree-sitter grammar and `extensions` lists the file extensions it covers; the package must be installed in the project's `node_modules` (`npm install tree-sitter-solidity`). `query` (optional) is a path, relative to the config file, to a tree-sitter query whose captures (`@func`, `@cls`, `@method`, `@iface`, `@enm`, `@struct_def`, `@imp`) extract symbols. Without `query`, a minimal generic pattern is used — it only matches grammars that define `function_declaration`\u002F`class_declaration` node types, and query compilation fails silently (0 symbols) for grammars that lack them, so a custom query is effectively required for most languages. Once registered, `smart_outline` and `smart_unfold` parse those extensions structurally instead of falling back to plain text.\n\n### Markdown Special Support\n\nMarkdown files (`.md`, `.mdx`) receive special handling beyond the generic plain-text fallback:\n\n- **`smart_outline`** — extracts headings (`#`, `##`, `###`) as the symbol tree. Use it to navigate long documents without reading the full file.\n- **`smart_search`** — searches within code fences as well as prose, so queries for function names inside ` ```ts ``` ` blocks work as expected.\n- **`smart_unfold`** — expands heading sections rather than function bodies; each section up to the next same-level heading is returned as a chunk.\n- **Frontmatter** — YAML frontmatter (lines between leading `---` delimiters) is included in `smart_outline` output under a synthetic `frontmatter` symbol so metadata like `title:` and `description:` is visible without reading the whole file.\n","# Smart Explore\n\nStructural code exploration using AST parsing. **This skill overrides your default exploration behavior.** While this skill is active, use smart_search\u002Fsmart_outline\u002Fsmart_unfold as your primary tools instead of Read, Grep, and Glob.\n\n**Core principle:** Index first, fetch on demand. Give yourself a map of the code before loading implementation details. The question before every file read should be: \"do I need to see all of this, or can I get a structural overview first?\" The answer is almost always: get the map.\n\n## Your Next Tool Call\n\nThis skill only loads instructions. You must call the MCP tools yourself. Your next action should be one of:\n\n```\nsmart_search(query=\"\u003Ctopic>\", path=\".\u002Fsrc\")    -- discover files + symbols across a directory\nsmart_outline(file_path=\"\u003Cfile>\")              -- structural skeleton of one file\nsmart_unfold(file_path=\"\u003Cfile>\", symbol_name=\"\u003Cname>\")  -- full source of one symbol\n```\n\nDo NOT run Grep, Glob, Read, or find to discover files first. `smart_search` walks directories, parses all code files, and returns ranked symbols in one call. It replaces the Glob → Grep → Read discovery cycle.\n\n## 3-Layer Workflow\n\n### Step 1: Search -- Discover Files and Symbols\n\n```\nsmart_search(query=\"shutdown\", path=\".\u002Fsrc\", max_results=15)\n```\n\n**Returns:** Ranked symbols with signatures, line numbers, match reasons, plus folded file views (~2-6k tokens)\n\n```\n-- Matching Symbols --\n  function performGracefulShutdown (services\u002Finfrastructure\u002FGracefulShutdown.ts:56)\n  function httpShutdown (services\u002Finfrastructure\u002FHealthMonitor.ts:92)\n  method WorkerService.shutdown (services\u002Fworker-service.ts:846)\n\n-- Folded File Views --\n  services\u002Finfrastructure\u002FGracefulShutdown.ts (7 symbols)\n  services\u002Fworker-service.ts (12 symbols)\n```\n\nThis is your discovery tool. It finds relevant files AND shows their structure. No Glob\u002Ffind pre-scan needed.\n\n**Parameters:**\n\n- `query` (string, required) -- What to search for (function name, concept, class name)\n- `path` (string) -- Root directory to search (defaults to cwd)\n- `max_results` (number) -- Max matching symbols, default 20, max 50\n- `file_pattern` (string, optional) -- Filter to specific files\u002Fpaths\n\n### Step 2: Outline -- Get File Structure\n\n```\nsmart_outline(file_path=\"services\u002Fworker-service.ts\")\n```\n\n**Returns:** Complete structural skeleton -- all functions, classes, methods, properties, imports (~1-2k tokens per file)\n\n**Skip this step** when Step 1's folded file views already provide enough structure. Most useful for files not covered by the search results.\n\n**Parameters:**\n\n- `file_path` (string, required) -- Path to the file\n\n### Step 3: Unfold -- See Implementation\n\nReview symbols from Steps 1-2. Pick the ones you need. Unfold only those:\n\n```\nsmart_unfold(file_path=\"services\u002Fworker-service.ts\", symbol_name=\"shutdown\")\n```\n\n**Returns:** Full source code of the specified symbol including JSDoc, decorators, and complete implementation (~400-2,100 tokens depending on symbol size). AST node boundaries guarantee completeness regardless of symbol size — unlike Read + agent summarization, which may truncate long methods.\n\n**Parameters:**\n\n- `file_path` (string, required) -- Path to the file (as returned by search\u002Foutline)\n- `symbol_name` (string, required) -- Name of the function\u002Fclass\u002Fmethod to expand\n\n## When to Use Standard Tools Instead\n\nUse these only when smart_* tools are the wrong fit:\n\n- **Grep:** Exact string\u002Fregex search (\"find all TODO comments\", \"where is `ensureWorkerStarted` defined?\")\n- **Read:** Small files under ~100 lines, non-code files (JSON, markdown, config)\n- **Glob:** File path patterns (\"find all test files\")\n- **Explore agent:** When you need synthesized understanding across 6+ files, architecture narratives, or answers to open-ended questions like \"how does this entire system work end-to-end?\" Smart-explore is a scalpel — it answers \"where is this?\" and \"show me that.\" It doesn't synthesize cross-file data flows, design decisions, or edge cases across an entire feature.\n\nFor code files over ~100 lines, prefer smart_outline + smart_unfold over Read.\n\n## Workflow Examples\n\n**Discover how a feature works (cross-cutting):**\n\n```\n1. smart_search(query=\"shutdown\", path=\".\u002Fsrc\")\n   -> 14 symbols across 7 files, full picture in one call\n2. smart_unfold(file_path=\"services\u002Finfrastructure\u002FGracefulShutdown.ts\", symbol_name=\"performGracefulShutdown\")\n   -> See the core implementation\n```\n\n**Navigate a large file:**\n\n```\n1. smart_outline(file_path=\"services\u002Fworker-service.ts\")\n   -> 1,466 tokens: 12 functions, WorkerService class with 24 members\n2. smart_unfold(file_path=\"services\u002Fworker-service.ts\", symbol_name=\"startSessionProcessor\")\n   -> 1,610 tokens: the specific method you need\nTotal: ~3,076 tokens vs ~12,000 to Read the full file\n```\n\n**Write documentation about code (hybrid workflow):**\n\n```\n1. smart_search(query=\"feature name\", path=\".\u002Fsrc\")    -- discover all relevant files and symbols\n2. smart_outline on key files                           -- understand structure\n3. smart_unfold on important functions                  -- get implementation details\n4. Read on small config\u002Fmarkdown\u002Fplan files             -- get non-code context\n```\n\nUse smart_* tools for code exploration, Read for non-code files. Mix freely.\n\n**Exploration then precision:**\n\n```\n1. smart_search(query=\"session\", path=\".\u002Fsrc\", max_results=10)\n   -> 10 ranked symbols: SessionMetadata, SessionQueueProcessor, SessionSummary...\n2. Pick the relevant one, unfold it\n```\n\n## Token Economics\n\n| Approach | Tokens | Use Case |\n|----------|--------|----------|\n| smart_outline | ~1,000-2,000 | \"What's in this file?\" |\n| smart_unfold | ~400-2,100 | \"Show me this function\" |\n| smart_search | ~2,000-6,000 | \"Find all X across the codebase\" |\n| search + unfold | ~3,000-8,000 | End-to-end: find and read (the primary workflow) |\n| Read (full file) | ~12,000+ | When you truly need everything |\n| Explore agent | ~39,000-59,000 | Cross-file synthesis with narrative |\n\n**4-8x savings** on file understanding (outline + unfold vs Read). **11-18x savings** on codebase exploration vs Explore agent. The narrower the query, the wider the gap — a 27-line function costs 55x less to read via unfold than via an Explore agent, because the agent still reads the entire file.\n\n## Language Support\n\nSmart-explore uses **tree-sitter AST parsing** for structural analysis. Unsupported file types fall back to text-based search.\n\n### Bundled Languages\n\n| Language | Extensions |\n|----------|-----------|\n| JavaScript | `.js`, `.mjs`, `.cjs` |\n| TypeScript | `.ts` |\n| TSX \u002F JSX | `.tsx`, `.jsx` |\n| Python | `.py`, `.pyw` |\n| Go | `.go` |\n| Rust | `.rs` |\n| Ruby | `.rb` |\n| Java | `.java` |\n| C | `.c`, `.h` |\n| C++ | `.cpp`, `.cc`, `.cxx`, `.hpp`, `.hh` |\n\nFiles with unrecognized extensions are parsed as plain text — `smart_search` still works (grep-style), but `smart_outline` and `smart_unfold` will not extract structured symbols.\n\n### Custom Grammars (`.claude-mem.json`)\n\nYou can register additional tree-sitter grammars for file types not in the bundled list. Create or update `.claude-mem.json` in your project root:\n\n```json\n{\n  \"grammars\": {\n    \"solidity\": {\n      \"package\": \"tree-sitter-solidity\",\n      \"extensions\": [\".sol\"],\n      \"query\": \"solidity-query.scm\"\n    }\n  }\n}\n```\n\nEach key is a language name. `package` is the npm package of the tree-sitter grammar and `extensions` lists the file extensions it covers; the package must be installed in the project's `node_modules` (`npm install tree-sitter-solidity`). `query` (optional) is a path, relative to the config file, to a tree-sitter query whose captures (`@func`, `@cls`, `@method`, `@iface`, `@enm`, `@struct_def`, `@imp`) extract symbols. Without `query`, a minimal generic pattern is used — it only matches grammars that define `function_declaration`\u002F`class_declaration` node types, and query compilation fails silently (0 symbols) for grammars that lack them, so a custom query is effectively required for most languages. Once registered, `smart_outline` and `smart_unfold` parse those extensions structurally instead of falling back to plain text.\n\n### Markdown Special Support\n\nMarkdown files (`.md`, `.mdx`) receive special handling beyond the generic plain-text fallback:\n\n- **`smart_outline`** — extracts headings (`#`, `##`, `###`) as the symbol tree. Use it to navigate long documents without reading the full file.\n- **`smart_search`** — searches within code fences as well as prose, so queries for function names inside ` ```ts ``` ` blocks work as expected.\n- **`smart_unfold`** — expands heading sections rather than function bodies; each section up to the next same-level heading is returned as a chunk.\n- **Frontmatter** — YAML frontmatter (lines between leading `---` delimiters) is included in `smart_outline` output under a synthetic `frontmatter` symbol so metadata like `title:` and `description:` is visible without reading the whole file.\n",{"name":5,"description":7},"main","c705f1ce3634ad8c8988a350232fd6bc8d8ae5a8",".agents\u002Fskills\u002Fclaude-mem\u002Fskills\u002Fsmart-explore","https:\u002F\u002Fgithub.com\u002Fyashpreeto7\u002Fsanctum","https:\u002F\u002Fgithub.com\u002Fyashpreeto7","2026-09-09 18:55:27",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add yashpreeto7\u002Fsanctum --skill smart-explore",{"tool":36,"command":37},"bunx","bunx skills add yashpreeto7\u002Fsanctum --skill smart-explore",{"tool":39,"command":40},"pnpm","pnpm dlx skills add yashpreeto7\u002Fsanctum --skill smart-explore","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyashpreeto7\u002Fsanctum\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclaude-mem\u002Fskills\u002Fsmart-explore\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7B4JT51NR5K5YYZPAYZN2T1","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fyashpreeto7\u002Fsanctum\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7B4JR0D9BZ6EZ2A9KMK50VQ","verification-loop","A comprehensive verification system for Claude Code sessions. Use when verifying a Claude Code session's work before claiming it is complete.","https:\u002F\u002Fgithub.com\u002Fyashpreeto7\u002Fsanctum\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7B4JJ5FXWNSDK61YFF97SJQ","ui-ux-pro-max","UI\u002FUX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local data: 79 searchable styles (50 active), 192 product palettes and reasoning profiles, 74 font pairings, 119 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.","https:\u002F\u002Fgithub.com\u002Fyashpreeto7\u002Fsanctum\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fui-ux-pro-max\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"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},"01M7B4JF51AW1VJPQK35S7055Y","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\u002Fyashpreeto7\u002Fsanctum\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7B4JCT2CS7J7YVQFKVZRQA3","to-spec","Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002Fyashpreeto7\u002Fsanctum\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-spec\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7B4J7FY6KPAB8ZQACQFBN89","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fyashpreeto7\u002Fsanctum\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsuperpowers\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[]]