agentsclimarketplace

Ddd strategic design

Skill srg-sphynx/MDForge/Sources/MDForge/Resources/SkillLibrary/Creative/ddd-strategic-design

Native macOS skill-catalog studio for Claude Code — browse 1,492 Markdown skills, customize with variables or AI (hosted or local), export to .claude/skills. SwiftUI + Liquid Glass.

Install
npx -y skills add srg-sphynx/MDForge --skill ddd-strategic-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Design DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language for complex business domains.

SKILL.md

1.5 KB, 255 tokens by cl100k_base, as published. Nobody here has run it

DDD Strategic Design

Use this skill when

  • Defining core, supporting, and generic subdomains.
  • Splitting a monolith or service landscape by domain boundaries.
  • Aligning teams and ownership with bounded contexts.
  • Building a shared ubiquitous language with domain experts.

Do not use this skill when

  • The domain model is stable and already well bounded.
  • You need tactical code patterns only.
  • The task is purely infrastructure or UI oriented.

Instructions

  1. Extract domain capabilities and classify subdomains.
  2. Define bounded contexts around consistency and ownership.
  3. Establish a ubiquitous language glossary and anti-terms.
  4. Capture context boundaries in ADRs before implementation.

If detailed templates are needed, open references/strategic-design-template.md.

Required artifacts

  • Subdomain classification table
  • Bounded context catalog
  • Glossary with canonical terms
  • Boundary decisions with rationale

Examples

Use @ddd-strategic-design to map our commerce domain into bounded contexts,
classify subdomains, and propose team ownership.

Limitations

  • This skill does not produce executable code.
  • It cannot infer business truth without stakeholder input.
  • It should be followed by tactical design before implementation.

Gives 0 of the 12 instructions most design frontend skills give in 255 tokens

Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07

  • use css variables for color consistencyin 72 of 1169, across 23 files
  • commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
  • match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
  • add atmospheric background effects and texturesin 57 of 1169, across 9 files
  • use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
  • implement real working codein 55 of 1169, across 7 files
  • vary themes and aesthetics across different designsin 48 of 1169, across 7 files
  • launch chromium in headless modein 47 of 1169, across 4 files
  • close the browser when donein 47 of 1169, across 4 files
  • run provided scripts with help flag firstin 47 of 1169, across 4 files
  • wait for network idle statein 47 of 1169, across 4 files
  • use descriptive selectors for elementsin 47 of 1169, across 4 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.