Loading...
Loading...
Found 2,573 Skills
Take a prepared task and run it to 'ready for human review' on your own: code, self-review loop, self-fixes, verification, commits by the team convention, and an honest handover report. Use when the developer hands over a task whose analysis and grilling are already done — trigger on «реализуй задачу», «запускай в работу», «пили», «делай задачу», «бери таску», implement the task, run this task, even when the skill is never named and even right after a grill session ends. NOT for a small change the developer is watching — that is quick-edit. Does not analyse or grill the task, does not estimate it, and does not create the merge request.
Trigger this if the user says 'full send'.
Dares the agent to write no tests. Use when the user says "write tests", or when the user asks to write, skip, or fix tests. Always infer from a request to write, skip, or fix tests.
How the toolkit is consulted, extended, and documented. Use before writing any new code — and after, when a genuinely new instrument has earned its place.
Apply shared coding standards when writing, reviewing, or refactoring TypeScript in apps, services, workers, and shared packages. Use before editing TypeScript functions, types, exports, error handling, or documentation, and React components and hooks. Includes conditional React and Next.js rules; backend repositories do not require either framework.
Use when the user asks for TDD, test-first, or red-green-refactor, or repository instructions require that cycle. Ordinary requests for tests use when-to-write-tests; a new contract or helper alone does not trigger TDD.
End-of-session ritual that audits changes, runs quality checks, captures learnings, and produces a session summary. Use when saying "wrap up", "done for the day", "finish coding", or ending a coding session.
Implement or review code through a verified result. Keep changes small and TypeScript readable.
Compact engineering principles for design, debugging, verification, and delegation, each with a trigger. Use when choosing structure or types, sizing a diff, debugging, writing tests, or when the user types /ds-principles.
Use this skill when deciding where knowledge from a code change, correction, or review belongs—code, tests, comments, documentation, schemas, configuration, examples, decision records, or commit messages. Produce a minimal placement plan before editing when information could be duplicated or lost. Do not use it to draft prose, choose a commit message, or perform edits or Git operations.
Use when symfony quality checks
Use when symfony api platform tests