[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DTY777PF4HC0144WBJ5281":3,"skill-same:01M7DTY777PF4HC0144WBJ5281":53},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7DTY777PF4HC0144WBJ5281","mk-project-organization",null,"Correct file paths, project layout, and naming conventions. Two modes: advisory (return a path) and organize (restructure).","ngocsangyem\u002FMeowKit","ngocsangyem","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F33769536?v=4","01M6J3FSMJAG9PVQEGRT7AQ9J2","Sang Nguyen","01M6J3FSRTJG0MNP6NV71639RM",16,"MIT","https:\u002F\u002Fgithub.com\u002Fngocsangyem\u002FMeowKit\u002Fblob\u002Fmain\u002Fkit\u002Fbundles\u002Fcodex\u002Froot\u002F.agents\u002Fskills\u002Fmk-project-organization\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"mk-project-organization\"\ndescription: \"Correct file paths, project layout, and naming conventions. Two modes: advisory (return a path) and organize (restructure).\"\n---\n\n# Project Organization\n\nStandardize file locations, naming conventions, and directory structure for projects.\n\n## When to Use\n\n- Creating a file and need the correct path\n- Organizing existing files after a messy session\n- Enforcing naming conventions across the project\n- Other skills need to know where to save output (advisory mode)\n\nExplicit: `the project-organization skill [targets]`\n\n## Workflow Integration\n\nOperates in **Phase 6 (Reflect)** or advisory mode (called by any skill). Output supports the `documenter` agent.\n\n## Modes\n\n| Mode         | Trigger                           | Behavior                                   |\n| ------------ | --------------------------------- | ------------------------------------------ |\n| **Advisory** | Other skills reference this skill | Return correct path + naming for file type |\n| **Organize** | User invokes directly             | Scan → propose → confirm → execute         |\n\n## Process (Organize Mode)\n\n1. **Scan + categorize** — list all files, assign each to directory category per `references\u002Fdirectory-rules.md`, check naming conventions\n2. **Propose** — present changes as from → to table, ask user approval\n3. **Execute + report** — move\u002Frename files, create missing directories, list final structure\n\n## Process (Advisory Mode)\n\n1. Determine file type from context (source? doc? plan? test? asset?)\n2. Look up correct path from directory categories\n3. Apply naming rules (timestamped \u002F evergreen \u002F variant)\n4. Return: `{path}\u002F{name}.{ext}`\n\n## Output Format\n\n```\n## Project Organization: {scope}\n\n**Mode:** {advisory | organize}\n**Files scanned:** {N}\n**Issues found:** {N}\n\n### Changes\n| From | To | Reason |\n|------|------|--------|\n| {old path} | {new path} | {rule violated} |\n\n### Final Structure\n{tree view of organized directories}\n```\n\n## References\n\n| Reference                                                 | When to load                      | Content                                              |\n| --------------------------------------------------------- | --------------------------------- | ---------------------------------------------------- |\n| **[directory-rules.md](.\u002Freferences\u002Fdirectory-rules.md)** | Steps 2-4 — categorizing + naming | Directory categories, naming patterns, nesting logic |\n\n## Failure Handling\n\n| Failure                                   | Recovery                             |\n| ----------------------------------------- | ------------------------------------ |\n| File conflict (target exists)             | Ask user: overwrite, rename, or skip |\n| Protected path (.git, .env, node_modules) | Skip silently — never touch          |\n| No files found in target                  | Report \"No files found in {path}\"    |\n\n## Constraints\n\n- Never overwrite existing files without confirmation\n- Never touch `.git\u002F`, `node_modules\u002F`, `.env` files\n- Respect `.gitignore` patterns\n- Use `mk:` prefix conventions for .agents\u002Fskills\u002F directories\n\n## Gotchas\n\n- **Monorepo package `name` in `package.json` and the directory name can diverge silently** — a workspace package at `packages\u002Fauth-service\u002F` with `\"name\": \"@company\u002Fauth\"` is referenced by consumers as `@company\u002Fauth`, but path aliases, Docker build contexts, and some bundlers resolve by directory name; mismatch causes \"cannot find module\" errors that only appear after a fresh install in CI.\n- **`tsconfig.json` path aliases are NOT honored by test runners without separate config** — `paths: { \"@\u002F*\": [\"src\u002F*\"] }` in `tsconfig.json` resolves in `tsc` and Vite but Vitest and Jest use their own module resolvers; tests using `@\u002F` aliases silently fall through to `node_modules` lookup and fail with \"Cannot find module '@\u002Futils'\" unless `moduleNameMapper` (Jest) or `alias` (Vitest) is configured separately.\n- **Circular path aliases break tree-shaking and cause `undefined` at runtime** — `src\u002Futils\u002Findex.ts` re-exporting from `src\u002Fcomponents\u002F` which imports from `src\u002Futils\u002F` creates a circular dependency that bundlers resolve non-deterministically; the symptom is a component that is `undefined` when imported via the alias but defined when imported by relative path.\n- **Absolute imports (`src\u002F`) vs relative imports (`..\u002F..\u002F`) inconsistency prevents reliable refactoring** — mixing both styles means automated refactoring tools (VS Code \"move file\", `ts-morph`) update only the form they recognize; half the import sites break silently on any file move; enforce one style via ESLint `import\u002Fno-relative-parent-imports` or `import\u002Fno-absolute-path`.\n- **`.gitignore` patterns not applying to already-tracked files causes `dist\u002F` to appear in PRs** — if `dist\u002F` was committed before being added to `.gitignore`, git continues tracking it; `git rm -r --cached dist\u002F` is required to untrack it, and omitting this step means every build output change appears as a diff in PRs.","# Project Organization\n\nStandardize file locations, naming conventions, and directory structure for projects.\n\n## When to Use\n\n- Creating a file and need the correct path\n- Organizing existing files after a messy session\n- Enforcing naming conventions across the project\n- Other skills need to know where to save output (advisory mode)\n\nExplicit: `the project-organization skill [targets]`\n\n## Workflow Integration\n\nOperates in **Phase 6 (Reflect)** or advisory mode (called by any skill). Output supports the `documenter` agent.\n\n## Modes\n\n| Mode         | Trigger                           | Behavior                                   |\n| ------------ | --------------------------------- | ------------------------------------------ |\n| **Advisory** | Other skills reference this skill | Return correct path + naming for file type |\n| **Organize** | User invokes directly             | Scan → propose → confirm → execute         |\n\n## Process (Organize Mode)\n\n1. **Scan + categorize** — list all files, assign each to directory category per `references\u002Fdirectory-rules.md`, check naming conventions\n2. **Propose** — present changes as from → to table, ask user approval\n3. **Execute + report** — move\u002Frename files, create missing directories, list final structure\n\n## Process (Advisory Mode)\n\n1. Determine file type from context (source? doc? plan? test? asset?)\n2. Look up correct path from directory categories\n3. Apply naming rules (timestamped \u002F evergreen \u002F variant)\n4. Return: `{path}\u002F{name}.{ext}`\n\n## Output Format\n\n```\n## Project Organization: {scope}\n\n**Mode:** {advisory | organize}\n**Files scanned:** {N}\n**Issues found:** {N}\n\n### Changes\n| From | To | Reason |\n|------|------|--------|\n| {old path} | {new path} | {rule violated} |\n\n### Final Structure\n{tree view of organized directories}\n```\n\n## References\n\n| Reference                                                 | When to load                      | Content                                              |\n| --------------------------------------------------------- | --------------------------------- | ---------------------------------------------------- |\n| **[directory-rules.md](.\u002Freferences\u002Fdirectory-rules.md)** | Steps 2-4 — categorizing + naming | Directory categories, naming patterns, nesting logic |\n\n## Failure Handling\n\n| Failure                                   | Recovery                             |\n| ----------------------------------------- | ------------------------------------ |\n| File conflict (target exists)             | Ask user: overwrite, rename, or skip |\n| Protected path (.git, .env, node_modules) | Skip silently — never touch          |\n| No files found in target                  | Report \"No files found in {path}\"    |\n\n## Constraints\n\n- Never overwrite existing files without confirmation\n- Never touch `.git\u002F`, `node_modules\u002F`, `.env` files\n- Respect `.gitignore` patterns\n- Use `mk:` prefix conventions for .agents\u002Fskills\u002F directories\n\n## Gotchas\n\n- **Monorepo package `name` in `package.json` and the directory name can diverge silently** — a workspace package at `packages\u002Fauth-service\u002F` with `\"name\": \"@company\u002Fauth\"` is referenced by consumers as `@company\u002Fauth`, but path aliases, Docker build contexts, and some bundlers resolve by directory name; mismatch causes \"cannot find module\" errors that only appear after a fresh install in CI.\n- **`tsconfig.json` path aliases are NOT honored by test runners without separate config** — `paths: { \"@\u002F*\": [\"src\u002F*\"] }` in `tsconfig.json` resolves in `tsc` and Vite but Vitest and Jest use their own module resolvers; tests using `@\u002F` aliases silently fall through to `node_modules` lookup and fail with \"Cannot find module '@\u002Futils'\" unless `moduleNameMapper` (Jest) or `alias` (Vitest) is configured separately.\n- **Circular path aliases break tree-shaking and cause `undefined` at runtime** — `src\u002Futils\u002Findex.ts` re-exporting from `src\u002Fcomponents\u002F` which imports from `src\u002Futils\u002F` creates a circular dependency that bundlers resolve non-deterministically; the symptom is a component that is `undefined` when imported via the alias but defined when imported by relative path.\n- **Absolute imports (`src\u002F`) vs relative imports (`..\u002F..\u002F`) inconsistency prevents reliable refactoring** — mixing both styles means automated refactoring tools (VS Code \"move file\", `ts-morph`) update only the form they recognize; half the import sites break silently on any file move; enforce one style via ESLint `import\u002Fno-relative-parent-imports` or `import\u002Fno-absolute-path`.\n- **`.gitignore` patterns not applying to already-tracked files causes `dist\u002F` to appear in PRs** — if `dist\u002F` was committed before being added to `.gitignore`, git continues tracking it; `git rm -r --cached dist\u002F` is required to untrack it, and omitting this step means every build output change appears as a diff in PRs.",{"name":5,"description":7},"main","c7ff0a9e672de2c0590b03f6459385c2d7a63c1a","kit\u002Fbundles\u002Fcodex\u002Froot\u002F.agents\u002Fskills\u002Fmk-project-organization",3,"https:\u002F\u002Fgithub.com\u002Fngocsangyem\u002FMeowKit","https:\u002F\u002Fdocs.meowkit.dev\u002F","https:\u002F\u002Fgithub.com\u002Fngocsangyem","Keep moving forward","2026-11-15 03:54:21",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add ngocsangyem\u002FMeowKit --skill mk-project-organization",{"tool":39,"command":40},"bunx","bunx skills add ngocsangyem\u002FMeowKit --skill mk-project-organization",{"tool":42,"command":43},"pnpm","pnpm dlx skills add ngocsangyem\u002FMeowKit --skill mk-project-organization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fngocsangyem\u002FMeowKit\u002Fblob\u002Fmain\u002Fkit\u002Fbundles\u002Fcodex\u002Froot\u002F.agents\u002Fskills\u002Fmk-project-organization\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fdirectory-rules.md","REFERENCE","参考文档",2549,"https:\u002F\u002Fgithub.com\u002Fngocsangyem\u002FMeowKit\u002Fblob\u002Fmain\u002Fkit\u002Fbundles\u002Fcodex\u002Froot\u002F.agents\u002Fskills\u002Fmk-project-organization\u002Freferences\u002Fdirectory-rules.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7DVHF481B4J41T4855KGM50","mk-worktree","Manages git worktrees for parallel agent isolation: creates parallel\u002F{name}-{timestamp} branches, merges with conflict detection. NOT for user feature branches (use git worktree directly).","https:\u002F\u002Fgithub.com\u002Fngocsangyem\u002FMeowKit\u002Fblob\u002Fmain\u002Fkit\u002Fbundles\u002Fcursor\u002Froot\u002F.cursor\u002Fskills\u002Fmk-worktree\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7DVHAWVKDKPB1EA3F1NC4JC","mk-workflow-orchestrator","Auto-invoked 7-phase workflow for complex-feature intent; fasttrack mode for pre-approved specs. NOT for explicit single tasks (mk:cook), green-field builds (mk:autobuild), or simple fixes (mk:fix).","https:\u002F\u002Fgithub.com\u002Fngocsangyem\u002FMeowKit\u002Fblob\u002Fmain\u002Fkit\u002Fbundles\u002Fcursor\u002Froot\u002F.cursor\u002Fskills\u002Fmk-workflow-orchestrator\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7DVH6SYBHWW00TRZXCC56JW","mk-web-to-markdown","Fetch a URL and return clean markdown, for arbitrary external pages (blog, RFC, GitHub issue, vendor doc) not covered by mk:docs-finder. Static-only by default; opt-in JS rendering available.","https:\u002F\u002Fgithub.com\u002Fngocsangyem\u002FMeowKit\u002Fblob\u002Fmain\u002Fkit\u002Fbundles\u002Fcursor\u002Froot\u002F.cursor\u002Fskills\u002Fmk-web-to-markdown\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7DVH3HGW47BX3PEF30JV6EJ","mk-vulnerability-scanner","Vulnerability analysis: OWASP Top 10, current threat landscape, supply chain security, attack surface mapping, risk prioritization. Use for security audits. NOT for STRIDE\u002FCSO infra audits (mk:cso).","https:\u002F\u002Fgithub.com\u002Fngocsangyem\u002FMeowKit\u002Fblob\u002Fmain\u002Fkit\u002Fbundles\u002Fcursor\u002Froot\u002F.cursor\u002Fskills\u002Fmk-vulnerability-scanner\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7DVGZBKMB9WDFH9MFMA99FV","mk-vue","Vue 3 authoring\u002Freview: components, composables, reactivity, Pinia, Pinia Colada, file routing, forms. Composition API + script setup. Auto-activates on .vue files. Deep review: mk:vue-best-practices.","https:\u002F\u002Fgithub.com\u002Fngocsangyem\u002FMeowKit\u002Fblob\u002Fmain\u002Fkit\u002Fbundles\u002Fcursor\u002Froot\u002F.cursor\u002Fskills\u002Fmk-vue\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7DVGSE12AA1M7599HB8HRCT","mk-vue-testing-best-practices","Vue 3 testing best-practices review: Vitest + Vue Test Utils for components, composables, Pinia, Router, async\u002FSuspense, forms, a11y, plus Playwright E2E strategy. Advisory only.","https:\u002F\u002Fgithub.com\u002Fngocsangyem\u002FMeowKit\u002Fblob\u002Fmain\u002Fkit\u002Fbundles\u002Fcursor\u002Froot\u002F.cursor\u002Fskills\u002Fmk-vue-testing-best-practices\u002FSKILL.md",[],[]]