Lucolucus
Community@lucolucus · italy
Lucolucus maintains mismAgent, a DDD architecture-driven build system that turns domain models into manifests, OpenAPI contracts, and verified code blocks.
Agent Skills by Lucolucus
Showing 51 vetted skills indexed across 1 GitHub repositories.
lucolucusseam-cross-deploy
Projects cross-deploy boundaries into OpenAPI contracts with Pact consumer-driven contract verification.
lucolucuscreate-contract
Reconciles cross-deploy boundary operations into a single executable OpenAPI contract.
lucolucusrealize-adapter
Implements Port adapters and persistence repositories with contract and round-trip tests.
lucolucuswrite-task
Writes spike and cleanup node files for mismAgent feature task folders.
lucolucusux-designer
Generates UI concepts, layouts, and component breakdowns with data views for feature design.
lucolucusrealize-ui
Implements UI blocks as testable presenters with thin views and mandatory render checks.
lucolucusrealize-port
Implements consumer-owned port interfaces with reusable contract tests for inter-context boundaries.
lucolucuswrite-infra-notes
Writes and amends project-level infrastructure notes mapping infra needs to tasks, ADRs, and CI gates.
lucolucusrun-app-smoke
Launches the app and records render-check evidence for UI blocks.
lucolucuswrite-adr
Writes Architecture Decision Records with executable grep-based enforcement rules for automated verification.
lucolucuscode-review
Reviews a block's git diff adversarially for correctness bugs, edge cases, and unsatisfied acceptance criteria.
lucolucusrealize-application-service
Implements a thin application service that orchestrates aggregates and ports without duplicating domain rules.
lucolucusexplore
Transforms a raw feature idea into a product brief and domain context map through structured dialogue.
lucolucuswrite-code-rules
Writes project code-rules.md with enforcement channels for each deliberated coding rule.
lucolucuswrite-tactical-model
Writes per-feature tactical-model.md files capturing aggregates, invariants, domain events, and commands.
lucolucusreadiness-gate
Validates a building-block manifest against the worker-composer Phase 1 survival test before build launch.
lucolucusrealize-read-model
Implements CQRS read-model projections with consumer-driven view contract tests.
lucolucusrealize-scaffold
Creates the minimal buildable project skeleton so the side's gate runs green on an empty tree.
lucolucusharvest-dev-architecture
Extracts real coding conventions from completed code blocks into a reusable dev-architecture skill.
lucolucuswrite-context-map
Writes and amends a project-level DDD context map with bounded contexts and ubiquitous language.
lucolucusseam-in-process
Implements in-process boundaries as code interfaces with consumer-driven contract tests.
lucolucusrealize-aggregate
Implements a DDD Aggregate root with confined invariants and invariant tests.
lucolucusbuild-manifest
Generates the building-blocks.yaml manifest and derived block files bridging tactical model to build.
lucolucusmismagent-realize-read-model
Implements CQRS read-model projections with consumer-driven view contract tests.
Frequently Asked Questions About Lucolucus
FAQPage SchemaWhat tasks can I accomplish with Lucolucus's mismAgent skills?▼
You can explore ideas into domain models and context maps, emit building-block manifests, reconcile OpenAPI contracts for cross-deploy boundaries, realize aggregates, ports, adapters, read-models and UI blocks with tests, run render-proof smoke checks, and coordinate wave-based builds via the worker-composer.
Who are the mismAgent skills designed for?▼
They target software architects and engineers practicing Domain-Driven Design who want an architecture-driven build flow: strategic context mapping, tactical modeling of aggregates and invariants, contract-first boundaries, and verified block-by-block implementation with enforced ADRs and code rules.
How does a typical mismAgent build run in practice?▼
Start with explore to produce a context map, then model to emit the building-blocks manifest and OpenAPI contract. The worker-composer reads the manifest, builds blocks in waves (scaffold first, boundary owners before consumers), keeps each block green at D1 and each seam green at D2 via contract tests.
What prerequisites does mismAgent require before building?▼
The readiness gate and worker-composer Phase 1 require a complete manifest: pinned boundary types, contract_test, projection choice (in-process or cross-deploy), concrete tests_nl and acceptance criteria, an executable gate, and git present. Cross-deploy contracts additionally require contract_form: openapi.
How does mismAgent verify code quality beyond compilation?▼
It layers a structural verifier checking mechanical ADR enforced_by lint rules, an adversarial fresh-context code review with Blind Hunter, Edge Case Hunter and Acceptance Auditor lenses, and run-app-smoke that launches the real app to record render-proof evidence for UI blocks.