Explorar skills

Audits codebases for common bug patterns and anti-patterns including timezone issues, null safety, type coercion, async handling, and performance problems. Searches for known problematic patterns and provides actionable fixes. Use when asked to find bugs, audit for issues, check for common problems, or hunt for bugs in codebase.

Draft, refine, prune, split, or rewrite Contexts and Dictionaries for the Context-Anchored Specifications framework. Use this skill whenever the user is asked to define a Context, draft a Dictionary from a Spec File, refine or prune terms, document Relationships between Contexts, or split a Context — even if they don't explicitly mention "Context" or "Dictionary". Applies anywhere project vocabula

Performs comprehensive code reviews checking for bugs, security issues, performance problems, testing gaps, and code quality. Accepts branch names or PR URLs (GitHub/Azure DevOps) to automatically checkout and review. Use when reviewing PRs, pull requests, code changes, commits, diffs, or when asked to review code, check code, audit changes, review my changes, check PR, review branch, or perform c

Write, review, or rewrite user stories. Use this skill whenever the user (or a subagent you spawn) is asked to draft, improve, refine, split, rewrite, or review user stories, convert functional requirements into stories, or groom a backlog — even if they don't explicitly mention "user stories". Applies anywhere stories are being produced, including prompts like "turn these requirements into ticket

Write, review, or rewrite user stories following Apprendere's agile practices guide. Use this skill whenever the user (or a subagent you spawn) is asked to draft, improve, refine, split, rewrite, or review user stories, convert functional requirements into stories, groom a backlog, translate a Confluence requirements page into stories, or create/update stories in Jira — even if they don't explicit

Write, review, or rewrite Acceptance Criteria for user stories. Use this skill whenever the user (or a subagent you spawn) is asked to draft, improve, refine, rewrite, or review acceptance criteria, turn a user story into AC, translate behavior specs into Given/When/Then, critique existing Gherkin scenarios, define the "definition of done" for a story, or expand on a story's expected behavior — ev

Draft, refine, prune, split, or rewrite Contexts and Dictionaries for the Context-Anchored Specifications framework. Use this skill whenever the user (or a subagent you spawn) is asked to define a Context, draft an initial Dictionary from a Spec File, add or refine a term and its definition, prune the Dictionary at a recurring spec review, document Relationships between Contexts, or split a Contex

Use this skill whenever working on a bug fix — from triage through implementation through verification. Triggers on: "fix this bug", "there's an error", "something is broken", "debug this", "this isn't working", "root cause", "why is this failing", "production issue", "investigate this", "hotfix needed", "patch this". This skill applies systematic root cause analysis before touching code, ensures

Use this skill for any quality assurance task: writing test plans, creating test cases, filing bug reports, performing test execution, defining quality gates, or planning regression testing. Triggers on: "write test cases", "test plan", "QA", "file a bug", "bug report", "how do I test this", "regression testing", "acceptance testing", "test coverage", "quality gate", "sign off on this", "validate

Use this skill for any task related to long-term project health: technical debt management, dependency updates, refactoring, performance optimization, quarterly reviews, codebase health assessments, legacy code modernization, or sustaining engineering. Triggers on: "tech debt", "refactor", "clean up the codebase", "update dependencies", "quarterly review", "codebase health", "legacy code", "modern

Personal Claude Code skills by Santhosh Gandhi — context-manager and frugal-token-usage

Use this skill for tech lead responsibilities: breaking down epics into tasks, creating technical design documents, setting code standards, making day-to-day technical decisions, maintaining the tech debt register, and mentoring developers. Triggers on: "break this down into tasks", "technical design", "TDD", "how should we implement", "sprint breakdown", "task estimation", "code standards", "tech