[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75MPVY6WGJAM53C5XBWW855":3,"skill-same:01M75MPVY6WGJAM53C5XBWW855":47},{"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},"01M75MPVY6WGJAM53C5XBWW855","nx-generate",null,"Generate code using nx generators. INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps\u002Flibs, or setting up project structure. Trigger words - scaffold, setup, create a new app, create a new lib, project structure, generate, add a new project. ALWAYS use this BEFORE calling nx_docs or exploring - this skill handles discovery internally.","whimzyLive\u002Fnightshift-ai","whimzyLive","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F22066605?v=4","01M75MMH22XX6R3NTAFHD7HEN7","Rushi Patel","01M75MMH32DHVVC61XRSHWVEV2",3,"MIT","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fnx-generate\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: nx-generate\ndescription: Generate code using nx generators. INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps\u002Flibs, or setting up project structure. Trigger words - scaffold, setup, create a new app, create a new lib, project structure, generate, add a new project. ALWAYS use this BEFORE calling nx_docs or exploring - this skill handles discovery internally.\n---\n\n# Run Nx Generator\n\nNx generators are powerful tools that scaffold projects, make automated code migrations or automate repetitive tasks in a monorepo. They ensure consistency across the codebase and reduce boilerplate work.\n\nThis skill applies when the user wants to:\n\n- Create new projects like libraries or applications\n- Scaffold features or boilerplate code\n- Run workspace-specific or custom generators\n- Do anything else that an nx generator exists for\n\n## Key Principles\n\n1. **Always use `--no-interactive`** - Prevents prompts that would hang execution\n2. **Read the generator source code** - The schema alone is not enough; understand what the generator actually does\n3. **Match existing repo patterns** - Study similar artifacts in the repo and follow their conventions\n4. **Verify with lint\u002Ftest\u002Fbuild\u002Ftypecheck etc.** - Generated code must pass verification. The listed targets are just an example, use what's appropriate for this workspace.\n\n## Steps\n\n### 1. Discover Available Generators\n\nUse the Nx CLI to discover available generators:\n\n- List all generators for a plugin: `npx nx list @nx\u002Freact`\n- View available plugins: `npx nx list`\n\nThis includes plugin generators (e.g., `@nx\u002Freact:library`) and local workspace generators.\n\n### 2. Match Generator to User Request\n\nIdentify which generator(s) could fulfill the user's needs. Consider what artifact type they want, which framework is relevant, and any specific generator names mentioned.\n\n**IMPORTANT**: When both a local workspace generator and an external plugin generator could satisfy the request, **always prefer the local workspace generator**. Local generators are customized for the specific repo's patterns.\n\nIf no suitable generator exists, you can stop using this skill. However, the burden of proof is high—carefully consider all available generators before deciding none apply.\n\n### 3. Get Generator Options\n\nUse the `--help` flag to understand available options:\n\n```bash\nnpx nx g @nx\u002Freact:library --help\n```\n\nPay attention to required options, defaults that might need overriding, and options relevant to the user's request.\n\n### Library Buildability\n\n**Default to non-buildable libraries** unless there's a specific reason for buildable.\n\n| Type                        | When to use                                                       | Generator flags                     |\n| --------------------------- | ----------------------------------------------------------------- | ----------------------------------- |\n| **Non-buildable** (default) | Internal monorepo libs consumed by apps                           | No `--bundler` flag                 |\n| **Buildable**               | Publishing to npm, cross-repo sharing, stable libs for cache hits | `--bundler=vite` or `--bundler=swc` |\n\nNon-buildable libs:\n\n- Export `.ts`\u002F`.tsx` source directly\n- Consumer's bundler compiles them\n- Faster dev experience, less config\n\nBuildable libs:\n\n- Have their own build target\n- Useful for stable libs that rarely change (cache hits)\n- Required for npm publishing\n\n**If unclear, ask the user:** \"Should this library be buildable (own build step, better caching) or non-buildable (source consumed directly, simpler setup)?\"\n\n### 4. Read Generator Source Code\n\n**This step is critical.** The schema alone does not tell you everything. Reading the source code helps you:\n\n- Know exactly what files will be created\u002Fmodified and where\n- Understand side effects (updating configs, installing deps, etc.)\n- Identify behaviors and options not obvious from the schema\n- Understand how options interact with each other\n\nTo find generator source code:\n\n- For plugin generators: Use `node -e \"console.log(require.resolve('@nx\u002F\u003Cplugin>\u002Fgenerators.json'));\"` to find the generators.json, then locate the source from there\n- If that fails, read directly from `node_modules\u002F\u003Cplugin>\u002Fgenerators.json`\n- For local generators: Typically in `tools\u002Fgenerators\u002F` or a local plugin directory. Search the repo for the generator name.\n\nAfter reading the source, reconsider: Is this the right generator? If not, go back to step 2.\n\n> **⚠️ `--directory` flag behavior can be misleading.**\n> It should specify the full path of the generated library or component, not the parent path that it will be generated in.\n>\n> ```bash\n> # ✅ Correct - directory is the full path for the library\n> nx g @nx\u002Freact:library --directory=libs\u002Fmy-lib\n> # generates libs\u002Fmy-lib\u002Fpackage.json and more\n>\n> # ❌ Wrong - this will create files at libs and libs\u002Fsrc\u002F...\n> nx g @nx\u002Freact:library --name=my-lib --directory=libs\n> # generates libs\u002Fpackage.json and more\n> ```\n\n### 5. Examine Existing Patterns\n\nBefore generating, examine the target area of the codebase:\n\n- Look at similar existing artifacts (other libraries, applications, etc.)\n- Identify naming conventions, file structures, and configuration patterns\n- Note which test runners, build tools, and linters are used\n- Configure the generator to match these patterns\n\n### 6. Dry-Run to Verify File Placement\n\n**Always run with `--dry-run` first** to verify files will be created in the correct location:\n\n```bash\nnpx nx g @nx\u002Freact:library --name=my-lib --dry-run --no-interactive\n```\n\nReview the output carefully. If files would be created in the wrong location, adjust your options based on what you learned from the generator source code.\n\nNote: Some generators don't support dry-run (e.g., if they install npm packages). If dry-run fails for this reason, proceed to running the generator for real.\n\n### 7. Run the Generator\n\nExecute the generator:\n\n```bash\nnx generate \u003Cgenerator-name> \u003Coptions> --no-interactive\n```\n\n> **Tip:** New packages often need workspace dependencies wired up (e.g., importing shared types, being consumed by apps). The `link-workspace-packages` skill can help add these correctly.\n\n### 8. Modify Generated Code (If Needed)\n\nGenerators provide a starting point. Modify the output as needed to:\n\n- Add or modify functionality as requested\n- Adjust imports, exports, or configurations\n- Integrate with existing code patterns\n\n**Important:** If you replace or delete generated test files (e.g., `*.spec.ts`), either write meaningful replacement tests or remove the `test` target from the project configuration. Empty test suites will cause `nx test` to fail.\n\n### 9. Format and Verify\n\nFormat all generated\u002Fmodified files:\n\n```bash\nnx format --fix\n```\n\nThis example is for built-in nx formatting with prettier. There might be other formatting tools for this workspace, use these when appropriate.\n\nThen verify the generated code works. Keep in mind that the changes you make with a generator or subsequent modifications might impact various projects so it's usually not enough to only run targets for the artifact you just created.\n\n```bash\n# these targets are just an example!\nnx run-many -t build,lint,test,typecheck\n```\n\nThese targets are common examples used across many workspaces. You should do research into other targets available for this workspace and its projects. CI configuration is usually a good guide for what the critical targets are that have to pass.\n\nIf verification fails with manageable issues (a few lint errors, minor type issues), fix them. If issues are extensive, attempt obvious fixes first, then escalate to the user with details about what was generated, what's failing, and what you've attempted.\n","# Run Nx Generator\n\nNx generators are powerful tools that scaffold projects, make automated code migrations or automate repetitive tasks in a monorepo. They ensure consistency across the codebase and reduce boilerplate work.\n\nThis skill applies when the user wants to:\n\n- Create new projects like libraries or applications\n- Scaffold features or boilerplate code\n- Run workspace-specific or custom generators\n- Do anything else that an nx generator exists for\n\n## Key Principles\n\n1. **Always use `--no-interactive`** - Prevents prompts that would hang execution\n2. **Read the generator source code** - The schema alone is not enough; understand what the generator actually does\n3. **Match existing repo patterns** - Study similar artifacts in the repo and follow their conventions\n4. **Verify with lint\u002Ftest\u002Fbuild\u002Ftypecheck etc.** - Generated code must pass verification. The listed targets are just an example, use what's appropriate for this workspace.\n\n## Steps\n\n### 1. Discover Available Generators\n\nUse the Nx CLI to discover available generators:\n\n- List all generators for a plugin: `npx nx list @nx\u002Freact`\n- View available plugins: `npx nx list`\n\nThis includes plugin generators (e.g., `@nx\u002Freact:library`) and local workspace generators.\n\n### 2. Match Generator to User Request\n\nIdentify which generator(s) could fulfill the user's needs. Consider what artifact type they want, which framework is relevant, and any specific generator names mentioned.\n\n**IMPORTANT**: When both a local workspace generator and an external plugin generator could satisfy the request, **always prefer the local workspace generator**. Local generators are customized for the specific repo's patterns.\n\nIf no suitable generator exists, you can stop using this skill. However, the burden of proof is high—carefully consider all available generators before deciding none apply.\n\n### 3. Get Generator Options\n\nUse the `--help` flag to understand available options:\n\n```bash\nnpx nx g @nx\u002Freact:library --help\n```\n\nPay attention to required options, defaults that might need overriding, and options relevant to the user's request.\n\n### Library Buildability\n\n**Default to non-buildable libraries** unless there's a specific reason for buildable.\n\n| Type                        | When to use                                                       | Generator flags                     |\n| --------------------------- | ----------------------------------------------------------------- | ----------------------------------- |\n| **Non-buildable** (default) | Internal monorepo libs consumed by apps                           | No `--bundler` flag                 |\n| **Buildable**               | Publishing to npm, cross-repo sharing, stable libs for cache hits | `--bundler=vite` or `--bundler=swc` |\n\nNon-buildable libs:\n\n- Export `.ts`\u002F`.tsx` source directly\n- Consumer's bundler compiles them\n- Faster dev experience, less config\n\nBuildable libs:\n\n- Have their own build target\n- Useful for stable libs that rarely change (cache hits)\n- Required for npm publishing\n\n**If unclear, ask the user:** \"Should this library be buildable (own build step, better caching) or non-buildable (source consumed directly, simpler setup)?\"\n\n### 4. Read Generator Source Code\n\n**This step is critical.** The schema alone does not tell you everything. Reading the source code helps you:\n\n- Know exactly what files will be created\u002Fmodified and where\n- Understand side effects (updating configs, installing deps, etc.)\n- Identify behaviors and options not obvious from the schema\n- Understand how options interact with each other\n\nTo find generator source code:\n\n- For plugin generators: Use `node -e \"console.log(require.resolve('@nx\u002F\u003Cplugin>\u002Fgenerators.json'));\"` to find the generators.json, then locate the source from there\n- If that fails, read directly from `node_modules\u002F\u003Cplugin>\u002Fgenerators.json`\n- For local generators: Typically in `tools\u002Fgenerators\u002F` or a local plugin directory. Search the repo for the generator name.\n\nAfter reading the source, reconsider: Is this the right generator? If not, go back to step 2.\n\n> **⚠️ `--directory` flag behavior can be misleading.**\n> It should specify the full path of the generated library or component, not the parent path that it will be generated in.\n>\n> ```bash\n> # ✅ Correct - directory is the full path for the library\n> nx g @nx\u002Freact:library --directory=libs\u002Fmy-lib\n> # generates libs\u002Fmy-lib\u002Fpackage.json and more\n>\n> # ❌ Wrong - this will create files at libs and libs\u002Fsrc\u002F...\n> nx g @nx\u002Freact:library --name=my-lib --directory=libs\n> # generates libs\u002Fpackage.json and more\n> ```\n\n### 5. Examine Existing Patterns\n\nBefore generating, examine the target area of the codebase:\n\n- Look at similar existing artifacts (other libraries, applications, etc.)\n- Identify naming conventions, file structures, and configuration patterns\n- Note which test runners, build tools, and linters are used\n- Configure the generator to match these patterns\n\n### 6. Dry-Run to Verify File Placement\n\n**Always run with `--dry-run` first** to verify files will be created in the correct location:\n\n```bash\nnpx nx g @nx\u002Freact:library --name=my-lib --dry-run --no-interactive\n```\n\nReview the output carefully. If files would be created in the wrong location, adjust your options based on what you learned from the generator source code.\n\nNote: Some generators don't support dry-run (e.g., if they install npm packages). If dry-run fails for this reason, proceed to running the generator for real.\n\n### 7. Run the Generator\n\nExecute the generator:\n\n```bash\nnx generate \u003Cgenerator-name> \u003Coptions> --no-interactive\n```\n\n> **Tip:** New packages often need workspace dependencies wired up (e.g., importing shared types, being consumed by apps). The `link-workspace-packages` skill can help add these correctly.\n\n### 8. Modify Generated Code (If Needed)\n\nGenerators provide a starting point. Modify the output as needed to:\n\n- Add or modify functionality as requested\n- Adjust imports, exports, or configurations\n- Integrate with existing code patterns\n\n**Important:** If you replace or delete generated test files (e.g., `*.spec.ts`), either write meaningful replacement tests or remove the `test` target from the project configuration. Empty test suites will cause `nx test` to fail.\n\n### 9. Format and Verify\n\nFormat all generated\u002Fmodified files:\n\n```bash\nnx format --fix\n```\n\nThis example is for built-in nx formatting with prettier. There might be other formatting tools for this workspace, use these when appropriate.\n\nThen verify the generated code works. Keep in mind that the changes you make with a generator or subsequent modifications might impact various projects so it's usually not enough to only run targets for the artifact you just created.\n\n```bash\n# these targets are just an example!\nnx run-many -t build,lint,test,typecheck\n```\n\nThese targets are common examples used across many workspaces. You should do research into other targets available for this workspace and its projects. CI configuration is usually a good guide for what the critical targets are that have to pass.\n\nIf verification fails with manageable issues (a few lint errors, minor type issues), fix them. If issues are extensive, attempt obvious fixes first, then escalate to the user with details about what was generated, what's failing, and what you've attempted.\n",{"name":5,"description":7},"main","7d4ebd573a4218d5e92eced411b259f34e9203fe",".opencode\u002Fskills\u002Fnx-generate",0,"https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai","https:\u002F\u002Fwithnightshift.com\u002F","https:\u002F\u002Fgithub.com\u002FwhimzyLive","Creator of @typedorm","2026-11-14 22:45:42",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add whimzyLive\u002Fnightshift-ai --skill nx-generate",{"tool":39,"command":40},"bunx","bunx skills add whimzyLive\u002Fnightshift-ai --skill nx-generate",{"tool":42,"command":43},"pnpm","pnpm dlx skills add whimzyLive\u002Fnightshift-ai --skill nx-generate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fnx-generate\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M7BCEWYHDS1FWAJ6G4CD9P54","designing-in-patterns","Use when designing, planning or auditing UI against a component library — naming surfaces with the repo's pattern vocabulary, deciding reuse versus extend versus new, exploring compositions, or writing the reuse table (component-plan.md, a spec's `## Reuse`, a UI audit). Carries the design method; the repo's own vocabulary, bundle and board rules come from project-context and the designer override.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fdesigning-in-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M75MVN6GACAC87SV9RBPBMKH","typeorm","Use when defining TypeORM entities, writing migrations, or building repository\u002Fquery-builder code in TypeScript. Covers entity and relation decorators, the Data Mapper pattern, migrations, the query builder, transactions, and multi-database configuration.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Ftypeorm\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M75MTEZV8SAZNS20YDSB7KG2","hono-api","Use when building or extending REST APIs with Hono + @hono\u002Fzod-openapi. Covers schema-first route declaration with createRoute, feature-grouped composable routers, a class-based service layer behind interfaces, the strategy pattern for multi-event webhooks, typed request validation, and auto-generated OpenAPI docs.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Fhono-api\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M75MTB91SB6HPB3ZRT20F950","electrodb","Use when defining DynamoDB entities, modeling indexes, or writing queries\u002Fmutations with the ElectroDB ORM. Covers entity schema, access patterns, CRUD operations, update expressions, and single-table design patterns.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Felectrodb\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M75MT7KT9A3XYX38TX5MY6MA","atomic-design","Use when structuring or decomposing any frontend UI into reusable components, regardless of framework. Applies Brad Frost's atomic design methodology — atoms, molecules, organisms, templates, and pages — to guide consistent component hierarchy, naming, and composition decisions.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Fatomic-design\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M75MSTQ54EY0K29PKBF212K1","writing-docs","Use when writing, restructuring, or reviewing any prose documentation — a tutorial, how-to guide, reference page, or explanation\u002Fconceptual doc — for a public docs site (e.g. Mintlify MDX, docs\u002F, README material), a getting-started guide, an API\u002FCLI reference page, or a \"why we built it this way\" conceptual page. Applies the Diátaxis framework (see https:\u002F\u002Fdiataxis.fr\u002F) — every document belongs to exactly one of the four quadrants (tutorial \u002F how-to guide \u002F reference \u002F explanation), and mixing quadrants inside one document is the single most common documentation failure. Covers the four-quadrant compass for picking the right form, per-quadrant structure templates, an anti-pattern list for quadrant drift, and generic voice\u002Fcraft rules — repo-specific voice and target output format (e.g. Mintlify MDX) are resolved from the repo's docs-manifest (falling back to project-context), never hardcoded here.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fwriting-docs\u002FSKILL.md",[],[]]