Loading...
Loading...
Found 444 Skills
Update an existing work item with status changes, effort tracking, test results, and related commits. Use when progressing work, recording test results, or adjusting estimates. Supports: (1) Status transitions (not_started → in_progress → testing → completed), (2) Feature branch creation and sync, (3) Automatic PR creation on testing transition, (4) Effort tracking (estimated_hours → actual_hours), (5) Test and commit tracking, (6) Dependency updates and notes
Run a final release checklist before shipping. Verifies no TODOs, no debug code, docs updated, tests passing, dependencies justified, and security reviewed.
Use this agent when you need a final review pass to ensure code changes are as simple and minimal as possible. This agent should be invoked after implementation is complete but before finalizing changes, to identify opportunities for simplification, remove unnecessary complexity, and ensure adherence to YAGNI principles. Examples: <example>Context: The user has just implemented a new feature and wants to ensure it's as simple as possible. user: "I've finished implementing the user authentication system" assistant: "Great! Let me review the implementation for simplicity and minimalism using the code-simplicity-reviewer agent" <commentary>Since implementation is complete, use the code-simplicity-reviewer agent to identify simplification opportunities.</commentary></example> <example>Context: The user has written complex business logic and wants to simplify it. user: "I think this order processing logic might be overly complex" assistant: "I'll use the code-simplicity-reviewer agent to analyze the complexity...
World-class UI design expertise combining the precision of Jony Ive's Apple work, the systems thinking of Figma's design philosophy, and the accessibility obsession of Inclusive Design principles. UI design is the craft of making interfaces that users don't notice - because they just work. Great UI isn't about making things pretty. It's about making the right thing obvious and the wrong thing impossible. Every pixel, every animation, every spacing decision either helps the user or hurts them. The best UI designers are invisible - users accomplish their goals without ever thinking about the interface. Use when "ui design, visual design, interface design, component, design system, figma, sketch, color, typography, spacing, layout, animation, motion, responsive, mobile design, button, form design, card, modal, navigation, icon, ui, design, visual, interface, components, design-system, figma, accessibility" mentioned.
Apply cognitive bias detection whenever the user (or Claude itself) is making an evaluation, recommendation, or decision that could be silently distorted by systematic thinking errors. Triggers on phrases like "I'm pretty sure", "obviously", "everyone agrees", "we already invested so much", "this has always worked", "just one more try", "I knew it", "the data confirms what we thought", "we can't go back now", or when analysis feels suspiciously aligned with what someone wanted to hear. Also trigger proactively when evaluating high-stakes decisions, plans with significant sunk costs, or conclusions that conveniently support the evaluator's existing position. The goal is not to paralyze — it's to flag where reasoning may be compromised so it can be corrected.
Control Sonos speakers through MCP tools - search and play music, manage queue and playlists, adjust volume. Use when users request music playback, mention artists/songs/albums, want to control Sonos speakers, manage playlists, or ask about what's playing.
Turn any record into a shared workspace where agents and humans collaborate. Attach a simple workspace schema to any entity — contacts, companies, deals, projects, tickets — and let any participant contribute updates, tasks, notes, and issues. The record becomes the coordination. No orchestrator, no message bus — just read the workspace, do your work, record what you did. Intelligence accumulates. Use when multiple agents, humans, or systems need to work on the same entity together.
Autonomous SDLC router. Takes a job, classifies complexity, executes the appropriate lev-* workflow (from trivial fix to full epic), and returns "done" with runnable instructions. One shot to full auto: spec/bd/poc/impl. Subagent returns completion artifact. Triggers: "sidequest", "side quest", "just do it", "autonomous", "one shot"
Your startup isn't just your team - it's an ecosystem of people who have a stake in your success. Investors, board members, advisors, partners, vendors. Each group has different needs, different communication rhythms, and different expectations. Get it wrong, and you lose credibility. Get it right, and you have an army of advocates multiplying your reach. This skill covers investor updates, board communications, partner management, advisor engagement, and vendor relationships. It's about building trust through consistent, thoughtful communication that treats stakeholders as partners in your mission, not just audiences to manage. Use when "stakeholder, investor update, board meeting, board deck, advisor, partner, vendor, monthly update, quarterly update, keep stakeholders informed, investor relations, stakeholder, investor, board, advisor, partner, vendor, updates, communications, relationship, engagement" mentioned.
GitHub Local Knowledge Base Manager and Query Assistant. This skill must be triggered when users mention github, repo, repository, warehouse, download repo, clone, copy repository, PR, issue, pull request, or any content related to GitHub projects. This skill knows the location of local repos, can clone new repos, and uses gh CLI to search issues, PRs, and repositories to answer questions. Use proactively—even if users just ask "Which repos do I have" or casually mention a GitHub account or project name.
Produces a social media and digital marketing budget plan for a client, allocating available monthly budget across channels, content production, tools, and paid amplification. Calibrated for Uganda/East Africa SME budgets with UGX rate tables and tier templates. Invoke this skill when a client asks how to allocate a marketing budget, wants to know what they should be spending and where, or needs to justify digital marketing expenditure to a stakeholder.
Apply vertical (domain-first) codebase architecture to any project. Use this skill whenever a user asks where to put a file, how to structure a codebase, how to organize code by feature or domain, how to refactor a "horizontal" structure (components/, hooks/, utils/, types/), or asks about code colocation, monorepo boundaries, shared code, or module ownership. Also trigger when the user creates a new module and needs to decide where it belongs, or when reviewing a PR that touches file organization. Works for any language or framework (Python, TypeScript, Go, Rust, etc.) — not just React or frontend.