Loading...
Loading...
Found 107 Skills
Build tool for Go projects. Use when the user wants to create, edit, or understand Way-specific Magefiles, build targets, or automate Go project tasks.
LOAD THIS SKILL when: updating npm packages, user mentions 'update packages', 'update-packages', 'outdated', 'dependency updates'. Covers autonomous npm package updates with breaking change handling, Bun updates, Playwright Docker sync, and package group coordination.
Configure Scarb.toml, dojo profiles, world settings, and dependencies. Use when setting up project configuration, managing dependencies, or configuring deployment environments.
Update, create, or reprioritize your product roadmap. Use when adding a new initiative and deciding what moves to make room, shifting priorities after new information comes in, moving timelines due to a dependency slip, or building a Now/Next/Later view from scratch.
How to create, structure, and publish self-contained Convex components with proper isolation, exports, and dependency management
Run knip to find and remove unused files, dependencies, and exports. Use for cleaning up dead code and unused dependencies.
General guidelines for Commits, formatting, CI, dependencies, security
Avoid common mistakes and debug issues in PydanticAI agents. Use when encountering errors, unexpected behavior, or when reviewing agent implementations.
Creates reproducible builds, manages flake inputs, defines devShells, and builds packages with flake.nix. Use when initializing Nix projects, locking dependencies, or running nix build/develop commands.
Runs the Ralph autonomous loop. Executes stories from prds/*.json using git worktrees.
Best practices for pnpm package manager, workspace management, and monorepo configuration
Review code architecture for maintainability, catch structural issues before they become debtUse when "Reviewing pull requests with structural changes, Planning refactoring work, Evaluating new feature architecture, Assessing technical debt, Before major releases, When code feels "hard to change", architecture, code-review, refactoring, design-patterns, technical-debt, dependencies, maintainability" mentioned.