[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MXSQKB5R6DAPHDK8EA322B":3,"skill-same:01M6MXSQKB5R6DAPHDK8EA322B":61},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M6MXSQKB5R6DAPHDK8EA322B","project-init",null,"Initialize OpenLogos project structure and directory layout. Use when the user wants to set up a new project with openlogos init or needs help with project initialization.","miniidealab\u002Fopenlogos","miniidealab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4251156?v=4","01M6MX6BM454XESZCRPBQQHKRT","FredHuang","01M6MX6BR4417H4QA658D4GW9X",581,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Fplugin\u002Fskills\u002Fproject-init\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"init","project init","project","directory","project structure","help","SET","new project","initialize","user","use","up","structure","layout","with","initialization","2026-11-10 10:12:30",false,"---\nname: project-init\ndescription: \"Initialize OpenLogos project structure and directory layout. Use when the user wants to set up a new project with openlogos init or needs help with project initialization.\"\n---\n\n# Skill: Project Init\n\n> Initialize a project structure following the OpenLogos methodology, generating configuration files, AI instruction files, and standard directories.\n\n## Trigger Conditions\n\n- User requests creating a new project or initializing a project structure\n- User mentions \"openlogos init\" or \"initialize project\"\n- No `logos\u002Flogos.config.json` exists in the current directory\n\n## Core Capabilities\n\n1. Create the `logos\u002F` directory and its standard substructure\n2. Generate the `logos\u002Flogos.config.json` configuration file\n3. Generate the `logos\u002Flogos-project.yaml` AI collaboration index\n4. Generate `AGENTS.md` \u002F `CLAUDE.md` AI instruction files (in the root directory)\n5. Create the `logos\u002Fchanges\u002F` change management directory\n\n## Execution Steps\n\n### Step 1: Gather Project Information\n\nConfirm the following information with the user:\n\n- **Project name**: Used for the `name` field in `logos\u002Flogos.config.json`\n- **Project description**: A one-sentence description\n- **Tech stack**: Main framework, language, database, deployment platform\n- **Document modules**: Whether additional modules are needed beyond the default prd\u002Fapi\u002Fscenario\u002Fdatabase\n\nIf the user does not provide these, use reasonable defaults.\n\n### Step 2: Create Directory Structure\n\n```\nproject-root\u002F\n└── logos\u002F\n    ├── resources\u002F\n    │   ├── prd\u002F\n    │   │   ├── 1-product-requirements\u002F\n    │   │   ├── 2-product-design\u002F\n    │   │   │   ├── 1-feature-specs\u002F\n    │   │   │   └── 2-page-design\u002F\n    │   │   └── 3-technical-plan\u002F\n    │   │       ├── 1-architecture\u002F\n    │   │       └── 2-scenario-implementation\u002F\n    │   ├── api\u002F\n    │   ├── database\u002F\n    │   └── scenario\u002F\n    └── changes\u002F\n```\n\n### Step 3: Generate logos\u002Flogos.config.json\n\n```json\n{\n  \"name\": \"{project name}\",\n  \"description\": \"{project description}\",\n  \"documents\": {\n    \"prd\": {\n      \"label\": { \"en\": \"Product Docs\", \"zh\": \"产品文档\" },\n      \"path\": \".\u002Fresources\u002Fprd\",\n      \"pattern\": \"**\u002F*.{md,html,htm,pdf}\"\n    },\n    \"api\": {\n      \"label\": { \"en\": \"API Docs\", \"zh\": \"API 文档\" },\n      \"path\": \".\u002Fresources\u002Fapi\",\n      \"pattern\": \"**\u002F*.{yaml,yml,json}\"\n    },\n    \"scenario\": {\n      \"label\": { \"en\": \"Scenarios\", \"zh\": \"业务场景\" },\n      \"path\": \".\u002Fresources\u002Fscenario\",\n      \"pattern\": \"**\u002F*.json\"\n    },\n    \"database\": {\n      \"label\": { \"en\": \"Database\", \"zh\": \"数据库\" },\n      \"path\": \".\u002Fresources\u002Fdatabase\",\n      \"pattern\": \"**\u002F*.sql\"\n    }\n  }\n}\n```\n\n> The `path` field is relative to the directory where `logos.config.json` itself resides (i.e., `logos\u002F`), so `.\u002Fresources\u002Fprd` points to `logos\u002Fresources\u002Fprd`.\n\n### Step 4: Generate logos\u002Flogos-project.yaml\n\n```yaml\nproject:\n  name: \"{project name}\"\n  description: \"{project description}\"\n  methodology: \"OpenLogos\"\n\ntech_stack:\n  framework: \"{framework provided by user}\"\n  language: \"{language provided by user}\"\n  # ... populate based on user-provided information\n\nresource_index: []\n  # Initially empty; entries are added incrementally as documents are produced\n\nconventions:\n  - \"Follow the OpenLogos three-layer progression model (Why → What → How)\"\n  - \"Every change must first create a change proposal in logos\u002Fchanges\u002F\"\n```\n\n### Step 5: Generate AGENTS.md (Root Directory)\n\nGenerate AGENTS.md based on the content from Step 3 and Step 4, placed in the **project root directory**:\n\n```markdown\n# AI Assistant Instructions\n\nThis project follows the **OpenLogos** methodology.\nRead `logos\u002Flogos-project.yaml` first to understand the project resource index.\n\n## Project Context\n- Config: `logos\u002Flogos.config.json`\n- Resource Index: `logos\u002Flogos-project.yaml`\n- Tech Stack: {extracted from logos-project.yaml}\n\n## Methodology Rules\n1. Never write code without first completing the design documents\n2. Follow the Why → What → How progression\n3. All API designs must originate from scenario sequence diagrams\n4. All code changes must have corresponding API orchestration tests\n5. Use the Delta change workflow for iterations (see logos\u002Fchanges\u002F directory)\n\n## Conventions\n{extracted from conventions in logos-project.yaml}\n```\n\nAlso generate `CLAUDE.md` with identical content to AGENTS.md.\n\n### Step 6: Output Initialization Report\n\nReport to the user which files and directories were created, and provide next-step suggestions:\n\n1. Edit `logos\u002Flogos.config.json` to refine the project configuration\n2. Start with Phase 1: Write the requirements document\n3. Use the `prd-writer` Skill to assist with writing\n\n## Output Specification\n\n- `logos\u002Flogos.config.json`: Valid JSON, conforming to `logos\u002Fspec\u002Flogos.config.schema.json`\n- `logos\u002Flogos-project.yaml`: Valid YAML\n- `AGENTS.md` \u002F `CLAUDE.md`: Markdown format, located in the project root directory\n- All directories under `logos\u002F` are created; empty directories contain `.gitkeep`\n\n## Best Practices\n\n- **Don't over-configure**: Keep configuration minimal during initialization; let users refine it gradually during use\n- **resource_index starts empty**: Add entries as documents are produced, avoiding meaningless placeholder content\n- **Keep AGENTS.md concise**: Only include project-specific information; use fixed templates for universal methodology rules\n- **Prioritize creating the directory structure**: The `logos\u002F` directory structure is the first step in adopting the methodology — more important than any document\n- **Low intrusiveness**: All methodology assets are contained within `logos\u002F`, keeping the project's own structure clean\n\n## Recommended Prompts\n\nThe following prompts can be copied directly for use with AI:\n\n- `Help me initialize an OpenLogos project`\n- `Initialize this project with OpenLogos, the project name is xxx`\n- `Help me integrate OpenLogos into an existing project`\n","# Skill: Project Init\n\n> Initialize a project structure following the OpenLogos methodology, generating configuration files, AI instruction files, and standard directories.\n\n## Trigger Conditions\n\n- User requests creating a new project or initializing a project structure\n- User mentions \"openlogos init\" or \"initialize project\"\n- No `logos\u002Flogos.config.json` exists in the current directory\n\n## Core Capabilities\n\n1. Create the `logos\u002F` directory and its standard substructure\n2. Generate the `logos\u002Flogos.config.json` configuration file\n3. Generate the `logos\u002Flogos-project.yaml` AI collaboration index\n4. Generate `AGENTS.md` \u002F `CLAUDE.md` AI instruction files (in the root directory)\n5. Create the `logos\u002Fchanges\u002F` change management directory\n\n## Execution Steps\n\n### Step 1: Gather Project Information\n\nConfirm the following information with the user:\n\n- **Project name**: Used for the `name` field in `logos\u002Flogos.config.json`\n- **Project description**: A one-sentence description\n- **Tech stack**: Main framework, language, database, deployment platform\n- **Document modules**: Whether additional modules are needed beyond the default prd\u002Fapi\u002Fscenario\u002Fdatabase\n\nIf the user does not provide these, use reasonable defaults.\n\n### Step 2: Create Directory Structure\n\n```\nproject-root\u002F\n└── logos\u002F\n    ├── resources\u002F\n    │   ├── prd\u002F\n    │   │   ├── 1-product-requirements\u002F\n    │   │   ├── 2-product-design\u002F\n    │   │   │   ├── 1-feature-specs\u002F\n    │   │   │   └── 2-page-design\u002F\n    │   │   └── 3-technical-plan\u002F\n    │   │       ├── 1-architecture\u002F\n    │   │       └── 2-scenario-implementation\u002F\n    │   ├── api\u002F\n    │   ├── database\u002F\n    │   └── scenario\u002F\n    └── changes\u002F\n```\n\n### Step 3: Generate logos\u002Flogos.config.json\n\n```json\n{\n  \"name\": \"{project name}\",\n  \"description\": \"{project description}\",\n  \"documents\": {\n    \"prd\": {\n      \"label\": { \"en\": \"Product Docs\", \"zh\": \"产品文档\" },\n      \"path\": \".\u002Fresources\u002Fprd\",\n      \"pattern\": \"**\u002F*.{md,html,htm,pdf}\"\n    },\n    \"api\": {\n      \"label\": { \"en\": \"API Docs\", \"zh\": \"API 文档\" },\n      \"path\": \".\u002Fresources\u002Fapi\",\n      \"pattern\": \"**\u002F*.{yaml,yml,json}\"\n    },\n    \"scenario\": {\n      \"label\": { \"en\": \"Scenarios\", \"zh\": \"业务场景\" },\n      \"path\": \".\u002Fresources\u002Fscenario\",\n      \"pattern\": \"**\u002F*.json\"\n    },\n    \"database\": {\n      \"label\": { \"en\": \"Database\", \"zh\": \"数据库\" },\n      \"path\": \".\u002Fresources\u002Fdatabase\",\n      \"pattern\": \"**\u002F*.sql\"\n    }\n  }\n}\n```\n\n> The `path` field is relative to the directory where `logos.config.json` itself resides (i.e., `logos\u002F`), so `.\u002Fresources\u002Fprd` points to `logos\u002Fresources\u002Fprd`.\n\n### Step 4: Generate logos\u002Flogos-project.yaml\n\n```yaml\nproject:\n  name: \"{project name}\"\n  description: \"{project description}\"\n  methodology: \"OpenLogos\"\n\ntech_stack:\n  framework: \"{framework provided by user}\"\n  language: \"{language provided by user}\"\n  # ... populate based on user-provided information\n\nresource_index: []\n  # Initially empty; entries are added incrementally as documents are produced\n\nconventions:\n  - \"Follow the OpenLogos three-layer progression model (Why → What → How)\"\n  - \"Every change must first create a change proposal in logos\u002Fchanges\u002F\"\n```\n\n### Step 5: Generate AGENTS.md (Root Directory)\n\nGenerate AGENTS.md based on the content from Step 3 and Step 4, placed in the **project root directory**:\n\n```markdown\n# AI Assistant Instructions\n\nThis project follows the **OpenLogos** methodology.\nRead `logos\u002Flogos-project.yaml` first to understand the project resource index.\n\n## Project Context\n- Config: `logos\u002Flogos.config.json`\n- Resource Index: `logos\u002Flogos-project.yaml`\n- Tech Stack: {extracted from logos-project.yaml}\n\n## Methodology Rules\n1. Never write code without first completing the design documents\n2. Follow the Why → What → How progression\n3. All API designs must originate from scenario sequence diagrams\n4. All code changes must have corresponding API orchestration tests\n5. Use the Delta change workflow for iterations (see logos\u002Fchanges\u002F directory)\n\n## Conventions\n{extracted from conventions in logos-project.yaml}\n```\n\nAlso generate `CLAUDE.md` with identical content to AGENTS.md.\n\n### Step 6: Output Initialization Report\n\nReport to the user which files and directories were created, and provide next-step suggestions:\n\n1. Edit `logos\u002Flogos.config.json` to refine the project configuration\n2. Start with Phase 1: Write the requirements document\n3. Use the `prd-writer` Skill to assist with writing\n\n## Output Specification\n\n- `logos\u002Flogos.config.json`: Valid JSON, conforming to `logos\u002Fspec\u002Flogos.config.schema.json`\n- `logos\u002Flogos-project.yaml`: Valid YAML\n- `AGENTS.md` \u002F `CLAUDE.md`: Markdown format, located in the project root directory\n- All directories under `logos\u002F` are created; empty directories contain `.gitkeep`\n\n## Best Practices\n\n- **Don't over-configure**: Keep configuration minimal during initialization; let users refine it gradually during use\n- **resource_index starts empty**: Add entries as documents are produced, avoiding meaningless placeholder content\n- **Keep AGENTS.md concise**: Only include project-specific information; use fixed templates for universal methodology rules\n- **Prioritize creating the directory structure**: The `logos\u002F` directory structure is the first step in adopting the methodology — more important than any document\n- **Low intrusiveness**: All methodology assets are contained within `logos\u002F`, keeping the project's own structure clean\n\n## Recommended Prompts\n\nThe following prompts can be copied directly for use with AI:\n\n- `Help me initialize an OpenLogos project`\n- `Initialize this project with OpenLogos, the project name is xxx`\n- `Help me integrate OpenLogos into an existing project`\n",{"name":5,"description":7},"master","abf55fdedadaeb660f928aa7258b9ec35d4ab003","plugin\u002Fskills\u002Fproject-init",10,"https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos","https:\u002F\u002Fgithub.com\u002Fminiidealab","2026-10-18 11:36:11",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add miniidealab\u002Fopenlogos --skill project-init",{"tool":53,"command":54},"bunx","bunx skills add miniidealab\u002Fopenlogos --skill project-init",{"tool":56,"command":57},"pnpm","pnpm dlx skills add miniidealab\u002Fopenlogos --skill project-init","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Fplugin\u002Fskills\u002Fproject-init\u002FSKILL.md",true,[],[62,108,120,129,137,146],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":87,"publishedAt":35},"01M6MXX45142DGRFD9ZYPT5YC9","ui-ux-pro-max","UI\u002FUX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI\u002FUX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn\u002Fui MCP for component search and examples.","https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Fskills\u002Fui-ux-pro-max\u002FSKILL.md",[68,73,76,79,84],{"categoryNo":69,"categoryName":70,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":74,"categoryName":75,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":77,"categoryName":78,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":85,"categoryName":86,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000033","数据分析师",[88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107],"ui ux","pro","max","ui ux pro max","ui","ux","projects","mode","card","app","tsx","fix","improve","Tailwind","Charts","Animation","design","actions","MCP","search",{"skillNo":109,"name":110,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":116,"publishedAt":35},"01M6MXWY8HJV93BBR8FPNJXAMV","test-writer","https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-writer\u002FSKILL.md",[113],{"categoryNo":114,"categoryName":115,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000008","测试与质量",[117,118,119],"writer","test writer","test",{"skillNo":121,"name":122,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":126,"publishedAt":35},"01M6MXWSAMN9AD3T8F6N099ZGY","test-orchestrator","https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-orchestrator\u002FSKILL.md",[125],{"categoryNo":114,"categoryName":115,"taxonomyType":71,"taxonomyTypeDesc":72},[127,128,119],"orchestrator","test orchestrator",{"skillNo":130,"name":131,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":35},"01M6MXWN29FY7K9ASMFRSPWQCN","slice-planner","https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Fskills\u002Fslice-planner\u002FSKILL.md",[],[135,136],"slice planner","planner",{"skillNo":138,"name":139,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":35},"01M6MXWFR1C1V66NSRTAM1FZPR","scenario-architect","https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Fskills\u002Fscenario-architect\u002FSKILL.md",[],[143,144,145],"architect","scenario","scenario architect",{"skillNo":147,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":35},"01M6MXWD6ZCGPT4FDT580S8K96","https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Fskills\u002Fproject-init\u002FSKILL.md",[],[20,19,21]]