lubochka/xiigen-general-skills
Cursor rule
Make assumptions visible and testable. Use during planning, architecture adaptation, and unclear requirements.
Open-source AI agent skills for safer Claude, Codex and Cursor coding workflows
lubochka/xiigen-general-skills
Cursor rule
Make assumptions visible and testable. Use during planning, architecture adaptation, and unclear requirements.
lubochka/xiigen-general-skills
Cursor rule
Resolve which instructions win when rules conflict. Use at the start of every task and whenever instructions disagree.
lubochka/xiigen-general-skills
Cursor rule
Verify claims before presenting them as facts. Use in final answers, reports, reviews, and architecture decisions.
lubochka/xiigen-general-skills
Cursor rule
Understand local code before changing it. Use before implementation, refactoring, test fixes, or architecture changes.
lubochka/xiigen-general-skills
Cursor rule
Run commands safely and intentionally. Use before executing build, test, lint, generation, migration, deploy, or cleanup commands.
lubochka/xiigen-general-skills
Cursor rule
Check risk before code actions. Use before running commands, editing files, deleting files, moving data, or changing configuration.
lubochka/xiigen-general-skills
Cursor rule
Package debugging work so another agent or human can resume it. Use for longer debugging tasks or handoffs.
lubochka/xiigen-general-skills
Cursor rule
Record important decisions and rationale. Use when selecting architecture, stack guide, adapter output, or release policy.
lubochka/xiigen-general-skills
Cursor rule
Avoid competing sources of truth. Use when adding, moving, or adapting docs.
lubochka/xiigen-general-skills
Cursor rule
Keep documentation aligned with behavior. Use when changing workflows, commands, APIs, examples, or user-facing behavior.
lubochka/xiigen-general-skills
Cursor rule
Design end-to-end coverage across critical paths. Use for release readiness, user workflows, UI/API flows, and adapter validation.
lubochka/xiigen-general-skills
Cursor rule
Prevent claiming completion without proof. Use before final responses, handoffs, releases, or review closure.
lubochka/xiigen-general-skills
Cursor rule
Separate execution from completion approval. Use when an agent both implements and reviews its own work.
lubochka/xiigen-general-skills
Cursor rule
Classify failures before changing implementation. Use after failed builds, tests, commands, or smoke checks.
lubochka/xiigen-general-skills
Cursor rule
Review generated code before trusting it. Use after AI-generated code, scaffolding, migration output, or copied snippets.
lubochka/xiigen-general-skills
Cursor rule
Check that delivered work matches the user's goal. Use before final response, release, or handoff.
lubochka/xiigen-general-skills
Cursor rule
Verify boundaries between components. Use when behavior crosses services, modules, tools, adapters, or data formats.
lubochka/xiigen-general-skills
Cursor rule
Prevent publishing sensitive material. Use before commits, reports, examples, adaptation outputs, and release.
lubochka/xiigen-general-skills
Cursor rule
Keep outputs readable for humans. Use before delivering plans, reports, READMEs, reviews, and adaptation output.
lubochka/xiigen-general-skills
Cursor rule
Create a bounded plan before non-trivial work. Use for multi-file, high-risk, ambiguous, or delegated work.
lubochka/xiigen-general-skills
Cursor rule
Ensure project-specific rules are read before meaningful action. Use at task startup, before editing files, running commands, or adapting skills.
lubochka/xiigen-general-skills
Cursor rule
Close actionable feedback through repeated review and repair. Use after plan review, code review, content review, or release-gate review.
lubochka/xiigen-general-skills
Cursor rule
Find the cause behind a symptom. Use when a failure repeats, appears indirect, or has multiple possible causes.
lubochka/xiigen-general-skills
Cursor rule
Keep scope and blockers explicit. Use when requirements are broad, ambiguous, or blocked by missing information.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: