[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6G44W0NM2QT98G91C4VSWDR":3,"skill-same:01M6G44W0NM2QT98G91C4VSWDR":48},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":21,"linkOnly":22,"markdownContent":23,"markdownBody":24,"frontMatter":25,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M6G44W0NM2QT98G91C4VSWDR","conductor-setup",null,"reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fother\u002Fconductor-setup\u002FSKILL.md",[],[18,19,20],"setup","conductor setup","conductor","2026-11-10 10:12:30",false,"---\nname: conductor-setup\ndescription: \"Initialize project with Conductor artifacts (product definition,\"\n  tech stack, workflow, style guides)\nmetadata:\n  argument-hint: \"[--resume]\"\nrisk: unknown\nsource: community\n---\n\n# Conductor Setup\n\nInitialize or resume Conductor project setup. This command creates foundational project documentation through interactive Q&A.\n\n## Use this skill when\n\n- Working on conductor setup tasks or workflows\n- Needing guidance, best practices, or checklists for conductor setup\n\n## Do not use this skill when\n\n- The task is unrelated to conductor setup\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\n## Pre-flight Checks\n\n1. Check if `conductor\u002F` directory already exists in the project root:\n   - If `conductor\u002Fproduct.md` exists: Ask user whether to resume setup or reinitialize\n   - If `conductor\u002Fsetup_state.json` exists with incomplete status: Offer to resume from last step\n\n2. Detect project type by checking for existing indicators:\n   - **Greenfield (new project)**: No .git, no package.json, no requirements.txt, no go.mod, no src\u002F directory\n   - **Brownfield (existing project)**: Any of the above exist\n\n3. Load or create `conductor\u002Fsetup_state.json`:\n   ```json\n   {\n     \"status\": \"in_progress\",\n     \"project_type\": \"greenfield|brownfield\",\n     \"current_section\": \"product|guidelines|tech_stack|workflow|styleguides\",\n     \"current_question\": 1,\n     \"completed_sections\": [],\n     \"answers\": {},\n     \"files_created\": [],\n     \"started_at\": \"ISO_TIMESTAMP\",\n     \"last_updated\": \"ISO_TIMESTAMP\"\n   }\n   ```\n\n## Interactive Q&A Protocol\n\n**CRITICAL RULES:**\n\n- Ask ONE question per turn\n- Wait for user response before proceeding\n- Offer 2-3 suggested answers plus \"Type your own\" option\n- Maximum 5 questions per section\n- Update `setup_state.json` after each successful step\n- Validate file writes succeeded before continuing\n\n### Section 1: Product Definition (max 5 questions)\n\n**Q1: Project Name**\n\n```\nWhat is your project name?\n\nSuggested:\n1. [Infer from directory name]\n2. [Infer from package.json\u002Fgo.mod if brownfield]\n3. Type your own\n```\n\n**Q2: Project Description**\n\n```\nDescribe your project in one sentence.\n\nSuggested:\n1. A web application that [does X]\n2. A CLI tool for [doing Y]\n3. Type your own\n```\n\n**Q3: Problem Statement**\n\n```\nWhat problem does this project solve?\n\nSuggested:\n1. Users struggle to [pain point]\n2. There's no good way to [need]\n3. Type your own\n```\n\n**Q4: Target Users**\n\n```\nWho are the primary users?\n\nSuggested:\n1. Developers building [X]\n2. End users who need [Y]\n3. Internal teams managing [Z]\n4. Type your own\n```\n\n**Q5: Key Goals (optional)**\n\n```\nWhat are 2-3 key goals for this project? (Press enter to skip)\n```\n\n### Section 2: Product Guidelines (max 3 questions)\n\n**Q1: Voice and Tone**\n\n```\nWhat voice\u002Ftone should documentation and UI text use?\n\nSuggested:\n1. Professional and technical\n2. Friendly and approachable\n3. Concise and direct\n4. Type your own\n```\n\n**Q2: Design Principles**\n\n```\nWhat design principles guide this project?\n\nSuggested:\n1. Simplicity over features\n2. Performance first\n3. Developer experience focused\n4. User safety and reliability\n5. Type your own (comma-separated)\n```\n\n### Section 3: Tech Stack (max 5 questions)\n\nFor **brownfield projects**, first analyze existing code:\n\n- Run `Glob` to find package.json, requirements.txt, go.mod, Cargo.toml, etc.\n- Parse detected files to pre-populate tech stack\n- Present findings and ask for confirmation\u002Fadditions\n\n**Q1: Primary Language(s)**\n\n```\nWhat primary language(s) does this project use?\n\n[For brownfield: \"I detected: Python 3.11, JavaScript. Is this correct?\"]\n\nSuggested:\n1. TypeScript\n2. Python\n3. Go\n4. Rust\n5. Type your own (comma-separated)\n```\n\n**Q2: Frontend Framework (if applicable)**\n\n```\nWhat frontend framework (if any)?\n\nSuggested:\n1. React\n2. Vue\n3. Next.js\n4. None \u002F CLI only\n5. Type your own\n```\n\n**Q3: Backend Framework (if applicable)**\n\n```\nWhat backend framework (if any)?\n\nSuggested:\n1. Express \u002F Fastify\n2. Django \u002F FastAPI\n3. Go standard library\n4. None \u002F Frontend only\n5. Type your own\n```\n\n**Q4: Database (if applicable)**\n\n```\nWhat database (if any)?\n\nSuggested:\n1. PostgreSQL\n2. MongoDB\n3. SQLite\n4. None \u002F Stateless\n5. Type your own\n```\n\n**Q5: Infrastructure**\n\n```\nWhere will this be deployed?\n\nSuggested:\n1. AWS (Lambda, ECS, etc.)\n2. Vercel \u002F Netlify\n3. Self-hosted \u002F Docker\n4. Not decided yet\n5. Type your own\n```\n\n### Section 4: Workflow Preferences (max 4 questions)\n\n**Q1: TDD Strictness**\n\n```\nHow strictly should TDD be enforced?\n\nSuggested:\n1. Strict - tests required before implementation\n2. Moderate - tests encouraged, not blocked\n3. Flexible - tests recommended for complex logic\n```\n\n**Q2: Commit Strategy**\n\n```\nWhat commit strategy should be followed?\n\nSuggested:\n1. Conventional Commits (feat:, fix:, etc.)\n2. Descriptive messages, no format required\n3. Squash commits per task\n```\n\n**Q3: Code Review Requirements**\n\n```\nWhat code review policy?\n\nSuggested:\n1. Required for all changes\n2. Required for non-trivial changes\n3. Optional \u002F self-review OK\n```\n\n**Q4: Verification Checkpoints**\n\n```\nWhen should manual verification be required?\n\nSuggested:\n1. After each phase completion\n2. After each task completion\n3. Only at track completion\n```\n\n### Section 5: Code Style Guides (max 2 questions)\n\n**Q1: Languages to Include**\n\n```\nWhich language style guides should be generated?\n\n[Based on detected languages, pre-select]\n\nOptions:\n1. TypeScript\u002FJavaScript\n2. Python\n3. Go\n4. Rust\n5. All detected languages\n6. Skip style guides\n```\n\n**Q2: Existing Conventions**\n\n```\nDo you have existing linting\u002Fformatting configs to incorporate?\n\n[For brownfield: \"I found .eslintrc, .prettierrc. Should I incorporate these?\"]\n\nSuggested:\n1. Yes, use existing configs\n2. No, generate fresh guides\n3. Skip this step\n```\n\n## Artifact Generation\n\nAfter completing Q&A, generate the following files:\n\n### 1. conductor\u002Findex.md\n\n```markdown\n# Conductor - [Project Name]\n\nNavigation hub for project context.\n\n## Quick Links\n\n- Product Definition\n- Product Guidelines\n- Tech Stack\n- Workflow\n- Tracks\n\n## Active Tracks\n\n\u003C!-- Auto-populated by \u002Fconductor:new-track -->\n\n## Getting Started\n\nRun `\u002Fconductor:new-track` to create your first feature track.\n```\n\n### 2. conductor\u002Fproduct.md\n\nTemplate populated with Q&A answers for:\n\n- Project name and description\n- Problem statement\n- Target users\n- Key goals\n\n### 3. conductor\u002Fproduct-guidelines.md\n\nTemplate populated with:\n\n- Voice and tone\n- Design principles\n- Any additional standards\n\n### 4. conductor\u002Ftech-stack.md\n\nTemplate populated with:\n\n- Languages (with versions if detected)\n- Frameworks (frontend, backend)\n- Database\n- Infrastructure\n- Key dependencies (for brownfield, from package files)\n\n### 5. conductor\u002Fworkflow.md\n\nTemplate populated with:\n\n- TDD policy and strictness level\n- Commit strategy and conventions\n- Code review requirements\n- Verification checkpoint rules\n- Task lifecycle definition\n\n### 6. conductor\u002Ftracks.md\n\n```markdown\n# Tracks Registry\n\n| Status | Track ID | Title | Created | Updated |\n| ------ | -------- | ----- | ------- | ------- |\n\n\u003C!-- Tracks registered by \u002Fconductor:new-track -->\n```\n\n### 7. conductor\u002Fcode_styleguides\u002F\n\nGenerate selected style guides from `$CLAUDE_PLUGIN_ROOT\u002Ftemplates\u002Fcode_styleguides\u002F`\n\n## State Management\n\nAfter each successful file creation:\n\n1. Update `setup_state.json`:\n   - Add filename to `files_created` array\n   - Update `last_updated` timestamp\n   - If section complete, add to `completed_sections`\n2. Verify file exists with `Read` tool\n\n## Completion\n\nWhen all files are created:\n\n1. Set `setup_state.json` status to \"complete\"\n2. Display summary:\n\n   ```\n   Conductor setup complete!\n\n   Created artifacts:\n   - conductor\u002Findex.md\n   - conductor\u002Fproduct.md\n   - conductor\u002Fproduct-guidelines.md\n   - conductor\u002Ftech-stack.md\n   - conductor\u002Fworkflow.md\n   - conductor\u002Ftracks.md\n   - conductor\u002Fcode_styleguides\u002F[languages]\n\n   Next steps:\n   1. Review generated files and customize as needed\n   2. Run \u002Fconductor:new-track to create your first track\n   ```\n\n## Resume Handling\n\nIf `--resume` argument or resuming from state:\n\n1. Load `setup_state.json`\n2. Skip completed sections\n3. Resume from `current_section` and `current_question`\n4. Verify previously created files still exist\n5. If files missing, offer to regenerate\n\n## Error Handling\n\n- If file write fails: Halt and report error, do not update state\n- If user cancels: Save current state for future resume\n- If state file corrupted: Offer to start fresh or attempt recovery\n","# Conductor Setup\n\nInitialize or resume Conductor project setup. This command creates foundational project documentation through interactive Q&A.\n\n## Use this skill when\n\n- Working on conductor setup tasks or workflows\n- Needing guidance, best practices, or checklists for conductor setup\n\n## Do not use this skill when\n\n- The task is unrelated to conductor setup\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\n## Pre-flight Checks\n\n1. Check if `conductor\u002F` directory already exists in the project root:\n   - If `conductor\u002Fproduct.md` exists: Ask user whether to resume setup or reinitialize\n   - If `conductor\u002Fsetup_state.json` exists with incomplete status: Offer to resume from last step\n\n2. Detect project type by checking for existing indicators:\n   - **Greenfield (new project)**: No .git, no package.json, no requirements.txt, no go.mod, no src\u002F directory\n   - **Brownfield (existing project)**: Any of the above exist\n\n3. Load or create `conductor\u002Fsetup_state.json`:\n   ```json\n   {\n     \"status\": \"in_progress\",\n     \"project_type\": \"greenfield|brownfield\",\n     \"current_section\": \"product|guidelines|tech_stack|workflow|styleguides\",\n     \"current_question\": 1,\n     \"completed_sections\": [],\n     \"answers\": {},\n     \"files_created\": [],\n     \"started_at\": \"ISO_TIMESTAMP\",\n     \"last_updated\": \"ISO_TIMESTAMP\"\n   }\n   ```\n\n## Interactive Q&A Protocol\n\n**CRITICAL RULES:**\n\n- Ask ONE question per turn\n- Wait for user response before proceeding\n- Offer 2-3 suggested answers plus \"Type your own\" option\n- Maximum 5 questions per section\n- Update `setup_state.json` after each successful step\n- Validate file writes succeeded before continuing\n\n### Section 1: Product Definition (max 5 questions)\n\n**Q1: Project Name**\n\n```\nWhat is your project name?\n\nSuggested:\n1. [Infer from directory name]\n2. [Infer from package.json\u002Fgo.mod if brownfield]\n3. Type your own\n```\n\n**Q2: Project Description**\n\n```\nDescribe your project in one sentence.\n\nSuggested:\n1. A web application that [does X]\n2. A CLI tool for [doing Y]\n3. Type your own\n```\n\n**Q3: Problem Statement**\n\n```\nWhat problem does this project solve?\n\nSuggested:\n1. Users struggle to [pain point]\n2. There's no good way to [need]\n3. Type your own\n```\n\n**Q4: Target Users**\n\n```\nWho are the primary users?\n\nSuggested:\n1. Developers building [X]\n2. End users who need [Y]\n3. Internal teams managing [Z]\n4. Type your own\n```\n\n**Q5: Key Goals (optional)**\n\n```\nWhat are 2-3 key goals for this project? (Press enter to skip)\n```\n\n### Section 2: Product Guidelines (max 3 questions)\n\n**Q1: Voice and Tone**\n\n```\nWhat voice\u002Ftone should documentation and UI text use?\n\nSuggested:\n1. Professional and technical\n2. Friendly and approachable\n3. Concise and direct\n4. Type your own\n```\n\n**Q2: Design Principles**\n\n```\nWhat design principles guide this project?\n\nSuggested:\n1. Simplicity over features\n2. Performance first\n3. Developer experience focused\n4. User safety and reliability\n5. Type your own (comma-separated)\n```\n\n### Section 3: Tech Stack (max 5 questions)\n\nFor **brownfield projects**, first analyze existing code:\n\n- Run `Glob` to find package.json, requirements.txt, go.mod, Cargo.toml, etc.\n- Parse detected files to pre-populate tech stack\n- Present findings and ask for confirmation\u002Fadditions\n\n**Q1: Primary Language(s)**\n\n```\nWhat primary language(s) does this project use?\n\n[For brownfield: \"I detected: Python 3.11, JavaScript. Is this correct?\"]\n\nSuggested:\n1. TypeScript\n2. Python\n3. Go\n4. Rust\n5. Type your own (comma-separated)\n```\n\n**Q2: Frontend Framework (if applicable)**\n\n```\nWhat frontend framework (if any)?\n\nSuggested:\n1. React\n2. Vue\n3. Next.js\n4. None \u002F CLI only\n5. Type your own\n```\n\n**Q3: Backend Framework (if applicable)**\n\n```\nWhat backend framework (if any)?\n\nSuggested:\n1. Express \u002F Fastify\n2. Django \u002F FastAPI\n3. Go standard library\n4. None \u002F Frontend only\n5. Type your own\n```\n\n**Q4: Database (if applicable)**\n\n```\nWhat database (if any)?\n\nSuggested:\n1. PostgreSQL\n2. MongoDB\n3. SQLite\n4. None \u002F Stateless\n5. Type your own\n```\n\n**Q5: Infrastructure**\n\n```\nWhere will this be deployed?\n\nSuggested:\n1. AWS (Lambda, ECS, etc.)\n2. Vercel \u002F Netlify\n3. Self-hosted \u002F Docker\n4. Not decided yet\n5. Type your own\n```\n\n### Section 4: Workflow Preferences (max 4 questions)\n\n**Q1: TDD Strictness**\n\n```\nHow strictly should TDD be enforced?\n\nSuggested:\n1. Strict - tests required before implementation\n2. Moderate - tests encouraged, not blocked\n3. Flexible - tests recommended for complex logic\n```\n\n**Q2: Commit Strategy**\n\n```\nWhat commit strategy should be followed?\n\nSuggested:\n1. Conventional Commits (feat:, fix:, etc.)\n2. Descriptive messages, no format required\n3. Squash commits per task\n```\n\n**Q3: Code Review Requirements**\n\n```\nWhat code review policy?\n\nSuggested:\n1. Required for all changes\n2. Required for non-trivial changes\n3. Optional \u002F self-review OK\n```\n\n**Q4: Verification Checkpoints**\n\n```\nWhen should manual verification be required?\n\nSuggested:\n1. After each phase completion\n2. After each task completion\n3. Only at track completion\n```\n\n### Section 5: Code Style Guides (max 2 questions)\n\n**Q1: Languages to Include**\n\n```\nWhich language style guides should be generated?\n\n[Based on detected languages, pre-select]\n\nOptions:\n1. TypeScript\u002FJavaScript\n2. Python\n3. Go\n4. Rust\n5. All detected languages\n6. Skip style guides\n```\n\n**Q2: Existing Conventions**\n\n```\nDo you have existing linting\u002Fformatting configs to incorporate?\n\n[For brownfield: \"I found .eslintrc, .prettierrc. Should I incorporate these?\"]\n\nSuggested:\n1. Yes, use existing configs\n2. No, generate fresh guides\n3. Skip this step\n```\n\n## Artifact Generation\n\nAfter completing Q&A, generate the following files:\n\n### 1. conductor\u002Findex.md\n\n```markdown\n# Conductor - [Project Name]\n\nNavigation hub for project context.\n\n## Quick Links\n\n- Product Definition\n- Product Guidelines\n- Tech Stack\n- Workflow\n- Tracks\n\n## Active Tracks\n\n\u003C!-- Auto-populated by \u002Fconductor:new-track -->\n\n## Getting Started\n\nRun `\u002Fconductor:new-track` to create your first feature track.\n```\n\n### 2. conductor\u002Fproduct.md\n\nTemplate populated with Q&A answers for:\n\n- Project name and description\n- Problem statement\n- Target users\n- Key goals\n\n### 3. conductor\u002Fproduct-guidelines.md\n\nTemplate populated with:\n\n- Voice and tone\n- Design principles\n- Any additional standards\n\n### 4. conductor\u002Ftech-stack.md\n\nTemplate populated with:\n\n- Languages (with versions if detected)\n- Frameworks (frontend, backend)\n- Database\n- Infrastructure\n- Key dependencies (for brownfield, from package files)\n\n### 5. conductor\u002Fworkflow.md\n\nTemplate populated with:\n\n- TDD policy and strictness level\n- Commit strategy and conventions\n- Code review requirements\n- Verification checkpoint rules\n- Task lifecycle definition\n\n### 6. conductor\u002Ftracks.md\n\n```markdown\n# Tracks Registry\n\n| Status | Track ID | Title | Created | Updated |\n| ------ | -------- | ----- | ------- | ------- |\n\n\u003C!-- Tracks registered by \u002Fconductor:new-track -->\n```\n\n### 7. conductor\u002Fcode_styleguides\u002F\n\nGenerate selected style guides from `$CLAUDE_PLUGIN_ROOT\u002Ftemplates\u002Fcode_styleguides\u002F`\n\n## State Management\n\nAfter each successful file creation:\n\n1. Update `setup_state.json`:\n   - Add filename to `files_created` array\n   - Update `last_updated` timestamp\n   - If section complete, add to `completed_sections`\n2. Verify file exists with `Read` tool\n\n## Completion\n\nWhen all files are created:\n\n1. Set `setup_state.json` status to \"complete\"\n2. Display summary:\n\n   ```\n   Conductor setup complete!\n\n   Created artifacts:\n   - conductor\u002Findex.md\n   - conductor\u002Fproduct.md\n   - conductor\u002Fproduct-guidelines.md\n   - conductor\u002Ftech-stack.md\n   - conductor\u002Fworkflow.md\n   - conductor\u002Ftracks.md\n   - conductor\u002Fcode_styleguides\u002F[languages]\n\n   Next steps:\n   1. Review generated files and customize as needed\n   2. Run \u002Fconductor:new-track to create your first track\n   ```\n\n## Resume Handling\n\nIf `--resume` argument or resuming from state:\n\n1. Load `setup_state.json`\n2. Skip completed sections\n3. Resume from `current_section` and `current_question`\n4. Verify previously created files still exist\n5. If files missing, offer to regenerate\n\n## Error Handling\n\n- If file write fails: Halt and report error, do not update state\n- If user cancels: Save current state for future resume\n- If state file corrupted: Offer to start fresh or attempt recovery\n",{},"master","dff58085da947e81e8418c922055644bf0082b1b","skills\u002Fother\u002Fconductor-setup","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":7,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add reikiplanet\u002Fdaoskills --skill conductor-setup",{"tool":40,"command":41},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill conductor-setup",{"tool":43,"command":44},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill conductor-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fother\u002Fconductor-setup\u002FSKILL.md",true,[],[49,76,88,103,123,146],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":21},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75],"games","web games","web","grep","principles","selection","community","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":21},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[83,84,74,85,86,62,64,65,66,59,87,60],"ar","vr ar","interaction","requirements","performance",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":21},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[90,95,96,97,98,99,62,100,66,101,102,59],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","applications",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":21},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[110,111,112,113,114,62,115,116,117,118,100,119,120,121,122],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":21},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[130,131,132,133,134,135,136,137,62,66,59,138,60,139,140,141,142,143,144,145],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":21},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[153,154,155,156,157,158,159,160,143,100,161,162,163,62,164,165,166,140,167,168],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]