[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75MT7KT9A3XYX38TX5MY6MA":3,"skill-same:01M75MT7KT9A3XYX38TX5MY6MA":57},{"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},"01M75MT7KT9A3XYX38TX5MY6MA","atomic-design",null,"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.","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\u002Fskills\u002Fatomic-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: atomic-design\ndescription: 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.\n---\n\n# Atomic Design — Component Hierarchy Methodology\n\nAtomic design is a mental model for breaking any user interface into five distinct levels of\nstructural complexity — atoms, molecules, organisms, templates, and pages — borrowed from\nchemistry's atoms-to-matter progression. It gives teams a shared vocabulary for talking about UI\nstructure and a repeatable way to decide \"does this need to be its own piece, and how big should\nthat piece be?\" The methodology itself is **framework-agnostic**: it describes how to think about\ncomposition, not which library or platform renders the result.\n\n## Why atomic design (rationale)\n\nWithout a shared hierarchy, teams tend to build UI ad hoc: some pieces get over-extracted into\ncomponents nobody reuses, others get duplicated because nobody realized a smaller shared piece\nalready existed, and naming drifts (is this a \"card,\" a \"widget,\" a \"block\"?). Atomic design solves\nthree recurring problems:\n\n- **Consistency** — the same five labels describe every piece of UI, so a design system and its\n  implementation stay aligned no matter who's talking about it.\n- **Reuse** — decomposing top-down into smaller named levels surfaces the shared building blocks\n  (a label, a button) that would otherwise get re-created inside every larger piece that needs one.\n- **Scalable vocabulary** — \"this is a molecule, not an organism\" is a fast, unambiguous design\n  conversation once the levels are understood, replacing long back-and-forth about scope.\n\nThe levels are a thinking tool, not a rigid folder structure to enforce everywhere — use them to\nreason about granularity, not as a law that every project must nest five matching directories.\n\n## The five levels (overview)\n\n1. **Atoms** — the smallest indivisible UI building blocks: a label, a single input field, a single\n   control. An atom has no meaningful sub-parts; splitting it further removes function rather than\n   simplifying it.\n2. **Molecules** — a small group of atoms bonded together to do one thing, such as a labelled input\n   paired with a submit control. A grouping becomes a molecule once two or more atoms combine for a\n   single, reusable purpose.\n3. **Organisms** — relatively complex groups of molecules and\u002For atoms that form a distinct,\n   recognisable section of an interface, such as a page header or a grid of item summaries. A\n   grouping becomes an organism once it reads as a standalone region rather than a helper piece.\n4. **Templates** — page-level layout skeletons that arrange organisms into a structure using\n   placeholder content. Templates are about arrangement, not real content.\n5. **Pages** — specific instances of a template populated with real, representative content. Pages\n   are the concrete end state used to validate that the whole system actually works with real data.\n\nSee [references\u002Fhierarchy.md](references\u002Fhierarchy.md) for the expanded per-level guidance —\ndefinitions, boundary rules, and additional neutral examples for each level.\n\n## How to apply it (decomposition workflow)\n\nFollow this ordered procedure to decompose an arbitrary UI description into the five levels:\n\n1. **Start from the whole screen.** Identify the page as the top-level unit — the thing a user\n   actually sees, with real content.\n2. **Strip content to find the template.** Mentally replace the real content with placeholders.\n   What's left — the arrangement of regions — is the template.\n3. **Identify the distinct regions inside the template.** Each standalone, recognisable section\n   (a header, a listing area, a footer) is a candidate organism.\n4. **Break each organism into its functional groupings.** Look for clusters of elements that work\n   together for one purpose (a labelled field plus its control). Each cluster is a candidate\n   molecule.\n5. **Break each molecule into its individual elements.** The remaining pieces that can't be\n   meaningfully split further are the atoms.\n6. **Name every level consistently** so the same piece is referred to the same way whether you're\n   discussing the design, the content, or the composition.\n\nThis procedure works top-down (screen → page → template → organism → molecule → atom) or\nbottom-up (start cataloguing atoms first, then group them upward) — pick whichever direction\nmatches how much of the UI already exists versus is being designed fresh.\n\n## Decision heuristics \u002F boundaries\n\n- **Atom vs. molecule:** if removing a piece breaks the element's basic function, it's still an\n  atom; if two or more atoms only make sense combined for one purpose, promote the grouping to a\n  molecule.\n- **Molecule vs. organism:** a molecule is a small, single-purpose helper; an organism is a\n  standalone section a user would recognise on its own, even if it contains several molecules.\n- **Organism vs. template:** an organism is content-bearing and reusable; a template is the\n  arrangement of organisms with placeholder content, not a piece of content itself.\n- **Template vs. page:** a template has no real content; a page is the same structure filled with\n  actual, representative content.\n- **When in doubt, prefer the smaller level.** Over-classifying something as an organism when it's\n  really a molecule tends to produce fewer reusable pieces overall.\n\n## Common pitfalls \u002F anti-patterns\n\n- **Over-nesting organisms** — wrapping every organism inside another organism \"for organization\"\n  defeats the purpose of a flat, recognisable set of regions; keep organism nesting shallow.\n- **Treating pages as templates** — a template must stay free of real content; once specific\n  content is baked in, it has become a page, not a reusable template.\n- **Framework leakage** — the five levels describe structural complexity, not implementation\n  detail; don't let a specific rendering technology's constraints redefine what counts as an atom\n  or an organism.\n- **Skipping levels** — jumping straight from atoms to organisms (skipping molecules) usually\n  hides a reusable grouping that other organisms could have shared.\n","# Atomic Design — Component Hierarchy Methodology\n\nAtomic design is a mental model for breaking any user interface into five distinct levels of\nstructural complexity — atoms, molecules, organisms, templates, and pages — borrowed from\nchemistry's atoms-to-matter progression. It gives teams a shared vocabulary for talking about UI\nstructure and a repeatable way to decide \"does this need to be its own piece, and how big should\nthat piece be?\" The methodology itself is **framework-agnostic**: it describes how to think about\ncomposition, not which library or platform renders the result.\n\n## Why atomic design (rationale)\n\nWithout a shared hierarchy, teams tend to build UI ad hoc: some pieces get over-extracted into\ncomponents nobody reuses, others get duplicated because nobody realized a smaller shared piece\nalready existed, and naming drifts (is this a \"card,\" a \"widget,\" a \"block\"?). Atomic design solves\nthree recurring problems:\n\n- **Consistency** — the same five labels describe every piece of UI, so a design system and its\n  implementation stay aligned no matter who's talking about it.\n- **Reuse** — decomposing top-down into smaller named levels surfaces the shared building blocks\n  (a label, a button) that would otherwise get re-created inside every larger piece that needs one.\n- **Scalable vocabulary** — \"this is a molecule, not an organism\" is a fast, unambiguous design\n  conversation once the levels are understood, replacing long back-and-forth about scope.\n\nThe levels are a thinking tool, not a rigid folder structure to enforce everywhere — use them to\nreason about granularity, not as a law that every project must nest five matching directories.\n\n## The five levels (overview)\n\n1. **Atoms** — the smallest indivisible UI building blocks: a label, a single input field, a single\n   control. An atom has no meaningful sub-parts; splitting it further removes function rather than\n   simplifying it.\n2. **Molecules** — a small group of atoms bonded together to do one thing, such as a labelled input\n   paired with a submit control. A grouping becomes a molecule once two or more atoms combine for a\n   single, reusable purpose.\n3. **Organisms** — relatively complex groups of molecules and\u002For atoms that form a distinct,\n   recognisable section of an interface, such as a page header or a grid of item summaries. A\n   grouping becomes an organism once it reads as a standalone region rather than a helper piece.\n4. **Templates** — page-level layout skeletons that arrange organisms into a structure using\n   placeholder content. Templates are about arrangement, not real content.\n5. **Pages** — specific instances of a template populated with real, representative content. Pages\n   are the concrete end state used to validate that the whole system actually works with real data.\n\nSee [references\u002Fhierarchy.md](references\u002Fhierarchy.md) for the expanded per-level guidance —\ndefinitions, boundary rules, and additional neutral examples for each level.\n\n## How to apply it (decomposition workflow)\n\nFollow this ordered procedure to decompose an arbitrary UI description into the five levels:\n\n1. **Start from the whole screen.** Identify the page as the top-level unit — the thing a user\n   actually sees, with real content.\n2. **Strip content to find the template.** Mentally replace the real content with placeholders.\n   What's left — the arrangement of regions — is the template.\n3. **Identify the distinct regions inside the template.** Each standalone, recognisable section\n   (a header, a listing area, a footer) is a candidate organism.\n4. **Break each organism into its functional groupings.** Look for clusters of elements that work\n   together for one purpose (a labelled field plus its control). Each cluster is a candidate\n   molecule.\n5. **Break each molecule into its individual elements.** The remaining pieces that can't be\n   meaningfully split further are the atoms.\n6. **Name every level consistently** so the same piece is referred to the same way whether you're\n   discussing the design, the content, or the composition.\n\nThis procedure works top-down (screen → page → template → organism → molecule → atom) or\nbottom-up (start cataloguing atoms first, then group them upward) — pick whichever direction\nmatches how much of the UI already exists versus is being designed fresh.\n\n## Decision heuristics \u002F boundaries\n\n- **Atom vs. molecule:** if removing a piece breaks the element's basic function, it's still an\n  atom; if two or more atoms only make sense combined for one purpose, promote the grouping to a\n  molecule.\n- **Molecule vs. organism:** a molecule is a small, single-purpose helper; an organism is a\n  standalone section a user would recognise on its own, even if it contains several molecules.\n- **Organism vs. template:** an organism is content-bearing and reusable; a template is the\n  arrangement of organisms with placeholder content, not a piece of content itself.\n- **Template vs. page:** a template has no real content; a page is the same structure filled with\n  actual, representative content.\n- **When in doubt, prefer the smaller level.** Over-classifying something as an organism when it's\n  really a molecule tends to produce fewer reusable pieces overall.\n\n## Common pitfalls \u002F anti-patterns\n\n- **Over-nesting organisms** — wrapping every organism inside another organism \"for organization\"\n  defeats the purpose of a flat, recognisable set of regions; keep organism nesting shallow.\n- **Treating pages as templates** — a template must stay free of real content; once specific\n  content is baked in, it has become a page, not a reusable template.\n- **Framework leakage** — the five levels describe structural complexity, not implementation\n  detail; don't let a specific rendering technology's constraints redefine what counts as an atom\n  or an organism.\n- **Skipping levels** — jumping straight from atoms to organisms (skipping molecules) usually\n  hides a reusable grouping that other organisms could have shared.\n",{"name":5,"description":7},"main","7d4ebd573a4218d5e92eced411b259f34e9203fe","skills\u002Fatomic-design",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 atomic-design",{"tool":39,"command":40},"bunx","bunx skills add whimzyLive\u002Fnightshift-ai --skill atomic-design",{"tool":42,"command":43},"pnpm","pnpm dlx skills add whimzyLive\u002Fnightshift-ai --skill atomic-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Fatomic-design\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"evals\u002Fevals.json","REFERENCE","参考文档",3939,"https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Fatomic-design\u002Fevals\u002Fevals.json",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fhierarchy.md",4879,"https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Fatomic-design\u002Freferences\u002Fhierarchy.md",[58,66,73,80,87,94],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":65},"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"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",[],[]]