Discover Tools skills, compare source repositories and read the instructions for each workflow.
Use when writing or modifying code. Enforces production-quality standards, prohibits common shortcuts, and ensures pre-existing issues are addressed. Invoked automatically by implementing-features and test-driv...
Use when session returns mode.type='tarot' - tarot archetypes collaborate via roundtable dialogue with instruction-engineering embedded
Use when building, creating, or adding functionality. Triggers: "implement X", "build Y", "add feature Z", "create X", "start a new project", "Would be great to...", "I want to...", "We need...", "Can we add......
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when reviewing large PRs to surface changes requiring human attention
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Use when instruction files (skills, prompts, CLAUDE.md) are too long or need token reduction while preserving capability. Triggers: "optimize instructions", "reduce tokens", "compress skill", "make this shorter...
Use on first session in a project, or when user asks for codebase overview. Creates persistent glossary, architecture maps, and decision records to solve agent amnesia.
Use when you have a written implementation plan to execute
Use when you have a spec or requirements for a multi-step task, before touching code
Use when merging parallel worktrees back together after parallel implementation
Use when debugging bugs, test failures, or unexpected behavior
Use when git merge or rebase fails with conflicts, you see 'unmerged paths' or conflict markers (
Use when starting any conversation
Use when: (1) constructing prompts for subagents, (2) invoking the Task tool, or (3) writing/improving skill instructions or any LLM prompts
Use when implementing any feature or bugfix, before writing implementation code
Use after modifying library skills, library commands, or agents to ensure CHANGELOG, README, and docs are updated
Use when tests are failing, test quality issues were identified, or user wants to fix/improve specific tests
Use when reviewing code changes, auditing documentation accuracy, validating technical claims before merge, or user says "verify claims", "factcheck", "audit documentation", "validate comments", "are these clai...
Use when reviewing design documents, technical specifications, or architecture docs before implementation planning
Use when reviewing implementation plans before execution, especially plans derived from design documents
Use when writing JavaScript or TypeScript code with asynchronous operations
Interactive command-line tool for Atlassian Jira. This skill should be used when users want to interact with Jira issues, epics, sprints, or when they mention Jira workflows, issue management, or need help with...
Enforces project Drizzle ORM coding conventions when creating or modifying database queries, schemas, and migrations. This skill ensures consistent patterns for query structure, type safety, permission filterin...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.