Develop, validate, restructure, or maintain reliable clio MCP guidance from live Creatio evidence. Use when researching an unfamiliar Creatio behavior, building a repeatable clio lab, turning runtime/source discoveries into agent-facing guidance, adding or revising GuidanceCatalog resources, eliminating duplicated guidance, or defining acceptance tests and ownership boundaries for a clio guidance family.
Develop, validate, restructure, or maintain reliable clio MCP guidance from live Creatio evidence. Use when researching an unfamiliar Creatio behavior, building a repeatable clio lab, turning runtime/source discoveries into agent-facing guidance, adding or revising GuidanceCatalog resources, eliminating duplicated guidance, or defining acceptance tests and ownership boundaries for a clio guidance family.
Develop, validate, restructure, or maintain reliable clio MCP guidance from live Creatio evidence. Use when researching an unfamiliar Creatio behavior, building a repeatable clio lab, turning runtime/source discoveries into agent-facing guidance, adding or revising GuidanceCatalog resources, eliminating duplicated guidance, or defining acceptance tests and ownership boundaries for a clio guidance family.
Turn this session into the Architect — a conversational orchestrator for the Clio codebase. The Architect investigates and reasons about the code WITH you (refactoring ideas, design questions, impact analysis), never edits code itself, and delegates implementation to `coder` subagents one unit at a time, reporting each result back. Use when you want to think through a change, plan a refactor, or have work implemented under supervision rather than editing directly.
Update a working branch from `master`, create or refresh a pull request, monitor build and quality gates, answer and resolve AI or human review comments, and merge the PR only after all actionable threads and checks are cleared. Use for clio delivery tasks that must go end-to-end through GitHub without missing follow-up steps.
Create, update, and validate custom Creatio Configuration Web Services and their tests. Use when users need to expose custom backend endpoints in Creatio, wire service contracts/implementations, return structured success/error results, or verify endpoints with integration-style and unit tests.
Create or update a clio MCP tool when command behavior, MCP exposure, prompts, or resources must be added or kept in sync. Use for work in `clio/Command/McpServer/Tools`, `Prompts`, or `Resources`, especially when adding a new MCP tool, updating arguments, or aligning the MCP contract with an existing command.
Add or update unit and end-to-end coverage for a clio MCP tool. Use when changing MCP tool arguments, tool names, command wiring, prompts, resources, destructive behavior, or when creating a new MCP tool that needs contract tests and E2E coverage.