Easyuseaide Project Bootstrap
Use this skill before the first implementation of a new durable software project, or when an existing long-running project lacks reliable repository context such as project rules, PRD, architecture, task cards, status, ADR, contracts, or cross-session handoff. It is required for a new multi-module, persistent-data, deployed, shared, maintainable, or planned-open-source project unless equivalent r…
Easyuseaide Project Delivery Readiness
Use this skill to establish, repair, or verify the delivery baseline of every long-lived, shared, published, deployed, or persistent-data software project, including personal and small projects. It is required before declaring the first implementation or a delivery milestone complete when any of those conditions apply, and whenever work adds or changes startup, CI, secrets, databases, files, back…
Easyuseaide High Risk Git Operation
Use this skill only for Git operations that can rewrite, delete, expose, or disrupt shared history or working data, including force push, filter-repo, reset --hard, clean, shared-branch rebase, secret removal, and recovery. Do not use it for ordinary commits, branches, merges, or worktree creation; if another branch workflow is active, apply this skill only as the safety gate around the risky ste…
Easyuseaide Public Repository Release
Use this skill when a local repository, its history, or a release will be pushed to a public code-hosting boundary, including open-sourcing an existing project, creating a public repository, or publishing a release. Do not use it merely to finish or merge an ordinary branch; if another completion workflow is active, keep it and add this skill's sensitive-data, history, license, remote, and public…
Easyuseaide Dependency Research
Use this skill before choosing, adding, upgrading, replacing, or validating any external library, framework, API, SDK, protocol, tool, or fast-changing technical practice, including dependencies selected during a new project build. It is required when editing a dependency manifest to introduce a package that the project did not already use. Do not use it for routine installation from an unchanged…
Easyuseaide Complex Debugging
Use this skill for intermittent, repeated, concurrent, performance, resource-leak, flaky-test, integration, or production-only failures that need investigation beyond an ordinary bug fix. If another general debugging workflow is active, keep it as the primary root-cause process and use this skill only for additional failure-mode checks; do not run two complete debugging workflows.