[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BCEWYHDS1FWAJ6G4CD9P54":3,"skill-same:01M7BCEWYHDS1FWAJ6G4CD9P54":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},"01M7BCEWYHDS1FWAJ6G4CD9P54","designing-in-patterns",null,"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.","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\u002Fplugins\u002Fsdlc\u002Fskills\u002Fdesigning-in-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: designing-in-patterns\ndescription: 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.\n---\n\n# designing-in-patterns — design method\n\n**Core principle:** a screen is assembled from components that already exist. The library moves before the screen, and every decision to add a component is made once, here, by the designer — never by whoever builds the screen.\n\n**Announce at start:** \"I'm using the designing-in-patterns skill.\"\n\nRepo-specific values (the vocabulary file, the bundle inventory folder, templates, board lint) are never named here: read them from the project-context `## Design` tokens and `.claude\u002Fproject\u002Fagents\u002Fdesigner.md`.\n\n## 1. Name every surface\n\n```text\nsurface := every visible thing on a board or in a spec, one row per surface per screen\nname    := a pattern from the `Pattern vocabulary` file, or `?` — never an invented name; on a wireframe it is the `data-pattern=\"\u003Cname>\"` tag of the block, never a visible label\ncounts  := a name counts only when the `Bundle inventory` folder has that component (ls\u002FGrep, never by reading component source)\nvocabulary names a component the inventory lacks -> the surface is `?`, not that pattern\n```\n\n## 2. Two tests before a `?` becomes new\n\n```text\nsecond occurrence := Grep the app's UI paths for the pattern\n                     present once as page code -> it is shared now: shared component AND a cleanup task in the same story (\"Replace \u003Cpath> with \u003CComponent>\")\nslot              := different children in an existing component meet the need -> reuse, note the slot; not new\nneither applies   -> new\n```\n\n## 3. Extend or new\n\n```text\nextend := a new option on an existing component: a tone, a size, a slot\nnew    := a different structure or behaviour\n```\n\nAn extension that needs a second rendering path inside the component is new; a new component that is the old one plus one option is an extension.\n\n## 4. Explore rows\n\nA row whose composition or feel the vocabulary does not settle is `Explore: yes`.\n\n```text\n2-3 shadcn compositions, each with phone and desktop behaviour and the keyboard behaviour they share\nbuilt as Storybook variant stories on the library branch (the `Component review` token serves them)\nthe human chooses before merge; losers are deleted in the same PR; only the winner reaches the bundle\nnever drawn by hand on a board\n```\n\n## 5. Reuse table\n\nOne format for `component-plan.md` and a spec's `## Reuse`:\n\n```text\n| Surface | Pattern | Template | Component | Action | Explore | Story |\n```\n\n| Column | Content |\n| --- | --- |\n| Surface | the visible thing as named on the draft (its `data-pattern` tag marks the pattern; `?` marks a gap) |\n| Pattern | a vocabulary name; `?` only while unsettled, never in a committed plan |\n| Template | the page template; `—` when the surface is not a page |\n| Component | the bundle export (PascalCase); `—` when none |\n| Action | `reuse` · `extend` · `new` |\n| Explore | `yes` · `no` |\n| Story | the library story key; `—` for `reuse` |\n\nA `new` row with no Story is an open question; the spec cannot be approved with it.\n\n## 5a. Controls inside a surface\n\nA pattern name settles the block, not what is drawn inside it. Before a plan is final, every distinct control and every list or table row structure is checked against the real bundle and library.\n\n```text\nverdict := reuse (a named export) | shadcn (a named ui part) | in source, not exported | compose (named parts; shared already or not) | missing\nanything but reuse | shadcn -> an open question with options and a recommendation; the human decides: extend, build new, export, accept the composition, or drop\na container being in the bundle says nothing about its rows, cells or items: check them by name\n```\n\nTable format and the rule: `refs\u002Fcomponent-plan.md` \"Controls checked\".\n\n## 6. Layering rules (the method respects these)\n\n```text\nslots not settings   := variation comes through children and slots, not a growing list of props\nno data in layers 1-4:= primitives, ui components, composites and layouts take values by props; no fetching, no domain types\nbuild downward       := a surface is built from layers below it; a higher layer never re-implements a lower one\nshared the second time:= the second use of a pattern makes it shared (test 2)\neverything in the bundle:= a component not exported to the design bundle does not exist for boards\n```\n\n## 7. Anti-patterns\n\n| Anti-pattern | Instead |\n| --- | --- |\n| Naming a pattern the bundle lacks | Mark the surface `?` and run the two tests |\n| A screen board introducing a component | Raise the library story first; the board mounts the bundle |\n| className restyling of a shared component | Change the component for everyone (extend), or reuse it unchanged |\n| A copy kept to pass a board | Fix the board or the component; never keep the copy |\n| Choosing the composition by hand-drawing it | Explore row: variant stories, human picks |\n","# designing-in-patterns — design method\n\n**Core principle:** a screen is assembled from components that already exist. The library moves before the screen, and every decision to add a component is made once, here, by the designer — never by whoever builds the screen.\n\n**Announce at start:** \"I'm using the designing-in-patterns skill.\"\n\nRepo-specific values (the vocabulary file, the bundle inventory folder, templates, board lint) are never named here: read them from the project-context `## Design` tokens and `.claude\u002Fproject\u002Fagents\u002Fdesigner.md`.\n\n## 1. Name every surface\n\n```text\nsurface := every visible thing on a board or in a spec, one row per surface per screen\nname    := a pattern from the `Pattern vocabulary` file, or `?` — never an invented name; on a wireframe it is the `data-pattern=\"\u003Cname>\"` tag of the block, never a visible label\ncounts  := a name counts only when the `Bundle inventory` folder has that component (ls\u002FGrep, never by reading component source)\nvocabulary names a component the inventory lacks -> the surface is `?`, not that pattern\n```\n\n## 2. Two tests before a `?` becomes new\n\n```text\nsecond occurrence := Grep the app's UI paths for the pattern\n                     present once as page code -> it is shared now: shared component AND a cleanup task in the same story (\"Replace \u003Cpath> with \u003CComponent>\")\nslot              := different children in an existing component meet the need -> reuse, note the slot; not new\nneither applies   -> new\n```\n\n## 3. Extend or new\n\n```text\nextend := a new option on an existing component: a tone, a size, a slot\nnew    := a different structure or behaviour\n```\n\nAn extension that needs a second rendering path inside the component is new; a new component that is the old one plus one option is an extension.\n\n## 4. Explore rows\n\nA row whose composition or feel the vocabulary does not settle is `Explore: yes`.\n\n```text\n2-3 shadcn compositions, each with phone and desktop behaviour and the keyboard behaviour they share\nbuilt as Storybook variant stories on the library branch (the `Component review` token serves them)\nthe human chooses before merge; losers are deleted in the same PR; only the winner reaches the bundle\nnever drawn by hand on a board\n```\n\n## 5. Reuse table\n\nOne format for `component-plan.md` and a spec's `## Reuse`:\n\n```text\n| Surface | Pattern | Template | Component | Action | Explore | Story |\n```\n\n| Column | Content |\n| --- | --- |\n| Surface | the visible thing as named on the draft (its `data-pattern` tag marks the pattern; `?` marks a gap) |\n| Pattern | a vocabulary name; `?` only while unsettled, never in a committed plan |\n| Template | the page template; `—` when the surface is not a page |\n| Component | the bundle export (PascalCase); `—` when none |\n| Action | `reuse` · `extend` · `new` |\n| Explore | `yes` · `no` |\n| Story | the library story key; `—` for `reuse` |\n\nA `new` row with no Story is an open question; the spec cannot be approved with it.\n\n## 5a. Controls inside a surface\n\nA pattern name settles the block, not what is drawn inside it. Before a plan is final, every distinct control and every list or table row structure is checked against the real bundle and library.\n\n```text\nverdict := reuse (a named export) | shadcn (a named ui part) | in source, not exported | compose (named parts; shared already or not) | missing\nanything but reuse | shadcn -> an open question with options and a recommendation; the human decides: extend, build new, export, accept the composition, or drop\na container being in the bundle says nothing about its rows, cells or items: check them by name\n```\n\nTable format and the rule: `refs\u002Fcomponent-plan.md` \"Controls checked\".\n\n## 6. Layering rules (the method respects these)\n\n```text\nslots not settings   := variation comes through children and slots, not a growing list of props\nno data in layers 1-4:= primitives, ui components, composites and layouts take values by props; no fetching, no domain types\nbuild downward       := a surface is built from layers below it; a higher layer never re-implements a lower one\nshared the second time:= the second use of a pattern makes it shared (test 2)\neverything in the bundle:= a component not exported to the design bundle does not exist for boards\n```\n\n## 7. Anti-patterns\n\n| Anti-pattern | Instead |\n| --- | --- |\n| Naming a pattern the bundle lacks | Mark the surface `?` and run the two tests |\n| A screen board introducing a component | Raise the library story first; the board mounts the bundle |\n| className restyling of a shared component | Change the component for everyone (extend), or reuse it unchanged |\n| A copy kept to pass a board | Fix the board or the component; never keep the copy |\n| Choosing the composition by hand-drawing it | Explore row: variant stories, human picks |\n",{"name":5,"description":7},"main","f05def4683d9cc0c3b39e87ee1043b64ad6dff24","plugins\u002Fsdlc\u002Fskills\u002Fdesigning-in-patterns",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 designing-in-patterns",{"tool":39,"command":40},"bunx","bunx skills add whimzyLive\u002Fnightshift-ai --skill designing-in-patterns",{"tool":42,"command":43},"pnpm","pnpm dlx skills add whimzyLive\u002Fnightshift-ai --skill designing-in-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fdesigning-in-patterns\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},"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",[],[],"2026-11-12 13:55:43",{"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":55},"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":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":55},"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":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":55},"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":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":55},"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",[],[],{"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":55},"01M75MSM0Z0AHA6YS4Q5E6R65T","writing-adrs","Use when authoring an Architecture Decision Record (ADR) — a short document that captures one significant, hard-to-reverse technical or architectural decision, its context, and its consequences. Triggered by the sdlc ADR pipeline (the knowledge-engineer agent behind \u002Fsdlc:docs seed adr and \u002Fsdlc:docs distill) when generating an ADR from a story, and by anyone hand-authoring an ADR under docs\u002Fadr\u002F today. Covers why ADRs are kept short and inverted-pyramid, the required sections (Title, Status, Decision, Context, Alternatives Considered, Consequences), the proposed→accepted→superseded (or →rejected) status lifecycle and the never-edit-only-supersede immutability rule, the NNNN-decision-slug.md filename convention, and the ADR frontmatter fields (status, agents, source-stories) the pipeline reads to route a generated ADR into docs\u002Fadr\u002Findex.md.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fwriting-adrs\u002FSKILL.md",[],[]]