llodev
- 19 skills
- 0 followers
- 11 hours ago last updated
- ▌ TS Ddd Dto · llodev bundleCreate, review, or guide Data Transfer Objects in a TypeScript + DDD monorepo. Use when the request involves the per-BC contracts package (`libs/contracts/<bc>/src/{interfaces,schemas,dtos}/`), Zod 4 schemas paired with `z.infer` DTO types, closed-set values modelled as string-backed `XxxEnum` (with `z.literal(EnumName.X)` for discriminators and `z.nativeEnum(EnumName)` for full-set validators), input contracts (`CreateXxxDTO`, `UpdateXxxDTO`), output contracts (`XxxResponseDTO`), CQRS read projections, pagination/filters/metadata, or wire-shape changes consumed by both `apps/api` and `apps/web`.
- ▌ Pm Tasks Core · llodev bundleCore extraction + vocabulary for the @llodev/pm-tasks-* family. Use when working with any pm-tasks-<tool> adapter (Trello, Asana, etc.) — provides Phases 1–3 (identify input, extract structure, build the generic card) plus the canonical CRUD vocabulary (task.create, checklist.check, task.close, task.due-date.set, task.assignee.add, task.comment.add, task.move, task.parent.set, task.estimate.set, task.sprint.set) consumed by adapters. Also defines autonomous-mode contract (sentinels, allowlist, scope, audit log) and the shared init UX. Triggered indirectly by any prompt that an adapter handles (e.g. "create Trello card", "publish plan to Asana", "[autonomous] create task"). Do NOT activate alone — it has no tool-specific formatting.
- ▌ Pm Tasks Jira · llodev bundleJira adapter for the @llodev/pm-tasks-* family. Use when the user mentions Jira, asks to "create Jira issue", "publish to Jira", "log to Jira", "check subtask in Jira", or uses --publish-jira; OR for CRUD on existing issues (check subtask, close issue, change due-date, assign person, comment, set estimate, set parent); OR when invoked autonomously by another agent with [autonomous] / --auto sentinel. Jira model: team-managed, Kanban; issue → Subtask hierarchy (one level); transitions resolved at runtime by status category (locale-safe); estimate via story_points or timetracking field. Modes: paste-ready (no MCP), MCP publish (via Atlassian Remote MCP, Streamable-HTTP transport), autonomous (write-through with allowlist). Implements 9 verbs (task.create, task.move, checklist.check, task.close, task.due-date.set, task.assignee.add, task.comment.add, task.parent.set, task.estimate.set) from skills/pm-tasks-core/references/contract.md. F2 task.sprint.set is NOT supported — Atlassian MCP exposes no sprint API. Req
- ▌ TS Ddd Entity · llodev bundleCreate, review, or guide Domain Entity implementation in a TypeScript + DDD codebase. Use when: the request touches `*.entity.ts` files under `apps/api/src/<bc>/domain/entities/` or their tests under `apps/api/test/<bc>/domain/entities/`; modeling business rules with `Entity` from `@acme/shared` (dual API `create`/`tryCreate`, `Result` / `Result.combine` validation); validating FK refs with `Id.required` or own id with `Id.tryCreate`; enforcing enum-backed closed-set fields (status / kind / layout / provider / palette) from `@acme/<bc>-contracts` instead of string literals; validating nested entities or arrays element-by-element; adding state transitions via `cloneWith` (leaf entity) or named domain methods like `publish`, `addSection`, `deactivate` that mutate `_field` + `touch()` (aggregate root); exposing typed getters or `toSnapshot()` for persistence boundaries.
- ▌ TS Query Cqrs · llodev bundleCreate, review, or guide read-side queries in a TypeScript + DDD CQRS codebase. Use when the request involves `*Query` interfaces, `*.query.ts` files, read use cases (`find-*`), DTO projections for API/front consumption, pagination/filters/aggregations, or separating read (query) from write (repository/command).
- ▌ Pm Tasks Asana · llodev bundleAsana adapter for the @llodev/pm-tasks-* family. Use when the user mentions Asana, asks to "create Asana task", "publish to Asana", "post to Asana", "publish", "add comment in Asana", or uses --publish-asana; OR for CRUD on existing tasks (check subtask, close task, change due-date, assign person, comment); OR when invoked autonomously by another agent with [autonomous] / --auto sentinel. Asana hierarchy: workspace > project > section > parent task > subtasks (one level), with custom fields and multi-assignee support. Modes: paste-ready (no MCP needed), MCP publish (via claude.ai Asana MCP), autonomous (write-through with allowlist). Implements 7 CRUD verbs (task.create, task.move, checklist.check, task.close, task.due-date.set, task.assignee.add, task.comment.add) from skills/pm-tasks-core/references/contract.md. Requires @llodev/pm-tasks-core installed.
- ▌ Pm Tasks Linear · llodev bundleLinear adapter for the @llodev/pm-tasks-* family. Use when the user mentions Linear, asks to "create Linear issue", "publish to Linear", "log to Linear", "set cycle/sprint", "check sub-issue", or uses --publish-linear; OR for CRUD on existing issues (check sub-issue, close, due-date, assign, comment, estimate, parent, sprint); OR when invoked autonomously with [autonomous] / --auto sentinel. Linear model: issue upsert via save_issue; sub-issues as hierarchy AND checklist mechanism (parentId); states by type (unstarted/ started/completed/canceled); cycles = sprints (team-gated); single assignee (set-not-add); labels are replace-set (est: idempotency read-modify-write). MCP: Linear MCP (Streamable-HTTP, OAuth, mcp__linear__ prefix). Modes: paste-ready, MCP publish, autonomous (write-through with allowlist), plan-execution. Implements 10 verbs (task.create, task.move, checklist.check, task.close, task.due-date.set, task.assignee.add, task.comment.add, task.parent.set, task.estimate.set, task.sprint.set). FIRST f
- ▌ Pm Tasks Monday · llodev bundle[SCAFFOLD — NOT YET IMPLEMENTED] Future Monday adapter for the @llodev/pm-tasks-* family. Do not activate. Scheduled for v1.x once MCP integration is finalized. See https://github.com/llodev/skills/issues for status.
- ▌ Pm Tasks Notion · llodev bundle[SCAFFOLD — NOT YET IMPLEMENTED] Future Notion adapter for the @llodev/pm-tasks-* family. Do not activate. Scheduled for v1.x once MCP integration is finalized. See https://github.com/llodev/skills/issues for status.
- ▌ Pm Tasks Trello · llodev bundleTrello adapter for the @llodev/pm-tasks-* family. Use when the user mentions Trello, asks to "create card", "publish to Trello", "post to Trello", "publish", or uses --publish; OR for CRUD on existing cards (check checklist item, close card, change due-date, add member, comment); OR when invoked autonomously by another agent with [autonomous] / --auto sentinel. Modes: paste-ready (no MCP needed), MCP publish (via atlassian-trello-mcp), autonomous (write-through with allowlist). Implements 7 CRUD verbs (task.create, task.move, checklist.check, task.close, task.due-date.set, task.assignee.add, task.comment.add) from skills/pm-tasks-core/references/contract.md. Requires @llodev/pm-tasks-core installed.
- ▌ TS Ddd Use Case · llodev bundleCreate, review, or guide use case (application service) implementation in a TypeScript + DDD codebase. Use when the request involves `*.usecase.ts` files under `apps/api/src/<bc>/application/usecases/`, `application/services/<name>.service.ts` orchestrators, `UseCase<IN,OUT>` from `@acme/shared`, NestJS `@Injectable()` + `@Inject(<REPO_TOKEN>)` wiring, `Result.ok` / `Result.fail` / `withFail` / `Result.combine`, repository-port orchestration (`findBySlug`, `save`, `listByStatus`), aggregate state-transitions (`publish`, `addSection`), enum-typed inputs (`CelebrationKind`, `CelebrationStatusEnum.DRAFT`), or use-case tests under `apps/api/test/<bc>/application/usecases/` using `InMemoryCelebrationRepository`.
- ▌ Pm Tasks Clickup · llodev bundle[SCAFFOLD — NOT YET IMPLEMENTED] Future ClickUp adapter for the @llodev/pm-tasks-* family. Do not activate. Scheduled for v1.x once MCP integration is finalized. See https://github.com/llodev/skills/issues for status.
- ▌ Pm Tasks Todoist · llodev bundle[SCAFFOLD — NOT YET IMPLEMENTED] Future Todoist adapter for the @llodev/pm-tasks-* family. Do not activate. Scheduled for v1.x once MCP integration is finalized. See https://github.com/llodev/skills/issues for status.
- ▌ Pm Tasks Bitrix24 · llodev bundle[SCAFFOLD — NOT YET IMPLEMENTED] Future Bitrix24 adapter for the @llodev/pm-tasks-* family. Do not activate. Scheduled for v1.x once MCP integration is finalized. See https://github.com/llodev/skills/issues for status.
- ▌ TS Ddd Controller · llodev bundleCreate, review, or guide HTTP controllers in a TypeScript + DDD api. Use when the request involves `*.controller.ts` under `apps/api/src/<bc>/presentation/controllers/`, route definition, `ApiKeyGuard` on mutations, `ZodValidationPipe` against `@acme/<bc>-contracts` schemas, use case orchestration, mapping `Result` to HTTP via `mapResultToHttp`, signed-URL enrichment through a response mapper, HTTP status conventions (200/201/204), or controller tests using `@nestjs/testing` + `supertest` with an in-memory repository.
- ▌ TS Ddd Repository · llodev bundleCreate, review, or guide repository contracts and implementations in a TypeScript + DDD codebase. Use when the request involves `*.repository.ts` files under `apps/api/src/<bc>/domain/repositories/` or `apps/api/src/<bc>/infra/{firestore,memory}/`, persistence operations (save / findBy* / list*), the `<NAME>_REPOSITORY` DI token, adapting the Firebase Admin SDK to a domain port, `toFirestore`/`fromFirestore` mappers, the side-by-side Firestore + InMemory adapter pair, contract tests under `apps/api/test/<bc>/infra/{firestore,memory}/`, `Result` error handling, or CQRS Repository vs Query separation.
- ▌ TS Ddd Value Object · llodev bundleCreate, review, or guide Value Object implementation in a TypeScript + DDD codebase. Use when the request involves 'value object', 'VO', `*.vo.ts` files (either shared at `libs/shared/src/vo/...` or BC-local at `apps/api/src/<bc>/domain/value-objects/...`), domain attribute validation/normalization, closed-set VOs derived from string enums (PaletteKey-style), composite-value VOs (ImageRef-style), `ValueObject` + `Result` pattern, `ValueObjectConfig`, `tryCreate`/`create` dual API, or VO test coverage.
- ▌ Django Schema Design · llodev bundleDesign robust Django database schemas with model best practices, migration patterns, and primary key strategy (incremental, UUID, UUIDv7). Use when designing Django models, choosing PK types, writing migrations, or reviewing app schema. Covers Django ORM, PostgreSQL, indexes, constraints, and security considerations for IDs.
- ▌ TS Ddd Domain Service · llodev bundleCreate, review, or guide pure Domain Service implementation in a TypeScript + DDD monorepo. Use when the request involves `*.service.ts` files inside `apps/api/src/<bc>/domain/services/`, domain policies, pure calculations/rules across multiple entities/VOs, naming patterns (`*Policy`, `*Calculator`, `*Resolver`, `*Specification`), branching on closed-set enums (status / kind / role) from `@acme/celebrations-contracts`, or tests in `apps/api/test/<bc>/domain/services/`. Scope is the *pure* domain layer; for orchestrators that need a repository or other I/O (e.g. `SlugAllocator`), see the sibling `application/services/` section at the end.