// When the user wants to use open source as a distribution strategy, grow on GitHub, convert README traffic, design open-core, or build community-led funnels (stars, deploys, sponsors, plugins).
Writes, edits, and creates dbt models following best practices. Use when user needs to create new dbt SQL models, update existing models, or convert raw SQL to dbt format. Handles staging, intermediate, and mart models with proper config blocks, CTEs, and documentation.
Apply Domain-Driven Design, Clean Architecture, CQRS, and command/query patterns to code reviews and feature design. Use when analyzing or designing code in Application, Service, Infrastructure, DataAccess, Validation, Domain, or Functions projects, or when addressing architectural concerns, layering, mapping, entities, value objects, repositories, or validators in the Rome Repair Order Service.
Analyzes and refactors code using Domain-Driven Design principles. Use when refactoring domain models, identifying DDD anti-patterns, improving domain clarity, or applying tactical/strategic DDD patterns.
Guide for DDD strategic design - analyzing domains through structured questioning, conducting stakeholder interviews (PM/domain experts/users), and producing Bounded Context analysis, Context Maps, and Ubiquitous Language. Use when user needs help understanding domain boundaries, planning domain interviews, or structuring DDD strategic artifacts.
Win competitive rounds: run a clean process, deliver value previews before asking, coordinate partners, and manage timelines. Use when you're trying to close a 'must win' deal against other funds.
End-to-end associate workflow with time-boxed gates: thesis -> sourcing -> meetings -> diligence -> memo, ending with either IC-ready memo or explicit kill decision. Use when you need to run the full pipeline for a sector or a specific deal.
| name | github-marketing |
| description | When the user wants to use open source as a distribution strategy, grow on GitHub, convert README traffic, design open-core, or build community-led funnels (stars, deploys, sponsors, plugins). |
Turn GitHub attention into real users, community, and revenue without eroding trust.
Make the boundary obvious:
If it takes >10s to see value, you lose. Reduce steps, give defaults, add deploy buttons.
Open source is credibility marketing. Earn trust before asking for upgrade.
Stars → users → contributors → referrals. Build loops, not launches.
Docs, examples, templates, and plugins are product. Treat them as such.
references/assessment.md and references/questions.md.references/playbooks.md.references/metrics.md.references/output-format.md.