Evidence Before Final
Prevent claiming completion without proof. Use before final responses, handoffs, releases, or review closure.
Integration Testing
Verify boundaries between components. Use when behavior crosses services, modules, tools, adapters, or data formats.
Xiigen General Skills
Open-source AI agent skills for safer Claude, Codex and Cursor coding workflows
Executor Cannot Self Finish
Separate execution from completion approval. Use when an agent both implements and reviews its own work.
Code Execution
Run commands safely and intentionally. Use before executing build, test, lint, generation, migration, deploy, or cleanup commands.
Documentation Sync
Keep documentation aligned with behavior. Use when changing workflows, commands, APIs, examples, or user-facing behavior.
Session Output Contract
Make session output useful, complete, and resumable. Use at handoff, final response, or long-running task summary.
Goal Delivery Completeness
Check that delivered work matches the user's goal. Use before final response, release, or handoff.
Scope And Blockers
Keep scope and blockers explicit. Use when requirements are broad, ambiguous, or blocked by missing information.
Test Integrity
Keep tests meaningful and honest. Use when writing, changing, disabling, or interpreting tests.
Review Fix Loop
Close actionable feedback through repeated review and repair. Use after plan review, code review, content review, or release-gate review.
Plan Before Execution
Create a bounded plan before non-trivial work. Use for multi-file, high-risk, ambiguous, or delegated work.
Code Request Safety
Check risk before code actions. Use before running commands, editing files, deleting files, moving data, or changing configuration.
Debug Session
Package debugging work so another agent or human can resume it. Use for longer debugging tasks or handoffs.
Output Readability Gate
Keep outputs readable for humans. Use before delivering plans, reports, READMEs, reviews, and adaptation output.
Decision Capture
Record important decisions and rationale. Use when selecting architecture, stack guide, adapter output, or release policy.
Assumption Registry
Make assumptions visible and testable. Use during planning, architecture adaptation, and unclear requirements.
Project Rules First
Ensure project-specific rules are read before meaningful action. Use at task startup, before editing files, running commands, or adapting skills.
User Journey Testing
Validate work through a realistic user path. Use for UX, tool workflows, onboarding, and generated instructions.
E2e Test Matrix
Design end-to-end coverage across critical paths. Use for release readiness, user workflows, UI/API flows, and adapter validation.
Stale Baseline Guard
Avoid acting on outdated context. Use after interruptions, long sessions, branch changes, or concurrent edits.
Root Cause Tracing
Find the cause behind a symptom. Use when a failure repeats, appears indirect, or has multiple possible causes.
Systematic Debugging
Make debugging reproducible and disciplined. Use for unclear failures, regressions, or unstable behavior.
Authority Chain
Resolve which instructions win when rules conflict. Use at the start of every task and whenever instructions disagree.
No Secrets
Prevent publishing sensitive material. Use before commits, reports, examples, adaptation outputs, and release.
Claim Verification
Verify claims before presenting them as facts. Use in final answers, reports, reviews, and architecture decisions.
Generated Code Review
Review generated code before trusting it. Use after AI-generated code, scaffolding, migration output, or copied snippets.
Document Hierarchy
Avoid competing sources of truth. Use when adding, moving, or adapting docs.
Code Examination
Understand local code before changing it. Use before implementation, refactoring, test fixes, or architecture changes.
Failure Triage
Classify failures before changing implementation. Use after failed builds, tests, commands, or smoke checks.