Plan end-to-end implementation steps for a new evitaDB query constraint.
npx skills add https://github.com/FgForrest/evitaDB --skill new-constraint
Please help me install this Agent Skill. Skill: new-constraint Source: https://github.com/FgForrest/evitaDB/tree/main/.claude/skills/new-constraint Command: npx skills add https://github.com/FgForrest/evitaDB --skill new-constraint
This skill helps engineering teams plan and execute the full integration of a new evitaDB query constraint (filter, order, or require) by producing a detailed, layer-spanning implementation plan with exact file paths.
Provide a complete end-to-end plan for a new constraint and save it to docs/plans with a descriptive filename.
High-intent search queries and answers about installing and using this skill.
To plan a new evitaDB constraint, gather requirements to define its type and behavior, then trace an existing template constraint across all layers to generate a complete file manifest with exact paths for modification.
Adding a new evitaDB constraint requires modifying files across the query model, EvitaQL grammar, engine translators, Kryo serializers, external APIs, tests, and documentation, ensuring all Kryo registration rules are followed.
evitaDB constraint planning validates critical rules by tracing template constraints through EvitaQL grammar regeneration and Kryo serializer registration to ensure the new constraint is production-ready across all engine layers.
Yes, you can identify the closest existing constraint template and trace its influence across all layers to produce a complete implementation plan, noting any deviations from the original template behavior and scope.
The best way to document a new evitaDB constraint plan is to save the complete end-to-end implementation steps, including exact file paths and deviation notes, to the docs/plans directory with a clear, descriptive filename.
Yes, a new evitaDB constraint requires test coverage validated against guidelines, ensuring the query model, EvitaQL grammar, engine translation, and external APIs all function correctly before production rollout.
saolalabGather and validate stakeholder requirements into a traceability matrix and BRD.
FgForrestApply evitaDB schema changes across contracts, DTOs, builders, mutations, and serializers.
apecloudExpose KubeBlocks database services via LoadBalancer or NodePort OpsRequests.
stacksjsAnalyze proposed Stacks changes for scope, data flow, dependencies, and delivery artifacts.
