One control layer.Built for every coding agent.
Today, Schemyx indexes the patterns, rules, and conventions your repo already proves, then matches each prepared task to focused, source-backed guidance. Next, the beta will normalize agent-specific skill formats, route the right skills by task, and enforce guardrails during generation.
route.app.dashboardservice.auth.sessionmodel.project.configschemyx_prepare_taskPrompts are not durable policy
Every agent should start from the same project truth.
Repo paradigms should not depend on remembered prompts. Schemyx makes the applicable pattern, compatibility limits, and review state available at task time.
Match → filter → verify
Start with indexed paradigms. Expand only when evidence requires it.
Task preparation matches indexed repo paradigms to bounded recipes, filters incompatible results, preserves ambiguity and review state, and gates exact-source fallback by reason.
schemyx_prepare_taskFrame the work
Verify freshness, match indexed paradigms, apply compatibility filters, and preserve review state.
schemyx_search_codebaseFind the right keys
Search the paradigm and recipe index before walking broadly through the repository.
schemyx_get_codebase_recipeLoad matched recipe
Fetch the precise source-backed route, component, service, model, style, or rule the task matched.
schemyx_get_context_packExpand relationships
Pull a bounded pack of connected facts when one recipe is not enough to implement safely.
$ schemyx_prepare_task“Refactor the dashboard navigation without breaking auth.”
Source-backed guidance, not a project dump
Control starts with evidence the agent can verify.
Today’s MCP indexes source-backed patterns, rules, and conventions. The beta direction is to normalize agent-specific skill formats, require the right skills for each task, and enforce guardrails during generation—not current enforcement.
Routes & UI
Source-backed route, component, responsive, and styling paradigms indexed from repository evidence.
Services & APIs
Controller, service, module, and endpoint paradigms with compatibility and source relationships intact.
Data & models
Prisma, SQL, ORM, schema, and model paradigms returned as bounded recipes instead of a repository dump.
Guarded source
Exact-file reads require a reason when compatible recipes cannot answer the task with sufficient evidence.
The evidence boundary stays explicit.
The current local beta scans an explicit source scope and writes a generated index under .schemyx/codebase. Agents receive bounded recipes and context packs first; exact-file reads require a recorded fallback reason.
frontendRoutes, UI components, hooks, styles, templates, and frontend configuration.
backendControllers, services, modules, APIs, databases, models, and backend configuration.
fullThe repository with safe generated, dependency, build, and VCS ignores applied.
customOnly explicit include paths when the user has selected an exact boundary.
Bring the same repo truth to every connected coding agent.
Use task-matched paradigms today. Help shape agent-specific skill routing and enforceable generation guardrails next.
Request beta access