[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71GC1CV7F7RZBH264VP9WB2":3,"skill-same:01M71GC1CV7F7RZBH264VP9WB2":64},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M71GC1CV7F7RZBH264VP9WB2","projectvault-new-idea",null,"Use when working in ProjectVault and a new project idea is being described or explored. Handles the full brainstorm-to-spec workflow using vault conventions, Stack-Preferences, and Prompter-Profile. Do NOT invoke superpowers:brainstorming in this context.","Junqing\u002Fproject-vault","Junqing","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3631684?v=4","01M71GBSJSHPHYN153VT0D6PXX","Jin","01M71GBSKJERAK4MHPGBV75PXS",0,"MIT","https:\u002F\u002Fgithub.com\u002FJunqing\u002Fproject-vault\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fprojectvault-new-idea\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"new","idea","projectvault new idea","full","conventions","spec","spec workflow","brainstorming","vault","stack","workflow","when","invoke","use","preferences","superpowers","vault conventions","brainstorm","project","do","2026-11-10 10:12:30",false,"---\nname: projectvault-new-idea\ndescription: >\n  Use when working in ProjectVault and a new project idea is being described or explored.\n  Handles the full brainstorm-to-spec workflow using vault conventions, Stack-Preferences,\n  and Prompter-Profile. Do NOT invoke superpowers:brainstorming in this context.\n---\n\n# ProjectVault: New Idea Design Skill\n\nYou are running the full single-idea brainstorm-to-spec workflow for the ProjectVault. This skill replaces `superpowers:brainstorming` entirely. Do not invoke that skill.\n\n## Step 0: Load Context\n\nBefore asking any questions, read:\n1. `_shared\u002FStack-Preferences.md`\n2. `_shared\u002FPrompter-Profile.md`\n\nIf `Stack-Preferences.md` is missing, run the stack setup flow (see below) before continuing.\nIf `Prompter-Profile.md` is missing, run the guest setup flow (see below) before continuing.\nIf both are missing, run stack setup first, then guest setup.\n\n---\n\n## Step 1: Richness Check\n\nAssess how much the prompter has already provided. Look for these 4 signals in their message:\n- **Slug**: is there a clear short name for the idea?\n- **Audience**: who is it for?\n- **Interaction model**: how does the user interact with it?\n- **Constraints**: any tech, scope, or platform constraints stated?\n\n| Signals present | Q&A approach |\n|-----------------|-------------|\n| All 4 | Skip questions. Confirm inferred scope in 1 message, get approval, proceed. |\n| 3 of 4 | Max 2 clarifying questions. |\n| 2 or fewer | Ask up to `max_clarifying_questions` (from profile, default: 4), one at a time. |\n\nNever exceed the profile's `max_clarifying_questions` cap.\n\n---\n\n## Step 2: Ask Clarifying Questions\n\nAsk one question at a time. Prefer multiple-choice options when possible. Stop as soon as you have enough to propose approaches.\n\n**Before each question, check:**\n- Is this topic in the profile's `skip_questions` list? If yes, skip it.\n- Is `assumed_stack: true`? If yes, skip all stack\u002Finfra questions.\n\n**Adapt framing based on `technical_depth`:**\n\n| technical_depth | Infra questions | Stack questions |\n|-----------------|----------------|-----------------|\n| senior \u002F mid | Ask directly: \"ECS or Lambda?\" | Ask directly: \"FastAPI or Django?\" |\n| junior | Ask as tradeoffs: \"Always-on vs pay-per-request?\" | Ask as outcomes: \"One language or best-fit per layer?\" |\n| non-technical | Suppress infra questions entirely | Ask as outcomes: \"Do users need accounts?\" |\n\n---\n\n## Step 3: Propose 2–3 Approaches\n\nPresent architectural options. Always lead with Approach A pre-populated from `Stack-Preferences.md` defaults. Include trade-offs for each. Make a clear recommendation with reasoning.\n\nWait for the prompter to choose before proceeding.\n\n---\n\n## Step 4: Present Design Sections\n\nWalk through the design one section at a time:\n1. Architecture overview\n2. Data model\n3. Frontend components + routes\n4. API endpoints + deployment\n\nAfter each section, ask: \"Does this look right?\" Wait for approval before moving on.\n\n**Visual companion:** If `prefer_visuals: true` in profile (and not already offered this session), offer the visual companion once before starting design sections:\n> \"Some of what we're working on might be easier to explain in a browser — mockups, diagrams, architecture views. Want to try it? (Requires opening a local URL)\"\n\nWait for response. Only offer once.\n\n---\n\n## Step 5: Create Files (in this exact order)\n\n### 1. `ideas\u002F[slug]\u002FOverview.md`\n```markdown\n---\ntags: [projectvault, [slug]]\ntype: index\nstatus: Exploring\ncreated: YYYY-MM-DD\n---\n\n# [Idea Name]\n\n## Elevator Pitch\n[One paragraph]\n\n## Goals\n- [goal 1]\n- [goal 2]\n\n## Non-Goals\n- [non-goal 1]\n\n## Status\nExploring\n```\n\n### 2. `ideas\u002F[slug]\u002FStack.md`\nUse this structure for each significant decision:\n```markdown\n## Decision: [e.g., Database]\n\n**Chosen:** [option]\n\n| Option | Pros | Cons |\n|--------|------|------|\n| ...    | ...  | ...  |\n\n**Why:** [reasoning]\n```\nInclude a Standing Decisions table at the end for choices that match Stack-Preferences defaults (no table needed, just list them with a note).\n\n### 3. `ideas\u002F[slug]\u002FArchitecture.md`\n- Mermaid `flowchart LR` for system overview (if more than 1 component)\n- Mermaid `erDiagram` for data model\n- Mermaid `flowchart TD` for component tree\n- JSON code block for any JSONB or complex schema shapes\n- API tables: Method | Path | Auth | Notes\n- Frontend routes table: Route | Type (SSR\u002FCSR) | Component | Notes\n\n### 4. `ideas\u002F[slug]\u002FPhases.md`\n```markdown\n## Phase 1: [Name]\n**Goal:** [one sentence]\n- [ ] [feature\u002Fcomponent]\n\n## Phase 2: [Name]\n...\n```\n\n### 5. `ideas\u002F[slug]\u002FDesign-Spec.md`\nNine required sections:\n1. Product Overview\n2. Users & Roles\n3. Core Model\n4. Data Model\n5. API\n6. Frontend\n7. Infrastructure\n8. Phased Build\n9. Out of Scope\n\n### 6. `ideas\u002F[slug]\u002FResearch\u002F*.html`\nSave all interactive artifacts from brainstorming as standalone static HTML files. Each file must be fully self-contained (no server required), respond to dark\u002Flight mode via CSS `prefers-color-scheme`, and retain click interactivity.\n\nName files semantically: `layout-types.html`, `design-architecture.html`, etc.\n\n### 7. Update `README.md`\nAdd a row to the Ideas table:\n```\n| [[ideas\u002F[slug]\u002FOverview\\|[slug]]] | Exploring | [stack summary] | [one-line description] |\n```\n\n---\n\n## Step 6: End State\n\nAfter all files are created:\n> \"Design complete. All files saved in `ideas\u002F[slug]\u002F`. When you're ready to build, say `\u002Fvault-init [slug]`.\"\n\nDo NOT invoke `writing-plans`. This vault is design-only. Implementation handoff happens via `ProjectInitialize.md`.\n\n---\n\n## Stack Setup Flow\n\nTriggered when `_shared\u002FStack-Preferences.md` is missing. Ask these questions one at a time, then write the file before continuing.\n\n1. \"What's your primary backend language?\" (e.g., Python, Go, TypeScript, Java)\n2. \"What's your preferred web framework for that language?\" (e.g., FastAPI, Django, Express, Spring)\n3. \"What's your default database?\" (e.g., PostgreSQL, MySQL, SQLite, DynamoDB)\n4. \"Where do you typically deploy?\" (e.g., AWS, GCP, Azure, Fly.io, self-hosted)\n5. \"Any preferred frontend approach?\" (e.g., Next.js, plain HTML\u002FHTMX, React SPA, no preference)\n6. \"Any preferred IaC tool?\" (e.g., Terraform, CDK, Pulumi, none)\n\nWrite the results to `_shared\u002FStack-Preferences.md`:\n\n```markdown\n---\ntags: [projectvault, stack]\ntype: reference\ncreated: YYYY-MM-DD\n---\n\n# Stack Preferences\n\nDefault technology choices for this ProjectVault. Override per-idea in `Stack.md`.\n\n| Domain | Choice | Notes |\n|--------|--------|-------|\n| Backend language | [answer] | |\n| Web framework | [answer] | |\n| Database | [answer] | |\n| Cloud \u002F deployment | [answer] | |\n| Frontend | [answer] | |\n| IaC | [answer] | |\n```\n\n---\n\n## First-Time Setup Flow\n\nTriggered when `Prompter-Profile.md` is missing. Ask these 4 questions (one at a time), then write the profile before doing anything else.\n\n1. \"What's your name?\"\n2. \"Are you technical? (yes \u002F somewhat \u002F no)\"\n   - yes → `technical_depth: senior`\n   - somewhat → `technical_depth: mid`\n   - no → `technical_depth: non-technical`\n3. \"Do you have a preferred tech stack, or would you like to be asked about it for each idea?\"\n   - have preferences → ask them to briefly describe their stack, set `assumed_stack: true` and capture choices in `stack_overrides`\n   - ask each time → `assumed_stack: false`\n4. \"When you mention an idea, do you want a full detailed design right away, or just a quick stub to come back to later?\"\n   - full → `rapid_mode_default: false`\n   - stub → `rapid_mode_default: true`\n\nWrite the profile to `_shared\u002FPrompter-Profile.md` using the schema below, then resume the current request.\n\n```yaml\n---\nname: [name]\nrole: owner\ntechnical_depth: [from Q2]\nassumed_stack: [from Q3]\nskip_questions: []\nrapid_mode_default: [from Q4]\nprefer_visuals: true\nmax_clarifying_questions: 4\nstack_overrides: {}\n---\n\n[Name]'s profile for ProjectVault brainstorming sessions.\n```\n","# ProjectVault: New Idea Design Skill\n\nYou are running the full single-idea brainstorm-to-spec workflow for the ProjectVault. This skill replaces `superpowers:brainstorming` entirely. Do not invoke that skill.\n\n## Step 0: Load Context\n\nBefore asking any questions, read:\n1. `_shared\u002FStack-Preferences.md`\n2. `_shared\u002FPrompter-Profile.md`\n\nIf `Stack-Preferences.md` is missing, run the stack setup flow (see below) before continuing.\nIf `Prompter-Profile.md` is missing, run the guest setup flow (see below) before continuing.\nIf both are missing, run stack setup first, then guest setup.\n\n---\n\n## Step 1: Richness Check\n\nAssess how much the prompter has already provided. Look for these 4 signals in their message:\n- **Slug**: is there a clear short name for the idea?\n- **Audience**: who is it for?\n- **Interaction model**: how does the user interact with it?\n- **Constraints**: any tech, scope, or platform constraints stated?\n\n| Signals present | Q&A approach |\n|-----------------|-------------|\n| All 4 | Skip questions. Confirm inferred scope in 1 message, get approval, proceed. |\n| 3 of 4 | Max 2 clarifying questions. |\n| 2 or fewer | Ask up to `max_clarifying_questions` (from profile, default: 4), one at a time. |\n\nNever exceed the profile's `max_clarifying_questions` cap.\n\n---\n\n## Step 2: Ask Clarifying Questions\n\nAsk one question at a time. Prefer multiple-choice options when possible. Stop as soon as you have enough to propose approaches.\n\n**Before each question, check:**\n- Is this topic in the profile's `skip_questions` list? If yes, skip it.\n- Is `assumed_stack: true`? If yes, skip all stack\u002Finfra questions.\n\n**Adapt framing based on `technical_depth`:**\n\n| technical_depth | Infra questions | Stack questions |\n|-----------------|----------------|-----------------|\n| senior \u002F mid | Ask directly: \"ECS or Lambda?\" | Ask directly: \"FastAPI or Django?\" |\n| junior | Ask as tradeoffs: \"Always-on vs pay-per-request?\" | Ask as outcomes: \"One language or best-fit per layer?\" |\n| non-technical | Suppress infra questions entirely | Ask as outcomes: \"Do users need accounts?\" |\n\n---\n\n## Step 3: Propose 2–3 Approaches\n\nPresent architectural options. Always lead with Approach A pre-populated from `Stack-Preferences.md` defaults. Include trade-offs for each. Make a clear recommendation with reasoning.\n\nWait for the prompter to choose before proceeding.\n\n---\n\n## Step 4: Present Design Sections\n\nWalk through the design one section at a time:\n1. Architecture overview\n2. Data model\n3. Frontend components + routes\n4. API endpoints + deployment\n\nAfter each section, ask: \"Does this look right?\" Wait for approval before moving on.\n\n**Visual companion:** If `prefer_visuals: true` in profile (and not already offered this session), offer the visual companion once before starting design sections:\n> \"Some of what we're working on might be easier to explain in a browser — mockups, diagrams, architecture views. Want to try it? (Requires opening a local URL)\"\n\nWait for response. Only offer once.\n\n---\n\n## Step 5: Create Files (in this exact order)\n\n### 1. `ideas\u002F[slug]\u002FOverview.md`\n```markdown\n---\ntags: [projectvault, [slug]]\ntype: index\nstatus: Exploring\ncreated: YYYY-MM-DD\n---\n\n# [Idea Name]\n\n## Elevator Pitch\n[One paragraph]\n\n## Goals\n- [goal 1]\n- [goal 2]\n\n## Non-Goals\n- [non-goal 1]\n\n## Status\nExploring\n```\n\n### 2. `ideas\u002F[slug]\u002FStack.md`\nUse this structure for each significant decision:\n```markdown\n## Decision: [e.g., Database]\n\n**Chosen:** [option]\n\n| Option | Pros | Cons |\n|--------|------|------|\n| ...    | ...  | ...  |\n\n**Why:** [reasoning]\n```\nInclude a Standing Decisions table at the end for choices that match Stack-Preferences defaults (no table needed, just list them with a note).\n\n### 3. `ideas\u002F[slug]\u002FArchitecture.md`\n- Mermaid `flowchart LR` for system overview (if more than 1 component)\n- Mermaid `erDiagram` for data model\n- Mermaid `flowchart TD` for component tree\n- JSON code block for any JSONB or complex schema shapes\n- API tables: Method | Path | Auth | Notes\n- Frontend routes table: Route | Type (SSR\u002FCSR) | Component | Notes\n\n### 4. `ideas\u002F[slug]\u002FPhases.md`\n```markdown\n## Phase 1: [Name]\n**Goal:** [one sentence]\n- [ ] [feature\u002Fcomponent]\n\n## Phase 2: [Name]\n...\n```\n\n### 5. `ideas\u002F[slug]\u002FDesign-Spec.md`\nNine required sections:\n1. Product Overview\n2. Users & Roles\n3. Core Model\n4. Data Model\n5. API\n6. Frontend\n7. Infrastructure\n8. Phased Build\n9. Out of Scope\n\n### 6. `ideas\u002F[slug]\u002FResearch\u002F*.html`\nSave all interactive artifacts from brainstorming as standalone static HTML files. Each file must be fully self-contained (no server required), respond to dark\u002Flight mode via CSS `prefers-color-scheme`, and retain click interactivity.\n\nName files semantically: `layout-types.html`, `design-architecture.html`, etc.\n\n### 7. Update `README.md`\nAdd a row to the Ideas table:\n```\n| [[ideas\u002F[slug]\u002FOverview\\|[slug]]] | Exploring | [stack summary] | [one-line description] |\n```\n\n---\n\n## Step 6: End State\n\nAfter all files are created:\n> \"Design complete. All files saved in `ideas\u002F[slug]\u002F`. When you're ready to build, say `\u002Fvault-init [slug]`.\"\n\nDo NOT invoke `writing-plans`. This vault is design-only. Implementation handoff happens via `ProjectInitialize.md`.\n\n---\n\n## Stack Setup Flow\n\nTriggered when `_shared\u002FStack-Preferences.md` is missing. Ask these questions one at a time, then write the file before continuing.\n\n1. \"What's your primary backend language?\" (e.g., Python, Go, TypeScript, Java)\n2. \"What's your preferred web framework for that language?\" (e.g., FastAPI, Django, Express, Spring)\n3. \"What's your default database?\" (e.g., PostgreSQL, MySQL, SQLite, DynamoDB)\n4. \"Where do you typically deploy?\" (e.g., AWS, GCP, Azure, Fly.io, self-hosted)\n5. \"Any preferred frontend approach?\" (e.g., Next.js, plain HTML\u002FHTMX, React SPA, no preference)\n6. \"Any preferred IaC tool?\" (e.g., Terraform, CDK, Pulumi, none)\n\nWrite the results to `_shared\u002FStack-Preferences.md`:\n\n```markdown\n---\ntags: [projectvault, stack]\ntype: reference\ncreated: YYYY-MM-DD\n---\n\n# Stack Preferences\n\nDefault technology choices for this ProjectVault. Override per-idea in `Stack.md`.\n\n| Domain | Choice | Notes |\n|--------|--------|-------|\n| Backend language | [answer] | |\n| Web framework | [answer] | |\n| Database | [answer] | |\n| Cloud \u002F deployment | [answer] | |\n| Frontend | [answer] | |\n| IaC | [answer] | |\n```\n\n---\n\n## First-Time Setup Flow\n\nTriggered when `Prompter-Profile.md` is missing. Ask these 4 questions (one at a time), then write the profile before doing anything else.\n\n1. \"What's your name?\"\n2. \"Are you technical? (yes \u002F somewhat \u002F no)\"\n   - yes → `technical_depth: senior`\n   - somewhat → `technical_depth: mid`\n   - no → `technical_depth: non-technical`\n3. \"Do you have a preferred tech stack, or would you like to be asked about it for each idea?\"\n   - have preferences → ask them to briefly describe their stack, set `assumed_stack: true` and capture choices in `stack_overrides`\n   - ask each time → `assumed_stack: false`\n4. \"When you mention an idea, do you want a full detailed design right away, or just a quick stub to come back to later?\"\n   - full → `rapid_mode_default: false`\n   - stub → `rapid_mode_default: true`\n\nWrite the profile to `_shared\u002FPrompter-Profile.md` using the schema below, then resume the current request.\n\n```yaml\n---\nname: [name]\nrole: owner\ntechnical_depth: [from Q2]\nassumed_stack: [from Q3]\nskip_questions: []\nrapid_mode_default: [from Q4]\nprefer_visuals: true\nmax_clarifying_questions: 4\nstack_overrides: {}\n---\n\n[Name]'s profile for ProjectVault brainstorming sessions.\n```\n",{"name":5,"description":7},"main","c5cfc6189ab5d14e0d8a5ce392f939cdcec18be1",".claude\u002Fskills\u002Fprojectvault-new-idea","https:\u002F\u002Fgithub.com\u002FJunqing\u002Fproject-vault","https:\u002F\u002Fgithub.com\u002FJunqing","2026-04-24 04:35:46",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add Junqing\u002Fproject-vault --skill projectvault-new-idea",{"tool":56,"command":57},"bunx","bunx skills add Junqing\u002Fproject-vault --skill projectvault-new-idea",{"tool":59,"command":60},"pnpm","pnpm dlx skills add Junqing\u002Fproject-vault --skill projectvault-new-idea","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJunqing\u002Fproject-vault\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fprojectvault-new-idea\u002FSKILL.md",true,[],[65,78,101,113,130,140],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":39},"01M71GCC1NC8BEDF502J5XKN1Z","vault-status","Use when \u002Fvault-status is invoked in ProjectVault. Reads README.md and renders a formatted table of all ideas with their status, stack, and description.","https:\u002F\u002Fgithub.com\u002FJunqing\u002Fproject-vault\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvault-status\u002FSKILL.md",[],[72,27,73,74,28,32,30,75,76,77],"status","vault status","table","ideas","README","with",{"skillNo":79,"name":80,"nameZh":6,"description":81,"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":89,"publishedAt":39},"01M71GC99B4VWN8W8WDXY3DCVN","vault-resync","Use when \u002Fvault-resync is invoked in ProjectVault, or when the user asks to resync, repair, or update the vault harness after workflow changes. Audits CLAUDE.md, skill files, README.md, and idea folder structures for drift, then proposes and applies fixes.","https:\u002F\u002Fgithub.com\u002FJunqing\u002Fproject-vault\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvault-resync\u002FSKILL.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[90,27,91,92,93,94,76,95,32,30,29,96,97,98,99,100,20],"vault resync","fixes","repair","harness","for","files","drift","changes","folder","update","user",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":39},"01M71GC7DJ3K21GWG6BSNW91DW","vault-init","Use when \u002Fvault-init is invoked in ProjectVault. Delegates to the projectvault-init-repo skill with the provided slug argument.","https:\u002F\u002Fgithub.com\u002FJunqing\u002Fproject-vault\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvault-init\u002FSKILL.md",[],[27,108,109,110,111,30,112,32,77],"vault init","init","repo","delegates","argument",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":39},"01M71GC46S2GW6M3EF4NFJBHQ7","projectvault-rapid-intake","Use when working in ProjectVault and the prompter lists multiple project ideas at once, or uses \u002Fintake. Creates Overview.md stubs (status: Seed) for each idea. Never creates Stack.md, Architecture.md, Phases.md, or Design-Spec.md — only Overview stubs.","https:\u002F\u002Fgithub.com\u002FJunqing\u002Fproject-vault\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fprojectvault-rapid-intake\u002FSKILL.md",[],[120,121,122,72,123,75,94,37,124,125,126,32,30,127,28,128,24,129,20],"intake","RAPID","projectvault rapid intake","never","overview","design","only","architecture","at","seed",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":39},"01M71GBYQ5HWJ3S9T6BNFVB09T","projectvault-init-repo","Use when working in ProjectVault and the prompter uses \u002Fvault-init [slug] or asks to move an idea to a real repo. Reads the idea's design files, generates ProjectInitialize.md, and updates the idea's status to Building.","https:\u002F\u002Fgithub.com\u002FJunqing\u002Fproject-vault\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fprojectvault-init-repo\u002FSKILL.md",[],[110,137,109,138,30,32,95,125,72,139,27,20],"projectvault init repo","updates","move",{"skillNo":141,"name":120,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":39},"01M71GBWS7NR9KRMZGEC3SQYWN","Use when \u002Fintake is invoked in ProjectVault. Delegates to the projectvault-rapid-intake skill for batch idea capture.","https:\u002F\u002Fgithub.com\u002FJunqing\u002Fproject-vault\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fintake\u002FSKILL.md",[],[120,146,20,94,111,30,147,32,121],"batch","capture"]