全部 Agent Skills
41,263 个结果
- Dependency Auditwu529778790Use when auditing project dependencies for security vulnerabilities, outdated packages, or license compliance across npm/yarn/pnpm, pip, go, and cargo.
- Depth BreakdownwhoamimiBreaks a project idea, or an existing list of steps, into nested subtasks to a chosen depth (1-5), drawn as a Mermaid flowchart whose smallest tasks can each be built in one sitting, with open-source tools suggested for each. Use when the user wants to plan or scope a project, split a big task into steps, or turn a rough plan into buildable pieces.
- Design Pattern ApplicationdasienApply Gang of Four and architectural patterns appropriately to solve common software design problems
- Designing Beautiful WebsitestristanmanchesterDesign, implement, or critique website and web-app UX/UI: information structure, user flows, responsive layouts, visual systems, content, and interaction states. Use for a requested interface or visual-design change; do not expand a small component edit into an unrequested product redesign.
- designing-databasesvstlmkhDesign, audit and tune relational databases on PostgreSQL and MySQL/InnoDB — table and key design, index strategy, slow-query and EXPLAIN-plan diagnosis, transaction isolation and locking, and zero-downtime migrations in any framework (Alembic, Django, Laravel, Doctrine, Prisma, TypeORM, Knex, Drizzle, Flyway, Liquibase, Atlas, golang-migrate).
- Desktop ControlpatrickportoControl mouse, keyboard, and screen for desktop automation tasks
- DeslopemgiezetRefactors a file or directory to remove AI slop — duplication, dead code, speculative abstraction, bloated functions — without changing observable behaviour. Takes a path argument. Invoke with /slop-guard:deslop <path>.
- DeveloperCognitive-Interface-LabHow Claude works as the implementing developer for a separate tech lead. Execute tech-lead-planned GitHub issues in dedicated worktrees. Deliver Ready sub-issues sequentially in child worktrees, keep the parent issue branch integrated, communicate progress through tagged issue comments, and hand verified work over in In review.
- Developer Case StudysamberTurns a customer's real production deployment into a technical case study engineers believe - measured numbers tied to how they were measured, before-and-after architecture, published limitations, and cleared naming and quote approval.
- Developer ChampionssamberDesigns an unpaid, perks-only developer champions or ambassador program end to end - readiness check, intake model, published selection criteria, behaviour-based obligations, an access-first perk ladder, fixed terms with renewal and alumni status, and a cohort scorecard.
- Developer Community Healthsamberdeveloper-community-health — an installable skill for AI agents.
- Developer Community LaunchsamberDecides whether, where and when to launch a developer community, then plans its seeding and first 90 days - venue selection, founding-member seeding, go/no-go criteria, the cheaper no-community alternatives, and shutdown criteria.
- Developer Community ModerationsamberWrites a developer community's code of conduct and the moderation playbook behind it - scope, enforcement ladder, reporting channels, incident-response runbook, moderator roster, platform controls. Use whenever the user mentions a code of conduct, CODE_OF_CONDUCT.md, community moderation, moderator recruitment, an escalation ladder, banning or suspending a member, harassment, trolls, brigading…
- Developer Docs Structure AuditsamberAudits an existing developer documentation set's structure - a page-by-page inventory classified against the Diátaxis modes (tutorial, how-to, reference, explanation), mixed-mode and misplaced pages, coverage gaps per product surface, navigation drift against the file tree, a CNCF TechDocs rubric score, and a prioritized remediation queue.
- Developer Ecosystem StrategysamberDecides whether, when and how far a developer product should open into a platform other companies build on - extension points, partner-built integrations, third-party apps, a complement ecosystem - and what that permanently obliges you to.
- Developer Education StrategysamberDecides whether and how to invest in structured developer education, such as learning paths, a developer academy, hands-on labs, badges or a full certification program - instead of more ad-hoc content, then designs its operating model, staffing, refresh cadence, measurement and kill rules.
- Developer Event SponsorshipsamberBuilds a developer-event sponsorship plan - which conferences, meetups and hackathons to sponsor, at which tier, with which on-site activation, and how to prove the money worked. Use whenever a DevRel lead, developer marketer or founder mentions sponsoring a conference, booth cost, a sponsorship tier or package negotiation, splitting an event budget across events, hackathon sponsorship, or event…
- Developer First GtmsamberDesigns the go-to-market motion for a developer-facing product - bottom-up self-serve adoption, developer-influenced sales, top-down with developer proof, or ecosystem-mediated distribution - plus the self-serve entry, the developer-to-buyer handoff rule and the land-and-expand path.
- Developer Journey MapsamberMaps the developer journey for one audience segment - discovery, trial, adoption, contribution, advocacy - as a stage-by-stage table where each stage carries an exit event, a named owner, cited friction evidence and one signal, and names the single leak worth fixing next.
- Developer Keyword ResearchsamberBuilds a prioritized keyword list for technical search queries (error strings, "how to X in Y" tasks, integration intents, comparisons, migrations) mined from docs search logs, support tickets, issue trackers and first-party query data rather than keyword-tool volume.
- Developer Meetup ProgramsamberDesigns and runs a recurring developer meetup or user group - purpose and host model, format menu, cadence, a standing speaker pipeline, in-kind venue and food sponsors with their conduct limits, no-show planning, the attendee-to-co-organizer ladder, and a health scorecard.
- Developer Quickstart GuidesamberWrites or audits a developer quickstart that carries a reader from zero to one verified success - minimal path, copy-paste commands, expected output at every step, fail branches, and a cold-run time budget.
- Developer Relations KickoffsamberBefore starting any developer-relations work - and again at the start of each new session on an existing DevRel project - routes the current task to the right skill of the samber/developer-relations-skills collection, or says plainly that none fits, then bootstraps or resumes the project's shared devrel-context.md artifact.
- Developer SegmentationsamberCuts a developer audience into a few named, sized and ranked segments - the two dimensions worth cutting on, a size range with a confidence tier, the user/champion/approver/buyer split inside each, a weighted score, one primary and one secondary segment, and a written anti-segment.