Intent Architect
Official@IntentArchitect
The first architecture-centric code automation platform for professional developers.
Agent Skills by Intent Architect
Showing 30 vetted skills indexed across 1 GitHub repositories.
IntentArchitectintent-architect-mcp
Orchestrates Intent Architect MCP tools for model-driven design, code generation, and compilation verification.
IntentArchitectmediatr-command-handler
Implements business logic in MediatR command handler Handle methods following clean architecture layer boundaries.
IntentArchitectdomain-entity
Implements domain behaviour, invariants, and constructors on C# entities and aggregates.
IntentArchitectfluent-validation-custom-validation
Implements custom async FluentValidation rules inside existing C# validator files.
IntentArchitectapplication-service-implementation
Implements business logic in traditional non-CQRS application service classes.
IntentArchitectmediatr-query-handler
Implements business logic in MediatR query handler Handle methods in C#.
IntentArchitectef-repository
Extends Entity Framework repository contracts and implementations with custom query methods.
IntentArchitectmodule-debugging
Insert temporary log statements into designer scripts and module C# code to inspect runtime values.
IntentArchitectmodule-context-capture
Records architectural decisions and invariants in a module's CONTEXT.md file.
IntentArchitectmodule-version-increment
Increment Intent Architect module versions and propagate changes to dependent modules.
IntentArchitectmodule-building-strategies
Guides design decisions for decomposing, configuring, and verifying Intent Architect modules.
IntentArchitectmodule-versioning
Sets an Intent Architect module version via Module Settings and propagates it to dependents.
IntentArchitectmodule-dependency-audit
Verify .imodspec dependencies match actual code and template references in Intent Architect modules.
IntentArchitectmodule-docs
Completes release-notes.md, docs/README.md, and .imodspec metadata for Intent Architect modules.
IntentArchitectmodule-svg-icon
Creates a house-style SVG icon and applies it as a module's package icon in .application.config.
IntentArchitectintent-metadata-consumer
Reads Intent Architect stereotypes and model metadata through generated typed accessors in templates.
IntentArchitectfile-builder-expert
Author and fix C# code-generation templates using the Fluent CSharpFile builder API.
IntentArchitectadd-module-migration
Creates version migrations that edit consumer application metadata during module install or update.
IntentArchitectsdd-build-module
Orchestrates golden-sample-driven SDD workflow for building Intent Architect modules end to end.
IntentArchitectadd-association-type
Creates a new Association Settings type with configured source and target ends in the Module Builder designer.
IntentArchitectadd-designer-extension
Adds context menu options to foreign Intent Architect designer elements via package, element, or association extensions.
IntentArchitectintent-mapping-architect
Generates recursive C# mapping statements from designer-modelled mappings via the MappingManager API.
IntentArchitectintent-modelers-integration
Look up install identities and API references for Intent Architect's Domain, Services, Eventing, and UI designers.
IntentArchitectarchitecture-templates
Builds Intent Architect architecture templates and seeds default designer metadata for new applications.
Frequently Asked Questions About Intent Architect
FAQPage SchemaWhat tasks can I accomplish using Intent Architect's skills?▼
You can implement MediatR command/query handlers, domain entities with invariants, FluentValidation rules, EF repository extensions, and traditional application services. You can also build Intent Architect modules: designer extensions, association types, architecture templates, version migrations, SVG icons, and cross-module DI wiring.
Who are Intent Architect's skills designed for?▼
They target professional .NET developers generating application code from designer models, and module authors extending the Intent Architect platform. Module authors get guidance on decomposition strategies, template authoring, metadata consumption, versioning, and release close-out; application developers get handler, entity, and validation implementation patterns.
How do the skills fit into a practical development session?▼
Each skill declares when it must load — for example, before editing any *CommandHandler.cs or *Validator.cs file. Module work follows a phased flow: increment the version, implement, run the dependency audit against the .imodspec, then update release notes and README. The MCP skill routes designer edits through Intent Architect rather than raw XML file changes.
What prerequisites do Intent Architect skills require?▼
Prerequisites vary per skill and are stated explicitly: an open Module Builder designer, generated *StereotypeExtensions.cs accessors, identified element type GUIDs, a modelled mapping with CSharpMappingBase inheritance, or a supplied target version string. Skills refuse to run when their required context — such as an existing module project folder — is absent.
How do the skills keep module releases consistent?▼
Dedicated skills separate concerns: module-version-increment decides the bump, module-versioning applies a supplied version, module-dependency-audit verifies .imodspec dependencies against actual code references, and module-docs-chore updates release notes and README in the same turn as any observable change.